-
Notifications
You must be signed in to change notification settings - Fork 5
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
Check flex to normal queue for frontera #64
Comments
@janahaddad , @ufuk let's have this discussion in Monday's meeting |
in parallel with #59 |
@pvelissariou1 @janahaddad After sync, now Hercules is using |
It seems that |
Maybe |
@uturuncoglu development waltime is 30min only. Running the atlantic RTs might require more time (especially with WW3 coupling). I'll check and report back. |
@pvelissariou1 As I know the RT system is just for small jobs that runs quickly to test the capability. If we want to run realistic high resolution cases, that could be part of testing in the application level. BTW, |
@uturuncoglu I understand this. From our side we need to run/test the large cases maybe not on Frontera but in ther HPC platforms. Let's switch to develop (as the default) on Frontera, if the user wants he/she can change to some other queue. Since you are comfortable doing this from the ufs-weather-model side you might want to submit a PR for this? |
@pvelissariou1 Yes. That is totally understandable. We could have another level of testing in the application side to tests those large scale realistic cases. I am not sure how this is handled with HAFS. I think they have some level of testing with workflow: https://hafs.readthedocs.io/en/latest/RegressionTest.html. @janahaddad We might contact with HAFS team to learn about their experience about testing besides model level RTs. |
@pvelissariou1 @janahaddad JFYI, I switched to |
@uturuncoglu Thanks |
Great, thanks for checking. @uturuncoglu We might need to switch from flex to normal queue for frontera (or something it works for the users, need to check on that). Also for "hercules" we need to switch from "windfall" to the "batch" qos.
Originally posted by @pvelissariou1 in #46 (comment)
The text was updated successfully, but these errors were encountered: