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

Last edited Timestamp?

Author : AUTHOR_NAME

ticket : #937

Branch : BRANCH_NAME


Description

Mercator-1 : Improvment of OBC's


Testing

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

NVTK Tested '''YES'''
Other model configurations '''NO'''
Processor configurations tested [ sette layouts ]
If adding new functionality please confirm that the
New code doesn't change results when it is switched off
and ''works'' when switched on
'''NO'''

(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) ? '''NO '''
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. ''
'''NO'''

If key_bdy and key_tide are not activated, modifications do not change either answers or results of standard configurations. Thus results changes only concern AMM12 standard configuration. These changes only come from the completely different tidal module implemented. Thus, there are not induced by the modifications of bdy package alone as long as the same options are used. Note however that some issues with overlapping analytical segments have been fixed in bdy package. It is now possible to obtain identical results with user defined "analytical" open boundary segments bounding the domain (ie identical to the case where a single unstructured segment is read from a netcdf file). As a consequence, diagnostics in AMM12 changes although no change in the diagnostics themselves has been introduced.

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'''
  • namelist changes:
    • nam_tide: Simplifications in the definition of tidal waves. Add a flag and time_scale to activate linear ramping of tidal motions.
    • nambdy_tide: Add a new option to read tidal boundary data from 2d file given on data domain.
    • nambdy: Add new options for bdy: Flags and times cales to apply relaxation on tracers and baroclinic velocities.
    • nambdy_index: Simplify definition of analytical segments.
  • About compiler options: Code update does not require any change in compiler options. Yet, we noticed that results are not reproductible unless the lowest level of optimization is used.

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