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

Add clm6_0 physics option to CLM_PHYSICS_VERSION #2378

Closed
ekluzek opened this issue Feb 20, 2024 · 5 comments
Closed

Add clm6_0 physics option to CLM_PHYSICS_VERSION #2378

ekluzek opened this issue Feb 20, 2024 · 5 comments
Assignees
Labels
enhancement new capability or improved behavior of existing capability
Milestone

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Feb 20, 2024

As closure to the ctsm5.2.0 branch work we need to add a clm6_0 physics option. This is because with ctsm5.2.0 clm5_1 physics no longer makes sense, because tags will no longer be ctsm5.1.devXXX but tags after that point. With the CESM3 release CTSM will be ctsm6.0.0, so the physics version should be clm6_0.

Once, this is added, other components like: CISM, CAM, CMEPS will need to update compsets to point to clm6_0 rather than clm5_1, and remove clm5_1 from all compsets. The same is true of CLM we'll remove clm5_1 from our compsets and tests.

Also do a general look through and make sure README files and documentation in the code is reasonable.

@ekluzek ekluzek added the enhancement new capability or improved behavior of existing capability label Feb 20, 2024
@ekluzek ekluzek added this to the ctsm5.2.0 milestone Feb 20, 2024
@ekluzek ekluzek self-assigned this Feb 20, 2024
@ekluzek
Copy link
Collaborator Author

ekluzek commented Mar 5, 2024

@cacraigucar after we make the ctsm5.2.0 tag I'll make issues in CAM and CESM to update compsets for this.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Mar 7, 2024

For testing I'm just going to leave clm4_5, clm5_0 testing alone. Move all of the clm5_1 tests to clm6_0 and only keep a few key clm5_1 tests so that CAM and CESM shouldn't break until they remove it from their compsets.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Mar 7, 2024

It looks like the only testing that CAM and CESM have with clm5_1 are for the ne30np4.pg3 grid for SMS and ERP, on derecho with debug. So the clm5_1 testing can be very limited.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Mar 9, 2024

Need a 1850 BGC-CROP version for CESM and HIST SP version for CAM.

@ekluzek
Copy link
Collaborator Author

ekluzek commented Apr 20, 2024

This came in with ctsm5.2.0 and #2417

@ekluzek ekluzek closed this as completed Apr 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new capability or improved behavior of existing capability
Development

No branches or pull requests

1 participant