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/0850 (diff) – NEMO

Changes between Initial Version and Version 1 of ticket/0850


Ignore:
Timestamp:
2011-07-20T12:46:54+02:00 (13 years ago)
Author:
vichi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0850

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