Howard Bushouse

Latest regtest run https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/1350/ using the latest CRDS-TEST context shows failures that are only due to different ref file version numbers between CRDS-OPS and CRDS-TEST. No differences in actual data...

I think it's good to go.

The CI failures are almost certainly due to the use of stcal 1.6.1, which was missing some recent api changes to the jump step. Running against stcal 1.7.0 should fix...

@emolter What's the status of all the suggestions from @jdavies-st ? Do you think they're reasonable?

Latest full regtest run has failures that are all unrelated to this PR (they're due to a separate update to datamodels). So this looks good. I'm approving and merging. Nice...

Started another regtest run at https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/1394 Results are clean. Looks good.

@jemorrison We should probably update the extract_1d step docs to mention the fact that we're now storing the aperture limits in these new keywords. And check to see if the...

All of our other existing keywords that record either subarray or 2-D cutout start/stop limits use values that are 1-indexed (in keeping with FITS conventions). Are these values 1-indexed or...

Latest regression test results look good, except for 1 hard error: https://plwishmaster.stsci.edu:8081/job/RT/job/JWST-Developers-Pull-Requests/1266/testReport/jwst.regtest/test_miri_lrs_slit_spec2/_stable_deps__test_miri_lrs_extract1d_image_ref/ Looks like an instance where `xstart` isn't populated at all (it's None) and hence it can't do math...

@jemorrison Has there been another regtest run that fixes the hard error encountered in 1266?