| 1 | | [[PageOutline]] |
| 2 | | Last edited [[Timestamp]] |
| 3 | | |
| 4 | | [[BR]] |
| 5 | | |
| 6 | | '''Author''' : Enda O'Dea |
| 7 | | '''ticket''' : #1319 |
| 8 | | |
| 9 | | '''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2014/dev_r4650_UKMO10_Tidally_Meaned_Diagnostics ] |
| 10 | | ---- |
| 11 | | |
| 12 | | === Description === |
| 13 | | |
| 14 | | |
| 15 | | ---- |
| 16 | | === Testing === |
| 17 | | Testing could consider (where appropriate) other configurations in addition to NVTK]. |
| 18 | | |
| 19 | | ||NVTK Tested||!'''YES/NO!'''|| |
| 20 | | ||Other model configurations||!'''YES/NO!'''|| |
| 21 | | ||Processor configurations tested||[ Enter processor configs tested here ]|| |
| 22 | | ||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!'''|| |
| 23 | | |
| 24 | | (Answering UNSURE is likely to generate further questions from reviewers.) |
| 25 | | |
| 26 | | 'Please add further summary details here' |
| 27 | | |
| 28 | | * Processor configurations tested |
| 29 | | * etc---- |
| 30 | | |
| 31 | | === Bit Comparability === |
| 32 | | ||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES/NO !'''|| |
| 33 | | ||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES/NO!'''|| |
| 34 | | ||Is this change expected to preserve answers in all possible model configurations?||!'''YES/NO!'''|| |
| 35 | | ||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES/NO!'''|| |
| 36 | | |
| 37 | | If you answered !'''NO!''' to any of the above, please provide further details: |
| 38 | | |
| 39 | | * Which routine(s) are causing the difference? |
| 40 | | * Why the changes are not protected by a logical switch or new section-version |
| 41 | | * 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. |
| 42 | | * What do you expect to see occur in the test harness jobs? |
| 43 | | * Which diagnostics have you altered and why have they changed?Please add details here........ |
| 44 | | |
| 45 | | ---- |
| 46 | | === System Changes === |
| 47 | | ||Does your change alter namelists?||!'''YES/NO !'''|| |
| 48 | | ||Does your change require a change in compiler options?||!'''YES/NO !'''|| |
| 49 | | |
| 50 | | If any of these apply, please document the changes required here....... |
| 51 | | |
| 52 | | ---- |
| 53 | | === Resources === |
| 54 | | !''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' |
| 55 | | |
| 56 | | ---- |
| 57 | | === IPR issues === |
| 58 | | ||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES/ NO !'''|| |
| 59 | | |
| 60 | | If No: |
| 61 | | |
| 62 | | * Identify the collaboration agreement details |
| 63 | | * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required.......... |
