1) General information :

Name and version of software :

TM version TMSCIA V1.3

Name of development coordinator and Institution :

Peter van Velthoven, KNMI

Contact address :

P.O. box 201, NL 3730 AE De Bilt, The Netherlands

Purpose of software :

Atmospheric Chemistry Transport model (requiring meteo-input)

Programming language :

fortran 90, tcsh script

Conditions under which the model is distributed for research purposes :

Yet to be settled

2) Interfaces of the model :

2.1) User inputs to configure model or experiment :

How are configuration parameters passed to the model :

Mostly read from a namelist defined in the calling script. This namelist is presently passed to the model in a control-file, control.ini. In the past it used to be passed to the model from the keyboard input unit (unit 5 in fortran).

The resolution parameters are in fortran parameter statements in a file dimension.f90, a module that is modified before compilation. Vertical model level parameters and constants are in file global_data.f90, another module that is modified before compilation.

Inputs required to configure the model :

Name of parameter	description	Units	Type and rank	Optional or mandatory	If optional what is the default value	Does it have dependencies with other parameters
namelist, control.ini:
nread	interval for input of meteorological data	s	INTEGER, scalar	optional	6*3600 seconds
ndyn	full advection time step	s	INTEGER, scalar	mandatory	3600	depends on resolution: im,jm
nconv	convection time step	s	INTEGER, scalar	optional	ndyn	ndyn
nchem	chemistry time step	s	INTEGER, scalar	optional	ndyn	ndyn
nsrce	time step for sources (emissions)	s	INTEGER, scalar	optional	ndyn	ndyn, nchem
ndiff	horizontal diffusion time step	s	INTEGER, scalar	optional	ndyn	ndyn
idatei	Date-time of start of simulation (yy,mm,dd,hh,min,sec)	-	INTEGER, array(6)	mandatory
idatee	Date-time of end of simulation (yy,mm,dd,hh,min,sec)	-	INTEGER, array(6)	mandatory
icalendo	calendar type	-	INTEGER, scalar	optional	2=real calendar
iyear0	base year for calendar	-	INTEGER, scalar	optional	1980
czeta	scaling factor for convective transport	-	REAL, scalar	optional	1 .0
czetak	scaling factor for vertical diffusion	-	REAL, scalar	optional	1. 0
limits	if true, slopes in the slopes advection scheme are limited to prevent negative tracer mixing ratios	-	LOGICAL	optional	false
dimension.f90:
im	number of longitudes	-	INTEGER, scalar	mandatory
jm	number of latitudes	-	INTEGER, scalar	mandatory
lm	number of vertical levels	-	INTEGER, scalar	mandatory
ntracet	number of transported tracers	-	INTEGER, scalar	fixed	e.g. 23	chemistry
ntrace	total number of tracers (>ntracet)	-	INTEGER, scalar	fixed	e.g. 38	chemistry
npts	number of points in an idealised vector loop (for vector processors)	-	INTEGER, scalar	mandatory
lat2	number of high latitude circles in each hemisphere with u-advection with half time step	-	INTEGER, scalar	mandatory
globalv.f90:
a	hybrid sigma-p half-level coefficients a	Pa	REAL, array(lm+1)	mandatory
b	hybrid sigma-p half-level coefficients b	-	REAL, array(lm+1)	mandatory

Are there other parameters which are not accesible to the user through this mechanism :

Probably a few. .

How do you rate your used interface (0-5): 2

2.2) Inputs read from files to set up the model :

Does the model have it's own restart mechanism :

Yes.

If yes, what is the file format and which library is used :

Format is hdf (libraries: libmfhdf, libdf, libz,
and libjpeg)

Can the model be started without restart files :

No, it would require a spinup time of the order of 10 years.

Are parameters needed by the model which are in data files :

Yes

Apart from the intialisation the model also needs emissions, total ozone fields (TOMS), and some tracer upper boundary conditions (UARS and and ozone profile climatology)

If so please describe the files and their content :

Name of file	File format	Variables contained	resolution of these variables
saveold.hdf	hdf	im,jm,lm,ntrace,ntracet*,idate (int(6)=[yy,mm,dd,hh,min,sec]),msg (char*64), advection_scheme (char*8="slopes" or "second_m"), label (char*160)	these are descriptive
idem	idem	rm (tracer mass in cells in kg) and rxm,rym,rzm (slopes of rm)	4-D arrays with dimension im,jm,lm,ntrace
idem	idem	if advection_scheme="second_m" also: rxxm,ryym,rzzm, rxym, rxzm, ryzm (second order moments of rm)	idem

* see 2.1

How do you rate your interface for ancillary data (0-5): insert text here

2.3) Inputs required for the time integration of the model, the forcing data :

From which other component is forcing needed to drive the model :

Atmospheric model (AGCM): meteorology, Land surface model: emission and deposition parameters, , Ocean model: tracer fluxes.

The frequency at which this is required :

6 hours, if possible more frequently

Is the model, especially when not being part of the PRISM project, already used in coupled climate simulation :

No.

Which algorithm of exchange or flow chart between the two models is used :

Meteorlogical data from AGCM would best be provided on the TM grid. It should be possible to make air mass fluxes (derived from divergence, vorticity and surface pressure) mass conserving. If necessary it is possible to pre-process the meteorlogical input data, i.e. interpolate them to the TM-grid before running TM. Vertical levels should preferentially be chosen as a subset of the AGCM.

How is this coupling implemented :

6-hourly input data in daily or monthly files. Spatial interpolation to TM grid can be done in a preprocessing step.

Can this forcing data also be provided from a files :

Yes.

Variables exchanged between both models :

- Physical variables in the forcing data: (Given is the presently used data from ECMWF)

Variable name	description	type and shape	units	time step	length of average	input or output	Memory management	sign convention	Notes
From AGCM:
D	Horizontal wind divergence	Real or Double, 3D	1/s	t-dt	0	Input			D,VO are preferred over U,V for spectral AGCMs
VO	Vorticity	Real or Double, 3D	1/s	t-dt	0	Input			for mass conservation reasons
LNSP	Natural logarithm of surface pressure	Real, 3D	ln(Pa)	t-dt,t-0.5dt,t	0	Input
W	Vertical velocity dp/dt	Real, 3D	Pa/s	t-0.5dt	0	Input		positive= downward
T	Temperature	Real, 3D	K	t-0.5dt	0	Input
q	Specific humidity	Real, 3D	kg/kg	t-0.5dt	0	Input
CC	Cloud cover	Real, 3D	0-1	t-0.5dt	0	Input
CLWC	Cloud liquid water	Real, 3D	kg/kg	t-0.5dt	0	Input
CLIC	Cloud ice water content	Real, 3D	kg/kg	t-0.5dt	0	Input
MU	Updraught mass flux	Real, 3D	kg/m2	accumulated over t-dt to t	dt, e.g. 6 hours	Input		always positive	on half-levels
UD	Updraught detrainment	Real, 3D	s/m	accumulated over t-dt to t	dt	Input		always positive	on half-levels
MD	Downdraught mass flux	Real, 3D	kg/m2	accumulated over t-dt to t	dt	Input		always positive
DD	Downdraught detrainment	Real, 3D	s/m	accumulated over t-dt to t	dt	Input		always positive
K	Turbulent diffusion coefficient (tracers or heat)	Real, 3D	m2	t-0.5dt or accumulated over t-dt to t	dt	Input			on half-levels
PRECIP	Total Precipitation (formation rate)	Real, 3D	kg/m2	accumulated over t-dt to t	dt	Input			on half-levels
LSP	Large scale precipitation	Real, 2D	m	accumulated over t-dt to t	dt	Input
CP	Convective precipitation	Real, 2D	m	accumulated over t-dt to t	dt	Input
SF	Snowfall	Real, 2D	m	accumulated over t-dt to t	dt	Input
SD	Snow Depth	Real, 2D	m	t-0.5dt	t	Input
SLHF	Surface latent heat flux	Real, 2D	W/m2s	accumulated over t-dt to t	dt	Input
SSHF	Surface sensible heat flux	Real, 2D	W/m2s	accumulated over t-dt to t	dt	Input
T2m	2m Temperature	Real, 2D	K	t-0.5dt	0	Input
u10m, v10m	10m Wind	Real, 2D	m/s	t-0.5dt	0	Input		positive eastward and northward
D2m	2 m Dew point	Real, 2D	K	t-0.5dt	0	Input
SSR	Surface solar radiation	Real, 2D	W/m2s	accumulated over t-dt to t	dt	Input
EWSS	Eastward component of turbulent stress	Real, 2D	N/m2s	accumulated over t-dt to t	dt	Input		positive eastward
NSSS	Northward component of turbulent stress	Real, 2D	N/m2s	accumulated over t-dt to t	dt	Input		positive northward
SR	(ln of) Surface roughness (heat)	Real, 2D	m	t-0.5dt	0	Input
From ocean (biochemistry) model:
	DMS flux from ocean	Real, 2D	kg/m2	accumulated over t-dt to dt	dt	Input		positive upward
Output of atm. chemistry model
CH4, O3	Radiatively active tracers	Real, 3D	kg/kg	t	0	Output
HNO3, NH4, SO4,	Aerosols: ammonium, sulfate, nitrate, OC, BC	Real, 3D	kg/kg	t	0	Output

- Grid description, control information and meta-data needed for the forcing data:

In the horizontal regular lon-lat grids can already be dealt with.

 

Variable name	description	type and shape	units	time step	length of average	input or output	sign convention	Notes
nlon	Number of longitudes	INTEGER		-	-	input
rlon1	First longitude	REAL	degrees	-	-	input	East from Greenwich positive
dlon	Longitude step	REAL	degrees	-	-	input
Longitude flag	EtoW or WtoE?	INTEGER		-	-	input
nlat	Number of latitudes	INTEGER		-	-	input	North from equator positive
rlat1	First latitude	REAL	degrees	-	-	input
dlat	Latitude step	REAL	degrees	-	-	input
Latitude flag	StoN or NtoS?	INTEGER		-	-	input

In the horizontal spherical harmonics are presently used for D, VO, T, and W:

This requires knowledge of the truncation structure and the way the coefficients are stored in the arrays.

All other meteorological parameters are presently used from a reduced gaussian grid:

 

Variable name	description	type and shape	units	time step	length of average	input or output	sign convention	Notes
nlons(nlat)	Number of longitudes	INTEGER		-	-	input
rlon1	First longitude	REAL	degrees	-	-	input	East from Greenwich positive
Longitude flag	EtoW or WtoE?	INTEGER		-	-	input
nlat	Number of latitudes	INTEGER		-	-	input	North from equator positive
lats(nlat)	Gaussian latitudes	REAL	degrees	-	-	input

In the vertical hybrid sigma-pressure levels are expected. In order to calculate the pressures of the full and half levels the coefficients a and b (see 2.1) and LNSP (6- hourly 2-D field, see above "Physical variables in the forcing data") are needed. Other vertical level structures could in principle be dealt with by applying an interpolation.

How do you rate your forcing interface (0-5): 2

3) Diagnostics provided by the model :