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
The implementation would require first checking "model_data" to see if the component is a parameter. If it isn't, then check the backend dataset variables/expressions to see if it is one of those. We shouldn't have to worry about name overlaps since a user cannot define the same name for any optimisation problem component (i.e., a parameter and decision variable cannot have the same name).
Calliope version
v0.7.0-dev
The text was updated successfully, but these errors were encountered:
brynpickering
changed the title
Allow variables and global eexpressions to be included in a YAML constraint "where" string
Allow variables and global expressions to be included in a YAML constraint "where" string
Apr 19, 2023
Problem description
Since variables and global expressions must be defined before constraints are added, they could also be used to "where" a constraint array, e.g.:
The implementation would require first checking "model_data" to see if the component is a parameter. If it isn't, then check the backend dataset variables/expressions to see if it is one of those. We shouldn't have to worry about name overlaps since a user cannot define the same name for any optimisation problem component (i.e., a parameter and decision variable cannot have the same name).
Calliope version
v0.7.0-dev
The text was updated successfully, but these errors were encountered: