-
Notifications
You must be signed in to change notification settings - Fork 92
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
Long-term/mid-term feature wishlist for the logging module #276
Comments
Generation of completely separate patches for infrastructure. These patches would have no-to-little survivorship. |
Modification to the parameter file that allows a series of independent events to occur at different points in the simulation, each with their own logging/disturbance/damage rates. |
A new parameter that describes the survivorship of understory plants that experience disturbance from logging, this may or may not be thought of as understory collateral death fraction. |
addition of disturbance tags and incorporation of those into patch fusion logic to allow the tracking of secondary forest area |
@ckoven should we start a new thread related to a wishlist or design improvements to disturbance in general? |
@rgknox not sure i understand the distinction. |
I was wondering if we needed tags for other types of event tracking, but if this is really relegated to logging, then maybe not. |
@rgknox @ckoven and @rosiealice I was trying to add a new issue related to bring the trunk product to the fates interface mainly because I realized that I had to back calculating it when writing the manuscript, and then realized that we already opened this issue a while back. It will be useful if we take this as an opportunity to conceptualize a general interface for simulating land use and management in FATES. Not sure how much could be done within NGEE-T but it won't hurt to think ahead. Then we could prioritize things based on resources available. What do you think? |
Yes, good call. Maybe we should revisit the plan we had back at the land use workshop? And perhaps bring in people who might be interested in these issues in the medium term? Joshua Rady, for example, has done a lot of work on column dynamics in CLM (can't tag anyone as I'm on my phone...) |
1 similar comment
Yes, good call. Maybe we should revisit the plan we had back at the land use workshop? And perhaps bring in people who might be interested in these issues in the medium term? Joshua Rady, for example, has done a lot of work on column dynamics in CLM (can't tag anyone as I'm on my phone...) |
@rosiealice agreed. Do you remember who was taking the notes? @jenniferholm was that you? |
@huangmy: Notes from that meeting are here: |
closing because out of date. |
This was fixed in #663 |
The version 1 of the logging module is nigh upon us.
I wanted to summarize some of the wishlist items people have brought up in discussion, and solicit input on other logging features that may be useful in further implementation.
The text was updated successfully, but these errors were encountered: