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

z0mr parameters are all the same in the default parameter file, inconsistant with CLM definitions. #1316

Closed
rosiealice opened this issue Jan 22, 2025 · 2 comments · Fixed by #1319

Comments

@rosiealice
Copy link
Contributor

The default parameters for fates_turb_z0mr (the "Ratio of momentum roughness length to canopy top height") are all 0.055. These are the same as the NLT values in CLM5 (table 2.5.1) but are likely wrongly defined for the other PFTs where the values are 0.075 for broadleaf evergreen trees and 0.12 for shrubs and grasses.

https://escomp.github.io/ctsm-docs/versions/release-clm5.0/html/tech_note/Fluxes/CLM50_Tech_Note_Fluxes.html

As far as i can tell, the required change to the parameter file is:

  • fates_turb_z0mr = 0.055, 0.055, 0.055, 0.055, 0.055, 0.055, 0.055, 0.055,
  • 0.055, 0.055, 0.055, 0.055, 0.055, 0.055 ;
  • fates_turb_z0mr = 0.075, 0.055, 0.055, 0.075, 0.055, 0.055, 0.12, 0.12,
  • 0.12, 0.12, 0.12, 0.12, 0.12, 0.12

This has non-trivial impacts on fluxes esp in semi arid regions.
https://ns9560k.web.sigma2.no/datalake/diagnostics/noresm/rosief/FATES-SP_rebaseddrydep.zengwang.twostream/compare/FATES-SP_rebaseddrydep.zengwang.twostream.z0mr/ANN/

Boundary layer conductance

Image

Sensible Heat

Image

Latent Heat

Image

@glemieux
Copy link
Contributor

Note to self: add this to the Monday software meeting agenda

@glemieux
Copy link
Contributor

Closed per #1319

@github-project-automation github-project-automation bot moved this from ❕Todo to ✔ Done in FATES issue board Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants