Changes between Initial Version and Version 1 of ticket/0864


Ignore:
Timestamp:
2011-09-27T16:26:39+02:00 (9 years ago)
Author:
cbricaud
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0864

    v1 v1  
     1[[PageOutline]] 
     2Last edited [[Timestamp]] 
     3 
     4[[BR]] 
     5 
     6'''Author''' : Clement Bricaud <cbricaud@mercator-ocean.fr> 
     7 
     8'''ticket''' : #864 
     9 
     10'''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2011/dev_r2802_MERCATOR10_diadct dev_r2802_MERCATOR10_diadct ]  
     11---- 
     12 
     13=== Description === 
     14Online computing of transport across sections ¶ 
     15 
     16---- 
     17=== Testing === 
     18Testing could consider (where appropriate) other configurations in addition to NVTK]. 
     19 
     20||NVTK Tested||!'''YES!'''|| 
     21||Other model configurations||!'''YES!'''|| 
     22||Processor configurations tested||[ 1*1,2*4,2*8 ]|| 
     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!'''|| 
     24 
     25(Answering UNSURE is likely to generate further questions from reviewers.) 
     26 
     27'Please add further summary details here' 
     28 
     29 Tests done on IBM power 6: 
     30 
     31 * reproductiblity: ORCA2_LIM: compare 2*8 and 4*4 configurations: results are identical ( for 75 time steps, with key_mpp_rep )  
     32 
     33                    GYRE : compare 2*8 and 4*4 configurations: results are identical ( for 60 time steps, with key_mpp_rep ) 
     34 
     35 * restartability: GYRE, with 1*1 configuration: compare 2 consecutives runs of 60 time steps with 1 run of 120 time steps : results are identical  
     36  
     37 
     38=== Bit Comparability === 
     39||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES !'''|| 
     40||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES!'''|| 
     41||Is this change expected to preserve answers in all possible model configurations?||!'''YES!'''|| 
     42||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES!'''|| 
     43 
     44If you answered !'''NO!''' to any of the above, please provide further details: 
     45 
     46 * Which routine(s) are causing the difference? 
     47 * Why the changes are not protected by a logical switch or new section-version 
     48 * 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. 
     49 * What do you expect to see occur in the test harness jobs? 
     50 * Which diagnostics have you altered and why have they changed?Please add details here........ 
     51 
     52---- 
     53=== System Changes === 
     54||Does your change alter namelists?||!'''YES !'''|| 
     55||Does your change require a change in compiler options?||!'''NO !'''|| 
     56 
     57If any of these apply, please document the changes required here....... 
     58add a bloc in namelist:namdct 
     59 
     60---- 
     61=== Resources === 
     62tests done on Dell cluster, 4*4 mpi configuration: 
     631 year of ORCA2_LIM without diadct computing: walltime=15 minutes, mem=1.56 Go 
     641 year of ORCA2_LIM with    diadct computing ( 1 transport computing + writing per day, 132 sections) : walltime=21 minutes, mem=1.52 Go 
     65 
     66---- 
     67=== IPR issues === 
     68||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES !'''|| 
     69 
     70If No: 
     71 
     72 * Identify the collaboration agreement details 
     73 * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required..........