Skip to content

Fix chrysalis cores per node: 64 not 128#424

Merged
xylar merged 1 commit into
E3SM-Project:mainfrom
xylar:fix-chrys-cores-per-node
May 22, 2026
Merged

Fix chrysalis cores per node: 64 not 128#424
xylar merged 1 commit into
E3SM-Project:mainfrom
xylar:fix-chrys-cores-per-node

Conversation

@xylar

@xylar xylar commented May 22, 2026

Copy link
Copy Markdown
Collaborator

The same applies to max. MPI tasks per node.

Checklist

  • Tests pass and new features are covered by tests
  • Testing comment, if appropriate, in the PR documents testing used to verify the changes

The same applies to max. MPI tasks per node.
@xylar

xylar commented May 22, 2026

Copy link
Copy Markdown
Collaborator Author

Testing

I ran a custom suite of tests on Chrysalis with this fix. I see that one node corresponds to 64 cores, as expected.

The tests were:

  mesh/spherical/icos/base_mesh/240km/task
  e3sm/init/icos240km/topo/remap
  e3sm/init/icos240km/topo/cull
  ocean/global_ocean/hydrography/woa23

@xylar xylar merged commit 6272019 into E3SM-Project:main May 22, 2026
10 checks passed
@xylar xylar added the bug Something isn't working label May 22, 2026
@xylar xylar deleted the fix-chrys-cores-per-node branch May 22, 2026 09:47
@xylar xylar self-assigned this May 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant