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

How to specify an included file when solving from FZN (for findMUS) #789

Open
raphaelboudreault opened this issue Jan 29, 2024 · 0 comments

Comments

@raphaelboudreault
Copy link

raphaelboudreault commented Jan 29, 2024

Hello,
I am currently trying to use findMUS on a model compiled for the Chuffed solver using it as a subsolver with option --subsolver chuffed.

In my model, I use the priority_search annotation by adding include "chuffed.mzn" at the top of the model file, which is required for MiniZinc to recognize the annotation. However, when compiling to FZN, the include statement disappears, making the MiniZinc driver running on the FZN file (minizinc <path to fzn file> --solver chuffed) return:

Error: type error: no function or predicate with name `priority_search' found

Is this a correct behavior? If not, how can I specify the definition file to include to MiniZinc? Or how can I tell MiniZinc to ignore the parsing phase and call chuffed directly?

Currently, this makes findMUS fail with since it calls the MinZinc driver with the generated FZN.


Also, I looked at findMUS solver options and I could provide additional subsolver options using --solver-flags <flags>. However, I noticed that --solver-flags is missing from the MSC file for findMUS.

Finally, is findMUS still actively maintained? I found the code on GitLab, but many branches are opened and unmerged in master/develop. I believe it would be really interesting for the CP community and industrials (as in my case) to further develop this module and allow it to be used in production. Maybe by making it accessible from GitHub?

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

No branches or pull requests

1 participant