#constraintprogramming #ortools #scheduling/#routing #optimization
I think I may have gotten this working in the toy problem. I can get a list of time-ordered optional intervals AND a circuit in the same order. That will let me put sequential constraints at the circuit level (I hope)
The key turned out to be to make sure all present intervals were also entered nodes AND that every x->y edge meant that x.time < y.time....and that the reverse is not true!
It's weird how confused I am by half-reified constraints, given that's *exactly* how programming languages do variable assignment.
a = b
makes a take the value b, but not vice versa.
