Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[simplify interface] closer integration between run_scm and run_scm_collect #408

Open
dfalster opened this issue May 22, 2024 · 0 comments
Labels
epic A new feature or capability

Comments

@dfalster
Copy link
Member

dfalster commented May 22, 2024

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

@dfalster dfalster added this to the Interface milestone May 22, 2024
@dfalster 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 dfalster added interface epic A new feature or capability and removed epic A new feature or capability labels Jun 17, 2024
@dfalster 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
@dfalster dfalster removed this from the Improve Interface milestone Jun 17, 2024
@dfalster dfalster moved this to Backlog in Plant model development Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic A new feature or capability
Projects
Status: Backlog
Development

No branches or pull requests

1 participant