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

Check flex to normal queue for frontera #64

Closed
janahaddad opened this issue Apr 5, 2024 · 11 comments
Closed

Check flex to normal queue for frontera #64

janahaddad opened this issue Apr 5, 2024 · 11 comments
Assignees

Comments

@janahaddad
Copy link
Collaborator

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)

@pvelissariou1
Copy link
Collaborator

@janahaddad , @ufuk let's have this discussion in Monday's meeting

@janahaddad
Copy link
Collaborator Author

in parallel with #59

@uturuncoglu
Copy link
Collaborator

@pvelissariou1 @janahaddad After sync, now Hercules is using batch queue. So, there is no need to update rt.sh. I'll test Frontera queue.

@uturuncoglu
Copy link
Collaborator

It seems that normal queue requires at least 3 nodes. There are new queue which is called as small. This can be used for RT runs but I am not how different from flex. Anyway, let's keep flex at this point and if you see small is better. We could switch to that one.

@uturuncoglu
Copy link
Collaborator

Maybe development could be an option.

@pvelissariou1
Copy link
Collaborator

@uturuncoglu development waltime is 30min only. Running the atlantic RTs might require more time (especially with WW3 coupling). I'll check and report back.

@uturuncoglu
Copy link
Collaborator

@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, development queue has fast turn around.

@pvelissariou1
Copy link
Collaborator

@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?

@uturuncoglu
Copy link
Collaborator

@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.

@uturuncoglu
Copy link
Collaborator

@pvelissariou1 @janahaddad JFYI, I switched to development queue on Frontera and fixed the issues.

@pvelissariou1
Copy link
Collaborator

@uturuncoglu Thanks

@janahaddad janahaddad removed this from the Ready for start of Workflow Dev milestone May 20, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in ufs-coastal project May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants