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
However, I would find it helpful to see what vec is before waiting a few hours for the profiles to run and looking at the resulting figures and tables. This could be combined with #25, such that if you could call profile_wrapper() without running the models or making the plots, you could see if the profile vectors calculated from the inputs on a multiplier or relative scale look reasonable.
Also very low priority.
The text was updated successfully, but these errors were encountered:
Another suggestion outside the scope of #24.
I think the calculation of profile vectors described in detail in
https://github.com/pfmc-assessments/nwfscDiag/blob/main/R/get_settings_profile.R#L7-L15
is really brilliant for providing a range that works for lots of models.
However, I would find it helpful to see what
vec
is before waiting a few hours for the profiles to run and looking at the resulting figures and tables. This could be combined with #25, such that if you could callprofile_wrapper()
without running the models or making the plots, you could see if the profile vectors calculated from the inputs on a multiplier or relative scale look reasonable.Also very low priority.
The text was updated successfully, but these errors were encountered: