Changes between Version 2 and Version 3 of ticket/0650
- Timestamp:
- 2010-09-27T14:17:45+02:00 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ticket/0650
v2 v3 35 35 36 36 === Bit Comparability === 37 ||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!''' YES/NO !'''||38 ||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!''' YES/NO!'''||39 ||Is this change expected to preserve answers in all possible model configurations?||!''' YES/NO!'''||40 ||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!''' YES/NO!'''||37 ||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''NO !'''|| 38 ||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''NO!'''|| 39 ||Is this change expected to preserve answers in all possible model configurations?||!'''NO!'''|| 40 ||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''NO!'''|| 41 41 42 If you answered !'''NO!''' to any of the above, please provide further details: 43 44 * Which routine(s) are causing the difference? 45 * Why the changes are not protected by a logical switch or new section-version 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 * What do you expect to see occur in the test harness jobs? 48 * Which diagnostics have you altered and why have they changed?Please add details here........ 42 Same answer as above. 49 43 50 44 ---- 51 45 === System Changes === 52 ||Does your change alter namelists?||!'''YES /NO!'''||53 ||Does your change require a change in compiler options?||!''' YES/NO !'''||46 ||Does your change alter namelists?||!'''YES !'''|| 47 ||Does your change require a change in compiler options?||!'''NO !'''|| 54 48 55 If any of these apply, please document the changes required here....... 49 Now dtatem and dtasal have their namelist: 50 51 !----------------------------------------------------------------------- 52 53 &namdta_tem ! surface boundary condition : sea surface restoring 54 55 !----------------------------------------------------------------------- 56 57 ! ! file name ! frequency (hours) ! variable ! time interpol. ! clim !'yearly' or ! weights ! rotation ! 58 59 ! ! ! (if <0 months) ! name ! (logical) ! (T/F) ! 'monthly' ! filename ! pairing ! 60 61 sn_tem = 'data_1m_potential_temperature_nomask', -1 , 'votemper' , .true. , .true. , 'yearly' , ' ' , ' ' 62 63 ! 64 65 cn_dir = './' ! root directory for the location of the runoff files 66 67 / 68 69 !----------------------------------------------------------------------- 70 71 &namdta_sal ! surface boundary condition : sea surface restoring 72 73 !----------------------------------------------------------------------- 74 75 ! ! file name ! frequency (hours) ! variable ! time interpol. ! clim ! 'yearly' or ! weights ! rotation ! 76 77 ! ! ! (if <0 months) ! name ! (logical) ! (T/F) ! 'monthly' ! filename ! pairing ! 78 79 sn_sal = 'data_1m_salinity_nomask' , -1 , 'vosaline' , .true. , .true. , 'yearly' , '' , ' ' 80 81 ! 82 83 cn_dir = './' ! root directory for the location of the runoff files 84 85 / 86 56 87 57 88 ----