Agenda of the developments

Description of the development Agenda for 2015 : Agenda development of CMIP6

The agenda propose a set of Actions by little groups to be done before 2015 for merging into the TRUNC all developments that are needed to perform CMIP6 v1 (and also the Very low resolution case focussing on Chemistry)

Note that we agreed that CMIP6 will be done only with the TRUNC so that we need to merge all developments into the TRUNC

For each "merging Dev tasks" few informations are also provided in the attached pdf

Any remarks, progresses about each task should be reported in the section below

Progresses and comments

To be updated when questions appear or when developments are done

• ??

Working Groups

Developement of the physical component for CMIP6-V1

See specific page of the Agenda and progresses under Physic for CMIP6?

Developement of the Biogeochemical component for CMIP6-V1

See specific page of the Agenda and progresses under Biogeochemistry for CMIP6

Improvement of Land-cover management (LCC) for CMIP6-V1

See specific page of the Agenda and progresses under LandCoverChanges for CMIP6

NOTES on the Functionning of the group to reach CMIP6 objectives =

We discussed a lot on the best way to integrate existing developements and how to agree accross the ORCHIDEE group. The following points emerged:

• We need first to define a "set of minimum criteria" to commit a new developement in the TRUNC: Conservation of Energy, Water and Carbon (to a reasonable order); suitability for parrallelisation, and appropriate documentation. Check / Implementation of the conservation diagnostics should be done as soon as possible.

• Each time a new model developement is proposed to the TRUNC, it needs to receive as much as possible the "agreement" of the "WHOLE (or MOST OF)" the ORCHIDEE group! This effort of "education" should not be avoided.

• We should work in parallele in small groups with: clear objectives, a precise roadmap, one person that is responsible (or a binome). Each group should report to the rest of the project team regularly (each month or two).

• We have to benefit as much as possible from the ongoing "faster" branch developement that are following specific scientific objectives (ex: MICT with the IMBALANCE_P and few others projects)