Version 4 (modified by cbricaud, 9 years ago) (diff)

Last edited Timestamp?


ticket : #859

Branch : dev_r2802_MERCATOR9_floats


Online monitoring of water particles (position + (T,S) signature): improvements of ascii input: initialisation of particules can be made with lon/lat position or I/J positions implementation of ouputs : write output in netcdf files ( with Ariane (B Blanke) convention ) ; availaible with IOISL andf IOM.

add cpp key key_floats.


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

NVTK Tested'''YES'''
Other model configurations'''YES'''
Processor configurations tested1*1, 2*8,4*4
If adding new functionality please confirm that the
New code doesn't change results when it is switched off
and ''works'' when switched on

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

'Please add further summary details here'

Tests done on IBM power 6.

  • reproductiblity: ORCA2_LIM: compare 2*8 and 4*4 configurations: results are identical ( for 75 time steps, with key_mpp_rep )

GYRE : compare 2*8 and 4*4 configurations: results are identical ( for 60 time steps, with key_mpp_rep )

  • restartability: GYRE, with 1*1 configuration: compare 2 consecutives runs of 60 time steps with 1 run of 120 time steps : results are identical

Bit Comparability

Does this change preserve answers in your tested standard configurations (to the last bit) ?'''YES '''
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?
,,''Preserving answers in model runs does not necessarily imply preserved diagnostics. ''

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 '''
Does your change require a change in compiler options?'''NO '''

If any of these apply, please document the changes required here……. New variables in namflo bloc:

  • numbers of floats ( jpnfl and jpnnewflo).
  • ln_ariane: T: Input with Ariane tool convention ( I-J coordinates), F: Input with long/lat convention.
  • ln_ascii: T: Output in ascii F: Output in netcdf.


tests done on Dell cluster, 4*4 mpi configuration:

  • 1 year of ORCA2_LIM without floats : walltime=15 minutes, mem=1.56 Go.
  • 1 year of ORCA2_LIM with 5 floats ( 1 writing per day) : walltime= 16 minutes, mem=1.56 Go.

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