Version 4 (modified by davestorkey, 5 years ago) (diff)

Last edited Timestamp?


Author : Dave Storkey

ticket : #1590

Branch : icebergs_restart_single_file


Description

Converts the iceberg restart reading routine icb_rst_read in icbrst.F90 to use the IOM library. The main motivation is to allow to the routine to be able to start from a single rebuilt restart file as well as a decomposed set of restart files. (So the behaviour is the same as for the standard NEMO restart). Two small modifications to the IOM module are required.

Also includes a python module in TOOLS/REBUILD_NEMO to allow rebuilding of multiple iceberg restart files into a single file.


Testing

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

NVTK Tested'''YES'''
Other model configurations'''YES'''
Processor configurations tested eORCA025 on 480 PEs of Cray XC40
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'

  • Tested in eORCA025-CICE configuration on Cray XC40
  • Test setup: one-day integrations starting from iceberg restart file:
    • old code starting from multiple iceberg restart files
    • new code starting from multiple iceberg restart files
    • new code starting from a single (rebuilt) iceberg restart file
  • All three integrations gave bit-comparable restarts after one day.

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