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

Long-term/mid-term feature wishlist for the logging module #276

Closed
rgknox opened this issue Sep 22, 2017 · 14 comments
Closed

Long-term/mid-term feature wishlist for the logging module #276

rgknox opened this issue Sep 22, 2017 · 14 comments

Comments

@rgknox
Copy link
Contributor

rgknox commented Sep 22, 2017

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.

@rgknox
Copy link
Contributor Author

rgknox commented Sep 22, 2017

Generation of completely separate patches for infrastructure. These patches would have no-to-little survivorship.

@rgknox
Copy link
Contributor Author

rgknox commented Sep 22, 2017

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.

@rgknox
Copy link
Contributor Author

rgknox commented Sep 22, 2017

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.

@rgknox rgknox changed the title Feature wishlist for the logging module Long-term/mid-term feature wishlist for the logging module Sep 22, 2017
@ckoven
Copy link
Contributor

ckoven commented Sep 22, 2017

addition of disturbance tags and incorporation of those into patch fusion logic to allow the tracking of secondary forest area

@rgknox
Copy link
Contributor Author

rgknox commented Sep 22, 2017

@ckoven should we start a new thread related to a wishlist or design improvements to disturbance in general?

@ckoven
Copy link
Contributor

ckoven commented Sep 22, 2017

@rgknox not sure i understand the distinction.

@rgknox
Copy link
Contributor Author

rgknox commented Sep 22, 2017

I was wondering if we needed tags for other types of event tracking, but if this is really relegated to logging, then maybe not.

@huangmy
Copy link

huangmy commented Feb 13, 2018

@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?

@rosiealice
Copy link
Contributor

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
@rosiealice
Copy link
Contributor

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...)

@huangmy
Copy link

huangmy commented Feb 14, 2018

@rosiealice agreed. Do you remember who was taking the notes? @jenniferholm was that you?

@ckoven
Copy link
Contributor

ckoven commented Feb 14, 2018

@ckoven
Copy link
Contributor

ckoven commented May 19, 2022

closing because out of date.

@ckoven ckoven closed this as completed May 19, 2022
@glemieux
Copy link
Contributor

This was fixed in #663

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

5 participants