#constraintprogramming #ortools #scheduling/#routing #optimization
I think I'm thinking about this wrong.
My basic problem is scheduling #radar collection intervals in continuous time. There are many constraints on the intervals already and that's all working (by which I mean "running"--I'm not actually connected to a radar yet).
However, I also want to put a constraint on interval *transitions* to make sure we don't require the dish to move instantaneously.
AFAIK, the only way to constrain adjacent items like this is via a circuit. So I was going to add a "circuit overlay" to the model. Then I could say that the "edge" from radar dwell A to radar dwell B had to be a certain time distance apart or whatever.
I'm writing a tiny test program to see how that works and it isn't doing what I expect.
But in debugging that, I think I just realized my entire plan doesn't work. There's no reason the circuit overlay is going to come out in the same order as the intervals as laid out in time. That voids the entire plan!
Also, even though all the kids are home for #christmas none of the #nerd are awake for rubber-duckying
GRRRRRRRRRRRRRR


