Skip to content

/ gecode

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

Jump to bottom

Try moving the decomposition of the MiniZinc `gecode_cumulatives` constraint into MiniZinc #81

Open
zayenz opened this issue Aug 28, 2020 · 0 comments
Open

Try moving the decomposition of the MiniZinc `gecode_cumulatives` constraint into MiniZinc #81

zayenz opened this issue Aug 28, 2020 · 0 comments
Labels
good first issue help wanted

Comments

@zayenz
Copy link
Member

@zayenz zayenz commented Aug 28, 2020

The gecode_cumulatives MiniZinc constraint is used for implementing fzn_cumulative. The registry post function does a lot of inspection of the arguments, posting different variants of the constraint.

This requires first fixing #80 so that the relevant Gecode scheduling constraints are available in MiniZinc.

One potential benefit of this, is that the required start[i] + duration[i] = end[i] constraints would be available for common subexpression elimination for MiniZinc.
@zayenz zayenz mentioned this issue Aug 28, 2020
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue help wanted
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@zayenz
You can’t perform that action at this time.