You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the following issue: I'm solving a relatively huge problem using Gecode. I can see that gecode solved (solution displayed) it, but something is still going on. This delay could be very significant, more than the solution time. For example, I can see the solution on my machine when the timer is on ~2:30, but it still needs to be finished at ~6:00.
My wild guess is that it's related to some memory cleaning. Could it be cut if only one solution is required?
Thanks in advance!
Ilya
The text was updated successfully, but these errors were encountered:
The difference between the time would normally be explained by the output processing. MiniZinc takes the output from the solver and translates it back in terms of the model, evaluating the output model created during flattening. Usually this does not take much time, especially for solvers like Gecode, where the decisions representation is generally the same as in the MiniZinc model. For MIP or SAT solvers, it is not uncommon that this might take longer.
Since the output model can contain many type of functions, there is no limit on the amount of time. If you want to share the model where the time difference is so surprising, then we might be able to help explain it in the specific case.
Hello,
I have the following issue: I'm solving a relatively huge problem using Gecode. I can see that gecode solved (solution displayed) it, but something is still going on. This delay could be very significant, more than the solution time. For example, I can see the solution on my machine when the timer is on ~2:30, but it still needs to be finished at ~6:00.
My wild guess is that it's related to some memory cleaning. Could it be cut if only one solution is required?
Thanks in advance!
Ilya
The text was updated successfully, but these errors were encountered: