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
Currently we have run_scm, run_scm_collect, run_scm_error and build_schedule.
There's considerable duplication and it's frankly confusing. Suggest combining, make collect, refine_schedule arguments in run_plant instead of different functions?
Additionally, As per #206, suggest renaming to run_patch, run_plant? Actually, how about solve_system. The stochastic version could then be stimulate_system
The text was updated successfully, but these errors were encountered:
dfalster
changed the title
closer integration between run_scm and run_scm_collect
[pitch] closer integration between run_scm and run_scm_collect
Jun 17, 2024
dfalster
changed the title
[pitch] closer integration between run_scm and run_scm_collect
[simplify interface] closer integration between run_scm and run_scm_collect
Jun 17, 2024
Currently we have
run_scm
,run_scm_collect
,run_scm_error
andbuild_schedule
.There's considerable duplication and it's frankly confusing. Suggest combining, make
collect
,refine_schedule
arguments inrun_plant
instead of different functions?Additionally, As per #206, suggest renaming to
run_patch
,run_plant
? Actually, how aboutsolve_system
. The stochastic version could then bestimulate_system
The text was updated successfully, but these errors were encountered: