8000 JP-2704 MIRI MRS Failures in Cube when there is no valid data on rate/cal image by jemorrison · Pull Request #6998 · spacetelescope/jwst · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

JP-2704 MIRI MRS Failures in Cube when there is no valid data on rate/cal image #6998

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

Merged
merged 3 commits into from
Aug 22, 2022

Conversation

jemorrison
Copy link
Collaborator
@jemorrison jemorrison commented Aug 19, 2022

Resolves JP-2704

This PR addresses when no valid data is found on the detector because all the pixels are marked as DO_NOT_USE.
An additional bug fix was made for correctly updating the naxis3 value of the final cube when wavelength planes are removed from the IFUCube because they contain no valid data.

Checklist for maintainers

8000

@jemorrison jemorrison added this to the Build 9.0 milestone Aug 19, 2022
@codecov
Copy link
codecov bot commented Aug 19, 2022

Codecov Report

Merging #6998 (26f963e) into master (04ec022) will increase coverage by 0.00%.
The diff coverage is 84.37%.

@@           Coverage Diff           @@
##           master    #6998   +/-   ##
=======================================
  Coverage   79.57%   79.57%           
=======================================
  Files         411      411           
  Lines       37197    37217   +20     
=======================================
+ Hits        29600    29616   +16     
- Misses       7597     7601    +4     
Flag Coverage Δ
nightly 79.54% <84.37%> (+<0.01%) ⬆️
unit 53.22% <0.00%> (-0.03%) ⬇️
Impacted Files Coverage Δ
jwst/cube_build/ifu_cube.py 91.44% <84.37%> (-0.18%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Copy link
Collaborator
@drlaw1558 drlaw1558 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok to me; tested that it fixes the crash that we were seeing in https://jira.stsci.edu/browse/JP-2704

Copy link
Collaborator
@hbushouse hbushouse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So what happens when there's no good data and this function returns a list of None values? I assume the higher-level calling routines are already setup to handle that and skip the creation of an s3d file? And the pipeline flow also properly recognizes that no s3d was created and hence the extract_1d step also gets skipped?

@jemorrison
Copy link
Collaborator Author

I checked and if running in calspec2 and all the wavelength planes in a cube have zero data, then a log.error message is given. No IFU cube is created and the extract1d step is skipped.

Copy link
Collaborator
@hbushouse hbushouse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@hbushouse hbushouse merged commit dc52c6e into spacetelescope:master Aug 22, 2022
@hbushouse hbushouse added the 8.1 patch PR candidate for an 8.1 patch release label Aug 30, 2022
zacharyburnett pushed a commit to zacharyburnett/jwst that referenced this pull request Aug 31, 2022
…/cal image (spacetelescope#6998)

* check if no data is mapped

* updates to ifu_cube when DO_NOT_USE is set for most of data

* update change log

(cherry picked from commit dc52c6e)
@hbushouse hbushouse modified the milestones: Build 9.0, Build 8.1.2 Sep 7, 2022
@jemorrison jemorrison deleted the JP-2704 branch January 10, 2023 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.1 patch PR candidate for an 8.1 patch release cube_build
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0