New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
ticket/0855 – NEMO
wiki:ticket/0855

Version 2 (modified by kpedwards, 13 years ago) (diff)

--

      1. Description
      2. Testing
      3. Bit Comparability
      4. System Changes
      5. Resources
      6. IPR issues

Last edited Timestamp?


Author : Karen Edwards

ticket : #855

Branch : https://forge.ipsl.jussieu.fr/nemo/browser/branches/2011/dev_r2802_TOP_substepping

Description

Update the substepping option (using nn_dttrc) to work in the new TOP routines in VN3.3.1. This includes reintroducing the variable nittrc000 throughout the code and including the provision for averaging physics variables over the substep period.

Testing

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

NVTK Tested'''NO'''
Other model configurations'''AMM7, MED12
Processor configurations tested[1x1, 1x2 and 4x8]
If adding new functionality please confirm that the
New code doesn't change results when it is switched off
and ''works'' when switched on		'''YES'''

(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 - for physics/ NO - for TOP models
Is this change expected to preserve all diagnostics?
,,''Preserving answers in model runs does not necessarily imply preserved diagnostics. ''		'''YES'''

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

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......'' If substepping is used (nn_dttrc >1 in namelist_top), a set of time mean arrays is set up to average a number of the physics variables over the tracer step. This will also decrease run time needed as the main TOP_SRC routines are not called every model time step.

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