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
run and model configs mix up configuration and parameters. We want to be able to pipe these parameters to the Calliope model dataset and then onto the backend. We handle that at the moment with hardcoding which are parameters in the core code, which isn't ideal. An idea on how to change these YAML structures:
All config items could become arguments in the relevant methods (init in calliope.Model)/(build in calliope.Model.build)/(solve in calliope.Model.solve).
^ config items then have to be flattened so they can be used by args.
parameters can be dimensionless or have dimensions in a dict form (for non-tech/node/tech+node dims). This is very simplified and wouldn't work well for large parameters. That's ok because we would solve it in the long (hopefully medium) term with Load non-timeseries data from file #92.
Users can then add their own top-level parameters to 'parameters' for use in their custom constraints.
Calliope version
v0.7.0-dev
The text was updated successfully, but these errors were encountered:
Problem description
run
andmodel
configs mix up configuration and parameters. We want to be able to pipe these parameters to the Calliope model dataset and then onto the backend. We handle that at the moment with hardcoding which are parameters in the core code, which isn't ideal. An idea on how to change these YAML structures:Other things:
file_allowed
is deprecated.init
incalliope.Model
)/(build
incalliope.Model.build
)/(solve
incalliope.Model.solve
).Calliope version
v0.7.0-dev
The text was updated successfully, but these errors were encountered: