Skip to content

CableCarbon

rml599gh edited this page Apr 22, 2015 · 1 revision

CABLE carbon video conference, 23/4/15

1. Carbon applications – what carbon-related work are people using CABLE (with CASA-CNP) for?

  • CSIRO-Canberra (Vanessa, Lars, Peter): Australian continent carbon budget, role of veg dynamics. Also global interest (POP model)
  • CSIRO-Aspendale (Tilo, Rachel): ACCESS-ESM1
  • CSIRO-Aspendale (Ying-Ping, Bernard, Chris): Offline, plant traits, version 2 write-up including CASA-CNP, Trendy analysis, simulations with NCAR met forcing 1900-2100, CASA-CNP with different soil carbon formulation, parameter estimation, land cover change
  • CSIRO-Aspendale (Cathy): parameter estimation, data assimilation, nutrient limitation, Australia, offline
  • CSIR, South Africa (Tami): offline site validation
  • Macquarie (Martin_: continental Australia simulation, FACE
  • UNSW (Mark, Jatin, others): test Medlyn stomatal, land use, land cover change, LUCID, LUMIP, LS3MIP – impact of nutrients
  • Uni Melb (Alex): plans for coupling fluorescence model to CABLE for estimating GPP globally, data assimilation work
  • CSIRO L&W: hydrology with dynamic LAI

2. Clarifying which versions different people are using and what capability different applications need.

  • Vanessa: d9c9b5b7d1897c3bbb8d7e6990abb2466cef95ba – branch consolidating SLI, POP and YPW’s branch
  • ESM: CABLE2.2.3
  • YPW: similar to d9c9b5b7d1897c3bbb8d7e6990abb2466cef95ba, close to Bernards, used for data assimilation, removed hard-wired parameters
  • Bernard: includes more of trunk updates, carbon pool outputs written to CABLE restart netcdf file
  • Chris and YPW: shared branch with landuse change code in
  • Mark: GSWP3 forcing, 0.5 deg, 3 hourly (I/O changes, with flag) – priority to ticket and add to trunk (Mark and Jhan)

[ Aside: Mark’s hydrology – runs in AMIP style ACCESS, testing in fully coupled model required, impact on carbon to be assessed.]

a. Is a consolidated version required?

b. What capability needs to be in the CABLE trunk?

  • These questions to be addressed at another time

c. Input/Output needs?

Netcdf input/output CASA – Bernard and Vanessa/Peter/Lars to look at I/O and merging if useful

d. Identifying parameter files for different applications.

  • Important to do but not now. Also need to consider recommended switches for different applications. Potential link with restructuring of repository to provide example cases.

e. Ticketing a process to work towards a consolidated version.

  • Please ticket any potential changes being worked on so that we can anticipate inclusion in the trunk and interaction with other work

3. What issues have emerged when using different versions/applications?

  • Negative NPP related size of woody biomass – proposing to use sap wood (from POP) – need to implement for nitrogen, phosphorus – or respiration could use a sap wood/total wood ratio (ratio from POP?) - *** perhaps Vanessa to provide more details on what she has done and what fix might be useful in cases when POP not being used ***
  • Carbon conservation – negative NPP, not enough moisture, carbon pools go to zero, fixed minimum LAI, incompatibility – linked to hydrology – offline has CABLE dying back too fast - YPW commented on possible contribution from not being well enough spun up - need less sensitivity to low moisture and internally consistent behaviour if/when carbon pools deplete to zero.
  • Low leaf areas in deciduous forests - Vanessa to add information about solution (turnover sensitivity to phenology)

4. What solutions do we already have or need to find for any of these issues e.g. to ensure carbon conservation?

  • see above with issues

5. Spin-up and equilibration, with and without nutrient limitation.

a. Can we define a recommended process?

  • Document available – make into a wiki page (YPW). Requires multi processor version.
  • Problems if spin-up doesn’t get you to consistency with obs.
  • Provision of pre spun up files e.g. suitable for different met forcing datasets? Shared restart files. History file of pool sizes. Spin-up done for GSWP2, Trendy, still need to do GSWP3. (Bernard to coordinate)

b. Can offline spin-up be useful for online applications?

  • High priority. To be sorted out by Aspendale.

c. How do we spin-up most efficiently?

  • Monthly time-step – accelerated spin-up should be equivalent to doing this.
Clone this wiki locally