Solver tips and tricks
You must not specify idle time without an valid reason ( > 0) when creating transition matrix definitions. Additionally, you must not switch non-standard setup at resource without a specific reason when creating resources. This can have severe performance penalties for the solver, especially when utility/enabling claim on changeover or setup is available.
This Restarting, some inconsistencies were detected message is displayed when a schedule is not feasible and is detected before the search phase starts.
The solver starts over, adding all the constraints of all batches to the model and finally printing the constraint that is violated. The solver also prints the batch state before the violated constraint is added. You can identify the reason why the schedule is not feasible.
The log output example of a batch is as follows:
- For each segment of the batch, the valid propagated minimum and maximum time bound are printed from the start and end variable of the segment.
- The propagated minimum and maximum duration of each segment is also printed.
- The initial domains of segments are the complete horizon interval. Each time a constraint is added to the model, the domains for some variables involved with the constraint can be small.