FATES meeting. 25 June 2020

Experimental Notes. (feel free to add things!) Semi inspired by https://github.com/ESCOMP/CTSM/wiki/Meeting-Notes-2020-Science

Agenda: Open discussion

1. Pull request updates:

8 pull requests currently open.

https://github.com/NGEET/fates/pull/665 is ready. Allows Fire and FATES-hydro to coexist.

Ryan’s nutrients. Lots of code… https://github.com/NGEET/fates/pull/598 Maybe not ready for next month

https://github.com/NGEET/fates/pull/661 Yilin’s hydro solve. Fixed some bugs. Needs more work for convergency. Could do with hydro people having a look. Yiling has made some more tests after integrating Ryan’s updates.

Charlie’s land use code. Closer to ready than anticipated :) Needs syncing with E3SM. https://github.com/NGEET/fates/pull/663

Sam L. Lightening data coming from CTSM. Needs larger more robust set of tests. Jackie testing in S America and Polly in the Sierra. https://github.com/NGEET/fates/pull/635

Chonggang. Grass carbon allocation. Hold off on regression testing for now. Ryan to check in offline. https://github.com/NGEET/fates/pull/628

Greg canopy trimming. Should be done this work. Few little things left; mostly adding requested comments. FATES-doc update in work as well. https://github.com/NGEET/fates/pull/623

Active crown fire. Hypothesis changed half was through development and development on hold. Science issues to resolve. Does canopy fire cause feedback to fire behaviour? Could be scaled back to consumption of crown fuels by itself. Needs a little piece to finish that. Lots of extra code might need to be moved. https://github.com/NGEET/fates/pull/584

2. Switching from FATES Release branch to Master/Main branch

Moving to master from the release branch

https://github.com/ESCOMP/CTSM/tree/master

https://github.com/ESCOMP/CTSM/tree/release-clm5.0

Greg has been doing the (large) job of switching branches. The shift will be answer changing and in making the change we will need to re-write the history of the FATES_NEXT_API branch which will be a new branch with a different history (due to git rebase operation). Maybe with a new name. The new ‘next_api’ branch will become the default FATES CTSM branch. New updates to next_api need to be planned with respect to this switch. GET IN TOUCH IF YOUR WORK NEEDS CHANGES TO FATES_NEXT_API.

Will: need to plan merging strategy in future code management and how to keep up with master. ELM code structure is different as FATES is in lne with the Master branch.

We are changing from MASTER to MAIN, because it’s a good idea. Waiting on a protocol from Github which should be forthcoming soon.

3. LAND USE TESTS (Charlie and Alan)

Using an amalgamated version of LUH2 (add details) to drive the existing logging module. Charlie is concerned that the secondary land use may not be working correctly.

Link to notebook: https://github.com/ckoven/landuse_runscripts/blob/master/landuse_global_analysis.ipynb

Cherry: Discussion of how to link San Lorenzo inventory files to FATES files. Each quadrat in dataset can be considered a patch in the initialization file, and FATES will consolidate the observed patches into modeled patch elements. Similarly for cohorts.

4. Future of Medlyn Stomatal update

Ryan asked Cherry about status and about using as default in fates.