Last edited Timestamp?

Author : Clement BRICAUD

ticket : #650

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

---

Description

On-the-fly interpolation for 3D files. It will replace time-interpolation for intial state in dtatem and dtasal. In fldread, fnow has now a third dimension ( vertical ) and fdta a forth dimension ( vertical too). In consequence, all routines using fldread will be modified, when fdta and fnow are allocated ; we decided to not allocate fdta when time-interpolation is not used.

---

Testing

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

NVTK Tested	'''YES'''
Other model configurations	'''YES'''
Processor configurations tested	[ 2*1 , 1*2 , 2*2 ]
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'''

In dtatem and dtasal, time-interpolation formula is :

zxy = FLOAT( nday + 15 - 30 * i15 ) / 30.

t_dta(:,:,:) = (1.-zxy) * temdta(:,:,:,1) + zxy * temdta(:,:,:,2)

Here, lenght of month is hard-coded: 30 days.

Now, with fldread, computing is exact.

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

Same answer as above.

---

System Changes

Does your change alter namelists?	'''YES '''
Does your change require a change in compiler options?	'''NO '''

Now dtatem and dtasal have their namelist:

!-----------------------------------------------------------------------

&namdta_tem ! surface boundary condition : sea surface restoring

!-----------------------------------------------------------------------

! ! file name ! frequency (hours) ! variable ! time interpol. ! clim !'yearly' or ! weights ! rotation !

! ! ! (if <0 months) ! name ! (logical) ! (T/F) ! 'monthly' ! filename ! pairing !

sn_tem = 'data_1m_potential_temperature_nomask', -1 , 'votemper' , .true. , .true. , 'yearly' , ' ' , ' '

!

cn_dir = './' ! root directory for the location of the runoff files

/

!-----------------------------------------------------------------------

&namdta_sal ! surface boundary condition : sea surface restoring

!-----------------------------------------------------------------------

! ! file name ! frequency (hours) ! variable ! time interpol. ! clim ! 'yearly' or ! weights ! rotation !

! ! ! (if <0 months) ! name ! (logical) ! (T/F) ! 'monthly' ! filename ! pairing !

sn_sal = 'data_1m_salinity_nomask' , -1 , 'vosaline' , .true. , .true. , 'yearly' , , ' '

!

cn_dir = './' ! root directory for the location of the runoff files

/

---

Resources

No change in runtime or memory.

---

IPR issues

Has the code been wholly (100%) produced by NEMO developers staff working exclusively on NEMO?

'''YES '''