Rectify time span in max elevation tests #98
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Realized after commenting on #97 (comment) that there was something extremely fishy with the time span of the max elevation tests. Turned out that I by mistake had tested passes at 1, 3, 6, 10, 15, ..., 210 days from the TLE epoch, instead of 1, 2, ..., 20 days from the epoch. Prediction time for MOLNIYA and SIRIUS-1 increases linearly with the time from TLE epoch (see issue comment), so this led to larger test times.
Old running times for the tests:
New running times for the tests after correction:
Due to the other factors mentioned in #97 (comment), they still take 2.45 seconds at worst, but it is better than 14 seconds. :-)