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
I just noticed that if you specify output in your scenario_config file which is mapped to cfg$output for standalone runs in configureCfg, that does not work in a coupled run. Also means it does not work in the short cascade of the model tests. There is simply no code in start_bundle_coupled.R that does it.
Which makes me think whether we should adjust start_bundle_coupled.R such that it also calls configureCfg to avoid repeating code (of course, that might need some adjustments here and there).
Actually unrelated, but I would like to have this feature: Specify cfg$output,fixOnRef in the output column, and then the scripts adds fixOnRef to the output scripts defined in default.cfg. Should not be that difficult.
The text was updated successfully, but these errors were encountered:
I will close this issue with PR #1575 but find your ideas useful regarding configureCfg and cfg$output,fixOnRef and move them to new issues in development_issues.
I just noticed that if you specify
output
in yourscenario_config
file which is mapped tocfg$output
for standalone runs in configureCfg, that does not work in a coupled run. Also means it does not work in the short cascade of the model tests. There is simply no code instart_bundle_coupled.R
that does it.Which makes me think whether we should adjust
start_bundle_coupled.R
such that it also callsconfigureCfg
to avoid repeating code (of course, that might need some adjustments here and there).Actually unrelated, but I would like to have this feature: Specify
cfg$output,fixOnRef
in theoutput
column, and then the scripts addsfixOnRef
to the output scripts defined indefault.cfg
. Should not be that difficult.The text was updated successfully, but these errors were encountered: