JP-3632: Change the Spec of Ramp Fitting to Select Algorithm

[kmacdonald-stsci]

Resolves JP-3632

Closes #8501

This PR addresses the ability to select the C extension implementation of ramp fitting or the python implementation.

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

[hbushouse]

Does this require any changes in lower-level functions in order to pass this new param value? Or is it already there, hardwired to the 'OLS' value?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.97%. Comparing base (781e0e0) to head (f24f296).
Report is 10 commits behind head on master.

❗ Current head f24f296 differs from pull request most recent head 14b4a19

Please upload reports for the commit 14b4a19 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8503      +/-   ##
==========================================
+ Coverage   57.93%   57.97%   +0.04%     
==========================================
  Files         387      387              
  Lines       38839    38830       -9     
==========================================
+ Hits        22502    22513      +11     
+ Misses      16337    16317      -20     

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

[kmacdonald-stsci]

Does this require any changes in lower-level functions in order to pass this new param value? Or is it already there, hardwired to the 'OLS' value?

I'm not quite sure what you're asking here, but in STCAL the algorithm selection is here:

https://github.com/spacetelescope/stcal/blob/6739c1c6b0559943bd4ac29e90e009541e217f00/src/stcal/ramp_fitting/ramp_fit.py#L175

[hbushouse]

Does this require any changes in lower-level functions in order to pass this new param value? Or is it already there, hardwired to the 'OLS' value?

I'm not quite sure what you're asking here, but in STCAL the algorithm selection is here:

https://github.com/spacetelescope/stcal/blob/6739c1c6b0559943bd4ac29e90e009541e217f00/src/stcal/ramp_fitting/ramp_fit.py#L175

OK, I see that algorithm is already being passed as an argument to the ramp_fit function here:
https://github.com/spacetelescope/stcal/blob/6739c1c6b0559943bd4ac29e90e009541e217f00/src/stcal/ramp_fitting/ramp_fit.py#L96

so it's all good.

[hbushouse]

Looks good to me. And I don't see the need for a regtest run, since this shouldn't have any change on anything.