Changes between Initial Version and Version 1 of ticket/0994

2012-10-19T12:19:24+02:00 (8 years ago)


  • ticket/0994

    v1 v1  
     2Last edited [[Timestamp]] 
     6'''Author''' : Rachel Furner 
     8'''ticket''' : #994 
     10'''Branch''' : [      BRANCH_NAME ]  
     13=== Description === 
     15Currently it is only possibly to specify a regular interval at which to output restart files.  Instead the code will be amended to allow specification of an array of restart times, with the code defaulting to the original method of regular intervals if only one entry is given in the array. 
     18=== Testing === 
     19Testing could consider (where appropriate) other configurations in addition to NVTK]. 
     21||NVTK Tested||!'''YES/NO!'''|| 
     22||Other model configurations||!'''YES/NO!'''|| 
     23||Processor configurations tested||[ Enter processor configs tested here ]|| 
     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||!'''YES/NO/NA!'''|| 
     26(Answering UNSURE is likely to generate further questions from reviewers.) 
     28'Please add further summary details here' 
     30 * Processor configurations tested 
     31 * etc---- 
     33=== Bit Comparability === 
     34||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES/NO !'''|| 
     35||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES/NO!'''|| 
     36||Is this change expected to preserve answers in all possible model configurations?||!'''YES/NO!'''|| 
     37||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES/NO!'''|| 
     39If you answered !'''NO!''' to any of the above, please provide further details: 
     41 * Which routine(s) are causing the difference? 
     42 * Why the changes are not protected by a logical switch or new section-version 
     43 * 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. 
     44 * What do you expect to see occur in the test harness jobs? 
     45 * Which diagnostics have you altered and why have they changed?Please add details here........ 
     48=== System Changes === 
     49||Does your change alter namelists?||!'''YES/NO !'''|| 
     50||Does your change require a change in compiler options?||!'''YES/NO !'''|| 
     52If any of these apply, please document the changes required here....... 
     55=== Resources === 
     56!''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' 
     59=== IPR issues === 
     60||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES/ NO !'''|| 
     62If No: 
     64 * Identify the collaboration agreement details 
     65 * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required..........