@brianlangseth-NOAA and I discussed this by email and he started this Google Doc a few weeks ago to gather ideas for what the checker could check: https://docs.google.com/document/d/1_bw81a0iF-BeP11kuPenqMGIZb1tYrh8JRqlvpK6rw8/edit
Feel free to add to the doc or comment here, especially as the team works through Stock Synthesis input files.
I'm imagining that the user experience would be something like
> PEPtools::check_inputs()
check_inputs() found 2 issues:
1. starter line 29: max yr for sdreport outputs is -1 but should be -2 for endyr+Nforecastyrs
2. forecast line 27: control rule method is 1 but should be 3: ramp does catch=f(SSB)
This function would focus on things that are specific to PFMC ToR, not general advise for Stock Synthesis (which could instead be added to the warning messages that SS3 returns).
@brianlangseth-NOAA and I discussed this by email and he started this Google Doc a few weeks ago to gather ideas for what the checker could check: https://docs.google.com/document/d/1_bw81a0iF-BeP11kuPenqMGIZb1tYrh8JRqlvpK6rw8/edit
Feel free to add to the doc or comment here, especially as the team works through Stock Synthesis input files.
I'm imagining that the user experience would be something like
This function would focus on things that are specific to PFMC ToR, not general advise for Stock Synthesis (which could instead be added to the warning messages that SS3 returns).