-
Notifications
You must be signed in to change notification settings - Fork 174
JP-3781: Use center=False for compute_s_region_imaging #8897
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
Conversation
Quick question - I believe cube_build already uses S_REGION to get spatial footprints for IFU data. Does this change impact that mode? |
Ok interesting. Cube_build does use the S_REGIONS. S_REGIONS is filled in in assign_wcs right ? Should it be updated there so downstream steps get the correct values ? |
This only impacts anything that uses |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8897 +/- ##
==========================================
+ Coverage 61.80% 61.85% +0.04%
==========================================
Files 377 377
Lines 38824 38873 +49
==========================================
+ Hits 23994 24043 +49
Misses 14830 14830 ☔ View full report in Codecov by Sentry. |
all regression test failures (aside from the 4 also on the main branch) pertain to S_REGION keywords, and all appear to be the magnitude we would expect. Marking this ready for review. |
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.
Thanks, @emolter!
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.
LGTM, just aminor comment about the log message.
Co-authored-by: Nadia Dencheva <nadia.astropy@gmail.com>
restarting regression tests here on Github Actions, now that the last of the differences have been ok-ified there and the okify script operates there |
I looked over the modules in assign_wcs.py util.py that deal with spectral data. The way they are designed I agree with you that I do not think this is an issue for spectral data. Not IFU nor NIRSpec slit data. |
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.
Nice catch.
Looks good
…e#8897) Co-authored-by: Nadia Dencheva <nadia.astropy@gmail.com>
Resolves JP-3781
Closes #8896
This PR addresses a bug that makes the s_region for imaging data slightly incorrect. During testing of AL-837, it was discovered that the footprint encoded in model.meta.wcsinfo.s_region is not the same as what you get from
wcs.footprint()
. By default in the pipeline, the s_region is currently calculated as the center of each corner pixel of the footprint usingstcal.alignment.util.compute_sregion_imaging(wcs, center=True)
, but it should calculate the true corners of the footprint using the same function but using the optioncenter=False
. There is even a comment in that function stating thatcenter=False
is usually what is desired.The change is a one-liner, but a fairly large number of regression test failures are expected.
Tasks
Build 11.3
(use the latest build if not sure)no-changelog-entry-needed
)changes/
:echo "changed something" > changes/<PR#>.<changetype>.rst
(see below for change types)docs/
pageokify_regtests
to update the truth filesnews fragment change types...
changes/<PR#>.general.rst
: infrastructure or miscellaneous changechanges/<PR#>.docs.rst
changes/<PR#>.stpipe.rst
changes/<PR#>.datamodels.rst
changes/<PR#>.scripts.rst
changes/<PR#>.fits_generator.rst
changes/<PR#>.set_telescope_pointing.rst
changes/<PR#>.pipeline.rst
stage 1
changes/<PR#>.group_scale.rst
changes/<PR#>.dq_init.rst
changes/<PR#>.emicorr.rst
changes/<PR#>.saturation.rst
changes/<PR#>.ipc.rst
changes/<PR#>.firstframe.rst
changes/<PR#>.lastframe.rst
changes/<PR#>.reset.rst
changes/<PR#>.superbias.rst
changes/<PR#>.refpix.rst
changes/<PR#>.linearity.rst
changes/<PR#>.rscd.rst
changes/<PR#>.persistence.rst
changes/<PR#>.dark_current.rst
changes/<PR#>.charge_migration.rst
changes/<PR#>.jump.rst
changes/<PR#>.clean_flicker_noise.rst
changes/<PR#>.ramp_fitting.rst
changes/<PR#>.gain_scale.rst
stage 2
changes/<PR#>.assign_wcs.rst
changes/<PR#>.badpix_selfcal.rst
changes/<PR#>.msaflagopen.rst
changes/<PR#>.nsclean.rst
changes/<PR#>.imprint.rst
changes/<PR#>.background.rst
changes/<PR#>.extract_2d.rst
changes/<PR#>.master_background.rst
changes/<PR#>.wavecorr.rst
changes/<PR#>.srctype.rst
changes/<PR#>.straylight.rst
changes/<PR#>.wfss_contam.rst
changes/<PR#>.flatfield.rst
changes/<PR#>.fringe.rst
changes/<PR#>.pathloss.rst
changes/<PR#>.barshadow.rst
changes/<PR#>.photom.rst
changes/<PR#>.pixel_replace.rst
changes/<PR#>.resample_spec.rst
changes/<PR#>.residual_fringe.rst
changes/<PR#>.cube_build.rst
changes/<PR#>.extract_1d.rst
changes/<PR#>.resample.rst
stage 3
changes/<PR#>.assign_mtwcs.rst
changes/<PR#>.mrs_imatch.rst
changes/<PR#>.tweakreg.rst
changes/<PR#>.skymatch.rst
changes/<PR#>.exp_to_source.rst
changes/<PR#>.outlier_detection.rst
changes/<PR#>.tso_photometry.rst
changes/<PR#>.stack_refs.rst
changes/<PR#>.align_refs.rst
changes/<PR#>.klip.rst
changes/<PR#>.spectral_leak.rst
changes/<PR#>.combine_1d.rst
changes/<PR#>.ami.rst
other
changes/<PR#>.wfs_combine.rst
changes/<PR#>.white_light.rst
changes/<PR#>.cube_skymatch.rst
changes/<PR#>.engdb_tools.rst
changes/<PR#>.guider_cds.rst