Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Naive scheduler #95

Merged
merged 5 commits into from Oct 18, 2022
Merged

Naive scheduler #95

merged 5 commits into from Oct 18, 2022

Conversation

fjosw
Copy link
Contributor

@fjosw fjosw commented Oct 18, 2022

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

<scheduler>
    <schedulerType>naive</schedulerType>
</scheduler>

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 into geneticSchedule.

@fjosw fjosw requested a review from aportelli as a code owner October 18, 2022 12:13
@aportelli
Copy link
Owner

Looks great, many thanks!

@aportelli aportelli merged commit 54b1ee1 into aportelli:develop Oct 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants