-
Notifications
You must be signed in to change notification settings - Fork 15
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
Revise ncclimo default invocation #9
Comments
Do you encounter problems with the current zppy climo default? |
I experience long time for the queued jobs to run on Cori. At today's LR+RRM finalization meeting, @xuezhengllnl also mentioned long queue time for post processing jobs. I thought revising the ncclimo default invocation for climo will alleviate this problem as well. |
Did you use the debug queue? climos normally don't take long to compute and can fit in the cori debug queue. You can try, but I don't see an easy, optimal way as it depends on the machine queue configs and more importantly the realtime machine usage by others. |
@chengzhuzhang nd @czender : I'll gladly defer to you two regarding the best default settings for post-processing with ncclimo. Here is an example of a configuration file for some v1-HR output on chrysalis. Note that MPAS-Analysis will fail because some mpas-o output files are corrupted, so you may want to turn the task off.
|
zppy chooses to invoke ncclimo in MPI mode with requesting 4 nodes for climo jobs. Based on email exchanges with @czender: For all low resolution simulations, use the default background mode instead, will potentially reduce queue time and save resources. MPI mode can be useful for HR simulations, and those can either be assigned multiple nodes in MPI mode or accomplished in background mode by ratcheting down the number of concurrent processes (to relieve RAM pressure) with the --job_nbr option.
The text was updated successfully, but these errors were encountered: