Changes between Initial Version and Version 1 of ticket/1608_CNRS0_NOC1_ZDF

Timestamp:

2015-10-13T08:16:47+02:00 (9 years ago)

Author:

gm

Comment:

--

ticket/1608_CNRS0_NOC1_ZDF

@@ +1 @@
+[[PageOutline]] Last edited [[Timestamp]]
+
+'''Author''' : Gurvan Madec
+
+'''ticket''' : #1608
+
+'''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2015/dev_r5786_CNRS9_NOC3_LDF 2015/dev_r5786_CNRS9_NOC3_LDF]
+
+'''WP2015 Action''' : CNRS-9 and NOC-3
+
+----
+=== Description ===
+Development branch related to CNRS-9 and NOC-3 actions of 2015 work plan :[[BR]]• ZDF: simplify and improve the vertical physics in NEMO/OPA (remove CPP keys ;remove  avmu & avmv ; reduce the number of lvc_lnk call)[[BR]]• TRP: add in LDF a module computing the effective transport used by both TRA and TRC
+
+Others possible additions:
+
+• remove all remaining hard coded parts specific to a configuration (especially ORCA2)
+
+• vertical scale factors defined systematically in vvl case (no more domzgr_substitute.h90)
+
+• remove most of the remaining CPP keys (key_trabbl, key_zdf...)
+
+....
+
+----
+'''Strategy'''
+
+  ''' I. '''
+
+'''(I.1)''' 
+
+'''(I.2)'''
+
+  ''' [[BR]] [[BR]] II. '''
+
+'''(II.1)'''
+
+'''(II.2) —''' 
+
+'''(II.3)''' — '''Miscellaneous :'''
+
+...
+
+'''Pending issues''' : 
+
+'''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..........