Last edited Timestamp?
Author : Ed Blockley
ticket : #1347
Branch : TBC
Description
Two changes are planned to the restart functionality within NEMO/LIM:
- to allow users to exactly specify a list of timesteps on which the model will write out restart files. This will involve modification of OPA only
- to allow the user to specify the directory where restarts will be written to as is done in the SBC/fldread module. This will require modification of LIM2 & LIM3 as well as OPA
Testing
Testing could consider (where appropriate) other configurations in addition to NVTK].
NVTK Tested | '''YES''' |
Other model configurations | '''NO''' |
Processor configurations tested | [ Enter processor configs tested here ] |
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'
- All SETTE tests passed when functionality is turned off.
- ORCA2LIM3, ORCA2LIMPIS and ORCA2OFFPIS tested reading and writing restart files to other directories and with a list times to output restart files.
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? | '''YES ''' |
Does your change require a change in compiler options? | '''NO ''' |
If any of these apply, please document the changes required here....... Added cn_ocerst_indir, cn_ocerst_outdir, ln_rst
Resources
''Please ''summarize'' any changes in runtime or memory use caused by this change......'' Minimal changes
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..........