This issue was introduced by a change in 3.30.25. Now corrected in 3.30.25.1
Describe the bug
I noticed that Option 6 for M was not working as expected in the latest version of SS. @nathanvaughan-NOAA found the source of the error and submitted a pull request #773 to fix it.
To Reproduce
I ran two SS models, one with option 6 and one with option 2 using age ranges and reference age that should normally result in the same vector but it produced two very different vectors. Option 2 is the correct vector, I verified by doing the scaling outside of SS.
Expected behavior
I expected that running two SS models, one with option 6 and one with option 2, should result in the same M vector when using a reference age equivalent to the age range.
Screenshots
These are the M vectors resulting from option 2 vs option 6 using the same model setup.
Which OS are you seeing the problem on?
Windows
Which version of SS3 are you seeing the problem on?
3.30.25
Additional Context
No response
This issue was introduced by a change in 3.30.25. Now corrected in 3.30.25.1
Describe the bug
I noticed that Option 6 for M was not working as expected in the latest version of SS. @nathanvaughan-NOAA found the source of the error and submitted a pull request #773 to fix it.
To Reproduce
I ran two SS models, one with option 6 and one with option 2 using age ranges and reference age that should normally result in the same vector but it produced two very different vectors. Option 2 is the correct vector, I verified by doing the scaling outside of SS.
Expected behavior
I expected that running two SS models, one with option 6 and one with option 2, should result in the same M vector when using a reference age equivalent to the age range.
Screenshots
These are the M vectors resulting from option 2 vs option 6 using the same model setup.
Which OS are you seeing the problem on?
Windows
Which version of SS3 are you seeing the problem on?
3.30.25
Additional Context
No response