Skip to content

Comments

Unify F approach#580

Merged
Rick-Methot-NOAA merged 12 commits intomainfrom
unify_F_approach
Mar 18, 2024
Merged

Unify F approach#580
Rick-Methot-NOAA merged 12 commits intomainfrom
unify_F_approach

Conversation

@Rick-Methot-NOAA
Copy link
Collaborator

@Rick-Methot-NOAA Rick-Methot-NOAA commented Mar 13, 2024

continues development for issue #570 and especially #581
See description and example in #581
Substantial refactoring of the internal machinery for managing F as parameter vs F as hybrid
extends the F-detail approach previously available only for F_method 2 to F_method 4

only new input is for F_method 4 if using the F_detail feature.

@e-perl-NOAA
Copy link
Collaborator

Okay so the spinydogfish model echoinput file is stopping after:

GP Seas Area Use? female_recr_dist
1 1 1 1 0.5
 made the age_age' key 
Finished evaluating biology calculations once


Begin estimating

Warning file looks like the following:

Note 1 Information: Max data length bin: 132  < max pop len bins: 136; so will accumulate larger pop len bins
3 iter 1
 hrate for 1970: 

@Rick-Methot-NOAA
Copy link
Collaborator Author

that stop in dogfish might only be because I had not yet removed a specific output statement while debugging. It is gone now.

@e-perl-NOAA
Copy link
Collaborator

Yes, all seems to be working!

@Rick-Methot-NOAA Rick-Methot-NOAA linked an issue Mar 13, 2024 that may be closed by this pull request
2 tasks
@Rick-Methot-NOAA Rick-Methot-NOAA marked this pull request as ready for review March 13, 2024 23:35
Copy link
Contributor

@iantaylor-NOAA iantaylor-NOAA left a comment

Choose a reason for hiding this comment

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

Looks good. I didn't try to follow all the details, but I don't see any red flags. The tests are all passing, including the vermillion_snapper_F4 model which uses F Method 4.

I compared Report files and see the DISCARD_AT_AGE is now available in the forecast as intended (discussed in #569).
image

I see control.ss_new remains the same except for improved comments
image

if (max_harvest_rate < 1.0)
{

warnstream << "Max harvest rate typically is >1.0 for F_method 2, 3 or 4 " << max_harvest_rate;
Copy link
Contributor

Choose a reason for hiding this comment

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

For a long-lived stock, would setting a smaller max harvest rate ever be a useful tool for constraining the model to a reasonable parameter space, or is the ballpark F a better approach and max F should never be constraining?

@Rick-Methot-NOAA
Copy link
Collaborator Author

Thanks Ian. Nothing magic about the 2.9 value. The role of max F is mostly to keep model from exploring F levels that nearly extirpate older fish. In the attached example, it is constraining during early hybrid phases to keep F below 2.9, which creates a catch penalty, which moves model back to higher biomass and lower F values. For long-lived stocks a maxF of 0.4 might seem reasonable, but even 0.40 will not extirpate.

@Rick-Methot-NOAA Rick-Methot-NOAA merged commit fb2a396 into main Mar 18, 2024
@Rick-Methot-NOAA Rick-Methot-NOAA deleted the unify_F_approach branch March 18, 2024 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

refactor Fmethod controls and expand Fmethod 4 capabilities

3 participants