Make use of r4ss::run() and other functions for moving files and running models?
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 21
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
The r4ss issue https://github.com/r4ss/r4ss/issues/460 "create a single function for running SS models for use in r4ss, SSMSE, and ss3sim" has been resolved thanks to PR https://github.com/r4ss/r4ss/pull/722 so the modified functions are available for use in SSMSE. I'm not sure it's worth making changes here if the status-quo functions are working, but future developments could consider moving to the new r4ss functions.
Note this is a repeat of https://github.com/ss3sim/ss3sim/issues/385.
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 by reviewing the current SSMSE functions for moving files and running Stock Synthesis models, then read r4ss issue #460 and PR #722 alongside r4ss::run(). Done would require an agreed scope and, if migration is chosen, SSMSE using the relevant r4ss functions for file movement and model execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100