Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

canopy spread issues #988

Closed
ckoven opened this issue Feb 22, 2023 · 1 comment
Closed

canopy spread issues #988

ckoven opened this issue Feb 22, 2023 · 1 comment

Comments

@ckoven
Copy link
Contributor

ckoven commented Feb 22, 2023

A thing occurred to me recently that I am not sure about how we should deal with. Since #279 the canopy spread logic has been at the site rather than the patch level. In the case of a nocomp configuration, if the total area in which woody PFTs can grow is less than the canopy closure threshold parameter on a given gridcell, then the trees will always remain in the high-crown-area state. This doesn't seem ideal to me but I am not sure what the best alternative is. We could change the canopy spread parameter when in nocomp configuration to make it a vector of length nocomp PFTs and evaluate it separately on patches of each nocomp PFT. Or maybe we could leave as-is. Curious if others see this as a problem in the current scheme or if anyone sees a better solution.

@ckoven
Copy link
Contributor Author

ckoven commented Feb 22, 2023

Also noting that this will also apply when and if we have managed land-use types that exclude woody plants: if their total area approaches one minus the canopy closure threshold, then that would change the crown area allometry of trees in the unmanaged land-use types.

@glemieux glemieux changed the title canopy spread in nocomp mode canopy spread issues Feb 27, 2023
@NGEET NGEET locked and limited conversation to collaborators Feb 27, 2023
@glemieux glemieux converted this issue into discussion #990 Feb 27, 2023
@github-project-automation github-project-automation bot moved this from ❕Todo to ✔ Done in FATES issue board Feb 27, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant