Replies: 1 comment 1 reply
-
|
You would divide the task into subtasks, and have the subtasks refer to each other inside a collection of required concurrent tasks. Typically, a task would have a ready time (earilest possible start time), start time, and an end time. Ready time only depends on previous' end time, end time only depends on start time, and start time depends on ready time and the concurrent group's ready times. For an example, see |
Beta Was this translation helpful? Give feedback.
1 reply
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, Teams.
In the Chained Through Time pattern, when a task requires two employees to work together simultaneously, it's necessary to build on the Chained Through Time pattern with "automatic delay until last" logic to ensure both employees are available when the task starts.
I'm using PlanningListVariable with Shadow Variable in my project now. How should I implement logic - "automatic delay until last"? Should I implement this logic in the startTimeSupplier method, but I'm still unsure how to implement it? Do you have any ideas or implementation suggestions for this situation?
Thanks in advanced
About the automatic delay until last.
https://docs.timefold.ai/timefold-solver/latest/design-patterns/design-patterns#chainedThroughTimePattern
Beta Was this translation helpful? Give feedback.
All reactions