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

Slow validation runs/cores setting #137

Open
arezoorn opened this issue Aug 3, 2020 · 0 comments
Open

Slow validation runs/cores setting #137

arezoorn opened this issue Aug 3, 2020 · 0 comments

Comments

@arezoorn
Copy link
Collaborator

arezoorn commented Aug 3, 2020

When requesting the cores for a given basins, that core is used to start 2 CTRL/BEST validation runs. For example, we request a dedicated node and run the model with 36 cores during calibration which is fine. But for validation, there would be two jobs with 36 cores that run in the same dedicated node. I am not sure how it is possible to run jobs requiring more cores than it is available, but I have noticed a slow down in the runs. Easiest solution would be to run CTRL wait until finishes, and then run BEST.

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

No branches or pull requests

1 participant