Conversation
|
Okay so the spinydogfish model echoinput file is stopping after: Warning file looks like the following: |
|
that stop in dogfish might only be because I had not yet removed a specific output statement while debugging. It is gone now. |
|
Yes, all seems to be working! |
iantaylor-NOAA
left a comment
There was a problem hiding this comment.
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).

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

| if (max_harvest_rate < 1.0) | ||
| { | ||
|
|
||
| warnstream << "Max harvest rate typically is >1.0 for F_method 2, 3 or 4 " << max_harvest_rate; |
There was a problem hiding this comment.
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?
|
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. |
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.