Changes between Version 3 and Version 4 of 2014WP/ticket/1310


Ignore:
Timestamp:
2015-11-10T10:38:03+01:00 (5 years ago)
Author:
djlea
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • 2014WP/ticket/1310

    v3 v4  
    1313=== Description === 
    1414 
    15 NEMO is hard-wired to always start a run at the start of the day (at 0z). I propose to extend the option of setting the start date to allow for the setting of a start hour via a namelist option. 
     15NEMO is hard-wired to always start a run at the start of the day (at 0z). I propose to extend the option of setting the start date to allow for the setting of a start time via a namelist option. 
     16 
     17There was an old ticket which dealt with starting runs at arbitrary times (#1037). It was implemented here by changing the initial time step, but it was never committed to the trunk. The main problem with the approach suggested though was that if you change the length of the time step that would result in a potentially unpredictable change in the start time. The way it is done here by explicitly specifying the start time it is more flexible and controllable. 
     18 
     19The changes to the code are quite minimal and are mainly in the daymod routine. There are a few changes to OBS and ASM to make them aware of the start time. 
    1620 
    1721---- 
    1822=== Testing === 
    19 Testing could consider (where appropriate) other configurations in addition to NVTK]. 
     23Testing could consider (where appropriate) other configurations in addition to SETTE]. 
    2024 
    21 ||NVTK Tested||YES|| 
     25||SETTE Tested||YES|| 
    2226||Other model configurations||ORCA2, AMM12|| 
    2327||Processor configurations tested||All the standard SETTE tests|| 
     
    2933 
    3034 * The code passes all SETTE tests (at r5072 of the trunk) 
    31  * If starthour=0 then results of SETTE test results don’t change 
    32  * AMM12 is restartable with starthour=6 and all write statements indicate that correct forcing files are being read in to the model. AMM12 includes tides and these was the hardest bit to get right (but it now works!) 
    33  
     35 * If start time = 0000 then results of SETTE test results don’t change (this is the default if the start time is not specified) 
     36 * AMM12 is restartable with start time 0600 and all write statements indicate that correct forcing files are being read in to the model. AMM12 includes tides and these was the hardest bit to get right (but it now works!) 
     37 * I've tested the code with runs of less than a day and it is now restartable (this previously wasn't the case and also isn't for the trunk). I also tested this with starthour 1200. 
    3438 
    3539=== Bit Comparability === 
     
    5458If any of these apply, please document the changes required here....... 
    5559 
    56 There is an additional namelist variable nn_time0 in namrun namelist which is used to specify the start hour for the run. 
     60There is an additional namelist variable nn_time0 in namrun namelist which is used to specify the start time in hours and minutes (HHMM) for the run. 
    5761 
    5862----