Testing SSMSE with recent versions of SS3
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 21
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
I'm tring to set up SSMSE for a SS3 model developed with more recent versions of SS3 (>V3.30.22), but SSMSE does not seem to be compatible with these recent versions. When I apply the develop_OMs function, it throws the following error:
Error in run_ss_model(dir = tmp_mod_path, admb_options = "-maxfn 0 -phase 50 -nohess", :
New data file (data.ss_new if using SS3 v3.30.18 or data_echo.ss_new if using SS3 v3.30.21) was not created during the model run, which suggests SS3 did not run correctly.
After swapping SS3 excutables in the package, SS3 seems to read the input files correctly, but it still throws an error because the .par file name in the develop_OMs function seems to be hard-coded.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with develop_OMs and its run_ss_model call, then compare how recent SS3 versions create data.ss_new or data_echo.ss_new and how the .par filename is selected. Reproduce the reported run with a recent SS3 executable; done when develop_OMs completes without the missing-output or hard-coded .par error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100