Skip to content
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-3593: 2nd group saturation part 2 #8731

Merged
merged 13 commits into from
Sep 19, 2024

Conversation

drlaw1558
Copy link
Collaborator

@drlaw1558 drlaw1558 commented Aug 27, 2024

Ready for review: this addresses JP-3593, flagging cosmic ray saturation in group 2 data in a consistent manner between both IRS2 and non-IRS2 modes using the new use_readpatt keyword. This PR is tied to STCAL PR spacetelescope/stcal#283

Checklist for PR authors (skip items if you don't have permissions or they are not applicable)

  • added entry in CHANGES.rst within the relevant release section
  • updated or added relevant tests
  • updated relevant documentation
  • added relevant milestone
  • added relevant label(s)
  • ran regression tests, post a link to the Jenkins job below.
    How to run regression tests on a PR
  • All comments are resolved
  • Make sure the JIRA ticket is resolved properly

@drlaw1558 drlaw1558 requested a review from a team as a code owner August 27, 2024 15:03
Copy link

codecov bot commented Aug 27, 2024

Codecov Report

Attention: Patch coverage is 93.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 61.76%. Comparing base (da9691d) to head (0fd2201).

Files with missing lines Patch % Lines
jwst/saturation/saturation_step.py 50.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #8731   +/-   ##
=======================================
  Coverage   61.75%   61.76%           
=======================================
  Files         377      377           
  Lines       38750    38764   +14     
=======================================
+ Hits        23931    23943   +12     
- Misses      14819    14821    +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@drlaw1558
Copy link
Collaborator Author

@tapastro Should now be ready for review.

@nden nden requested review from schlafly and removed request for schlafly August 28, 2024 23:39
Copy link
Collaborator

@melanieclarke melanieclarke left a 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 me, given that Roman is happy with the corresponding changes in stcal, and given your testing across multiple instrument modes. Thanks for the unit tests and documentation updates!

One small documentation request below, for the new function parameters.

I will run regression tests when the system is free.

jwst/saturation/saturation.py Show resolved Hide resolved
jwst/saturation/saturation.py Show resolved Hide resolved
Copy link
Collaborator

@melanieclarke melanieclarke left a comment

Choose a reason for hiding this comment

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

Thanks for the update! One last small formatting thing - the type annotation should be the Python type (bool).

I started regression tests here:
https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/1709/

jwst/saturation/saturation.py Outdated Show resolved Hide resolved
jwst/saturation/saturation.py Outdated Show resolved Hide resolved
drlaw1558 and others added 2 commits September 12, 2024 15:55
Co-authored-by: Melanie Clarke <mclarke@stsci.edu>
Co-authored-by: Melanie Clarke <mclarke@stsci.edu>
Copy link
Collaborator

@melanieclarke melanieclarke left a comment

Choose a reason for hiding this comment

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

In the regtests, I see a difference for NIRISS rate files, which I think is because the corresponding stcal branch is out of date - the difference looks related to the chargeloss readnoise variance calculation change.

I also see one difference for a NIRSpec rate file, to the DQ plane only. It looks like some pixels that were do not use but not flagged as saturated are now also flagged as saturated. Looking at the image in a local run, it certainly looks like they were saturated, so this is a reasonable change.

I think this is good to go from my perspective, pending the merge of the corresponding stcal PR. @tapastro - can you please coordinate on the stcal side?

@nden nden added this to the Build 11.1 milestone Sep 13, 2024
@tapastro tapastro merged commit 8956a4b into spacetelescope:master Sep 19, 2024
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants