New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
ticket/0846 (diff) – NEMO

Changes between Version 12 and Version 13 of ticket/0846


Ignore:
Timestamp:
2011-09-27T12:40:09+02:00 (13 years ago)
Author:
vichi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0846

    v12 v13  
    398398---- 
    399399=== Testing === 
    400 Testing could consider (where appropriate) other configurations in addition to NVTK]. 
    401  
    402 ||NVTK Tested||!'''YES/NO!'''|| 
    403 ||Other model configurations||!'''YES/NO!'''|| 
    404 ||Processor configurations tested||[ Enter processor configs tested here ]|| 
    405 ||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!'''|| 
    406  
    407 (Answering UNSURE is likely to generate further questions from reviewers.) 
    408  
    409 'Please add further summary details here' 
    410  
    411  * Processor configurations tested 
    412  * etc---- 
    413  
    414 === Bit Comparability === 
    415 ||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES/NO !'''|| 
    416 ||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES/NO!'''|| 
    417 ||Is this change expected to preserve answers in all possible model configurations?||!'''YES/NO!'''|| 
    418 ||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES/NO!'''|| 
    419  
    420 If you answered !'''NO!''' to any of the above, please provide further details: 
    421  
    422  * Which routine(s) are causing the difference? 
    423  * Why the changes are not protected by a logical switch or new section-version 
    424  * 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. 
    425  * What do you expect to see occur in the test harness jobs? 
    426  * Which diagnostics have you altered and why have they changed?Please add details here........ 
     400 
    427401 
    428402---- 
    429403=== System Changes === 
    430 ||Does your change alter namelists?||!'''YES/NO !'''|| 
    431 ||Does your change require a change in compiler options?||!'''YES/NO !'''|| 
    432  
    433 If any of these apply, please document the changes required here....... 
    434404 
    435405---- 
    436406=== Resources === 
    437 !''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' 
     407 
    438408 
    439409---- 
    440410=== IPR issues === 
    441 ||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!''' NO !'''|| 
    442  
     411||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!''' YES !'''|| 
     412