JP-3597: Add new algorithm for EMI fit; clean up existing code

[melanieclarke]

Resolves JP-3597
Resolves JP-3674

Add a new algorithm for fitting and removing EMI noise in MIRI ramps.

In addition, a few minor bugs in the existing algorithm are fixed here:

• intermediate reference files generated on-the-fly were not formatted correctly and could not be saved
• retrieving subarray cases from the reference file sometimes returned incorrect matches
• the minmed function was not performing minimum calculations instead of median when nframes <= 2 as described

I have also added almost-complete unit test coverage for the new and existing algorithms, fixed code style for the new standards, updated documentation, and added a regression test for the new algorithm. Truth files for the new regression test were generated locally with this branch, so I do not expect diffs.

This PR replaces #9187, which implemented the new algorithm only. Changes introduced in that PR are all included here, with these further edits:

• style fixes for code and documentation
• edge case handling for fits to bad or trivially flat input data

Tasks

• request a review from someone specific, to avoid making the maintainers review every PR
• add a build milestone, i.e. Build 11.3 (use the latest build if not sure)
• Does this PR change user-facing code / API? (if not, label with no-changelog-entry-needed)
  • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see below for change types)
  • update or add relevant tests
  • update relevant docstrings and / or docs/ page
  • start a regression test and include a link to the running job (click here for instructions)
    • Do truth files need to be updated ("okified")?
      • after the reviewer has approved these changes, run okify_regtests to update the truth files
• if a JIRA ticket exists, make sure it is resolved properly

news fragment change types...

• changes/<PR#>.general.rst: infrastructure or miscellaneous change
• changes/<PR#>.docs.rst
• changes/<PR#>.stpipe.rst
• changes/<PR#>.datamodels.rst
• changes/<PR#>.scripts.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#>.source_catalog.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

[melanieclarke]

Initial regression tests here:
https://github.com/spacetelescope/RegressionTests/actions/runs/13505364015

Regtests show no diffs, as expected.

[melanieclarke]

@t-brandt - here is the new PR for the emicorr updates. Please review and let me know how it looks to you. I'll hold off on collecting other reviews until you're happy with it. I would especially like your eyes on the documentation - please let me know if I have something wrong or if there's more you think should be added.

[codecov]

Codecov Report

Attention: Patch coverage is 98.23009% with 6 lines in your changes missing coverage. Please review.

Project coverage is 73.97%. Comparing base (e2f4801) to head (2213781).
Report is 94 commits behind head on main.

Files with missing lines	Patch %	Lines
jwst/emicorr/emicorr.py	98.07%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9216      +/-   ##
==========================================
+ Coverage   73.67%   73.97%   +0.29%     
==========================================
  Files         369      369              
  Lines       36407    36554     +147     
==========================================
+ Hits        26824    27041     +217     
+ Misses       9583     9513      -70     

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

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[drlaw1558]

Thanks @melanieclarke ! A few quick comments:

• First, for anyone else testing this algorithm='joint' is the new method.
• I've confirmed that this version works as expected on my test cases from the previous PR, and now cleanly bails out when ngroups=2.
• It would be helpful if the log printed out which method was being used. It's in the params at the top of the log, but I'm thinking of a log.info statement when it enters either the joint or sequential subroutines.

[melanieclarke]

• It would be helpful if the log printed out which method was being used. It's in the params at the top of the log, but I'm thinking of a log.info statement when it enters either the joint or sequential subroutines.

Done! The documentation comment is now cleaned up as well.

[t-brandt]

This looks great, @melanieclarke, thank you! I added some very minor comments. The only one that may require a little thought and attention is the criterion used to determine which pixels are appropriate to fit the EMI amplitude and phase.

[penaguerrero]

Thanks for this work, Melanie! Looks great! just a couple of very minor things.

[penaguerrero]

LGTM!

[t-brandt]

Just for the record, I approve. Please go ahead and merge when ready!