-
Notifications
You must be signed in to change notification settings - Fork 26
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
Express "not equal" constraints #1798
Comments
So the list can be empty? That's odd. |
Yes. The water table may not exist (i.e. the slope is dry). |
So I can't help but wonder if this is kind of an artificial constraint, in that this constraint is an artifact of the current encoding of the problem, and that a different encoding would not need this. [Just trying to prioritize things.] |
Like #1800. But this one might require a design first, before going ahead with an implementation. |
Currently in Drasil, constraints can either be expressed as a
Range
,EnumeratedReal
, orEnumeratedStr
.Another type of constraint we need to express are constraints that something does not equal a certain value. For example, in SSP we have the constraint that the size of the list xwt cannot equal 1.
This could be constructed by a couple of
Range
constraints (one range for everything below 1, and another for everything above 1), but that seems like a hack.The text was updated successfully, but these errors were encountered: