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

Express "not equal" constraints #1798

Open
bmaclach opened this issue Aug 2, 2019 · 4 comments
Open

Express "not equal" constraints #1798

bmaclach opened this issue Aug 2, 2019 · 4 comments

Comments

@bmaclach
Copy link
Collaborator

bmaclach commented Aug 2, 2019

Currently in Drasil, constraints can either be expressed as a Range, EnumeratedReal, or EnumeratedStr.

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.

@JacquesCarette
Copy link
Owner

So the list can be empty? That's odd.

@bmaclach
Copy link
Collaborator Author

bmaclach commented Aug 2, 2019

Yes. The water table may not exist (i.e. the slope is dry).

@JacquesCarette
Copy link
Owner

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.]

@JacquesCarette
Copy link
Owner

Like #1800. But this one might require a design first, before going ahead with an implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To do
Development

No branches or pull requests

4 participants