19 | | * ONLY 1 routine for computing bulk transfer coefficients: TURB_CORE_2Z now handles both cases zt=zu and zt/=zu [[BR]]=> removed routine TURB_CORE_1Z |
20 | | * ONLY one call to TURB_CORE_2Z |
21 | | * improved and slightly optimized TURB_CORE_2Z by decreasing the number of 2D allocated arrays and number of operations |
22 | | * better first guess of stability by checking air-sea difference of virtual temperature rather than temperature difference only... |
23 | | * added function "cd_neutral_10m" that uses the improved parametrization of Large & Yeager 2008, including the drag coefficient reduction for Cyclone conditions (i.e. V10m >= 33m/s). |
| 19 | * ONLY 1 routine for computing bulk transfer coefficients: TURB_CORE_2Z now handles both cases zt=zu and zt/=zu [[BR]]=> removed routine TURB_CORE_1Z |
| 20 | * ONLY one call to TURB_CORE_2Z |
| 21 | * improved and slightly optimized TURB_CORE_2Z by decreasing the number of 2D allocated arrays and number of operations |
| 22 | * better first guess of stability by checking air-sea difference of virtual temperature rather than temperature difference only... |
| 23 | * added function "cd_neutral_10m" that uses the improved parametrization of Large & Yeager 2008, including the drag coefficient reduction for Cyclone conditions (i.e. V10m >= 33m/s). |
25 | | The new sbcblk_core.F90 has been tested in both ORCA2_LIM2 and ORCA1_LIM2. Not significant changes have been found (but obviously for analytical tropical cyclones). |
| 25 | ---- |
| 26 | === Changes === |
| 27 | code : new version of the sbcblk_core.F90 module |
| 28 | |
| 29 | namelist : suppression of "ln_2m" and "ln_bulk2z" in the namsbc_core |
| 30 | |
| 31 | ---- |
| 32 | === Testing === |
| 33 | The new sbcblk_core.F90 has been tested in both '''ORCA2_LIM2''' and '''ORCA1_LIM2'''. Not significant changes have been found (but obviously for analytical tropical cyclones). |
| 34 | |
| 35 | || NVTK Tested || !'''YES/NO!''' || |
| 36 | || Other model configurations || !'''YES/NO!''' || |
| 37 | || Processor configurations tested || [ Enter processor configs tested here ] || |
| 38 | || 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!''' || |
| 39 | |
| 40 | (Answering UNSURE is likely to generate further questions from reviewers.) |
| 41 | |
| 42 | 'Please add further summary details here' |
| 43 | |
| 44 | * Processor configurations tested |
| 45 | * etc---- |
| 46 | |
| 47 | === Bit Comparability === |
| 48 | || Does this change preserve answers in your tested standard configurations (to the last bit) ? || !'''YES/NO !''' || |
| 49 | || Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended) || !'''YES/NO!''' || |
| 50 | || Is this change expected to preserve answers in all possible model configurations? || !'''YES/NO!''' || |
| 51 | || Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !'' || !'''YES/NO!''' || |
| 52 | |
| 53 | If you answered !'''NO!''' to any of the above, please provide further details: |
| 54 | |
| 55 | * Which routine(s) are causing the difference? |
| 56 | * Why the changes are not protected by a logical switch or new section-version |
| 57 | * 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. |
| 58 | * What do you expect to see occur in the test harness jobs? |
| 59 | * Which diagnostics have you altered and why have they changed?Please add details here........ |
| 60 | |
| 61 | ---- |
| 62 | === System Changes === |
| 63 | || Does your change alter namelists? || !'''YES/NO !''' || |
| 64 | || Does your change require a change in compiler options? || !'''YES/NO !''' || |
| 65 | |
| 66 | If any of these apply, please document the changes required here....... |
| 67 | |
| 68 | ---- |
| 69 | === Resources === |
| 70 | !''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' |
| 71 | |
| 72 | ---- |
| 73 | === IPR issues === |
| 74 | || Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO? || !'''YES/ NO !''' || |
| 75 | |
| 76 | If No: |
| 77 | |
| 78 | * Identify the collaboration agreement details |
| 79 | * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required.......... |