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

RDDLConstraints does not parse constraints involving literals #241

Open
mike-gimelfarb opened this issue Feb 2, 2024 · 3 comments · Fixed by #246
Open

RDDLConstraints does not parse constraints involving literals #241

mike-gimelfarb opened this issue Feb 2, 2024 · 3 comments · Fixed by #246
Assignees
Labels
bug Something isn't working

Comments

@mike-gimelfarb
Copy link
Collaborator

RDDLConstraints cannot parse constraints such as

some-fluent(@o) > bound

when the type of @o contains multiple objects, since they all get assigned the same lower bound bound.

@mike-gimelfarb mike-gimelfarb added the bug Something isn't working label Feb 2, 2024
@mike-gimelfarb mike-gimelfarb self-assigned this Feb 2, 2024
@mike-gimelfarb
Copy link
Collaborator Author

This issue will be fixed by merging the v2-branch into main.

@mike-gimelfarb
Copy link
Collaborator Author

After careful investigation, the issue still remains. For example, using forall_{?x : obj, ?y : obj2} fluent(?x) >= non-fluent(?x, ?y) with the redundant ?y in l.h.s. causes the parsing to fail!

@ataitler ataitler linked a pull request Feb 10, 2024 that will close this issue
@mike-gimelfarb
Copy link
Collaborator Author

Was the above case resolved with the new commits? I think to definitely solve this, the _map function from the compiler's tracer will need to be employed here, as that function covers every single case of mapping objects between two parameterized expressions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant