[[PageOutline]] Last edited [[Timestamp]] '''Author''' : Fabien Roquet , Gurvan Madec '''ticket''' : #1294 '''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2014/dev_CNRS1_10_TEOS10_Ediag dev_CNRS1_10_TEOS10_Ediag] ---- === Description === Development branch related to CNRS-10 and NOC-10 action of 2014 work plan: * CNRS-1 : add Boussinesq TEOS10 ; add a simplified EOS ; improve the UNESCO 80 EOS ; correct the npc algorithm (see #1350) * CNRS-10 : complete the trends diagnostics (3D trends of tracers, momentum, kinetic energy and potential energy) ; manage the trends output (using xIOS) ---- === Changes === '''revision [https://forge.ipsl.jussieu.fr/nemo/log/branches/2014/dev_CNRS1_10_TEOS10_Ediag?rev=4615 4615] ''' contains the following changes (validated with GYRE only): * introduction of TEOS-10, EOS-80, and S_EOS * introduction of a fully re-design trend diagnostics (directory TRD) and the associated call in TRA and DYN modules '''revision [https://forge.ipsl.jussieu.fr/nemo/log/branches/2014/dev_CNRS1_10_TEOS10_Ediag?rev=4680 4680] '''contains the following changes (validated with ORCA2-LIM2 and ORCA1-LIM2): * new version of tranpc.F90 (see #1350) * small bug correction (use of eos_fzp) '''remaining to do :''' * conversion from Conservative temperature (CT) to potential temperature (PT) to be done on averaged temperature ssm_sst, not at each time step of the averaging procedure * ln_useCT is a misleading namelist parameter, force a hard coding of its value depending on the dos chosen * in forced mode in blk formula, use the CT to compute heat content of evaporation, not PT * ... * test with SETE (especially restartability and reproducibility ) ---- === Testing === Testing could consider (where appropriate) other configurations in addition to NVTK]. || NVTK Tested || !'''YES/NO!''' || || Other model configurations || !'''YES/NO!''' || || Processor configurations tested || [ Enter processor configs tested here ] || || If adding new functionality please confirm that the [[BR]]New code doesn't change results when it is switched off [[BR]]and !''works!'' when switched on || !'''YES/NO/NA!''' || (Answering UNSURE is likely to generate further questions from reviewers.) 'Please add further summary details here' * Processor configurations tested * etc---- === Bit Comparability === || Does this change preserve answers in your tested standard configurations (to the last bit) ? || !'''YES/NO !''' || || Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended) || !'''YES/NO!''' || || Is this change expected to preserve answers in all possible model configurations? || !'''YES/NO!''' || || Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !'' || !'''YES/NO!''' || If you answered !'''NO!''' to any of the above, please provide further details: * Which routine(s) are causing the difference? * Why the changes are not protected by a logical switch or new section-version * What is needed to achieve regression with the previous model release (e.g. a regression branch, hand-edits etc). If this is not possible, explain why not. * What do you expect to see occur in the test harness jobs? * Which diagnostics have you altered and why have they changed?Please add details here........ ---- === System Changes === || Does your change alter namelists? || !'''YES/NO !''' || || Does your change require a change in compiler options? || !'''YES/NO !''' || If any of these apply, please document the changes required here....... ---- === Resources === !''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' ---- === IPR issues === || Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO? || !'''YES/ NO !''' || If No: * Identify the collaboration agreement details * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required..........