Changes between Initial Version and Version 1 of ticket/0993


Ignore:
Timestamp:
2012-10-15T18:07:18+02:00 (8 years ago)
Author:
rfurner
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0993

    v1 v1  
     1[[PageOutline]] 
     2Last edited [[Timestamp]] 
     3 
     4[[BR]] 
     5 
     6'''Author''' : Rachel Furner  
     7 
     8'''ticket''' : #993 
     9 
     10'''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2012/dev_r3452_UKMO2_DIADCT ]  
     11---- 
     12 
     13=== Description === 
     14Currently the code used to calculate flow through transects sums all positive and negative components over each time step. For a tidal model this does not allow useful diagnostics for the separate flow components, and so instead it is suggested that the flow is summed over the relevant number of time steps at each grid box, and then the positive and negative components are separately summed over space. 
     15 
     16---- 
     17=== Testing === 
     18Testing could consider (where appropriate) other configurations in addition to NVTK]. 
     19 
     20||NVTK Tested||!'''NO!'''|| 
     21||Other model configurations||!'''NO!'''|| 
     22||Processor configurations tested||4x8|| 
     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||!'''NA!'''|| 
     24 
     25(Answering UNSURE is likely to generate further questions from reviewers.) 
     26 
     27'Please add further summary details here' 
     28 
     29The code has been tested to ensure the total transport results are the same as previously.  The code changes are limited to diadct, and so is key controlled.  General aspects of the diadct code where tested when this module was first implemented and as such have been skipped for this work. 
     30 
     31 * Processor configurations tested 
     32 * etc---- 
     33 
     34=== Bit Comparability === 
     35||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES !'''|| 
     36||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!''''''|| 
     37||Is this change expected to preserve answers in all possible model configurations?||!''''''|| 
     38||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''NO!'''|| 
     39 
     40If you answered !'''NO!''' to any of the above, please provide further details: 
     41 
     42 * Which routine(s) are causing the difference? 
     43 * Why the changes are not protected by a logical switch or new section-version 
     44 * 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. 
     45 * What do you expect to see occur in the test harness jobs? 
     46 * Which diagnostics have you altered and why have they changed?Please add details here........ 
     47 
     48 
     49Total flow rates given by diadct are the same, however positive and negative components are now dramatically different, so as to provide a more useful diagnostic for tidal models.  The change is not namelist or key protected as it not thought likely that anyone requires the previous method to be used. 
     50---- 
     51=== System Changes === 
     52||Does your change alter namelists?||!'''NO !'''|| 
     53||Does your change require a change in compiler options?||!'''NO !'''|| 
     54 
     55If any of these apply, please document the changes required here....... 
     56 
     57---- 
     58=== Resources === 
     59!''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' 
     60 
     61---- 
     62=== IPR issues === 
     63||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES'''|| 
     64 
     65If No: 
     66 
     67 * Identify the collaboration agreement details 
     68 * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required..........