Changes between Version 2 and Version 3 of ticket/0650

Timestamp:

2010-09-27T14:17:45+02:00 (14 years ago)

Author:

cbricaud

Comment:

--

ticket/0650

@@ -35 +35 @@
 
 === Bit Comparability ===
-||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES/NO !'''||
-||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES/NO!'''||
-||Is this change expected to preserve answers in all possible model configurations?||!'''YES/NO!'''||
-||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES/NO!'''||
+||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''NO !'''||
+||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''NO!'''||
+||Is this change expected to preserve answers in all possible model configurations?||!'''NO!'''||
+||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''NO!'''||
 
-If you answered !'''NO!''' to any of the above, please provide further details:
-
- * Which routine(s) are causing the difference?
- * Why the changes are not protected by a logical switch or new section-version
- * 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.
- * What do you expect to see occur in the test harness jobs?
- * Which diagnostics have you altered and why have they changed?Please add details here........
+Same answer as above.
 
 ----
 === System Changes ===
-||Does your change alter namelists?||!'''YES/NO !'''||
-||Does your change require a change in compiler options?||!'''YES/NO !'''||
+||Does your change alter namelists?||!'''YES !'''||
+||Does your change require a change in compiler options?||!'''NO !'''||
 
-If any of these apply, please document the changes required here.......
+Now dtatem and dtasal have their namelist:
+
+!-----------------------------------------------------------------------
+
+&namdta_tem    !   surface boundary condition : sea surface restoring
+
+!-----------------------------------------------------------------------
+
+!              !     file name                  ! frequency (hours) ! variable   ! time interpol. !  clim   !'yearly' or ! weights  ! rotation !
+
+!              !                                !  (if <0  months)  !   name     !    (logical)   !  (T/F)  ! 'monthly'  ! filename ! pairing  !
+
+  sn_tem       = 'data_1m_potential_temperature_nomask',  -1        , 'votemper' ,     .true.     , .true.  , 'yearly'   , ' '      , ' '
+
+!
+
+  cn_dir       = './'      !  root directory for the location of the runoff files
+
+/
+
+!-----------------------------------------------------------------------
+
+&namdta_sal    !   surface boundary condition : sea surface restoring
+
+!-----------------------------------------------------------------------
+
+!              !     file name                  ! frequency (hours) ! variable   ! time interpol. !  clim   ! 'yearly' or ! weights  ! rotation !
+
+!              !                                !  (if <0  months)  !   name     !    (logical)   !  (T/F)  !  'monthly'  ! filename ! pairing  !
+
+   sn_sal      =  'data_1m_salinity_nomask'     ,         -1        , 'vosaline' ,     .true.     , .true.  , 'yearly'    , ''       , ' '
+
+!
+
+   cn_dir      = './'      !  root directory for the location of the runoff files
+
+/
+
 
 ----