rewarding or penalizing constraint matches #185
pilioulian
started this conversation in
General
Replies: 1 comment
-
To the solver, the only thing that matters is the final score. Scores are ordered from best to worse, higher number means better score - whether you arrived there through rewards or penalties is of little consequence. Even though there may not be difference between how the two are handled, there is a difference in how you think about them. Some constraints may be naturally rewarding, some naturally penalizing. If the solver only offerred penalizing, for example, that may be too limiting for constraint design. But again, practically speaking, the solver won't mind - it only cares for the final score. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I was wondering about whether there is a recommended way of weighing constraints. Often constraints can either be modeled by penalizing as well as rewarding something, yielding the same result (e.g. to schedule something as early as possible penalize by begin or reward by span-begin).
Is there a best practice or does it even affect the solver when combining multiple constraints using a mix of penalize and reward?
From my understanding it should not matter, except maybe making it harder to understand the implications of single constraints in relation to the rest of the constraints
Beta Was this translation helpful? Give feedback.
All reactions