Working through the Debugging.R script shared by @JuanMatiasBraccini at https://drive.google.com/drive/folders/1oUEPHeFbU9gf33REEZuIvR5Mq_DAS2_E (private, but shared with @nathanvaughan-NOAA and me), I modified the base.dir to work for my computer and ran with DO='cod' and DO='gummy' and replicated the finding that the cod model worked and the gummy shark model didn't. The failure seems to be caused by the files in \Outputs\gummy_S1\1\gummy_OM_OM\ not working currently with SS3 due to a mismatch between forecast recdevs in modified par file vs the forecast file.
The ss3.par file has
# Fcast_recruitments:
0.00000000000 0.00000000000 0.00000000000 0.00000000000 0.00000000000
whereas the model has 2023 as both the ending year of the model and the last year of the main devs and forecast file has 1 #_Nforecastyrs, so there should only be one forecast recruitment parameter in the par file for it to run successfully. Trying to figure out when and where the wrong number is being set is too confusing for me, given my limited understanding of the package.
@JuanMatiasBraccini, sorry, I was clearly too optimistic about what it would take to update this package to work with recent versions of SS3.
@nathanvaughan-NOAA, if you have time to look at this at any point, or have debugging tips, please let me know how I can help.
Working through the Debugging.R script shared by @JuanMatiasBraccini at https://drive.google.com/drive/folders/1oUEPHeFbU9gf33REEZuIvR5Mq_DAS2_E (private, but shared with @nathanvaughan-NOAA and me), I modified the
base.dirto work for my computer and ran withDO='cod'andDO='gummy'and replicated the finding that the cod model worked and the gummy shark model didn't. The failure seems to be caused by the files in\Outputs\gummy_S1\1\gummy_OM_OM\not working currently with SS3 due to a mismatch between forecast recdevs in modified par file vs the forecast file.The ss3.par file has
whereas the model has 2023 as both the ending year of the model and the last year of the main devs and forecast file has
1 #_Nforecastyrs, so there should only be one forecast recruitment parameter in the par file for it to run successfully. Trying to figure out when and where the wrong number is being set is too confusing for me, given my limited understanding of the package.@JuanMatiasBraccini, sorry, I was clearly too optimistic about what it would take to update this package to work with recent versions of SS3.
@nathanvaughan-NOAA, if you have time to look at this at any point, or have debugging tips, please let me know how I can help.