Skip to content

[Bug]: Size Frequency section in data_boot_001.ss and data_expval.ss identical to input file #541

@e-perl-NOAA

Description

@e-perl-NOAA

Describe the bug

While testing PR #540 to fix the size frequency method in CompReport.sso, @iantaylor-NOAA saw that the size frequency section in data_boot_001.ss and data_expval.ss are identical to the input file (but were different in 3.30.19).

It looks like this commit 61d2cba, which included a variety of other changes, may have inadvertently led to the observed output getting written to all three data file types.

In particular this change looks incorrect: 61d2cba#diff-17a83800a032b2061d3ddd5c6da9d766d9796ecb81f2ebf1599b9808c206247eL775-R782
but the change includes moving from looping over size frequency observations to size frequency methods, so I'm assuming the fix is not as simple as swapping SzFreq_obs and SzFreq_exp.

Lesson from all this: more tests related to generalized size frequency and/or bootstrap data would be helpful.
The one test model with generalized size frequency data has the same scale and units for both size frequency methods: https://github.com/nmfs-ost/ss3-test-models/blob/main/models/two_morph_seas_areas/data.ss#L455. And I don't think we have any tests for expected values or bootstrap data.

To Reproduce

See PR #540.

Expected behavior

Size frequency section in data_boot_001.ss and data_expval.ss should be different from the input file.

Screenshots

No response

Which OS are you seeing the problem on?

No response

Which version of SS3 are you seeing the problem on?

Versions after v.3.30.19

Additional Context

No response

Metadata

Metadata

Labels

bugSomething isn't working; don't remove label after fixingchange loguse for issues that should appear in change logmisc. output

Type

No type

Projects

Status

Done

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions