-
Notifications
You must be signed in to change notification settings - Fork 174
JP-2261: Allow user-specified custom WCS parameters in the resample step #6364
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-2261: Allow user-specified custom WCS parameters in the resample step #6364
Conversation
@jdavies-st I think |
Feel free to do it here. It's a good improvement. Attaching an unofficial attribute to a WCS object was always dicey. |
Codecov Report
@@ Coverage Diff @@
## master #6364 +/- ##
==========================================
+ Coverage 78.58% 78.59% +0.01%
==========================================
Files 408 408
Lines 35058 35567 +509
==========================================
+ Hits 27550 27954 +404
- Misses 7508 7613 +105
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report at Codecov.
|
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 to me. Before we finalize this, however, it would be useful to post info in the JP-2261 ticket as to what new parameters are being added, so that the INS folks have a chance to review and comment.
PR spacetelescope/stpipe#33 fixes the issue with list arguments. I have also discussed offline with @jdavies-st the issue of |
So it looks like all comments have been resolved, such that once spacetelescope/stpipe#33 is finalized/merged, this PR can be declared done, right? |
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 great. And nice that we're using the APE 14 features that attaches array_shape
attribute to the WCS object. I didn't know such an attribute existed before this PR.
🚀
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.
Code looks good. But given that we're changing/adding step arguments, the step docs should also be updated to include those new params (https://jwst-pipeline.readthedocs.io/en/latest/jwst/resample/arguments.html). Can be done in a separate PR, if you want, or add it here.
@mcara needs a rebase to resolve the conflict. |
@hbushouse I will add documentation here. |
d6acecb
to
a1242f4
Compare
@hbushouse All tests used to pass before I rebased. Now |
@hbushouse I just documented arguments. Please review and feel free to merge. |
…tep (spacetelescope#6364) * Allow user-specified custom WCS parameters in the resample step * remove iraf starfinder * use lists for some parameters * remove itertools import - pep8 * remove data_size and fix failing tests * Add support for user specified absolute pixel scale for output of resample * Fix bug in the test * Fix pep8 * Update arguments docs for the resample step
…tep (spacetelescope#6364) * Allow user-specified custom WCS parameters in the resample step * remove iraf starfinder * use lists for some parameters * remove itertools import - pep8 * remove data_size and fix failing tests * Add support for user specified absolute pixel scale for output of resample * Fix bug in the test * Fix pep8 * Update arguments docs for the resample step
…tep (spacetelescope#6364) * Allow user-specified custom WCS parameters in the resample step * remove iraf starfinder * use lists for some parameters * remove itertools import - pep8 * remove data_size and fix failing tests * Add support for user specified absolute pixel scale for output of resample * Fix bug in the test * Fix pep8 * Update arguments docs for the resample step
Fixes #6301
Fixes #6358
Resolves JP-2261