Skip to content

Conversation

pllim
Copy link
Collaborator

@pllim pllim commented Aug 27, 2025

This PR addresses a little bit of #9383 , as seen in #9666 .

This round touches a lot of subpackages because I tried to do global search and replace for common offenders. Hopefully the diff is self-explanatory.

No need to run RT.

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

by addressing some low-hanging fruits
@pllim pllim mentioned this pull request Aug 27, 2025
11 tasks
Copy link

codecov bot commented Aug 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.49%. Comparing base (3bf3887) to head (6171930).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #9777   +/-   ##
=======================================
  Coverage   82.49%   82.49%           
=======================================
  Files         366      366           
  Lines       37134    37134           
=======================================
  Hits        30633    30633           
  Misses       6501     6501           

☔ 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 pllim marked this pull request as ready for review August 27, 2025 17:26
@pllim pllim requested review from a team as code owners August 27, 2025 17:26
@pllim pllim requested a review from melanieclarke August 27, 2025 17:26
Comment on lines +27 to +43
* ``--oversample``: The oversampling factor to be used in the model fit (default=3).
* ``--rotation``: Initial guess for the rotation of the PSF in the input image, in
units of degrees (default=0.0).
* ``--psf_offset``: List of PSF offset values to use when creating the model array
(default='0.0 0.0').
* ``--rotation_search``: List of start, stop, and step values that define the list of
rotation search values. The default setting of '-3 3 1'
results in search values of [-3, -2, -1, 0, 1, 2, 3].
* ``--bandpass``: ASDF file containing suitable array to override filter/source
(default=None)
* ``--usebp``: If True, exclude pixels marked DO_NOT_USE from fringe fitting
(default=True)
* ``--firstfew``: If not None, process only the first few integrations (default=None)
* ``--chooseholes``: If not None, fit only certain fringes e.g. ['B4','B5','B6','C2']
(default=None)
* ``--affine2d``: ASDF file containing user-defined affine parameters (default='commissioning')
* ``--run_bpfix``: Run Fourier bad pixel fix on cropped data (default=True)
Copy link
Collaborator

@zacharyburnett zacharyburnett Aug 27, 2025

Choose a reason for hiding this comment

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

I like that you put the arguments in inline code formatting, but I also did like the previous columns alignment compared to the new one:
Image

I don't know how these blocks were made, though; perhaps if you prepended :- to each line it would align the columns again?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Single dash is actually wrong if we are talking about CLI options. I have no idea why colon was even used as a list. It is not a valid Sphinx thingy.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The red and green background must be because you are not looking at the proper HTML output. They not supposed to be there.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

What exactly you not like about the diff? Please see the rendered RTD page. Thanks.

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.

2 participants