Adding a Fixed Duration Interruptible Task #143
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
tests are still missing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @tpaviot,
in #142 the
ResourceInterruptibleandResourcePeriodicallyInterruptibleresource constraints have been added and they work well with the existing Task variations:VariableDurationTaskspans over the interruption intervals whereas for the other task classes, the interrupting constraints act likeResourceUnavailableandResourcePeriodicallyUnavailable.The
VariableDurationTaskbrought my project visualizer a big step forward, but since there is no way to give an exact duration with respect to overlapped periods, I needed to implement a newFixedDurationInterruptibleTask.Here it is.
What's your opinion?