SSMSE icon indicating copy to clipboard operation
SSMSE copied to clipboard

Management Strategy Evaluation (MSE) using Stock Synthesis (SS3)

Results 30 SSMSE issues
Sort by recently updated
recently updated
newest added

Column header updates in r4ss in PR [#945](https://github.com/r4ss/r4ss/pull/945) will require updates in SSMSE functions such as those with [FltSvy](https://github.com/search?q=repo%3Anmfs-fish-tools%2FSSMSE+FltSvy&type=code). Additional changes in r4ss headers can be found in the [PR...

@e-perl-NOAA is working on making SSMSE compatible with SS3.30.21. This is because a user needs a feature that is only available in 3.30.21 and newer. SSMSE will continue to work...

enhancement
status: in progress

I am running an MSE using sablefish stock assessment files, which have catch inputs specified at the bottom of the forecast file that cap catch at the ACLs set by...

Thanks to @mkapur-noaa for reporting the following issue: As an aside, our implementation of the helper function didn't get us there at first because we actually had two separate chunks...

bug

Use the user manual classifications: https://nmfs-fish-tools.github.io/SSMSE/manual/intro.html#funs Some exported functions are not useful to users (they are exported so examples can run, I believe). How to curate pkgdown reference: https://pkgdown.r-lib.org/articles/pkgdown.html#reference

documentation

Pass back the future_om_dat object as a return from run_SSMSE so the user can double-check their inputs are being processed as expected. From #188

enhancement

Upon reading the [user manual custom example](https://nmfs-fish-tools.github.io/SSMSE/manual/SSMSE.html#example-using-custom-pattern-instead-of-model_change), it's not spelled out that the user should put in the actual parameter values desired From #188

documentation

SS3 v3.30.19.01 renames new data file as data_echo.ss_new (instead of previously named data.ss_new). This triggers an error in the function SSMSE:::copy_model_files(). See lines of code below. ``` if (!all(c("control.ss_new", "data.ss_new",...

as suggested in JOSS review - maybe add to the simple example?

documentation

A simple wrapper function to generate the file structure needed for the analysis (model_runs, figures, input_models) would be helpful. (Quang suggestion from JOSS review)

enhancement