Conversation
3ddd69a
to
5e5bdd4
Compare
Codecov Report
@@ Coverage Diff @@
## main #1235 +/- ##
==========================================
+ Coverage 90.82% 91.23% +0.40%
==========================================
Files 78 78
Lines 4121 4106 -15
Branches 363 360 -3
==========================================
+ Hits 3743 3746 +3
+ Misses 288 270 -18
Partials 90 90
Continue to review full report at Codecov.
|
Points and questions regarding coverage:
Since testing for the case when no epoch argument is passed might be more important than handling warnings, it might make sense to just suppress the warning if no better solution can be reached.
Question Thanks! |
@astrojuanlu Could you please guide me on the above and let me know your thoughts? Thanks! |
Hello @Yash-10! I'm about to review this PR. Would you please rebase on top of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a thorough review, thanks for your patience!
Regenerate baseline images
21a7c80
to
fc729ba
Compare
ac54550
to
870042a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to go! My only remaining question is: did we have to regenerate the images? The changes look like a 1 pixel displacement, and a diff on the tens or hundreds of bytes. Were image tests failing locally because of it? If not, I think we should remove the changes and squash the commit, to avoid increasing the size of the repository.
Merging & squashing after the tests pass 👍🏽 |
(Not sure the automerge will work because of the coverage check, but let's see) |
Continuing work from #1137. Thanks @ishanSrt !
Some analysis
test_propagate_long_times_keeps_geometry
) due to the dates being far into the future seem to be legitimate, since that test propagates an orbit for 100 years and hence the resultant orbit is mostly going to be out of the non-dubious range defined byerfa
.erfa
warnings, eg:Any date after about the year 1935 yields that warning. Here, it might be a good choice to just choose a "safe" date value to prevent these warnings pop up.
Thanks, and would love to get any suggestions!
The coverage decrease needs to be addressed and I am working on that...