-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
@objective in a (specific) model give "MethodError: no method matching iterate(::Nothing)" #220
Comments
Sorry that is a small error on my side. Good catch. A fix is on its way. Unfortunately my solver has quite some troubles solving it at the moment.Not sure why yet but I see that I need more testing with reified constraints for objective functions. Thanks again for the issue and the testing of my solver. It's a long way to go to make it really usable as it's a massive project but I enjoy the journey. |
The optimal solution is |
I found out why this is very slow in general:
Nevertheless in general a scheduling constraint needs to be implemented 😄 |
Thanks for looking into this, Ole. And I agree that there should be a dedicated scheduling constraint. :-) However, I don't understand your comment: "It's not immediately obvious that the sum over the b for each task needs to be the duration, so I would add that constraint.". Would you mind explain a little more what you mean? |
For clarification: This is given by your definition but it's not as easy for my solver to see. I would therefore add that constraint as a user. |
@Wikunia Yes, you have a good point and I will test this as well. (My formulation is one of the most used decompositions in the CP folk lore.) |
Unfortunately because of the other problems I have identified this will still take a minute to solve. |
Here is a model that works without
@objective
but adding an@objective
throwsMethodError: no method matching iterate(::Nothing)
. I don't know is this is a bug in my model or somewhere else. (It use a decomposition ofcumulative
and that might very well be the culprit.)And sorry about the largish model. I haven't had any similar problems with
@objective
before this.The text was updated successfully, but these errors were encountered: