| | 136 | |
| | 137 | Actions |
| | 138 | * Technical: Propose a Module Header (F.M.). |
| | 139 | * Technical: Create a LaTeX file grouping all variables names/symbols used in equations in order to harmonize. If available, add the corresponding CMIP5 name, see [http://forge.ipsl.jussieu.fr/igcmg/wiki/IPSLCM5A/Sorties/EquivalenceIPSLCMIP5]. |
| | 140 | * Organization: Check if attendees need a Mission Order. |
| | 141 | * Organization: Constitute a Review Committee including possibly P. Ciais, G. Krinner, S. Piao, ... (S.L./M.M./P.P.) |
| | 142 | * Organization: Plan a second meeting early in January to ensure the preparation of the retreat is efficient. (F.M.) |
| | 143 | * Communication: A report could be presented at the end of the retreat to some VIPs (IPSL, LSCE, LMD). (P.P.) |
| | 144 | |
| | 145 | What P. Peylin would like all of contributors to remember: |
| | 146 | * Better more than less. |
| | 147 | * Equations are very useful. |
| | 148 | * A flowchart is mandatory for all large subroutines. |
| | 149 | * DO NOT MODIFY THE CODE (only comments), but do not hesitate to do suggestions maybe in a separate file if you think about changing some variables names, modifying the structure to be more efficient (do/enddo, if/endif, ...), remove some obsolete code, ... |
| | 150 | |
