Changes between Initial Version and Version 1 of ticket/1428

2015-01-07T11:24:39+01:00 (6 years ago)


  • ticket/1428

    v1 v1  
     2Last edited [[Timestamp]] 
     6'''Author''' : Tim Graham  
     8'''ticket''' : #1428 
     10'''Branch''' : [      BRANCH_NAME ]  
     13=== Description === 
     14Updates to the CICE interface are required for use in coupled models. Currently these are contained in branches for use in Met Office models but should be added to the trunk ahead of the final v3.6_STABLE release. 
     16The changes are: 
     171) Salinity dependent freezing temperature 
     182) Changes to coupling code for multi category sea ice in CICE 
     193) Changes to coupling code for meltponds in CICE 
     21Reviewer: Andrew Coward 
     24=== Testing === 
     25Testing will include all standard SETTE tests (which should be unchanged) as well as testing in the coupled model. 
     27Testing could consider (where appropriate) other configurations in addition to NVTK]. 
     29||NVTK Tested||!'''YES/NO!'''|| 
     30||Other model configurations||!'''YES/NO!'''|| 
     31||Processor configurations tested||[ Enter processor configs tested here ]|| 
     32||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!'''|| 
     34(Answering UNSURE is likely to generate further questions from reviewers.) 
     36'Please add further summary details here' 
     38 * Processor configurations tested 
     39 * etc---- 
     41=== Bit Comparability === 
     42||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES/NO !'''|| 
     43||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES/NO!'''|| 
     44||Is this change expected to preserve answers in all possible model configurations?||!'''YES/NO!'''|| 
     45||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''YES/NO!'''|| 
     47If you answered !'''NO!''' to any of the above, please provide further details: 
     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........ 
     56=== System Changes === 
     57||Does your change alter namelists?||!'''YES/NO !'''|| 
     58||Does your change require a change in compiler options?||!'''YES/NO !'''|| 
     60If any of these apply, please document the changes required here....... 
     63=== Resources === 
     64!''Please !''summarize!'' any changes in runtime or memory use caused by this change......!'' 
     67=== IPR issues === 
     68||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES/ NO !'''|| 
     70If No: 
     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..........