Skip to content

Visit stops in 1st time window 1st then then orders in 2nd time window #4107

Discussion options

You must be logged in to vote

Enforcing it as hard-constraint is probably the easier one:

  • Define your "P"artially "O"rdered "Set" (Poset)
  • Add precedence-constraints in-between those antichains -> aka for each order F in FIRST; for each order S in SECOND: F precedes S

Enforcing it through an objective / soft is imho not that easy in the routing-solver as objective-structures are kind of fixed (opposed to the CP-solver mechanism in the hard-constraint parts) with good reasons: internal invariants.

There might be some "hacky" way of introducing VERY COSTLY transition-costs between those antichains reversed (arc from order in group SECOND -> order in group FIRST = EXPENSIVE!; then one would also add DEPOT -> SECOND = EX…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@PredatorXix
Comment options

Answer selected by PredatorXix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants