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.
I implemented an alternative scheduler which I call "naive". All it does is schedule modules in the order they are created. I need this feature for workflows with many
WilsonClover
type actions. As the Clover term is calculated in the constructor of the action the genetic scheduling for this kind of applications can exceed wall clock time. I think also @rrhodgson has applications where this kind of scheduling is needed.The alternative scheduler can be chosen via the following addition to the xml global header
If no scheduler is specified Hadrons defaults to the genetic algorithm but raises a warning.
For a more consistent naming one could consider renaming
schedule
intogeneticSchedule
.