Changes between Version 8 and Version 9 of ticket/0937


Ignore:
Timestamp:
2012-10-25T14:22:33+02:00 (8 years ago)
Author:
cbricaud
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0937

    v8 v9  
    2323Testing could consider (where appropriate) other configurations in addition to NVTK]. 
    2424 
    25 || NVTK Tested || !'''YES!''' || 
    26 || Other model configurations || !'''NO!''' || 
     25|| NVTK Tested || YES || 
     26|| Other model configurations || NO || 
    2727|| Processor configurations tested || [ sette layouts ] || 
    28 || 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 || !'''NO!''' || 
     28|| 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 || NO || 
    2929 
    30 (Answering UNSURE is likely to generate further questions from reviewers.) 
    31  
    32 'Please add further summary details here' 
    33  
    34  * Processor configurations tested 
    35  * etc---- 
     30Apart from NVTK tests, developments have been checked with AMM12 configuration with a 8 x 4 processor layout. 
    3631 
    3732=== Bit Comparability === 
    3833|| Does this change preserve answers in your tested standard configurations (to the last bit) ? || NO || 
    39 || Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended) || !'''YES!''' || 
    40 || Is this change expected to preserve answers in all possible model configurations? || !'''NO!''' || 
    41 || Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !'' || !'''NO!''' || 
     34|| Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended) || YES || 
     35|| Is this change expected to preserve answers in all possible model configurations? || NO || 
     36|| Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !'' || NO || 
    4237 
    4338__If key_bdy and key_tide are not activated, modifications do not change either answers or results of standard configurations__. Thus results changes only concern AMM12 standard configuration. These changes only come from the completely different tidal module implemented. Thus, there are not induced by the modifications of bdy package alone as long as the same options are used. Keeping new and previous tidal modules would have make the code and namelist interface much heavier so that we preferred to keep the new one. 
     
    4540Note that some issues with overlapping analytical segments have been fixed in bdy package. It is now possible to obtain identical results with user defined "analytical" open boundary segments bounding the domain (ie identical to the case where a single unstructured segment is read from a netcdf file). As a consequence, diagnostics in AMM12 change although no change in the diagnostics themselves has been introduced. 
    4641 
    47 If you answered !'''NO!''' to any of the above, please provide further details: 
    48  
    49  * Which routine(s) are causing the difference? 
    50  * Why the changes are not protected by a logical switch or new section-version 
    51  * 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. 
    52  * What do you expect to see occur in the test harness jobs? 
    53  * Which diagnostics have you altered and why have they changed?Please add details here........ 
    54  
    5542---- 
    5643=== System Changes === 
    57 || Does your change alter namelists? || !'''YES!''' || 
    58 || Does your change require a change in compiler options? || !'''NO!''' || 
     44|| Does your change alter namelists? || YES || 
     45|| Does your change require a change in compiler options? || NO || 
    5946 
    60  * namelist changes: 
     47 * '''namelist changes:''' 
    6148   * nam_tide: Simplifications in the definition of tidal waves. Add a flag and time_scale to activate linear ramping of tidal motions. 
    6249   * nambdy_tide: Add a new option to read tidal boundary data from 2d file given on data domain. 
     
    6451   * nambdy_index: Simplify definition of analytical segments. 
    6552   * namsbc_apr: Flag to add inverse barometer at open boundaries. Options to set reference pressure to a constant value or to the domain average. 
    66  * About compiler options: Code update does not require any change in compiler options. Yet, we noticed that results are not reproductible unless the lowest level of optimization is used. 
     53 * '''About compiler options:''' Code update does not require any change in compiler options. Yet, we noticed that results are not reproductible unless the lowest level of optimization is used. 
    6754 
    6855----