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

Adjust trop_cloud_top_lev for cam4 runs #284

Open
cacraigucar opened this issue Aug 6, 2024 · 1 comment
Open

Adjust trop_cloud_top_lev for cam4 runs #284

cacraigucar opened this issue Aug 6, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@cacraigucar
Copy link
Collaborator

What is the feature/what would you like to discuss?

Inside CAM's cloud_fraction.F90, trop_lev is adjusted to = 1 when macrop_scheme="rk". Since this is only set for CAM4 runs, we need to adjust this setting when CAM4 is implemented.

Is there anyone in particular you want to be part of this conversation?

No response

Will this change (regression test) answers?

No

Will you be implementing this enhancement yourself?

No

@cacraigucar cacraigucar added the enhancement New feature or request label Aug 6, 2024
@jimmielin jimmielin self-assigned this Oct 25, 2024
@jimmielin
Copy link
Member

jimmielin commented Feb 11, 2025

I've split that part of the cldfrc calculation off into a separate scheme, and introduced a CCPP variable vertical_layer_index_of_cloud_physics_top? that individual macrophysics schemes can set at initialization (so this has to be in the registry) to control the trop_lev.

I feel it will be cleaner this way to have this information contained in macrophysics schemes rather than let cloud_fraction query the model configuration like it was done in CAM for portability.

For cloud_fraction_fice I'll have to modify the metadata to do the same changes and assign it to the right value somewhere in initialization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants