Version 2 (modified by cbricaud, 11 years ago) (diff)

Last edited Timestamp?






Read 3D files like Levitus with fldread routine. Now it is possible to use spatial and temporal interpolation of fldread. In the public type "FLD" defined in fldead and used by severals routines, fnow becomes a 3D array and fdta a 4D array. So there are light changes in all routines that use fldread ( i.e that use FLD type ): sbcblk_clio.F90 sbcblk_core.F90 sbcflx.F90 sbcice_if.F90 sbcrnf.F90 sbcssr.F90 traqsr.F90


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

Other model configurationsYES
Processor configurations tested 2*4*8
If adding new functionality please confirm that the
New code doesn't change results when it is switched off
and ''works'' when switched on

*Now, dtasal and dtatem routines are doing the temporal interpolation with fldread routine, instead using temporal interpolation that is at the end of them.

It is not exactly the same formulation. but the temporal interpolation of fldread is better.

'Please add further summary details here'

*It is working on all Mercator's configuration (ATL12, ORCA025_LIM, ORCA12_LIM), on some differents computers (IBM, NEC ).

Bit Comparability

Does this change preserve answers in your tested standard configurations (to the last bit) ?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?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? Now, dtasal and dtatem routines are doing the temporal interpolation with fldread routine
  • Why the changes are not protected by a logical switch or new section-version? Because it is a new way for temporal interpolation of Levitus
  • 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. It is not possible for the same reson as above.
  • 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

We have to use the same namelist bloc as bulk formulations for dtatem and dtasal


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