New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
ticket/1260_CNRS0_NOC1_LDF (diff) – NEMO

Changes between Initial Version and Version 1 of ticket/1260_CNRS0_NOC1_LDF


Ignore:
Timestamp:
2014-03-18T16:23:46+01:00 (10 years ago)
Author:
gm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/1260_CNRS0_NOC1_LDF

    v1 v1  
     1[[PageOutline]] Last edited [[Timestamp]] 
     2 
     3'''Author''' : Gurvan Madec, Florian Lemarié, George Nurser 
     4 
     5'''ticket''' : #1260 
     6 
     7'''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2014/dev_CNRS0_NOC1_LDF 2014/dev_CNRS0_NOC1_LDF] 
     8 
     9'''WP2014 Action''' : [https://forge.ipsl.jussieu.fr/nemo/wiki/2014WP/2014Action_institutions_CNRS CNRS-0] & [https://https://forge.ipsl.jussieu.fr/nemo/wiki/2014WP/NOC NOC-1] 
     10 
     11---- 
     12=== Description === 
     13simplify and improve the lateral diffusion and dissipation in NEMO/OPA  
     14 
     15Simplification: [[BR]]change the way the eddy diffusivity and viscosity are specified and controlled by the user. 
     16 
     17Improvements: [[BR]] (1) introduce Beckers et al. (2000) compact stencil in the cross-isoneutral direction in triads formalism ; [[BR]] (2) introduce in both iso-neutral operator the Method of Stabilizing Correction (Lemarié et al. (2012) ; [[BR]] (3) implement bilaplacian iso-neutral operator (Lemarié et al. (2012) 
     18 
     19---- 
     20=== Testing === 
     21Testing could consider (where appropriate) other configurations in addition to NVTK]. 
     22 
     23|| NVTK Tested || !'''YES/NO!''' || 
     24|| Other model configurations || !'''YES/NO!''' || 
     25|| Processor configurations tested || [ Enter processor configs tested here ] || 
     26|| 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!''' || 
     27 
     28(Answering UNSURE is likely to generate further questions from reviewers.) 
     29 
     30'Please add further summary details here' 
     31 
     32 * Processor configurations tested 
     33 * etc---- 
     34 
     35=== Bit Comparability === 
     36|| Does this change preserve answers in your tested standard configurations (to the last bit) ? || !'''YES/NO !''' || 
     37|| Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended) || !'''YES/NO!''' || 
     38|| Is this change expected to preserve answers in all possible model configurations? || !'''YES/NO!''' || 
     39|| Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !'' || !'''YES/NO!''' || 
     40 
     41If you answered !'''NO!''' to any of the above, please provide further details: 
     42 
     43 * Which routine(s) are causing the difference? 
     44 * Why the changes are not protected by a logical switch or new section-version 
     45 * 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. 
     46 * What do you expect to see occur in the test harness jobs? 
     47 * Which diagnostics have you altered and why have they changed?Please add details here........ 
     48 
     49---- 
     50=== System Changes === 
     51|| Does your change alter namelists? || !'''YES/NO !''' || 
     52|| Does your change require a change in compiler options? || !'''YES/NO !''' || 
     53 
     54If any of these apply, please document the changes required here....... 
     55 
     56---- 
     57=== Resources === 
     58!''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' 
     59 
     60---- 
     61=== IPR issues === 
     62|| Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO? || !'''YES/ NO !''' || 
     63 
     64If No: 
     65 
     66 * Identify the collaboration agreement details 
     67 * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required..........