-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate ALK tolerance #342
Comments
let's retain the FUNCTION that does it, but remove it from conditional statements that invoke it and mark it as deprecated in the starter.ss file |
This section of code in SS_ALK.tpl is the only place calc_ALK_range is used: It can be replaced by just using the "else" clause (the last line). ALK_tolerance is then ignored. We could add a Note when ALK_tolerance is read that says something like "ALK_tolerance is not currently being used, but must remain in the starter.ss file". Or we could use the word "deprecated". |
Wow, this really messed up the code, didn't it? Here it is without formatting: |
I find a few more instances of ALK_range. See attached file |
Thanks. I have been commenting out ALK_range stuff. |
OK to force internally to 1, nlength |
Ok. Creating pull request. |
Discussion on nmfs-fish-tools/SSMSE#129 suggests that the ALK tolerance setting in the starter file should be deprecated. Perhaps we could add a warning first to suggest users set it to 0, then in a future release require users to reset it to 0?
@Rick-Methot-NOAA , feel free to comment on this issue if I didn't capture it how you were imagining
The text was updated successfully, but these errors were encountered: