Changes between Initial Version and Version 1 of ticket/0681_OBS_ASM


Ignore:
Timestamp:
2010-06-16T18:58:17+02:00 (10 years ago)
Author:
djlea
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0681_OBS_ASM

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