Last edited Timestamp?

Author : hadcv

ticket : #1085

Branch : ​dev_r3987_UKMO6_C1D

---

Description

Motivation

The changes proposed aim to expand the functionality of the NEMO C1D configuration. In its current form, the configuration is not particularly user-friendly and lacks some of the flexibility and functionality that might be desired by a prospective user. Based on anticipated requirements for the ​OSMOSIS project, a number of changes have been made to the C1D configuration. The changes make up an initial contribution to an overall enhancement of the C1D configuration, with further changes planned for the 2014 work plan.

Overview of changes

1. Add a namelist entry for C1D configuration options
2. Add namelist specification of the column location given latitude and longitude
3. Allow use of timeseries/mooring data (no x,y dimension) in fldread
4. Allow use of fldread record frequencies of less than 1hr
5. Add specification of measurement heights for forcing data
6. Allow use of tracer damping module in C1D configuration
7. Add momentum damping module for C1D configuration
8. Other minor changes

---

Testing

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

NVTK Tested	'''YES/NO'''
Other model configurations	YES
Processor configurations tested	1 processor only
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'

<ATTACHED DOC>

---

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

• Add namc1d namelist to miscellaneous namelists section
  • General C1D options
• Add namc1d_uvd namelist to miscellaneous namelists section
  • dta_uvd control, similar to namtsd
• Add namc1d_dyndmp namelist to miscellaneous namelists section
  • dyndmp control, only contains ln_dyndmp activation logical
• Modify namsbc_core namelist to include three new parameters
  • ln_bulk2z, rn_zqt & rn_zu, controlling functionality related to change 5 in the description above

---

Resources

C1D configuration Using XIOS attached mode, temperature output only, for a 150-day run

• Before changes: 18 seconds, 199mb
• After changes: 20 seconds, 347mb

3D configuration Using XIOS detached mode, standard assessment-level output, for a 5-day run

• Before changes: 908s, 34124mb (maximum node usage)
• After changes: 906s, 34546mb (maximum node usage)

---

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