Replies: 1 comment
-
|
There is documentation: https://docs.timefold.ai/timefold-solver/latest/using-timefold-solver/modeling-planning-problems#valueRangeProviderOnPlanningEntity The difference with this feature is that you don't need to store these value ranges anywhere, and you don't need to store the solution to compute them. This helps with cloning performance, because the cloner no longer needs to worry about these possibly very large collections. Nothing changes in terms of how you can use value ranges. They continue to be a one-time thing; they must not depend on any variable, and therefore must never change. |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, teams.
I noticed that there is a new feature in version 1.29.0 - "supporting parameters for the value Range annotated method". I'd like to know in what scenarios this feature can be used? Is there any related documentation about it?
Does it mean that different valure range can be return dynamically based on the parameters during solving?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions