| 1 | [[PageOutline]] |
| 2 | Last edited [[Timestamp]] |
| 3 | |
| 4 | [[BR]] |
| 5 | |
| 6 | '''Author''' : acc (on behalf of agn) |
| 7 | |
| 8 | '''ticket''' : #680 |
| 9 | |
| 10 | '''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/DEV_r1924_nocs_latphys DEV_r1924_nocs_latphys] |
| 11 | ---- |
| 12 | |
| 13 | === Description === |
| 14 | This branch will contain the latest version of |
| 15 | Griffies's implementation of the Gent and McWilliams eddy transport as a skew flux. This has the advantage that its numerical discretization can be written in terms of contributions from quarter cells – ‘triads’. This gives a tighter stencil, disallowing 2-gridpoint numerical noise that is permitted by the advective discretization. |
| 16 | A working prototype code for the iso-neutral and skew-flux operator was carefully reviewed in 2009. Considerable care has been taken in the formulation to ensure the tensorial representation is consistent with the variable volume layers (s-coordinate/z* representation). This has been documented and will be provided with the release.[[BR]] |
| 17 | |
| 18 | |
| 19 | '''Method'''[[BR]] |
| 20 | |
| 21 | (1) Discretise Isopycnal diffusion in terms of these triads. This will obviate the need to smooth isopycnal slopes horizontally with a Shapiro filter (as currently implemented in NEMO), or to apply a background horizontal diffusivity that mixes diapycnally.[[BR]] |
| 22 | |
| 23 | (2) Implement Visbeck et al.'s formulation of spatially varying diffusivities as an alternative to the current formulation based on the Held and Larichev timescale and the Rossby radius as a lengthscale (done).[[BR]] |
| 24 | |
| 25 | (3) Add a slope limiting algorithm (mixed-layer depth is sensitive to the slope limiting that is employed) that behaves satisfactorily within and immediately below the mixed layer.[[BR]] |
| 26 | |
| 27 | (4) Implementation in the trunk+ NVTK + documentation[[BR]] |
| 28 | |
| 29 | |
| 30 | ---- |
| 31 | === Testing === |
| 32 | Testing could consider (where appropriate) other configurations in addition to NVTK]. |
| 33 | |
| 34 | ||NVTK Tested||!'''YES/NO!'''|| |
| 35 | ||Other model configurations||!'''YES/NO!'''|| |
| 36 | ||Processor configurations tested||[ Enter processor configs tested here ]|| |
| 37 | ||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!'''|| |
| 38 | |
| 39 | (Answering UNSURE is likely to generate further questions from reviewers.) |
| 40 | |
| 41 | 'Please add further summary details here' |
| 42 | |
| 43 | * Processor configurations tested |
| 44 | * etc---- |
| 45 | |
| 46 | === Bit Comparability === |
| 47 | ||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES/NO !'''|| |
| 48 | ||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES/NO!'''|| |
| 49 | ||Is this change expected to preserve answers in all possible model configurations?||!'''YES/NO!'''|| |
| 50 | ||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES/NO!'''|| |
| 51 | |
| 52 | If you answered !'''NO!''' to any of the above, please provide further details: |
| 53 | |
| 54 | * Which routine(s) are causing the difference? |
| 55 | * Why the changes are not protected by a logical switch or new section-version |
| 56 | * 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. |
| 57 | * What do you expect to see occur in the test harness jobs? |
| 58 | * Which diagnostics have you altered and why have they changed?Please add details here........ |
| 59 | |
| 60 | ---- |
| 61 | === System Changes === |
| 62 | ||Does your change alter namelists?||!'''YES/NO !'''|| |
| 63 | ||Does your change require a change in compiler options?||!'''YES/NO !'''|| |
| 64 | |
| 65 | If any of these apply, please document the changes required here....... |
| 66 | |
| 67 | ---- |
| 68 | === Resources === |
| 69 | !''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' |
| 70 | |
| 71 | ---- |
| 72 | === IPR issues === |
| 73 | ||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES/ NO !'''|| |
| 74 | |
| 75 | If No: |
| 76 | |
| 77 | * Identify the collaboration agreement details |
| 78 | * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required.......... |