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

[[BR]]

'''Author''' : Steven Alderson 

'''ticket''' : #942

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

=== Description ===

Implement Martin & Adcroft's scheme for calving and drifting of icebergs (Ocean Modeling 34, 2010).

In this scheme icebergs are represented as lagrangian particles which propagate and decay according to momentum and mass balance equations.
They represent a propagating source of freshwater, which may be far removed from near land point runoff which has been traditionally used to represent iceberg influence.

'''New OPA_SRC files:'''

  ICB/icb_oce.F90
    Declarations of icebergs types and variables.  Icebergs are described by a new FORTRAN TYPE which is a linked list of icebergs.
  ICB/icbclv.F90
    Routines which convert calving flux into ice available for calving icebergs into each available class.
  ICB/icbdia.F90
    Extensive diagnostic information can be produced.  This module accumulates data for release at intervals determined by namelist variables.
  ICB/icbdyn.F90
    Module to handle momentum equation describing iceberg propagation.
  ICB/icbini.F90
    Initialisation routines.
  ICB/icblbc.F90
    Routines to deal with lateral boundaries: east-west cyclic condition, north fold and also MPP exchanges.
  ICB/icbrst.F90
    Write out restart files
  ICB/icbrun.F90
    Top level routine to call iceberg routines in the correct order
  ICB/icbthm.F90
    Module to calculate mass balance of icebergs
  ICB/icbtrj.F90
    Deal with iceberg trajectory output files
  ICB/icbutl.F90
    Various utility routines

'''Modified OPA_SRC files:'''

  DIA/diawri.F90
    added extra output for iceberg gridded files
  DYN/dynspg_flt.F90
  LBC/lbclnk.F90
  LBC/lib_mpp.F90
  SOL/solmat.F90
  SOL/solsor.F90
    All of the above five routines have been modified because of the need to perform boundary exchange on arrays inside the iceberg code independently of jpr2di, jpr2dj.
    This requires the halo size to be explicitly passed to lbc_lnk_e.
  SBC/sbc_oce.F90
    Add ln_icebergs declaration
  SBC/sbcmod.F90
    Perform timesteps and finalise icebergs from here
  nemogcm.F90
    Initialise iceberg code.


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

||NVTK Tested||!'''YES/NO!'''||
||Other model configurations||!'''YES/NO!'''||
||Processor configurations tested||[ Enter processor configs tested here ]||
||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!'''||

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

'Please add further summary details here'

 * Processor configurations tested
 * etc----

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

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

 * Which routine(s) are causing the difference?
 * Why the changes are not protected by a logical switch or new section-version
 * 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........

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

If any of these apply, please document the changes required here.......

----
=== Resources ===
!''Please !''summarize!'' any changes in runtime or memory use caused by this change......!''

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

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..........