You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: