1 of 20

Agenda

  • 1:15-2:00 pm (Seminar room)

FATES Practical Orientation:

“Running FATES: what do you need to know?”

  • 2:00 - 4:45 (Library)

Self guided FATES practical

  • 4:45 (Library)

CLM Tutorial Wrap Up

  • 5:15

Bus pick-up

2 of 20

Running FATES: what do you need to know?

  • NGEET/fates github website
  • Navigating the code and folder system
  • CLM <-> FATES compatibility
  • Modifying a run:
    • FATES namelist
    • FATES parameters
  • Modifying output (history)
  • Practical sessions

3 of 20

4 of 20

Where does the FATES code live? (in CTSM)

ctsm

cime

scripts

src

main

soilbiogechem

tools

other stuff...

biogeochem

biogeophys

fates

other stuff...

create_newcase, etc.

cime_config

doc

manage_externals

test/tools

tools

5 of 20

Where does the FATES code live? (in CTSM)

ctsm

cime

scripts

src

main

soilbiogechem

tools

other stuff...

biogeochem

biogeophys

fates

other stuff...

create_newcase, etc.

cime_config

doc

manage_externals

main

biogeochem

biogeophys

fire

test/tools

tools

parteh

parameter_files

tools

functional_unit_testing

6 of 20

Where will our practice runs live?

cime

scripts

tools

other stuff...

run1_1x1brazil

run2_1x1brazil_structure

run3_f45_2pfts

/glade/scratch/$USER

run1_1x1brazil

run2_1x1brazil_structure

run3_f45_2pfts

Scripts

Modifiers

Parameters

Namelists

The executable

Model Output

}

}

7 of 20

CLM <-> FATES COMPATIBILITY

8 of 20

FATES-master

CLM-master

Master FATES, shake my hand good fellow.

What is this rubbish, who holds their cane in their 7th hand!

9 of 20

FATES (master)

CLM (fates_next_api)

Yes, yes, much better

Yes indeed.

10 of 20

ESCOMP/CTSM, master

NCAR/fates-release, fates_s1.8.1_a3.0.0_rev2

repository

branch

repository

tag

CTSM master will automatically checkout a compatible FATES tag from their repository when you run:

./manage_externals/checkout_externals

Cutting edge

Not cutting edge

11 of 20

ESCOMP/CTSM, fates_next_api

NGEET/fates, master

repository

branch

repository

branch

To use the cutting-edge FATES code. You will need the master branch from the NGEET/ repository, and use git commands to checkout:

fates_next_api

Not cutting edge

Cutting edge

12 of 20

Modifying a Run - Namelist

13 of 20

Fates Namelist Controls https://github.com/NGEET/fates/wiki/Namelist-Options-and-Run-Time-Modes

Contact: jkshuman@ucar.edu

Contact: cxu@lanl.gov

Contact: maoyi.huang@pnnl.gov

Contact: cdkoven@lbl.gov

Contact: rgknox@lbl.gov

Contact: rgknox@lbl.gov

Contact: rgknox@lbl.gov

14 of 20

15 of 20

FATES History Variables,

where the magic happens.

https://github.com/NGEET/fates/blob/master/main/FatesHistoryInterfaceMod.F90

16 of 20

What if i want to be a developer?

https://github.com/NGEET/fates/blob/master/CONTRIBUTING.md

17 of 20

18 of 20

Model run 1 - (Getting a run going)

  1. Learn how to execute a simple fates run
  2. Two optional methods of evaluating output

Model run 2 - (studying output)

  1. Learn about differents sorts of FATES output
  2. Learn about adding new history variables.
  3. Plotting up FATES-specific size-structured output (python)

Model run 3 - (studying parameters)

  1. Learn about FATES PFTs
  2. Learn about changing PFT file.
  3. Do a global run
  4. Plot output of global run. (matlab)

19 of 20

Extra Slides

20 of 20

Where does the FATES code live? (in E3SM)

clm

cime

scripts

src

main

soilbiogechem

tools

other stuff...

biogeochem

biogeophys

fates

other stuff...

create_newcase, etc.

components

test

other stuff...

n.b. This directory structure is a bit different to earlier versions of CLM, if you are used to those.

main

biogeochem

biogeophys

fire

external_modules

components

ACME