You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem your feature request is related to.
Model features are too complicated to use a sweet of settings for a massive amount of species. So, instead I have found that a csv file that stores the configurations for each species is a better way forward. Thus, run() which takes a data frame of combinations of survey and species and "splits" them before calling run_sdmtmb() is no longer needed because the latter function is sufficient.
Describe the solution you'd like
Soft deprecate the function at first and then hard deprecate with suggested purrr::map() after dplyr::split() to show users how to use run_sdmtmb().
Describe alternatives you have considered
Keep the function ☹️
Additional context
No response
The text was updated successfully, but these errors were encountered:
Started the process in 6c16f68 but @chantelwetzel-noaa can you confirm that you are no longer using the run() function and instead are using run_sdmtmb() in your current scripts?
Describe the problem your feature request is related to.
Model features are too complicated to use a sweet of settings for a massive amount of species. So, instead I have found that a csv file that stores the configurations for each species is a better way forward. Thus,
run()
which takes a data frame of combinations of survey and species and "splits" them before callingrun_sdmtmb()
is no longer needed because the latter function is sufficient.Describe the solution you'd like
Soft deprecate the function at first and then hard deprecate with suggested
purrr::map()
afterdplyr::split()
to show users how to userun_sdmtmb()
.Describe alternatives you have considered
Keep the function☹️
Additional context
No response
The text was updated successfully, but these errors were encountered: