Perpetual tasks #490
Open
Perpetual tasks #490
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
|
Converted to a draft since the proposed KIS handling for perpetual tasks is not yet implemented. |
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.
Closes #467 by introducing the duration field on task type and task templates to be optional.
Documentation
There are a couple of consequences, which first are documented here but have to also be documented in a wiki page:
Semantics of Task (Type / Template) Duration
The duration is now optional, resulting in the semantic that if no duration is provided, the task will run perpetually, even after a restart of DRES.
Consequences
Syncrhonous Run
For perpetual tasks in a synchronous setting, administrators have to manually close (abort) the task.
Asynchronous Run
For perpetual tasks in an asynchronous setting, participants are free to skip the task, which might affect the scoring.
Other Changes
There is a new
NOOPscorer, the non-operational scorer simply does not calculate a score, yet feedback regarding the submisison is provided.