-
Notifications
You must be signed in to change notification settings - Fork 23
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
Rearrange allocation of submodels across nodes #212
Comments
I think that originally (long time ago) that was the order but it got changed for some reason. OASIS related I would guess but maybe YATM relies on being the root PE of MPI_COMM_WORLD. I'd hope not but I suppose it could be tested pretty quickly with the 1 degree config to see if there are any potential problems. |
Unfortunately your hunch was right @russfiedler. With submodules rearranged as MOM, CICE, YATM it exited with
with the last 2 lines repeated 240 times (which is the total number of MOM+CICE cpus). The first assertion that fails is in accessom2.F90. @nichannah - I guess this is needed for a good reason? |
slack discussion: https://arccss.slack.com/archives/CC78YM9EE/p1594782404008100 |
Back in the May TWG meeting we noted that YATM is allocated to the first PE on the first node, followed by the root PE of MOM on the same node. We discussed whether another placement of accessom2 components on nodes would be preferable for IO etc.
Should the order be CICE, MOM, YATM so the 3 root PEs are on separate nodes?
Is this simply a matter of changing the order of the submodels in config.yaml?
The text was updated successfully, but these errors were encountered: