[[PageOutline]]
Last edited [[Timestamp]]

[[BR]]

'''Author''' : Tim Graham

'''ticket''' : #1399

'''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/2014/dev_r4650_UKMO13_CICE_changes_take2   dev_r4650_UKMO13_CICE_changes_take2 ] 
----

=== Description ===
Changes to the CICE interface to allow NEMO to run with CICE5.

Variable names in the CICE5 model and included in NEMO via a USE statement are different to those in CICE4. For this reason a new key (key_cice5) is introduced to control whether CICE4 or CICE5 is used.


----
=== Testing ===
Testing could consider (where appropriate) other configurations in addition to NVTK].

||SETTE Tested||!'''YES'''||
||Other model configurations||!'''YES'''||
||Processor configurations tested|| Standard SETTE configs ||
||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'''||

(Answering UNSURE is likely to generate further questions from reviewers.)

'Please add further summary details here'


=== Bit Comparability ===
||Does this change preserve answers in your tested standard configurations (to the last bit) ?||!'''YES ! ( as these don't use CICE)'''||
||Does this change bit compare across various processor configurations. (1xM, Nx1 and MxN are recommended)||!'''YES!'''||
||Is this change expected to preserve answers in all possible model configurations?||!'''NO!'''||
||Is this change expected to preserve all diagnostics? [[BR]]!,,!''Preserving answers in model runs does not necessarily imply preserved diagnostics. !''||!'''NO!'''||

If you answered !'''NO!''' to any of the above, please provide further details:

 * Which routine(s) are causing the difference? - The changes in answers are from the updated CICE model rather than NEMO.
 * Why the changes are not protected by a logical switch or new section-version - CICE version is switchable.
 * 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.
 * What do you expect to see occur in the test harness jobs?
 * Which diagnostics have you altered and why have they changed?Please add details here........
Changes occur in ice area and feed back onto SST/surface fluxes/currents etc.

----
=== System Changes ===
||Does your change alter namelists?||!'''NO !'''||
||Does your change require a change in compiler options?||!'''YES !'''||

If any of these apply, please document the changes required here.......
To work with CICE5 model the code must be compiled with key_CICE5.
To work with CICE4 model the code must be compiled with key_CICE (this has not changed).

----
=== Resources ===
Little change

----
=== IPR issues ===
||Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?||!'''YES !'''||

If No:

 * Identify the collaboration agreement details
 * Ensure the code routine header is in accordance with the agreement, (Copyright/Redistribution etc).Add further details here if required..........