-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JP-3625: Switch to IRAF starfinder default #8487
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8487 +/- ##
==========================================
+ Coverage 57.93% 58.00% +0.06%
==========================================
Files 387 387
Lines 38839 38811 -28
==========================================
+ Hits 22502 22512 +10
+ Misses 16337 16299 -38 ☔ View full report in Codecov by Sentry. |
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.
Looks good David, thanks! Would you please also change the default of the make_tweakreg_catalog function here, for clarity?
It would also be good to run a regression test, as it's certainly possible this change would have a small effect on the solution coming from tweakreg.
Done! Not sure how to set off regression tests though. |
Started regtest run at https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/1458 |
Regtest run shows small, expected differences in level-3 imaging products, due to slight differences in tweakreg results. So I think this looks OK. |
Resolves JP-3625 by switching the code default starfinder for use in tweakreg to IRAF starfinder instead of DAO starfinder.
Checklist for PR authors (skip items if you don't have permissions or they are not applicable)
CHANGES.rst
within the relevant release sectionHow to run regression tests on a PR