Prevent VAR_RNOISE from being a zeroed array.

[mairanteodoro]

This PR updates a few unit tests to prevent VAR_RNOISE from being a zeroed array (such edge case might need to be addressed eventually).

For the following two unit tests, we increased the value of im.var_rnoise from zero to 0.01:

• test_custom_wcs_resample_imaging;
• test_custom_refwcs_resample_imaging;

Additionally, the error in test_custom_refwcs_pixel_shape_imaging was caused by an incorrect pixel_shape specification in the WCS. The test was setting result.meta.wcs.pixel_shape = data1.shape where data1.shape is in NumPy's (ny, nx) format (height, width), but WCS pixel_shape expects (nx, ny) format (width, height). The test now correctly verifies that:

• the WCS can use an explicit pixel_shape setting;
• the output shape matches the expected dimensions;
• the pixel area can be set correctly in the result metadata.

This PR also contains a temporary change to pyproject.toml so that it can run against the stcal changes listed in PR #359.

Note

This PR depends on changes in the following PR:

• stcal (RCAL-968: add inverse of sky variance as an option for creating weight map in resample. stcal#359).

Regression tests

All the regression tests are passing:

• https://github.com/spacetelescope/RegressionTests/actions/runs/17563400895

Tasks

• If you have a specific reviewer in mind, tag them.
• add a build milestone, i.e. Build 12.0 (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 changelog readme for instructions)
  • 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.38%. Comparing base (0986d7b) to head (9f376e1).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9813   +/-   ##
=======================================
  Coverage   83.38%   83.38%           
=======================================
  Files         366      366           
  Lines       37771    37771           
=======================================
  Hits        31494    31494           
  Misses       6277     6277           

☔ 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.

[pllim]

pre-commit.ci autofix

[pllim]

I took the liberty of asking the bot to fix pre-commit check failures. Hope you don't mind. Looking at what angered the bot, you might have to configure your editor to automatically delete trailing whitespace on save. FYI.

[mairanteodoro]

I took the liberty of asking the bot to fix pre-commit check failures. Hope you don't mind. Looking at what angered the bot, you might have to configure your editor to automatically delete trailing whitespace on save. FYI.

Thanks, @pllim! I will set my editor to take care of that, but I thought these simple style-check fixes were being taken care of during the pre-commit phase... apparently I'm wrong.