Changes between Initial Version and Version 1 of ticket/1344


Ignore:
Timestamp:
2014-06-17T18:12:33+02:00 (6 years ago)
Author:
hadcv
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/1344

    v1 v1  
     1[[PageOutline]] 
     2Last edited [[Timestamp]] 
     3 
     4[[BR]] 
     5 
     6'''Author''' : Daley Calvert 
     7 
     8'''ticket''' : #1344 
     9 
     10'''Branch''' : TO_BE_FILLED_IN  
     11---- 
     12 
     13=== Description === 
     14 
     15Some additional enhancements to the C1D configuration. 
     16 
     17* Add prescribed vertical velocity 
     18* Add option to more specifically define column (based on grid information instead of zoom) 
     19* Add case study framework to C1D namelist (incorporating #1152)  
     20 
     21... 
     22 
     23---- 
     24=== Testing === 
     25Testing could consider (where appropriate) other configurations in addition to NVTK]. 
     26 
     27||NVTK Tested||!'''YES/NO!'''|| 
     28||Other model configurations||!'''YES/NO!'''|| 
     29||Processor configurations tested||[ Enter processor configs tested here ]|| 
     30||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!'''|| 
     31 
     32(Answering UNSURE is likely to generate further questions from reviewers.) 
     33 
     34'Please add further summary details here' 
     35 
     36 * Processor configurations tested 
     37 * etc---- 
     38 
     39=== Bit Comparability === 
     40||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES/NO !'''|| 
     41||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES/NO!'''|| 
     42||Is this change expected to preserve answers in all possible model configurations?||!'''YES/NO!'''|| 
     43||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES/NO!'''|| 
     44 
     45If you answered !'''NO!''' to any of the above, please provide further details: 
     46 
     47 * Which routine(s) are causing the difference? 
     48 * Why the changes are not protected by a logical switch or new section-version 
     49 * 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. 
     50 * What do you expect to see occur in the test harness jobs? 
     51 * Which diagnostics have you altered and why have they changed?Please add details here........ 
     52 
     53---- 
     54=== System Changes === 
     55||Does your change alter namelists?||!'''YES/NO !'''|| 
     56||Does your change require a change in compiler options?||!'''YES/NO !'''|| 
     57 
     58If any of these apply, please document the changes required here....... 
     59 
     60---- 
     61=== Resources === 
     62!''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' 
     63 
     64---- 
     65=== IPR issues === 
     66||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES/ NO !'''|| 
     67 
     68If No: 
     69 
     70 * Identify the collaboration agreement details 
     71 * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required..........