| 1 | Last edited [[Timestamp]] |
| 2 | |
| 3 | [[PageOutline]] |
| 4 | |
| 5 | === Author === |
| 6 | Clement BRICAUD |
| 7 | |
| 8 | ---- |
| 9 | === Branch === |
| 10 | DEV_r1784_3DF |
| 11 | ---- |
| 12 | |
| 13 | === Description === |
| 14 | Read 3D files like Levitus with fldread routine. |
| 15 | fnow becomes a 3D array and fdta a 4D array. |
| 16 | |
| 17 | ---- |
| 18 | === Testing === |
| 19 | Testing could consider (where appropriate) other configurations in addition to NVTK]. |
| 20 | |
| 21 | ||NVTK Tested||YES|| |
| 22 | ||Other model configurations||YES|| |
| 23 | ||Processor configurations tested|| 2*4*8 || |
| 24 | ||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||NA|| |
| 25 | |
| 26 | *Now, dtasal and dtatem routines are doing the temporal interpolation with fldread routine, instead using temporal interpolation that is at the end of them. |
| 27 | It is not exactly the same formulation. but the temporal interpolation of fldread is better. |
| 28 | |
| 29 | 'Please add further summary details here' |
| 30 | |
| 31 | *It is working on all Mercator's configuration (ATL12, ORCA025_LIM, ORCA12_LIM), on some differents computers (IBM, NEC ). |
| 32 | |
| 33 | |
| 34 | === Bit Comparability === |
| 35 | ||Does this change preserve answers in your tested standard configurations (to the last bit) ?||NO|| |
| 36 | ||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES/NO!'''|| |
| 37 | ||Is this change expected to preserve answers in all possible model configurations?||NO|| |
| 38 | ||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||NO|| |
| 39 | |
| 40 | If you answered !'''NO!''' to any of the above, please provide further details: |
| 41 | |
| 42 | * Which routine(s) are causing the difference? |
| 43 | Now, dtasal and dtatem routines are doing the temporal interpolation with fldread routine |
| 44 | * Why the changes are not protected by a logical switch or new section-version? |
| 45 | Because it is a new way for temporal interpolation of Levitus |
| 46 | * 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. |
| 47 | It is not possible for the same reson as above. |
| 48 | * What do you expect to see occur in the test harness jobs? |
| 49 | * Which diagnostics have you altered and why have they changed?Please add details here........ |
| 50 | |
| 51 | ---- |
| 52 | === System Changes === |
| 53 | ||Does your change alter namelists?||YES|| |
| 54 | ||Does your change require a change in compiler options?||NO|| |
| 55 | |
| 56 | We have to use the same namelist bloc as bulk formulations for dtatem and dtasal |
| 57 | |
| 58 | ---- |
| 59 | === Resources === |
| 60 | !''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' |
| 61 | |
| 62 | ---- |
| 63 | === IPR issues === |
| 64 | ||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES/ NO !'''|| |
| 65 | |
| 66 | If No: |
| 67 | |
| 68 | * Identify the collaboration agreement details |
| 69 | * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required.......... |