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

(once ...) predicate missing #20

Closed
fairlight1337 opened this issue Oct 11, 2016 · 1 comment
Closed

(once ...) predicate missing #20

fairlight1337 opened this issue Oct 11, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@fairlight1337
Copy link
Owner

fairlight1337 commented Oct 11, 2016

(once ...) would cut off all solutions after the first one (if any). This is applicable for situations in which only a truth value is required, for example >=:

(<- (>= ?a ?b)
  (or (> ?a ?b)
      (= ?a ?b)))

When resolving this, it yields two solutions if both, > and = are met, instead of only one expected. The final predicate would be used like this:

(<- (>= ?a ?b)
  (once (or (> ?a ?b)
            (= ?a ?b)))
@fairlight1337 fairlight1337 added this to the AAMAS'17 milestone Oct 11, 2016
@fairlight1337 fairlight1337 self-assigned this Oct 11, 2016
@fairlight1337
Copy link
Owner Author

No. Just no.

The problem fomulated above (about (>= ...) yielding multiple solutions) is just plain wrong. Either > OR = holds, not both. That's what >= is for. Late night oddness.

Anyway, the once predicate has its designated spot for cutting off solutions after the first one. So I implemented it in c324edd. This closes this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant