Opened 12 years ago

Closed 12 years ago

#35 closed help (fixed)

Finding things in the D1 array

Reported by: s.keeley@… Owned by: jeff
Component: UM Model Keywords:
Cc: Platform:
UM Version:

Description

Hi,
Lois and I had discussed finding and writing things to the UM in the D1 array and not really knowing how to go about it.

Whilst reading some of the umui help pages I stumbled across this which suggests that fields do get written to the D1 array and there is a way of finding out what the pointers are using
UM routine FINDPTR. I was wondering if anyone knows where this routine might be? and if it is part of the standard UM setup….

Thanks,
Sarah

Help for window : atmos_STASH_Usage

This window allows users to define the attributes of the usage profile
within the STASH windows.

The useage profile defines the output destination of a diagnostic.

Most often, simple diagnostics are written to one of the user-PPfiles on
units 60-69.
The user can specify these as files to be reinitialised or recycled
(that is, new files are attached periodically to this output stream to
avoid the files becoming too large). In this case, each stream should be
dedicated to a particular sub-model. Several streams can be attached to
one sub-model. When the streams are defined as not reinitialised, users
can mix output onto these streams as they please. See
subindep_PostProc_PPInit.

Alternatively, diagnostics can be written to the D1 area (and the
external dump by implication). Users may wish to do this so that
diagnostics can be passed from one section of code to another. This
method is used by several of the STASHmacros. To allow the code to find
the particular diagnostic it is also Tagged and search routines can find
the STASHlist record that has such TAGs attached.
See UM routine FINDPTR.
These are the TAGs used by various code sections:

10 atmosphere to ocean coupling
11 ocean to atmosphere coupling
20 atmosphere to slab coupling
21 slab to atmosphere coupling
30 atmospheric assimilation dump extension

If the variable is not required in the dump (that is it is not time
processed or you are certain that all time processing occurs within the
dump intervals) you can similarly write tagged diagnostics to secondary
store. These are not written to the dump as they are in an extended area
of D1.

Alternatively, diagnostics can be written to the D1 area (and the
external dump by implication) and tagged to be picked up by the climate
meaning system. Users should attach this sort of profile to diagnostics
from sections other than the climate mean sections (21-24). Users may
wish to perform time processing (such as daily means sampling values
every timestep) and have these further processed by the climate meaning
system. This is the only way to obtain climate means with values
accurate to the nearest timestep. Such diagnostics need to be written to
the climate mean files for each meaning period. Specify the periods
required, the tagging will be added automatically from this information.

Diagnostics from the climate mean sections (21-24) are either "mean
prognostic variables" or diagnostics calculated from those variables.
They are the result of the climate mean dumps. The sampling frequency
for such meaning is the basic dumping frequency of the run for a given
sub-model. Such diagnostics are written direct to the climate mean
files.



Dr Sarah Keeley
Climatic Research Unit
University of East Anglia
Norwich
NR4 7TJ
UK

tel: +44 (0) 1603 592721

web: www.cru.uea.ac.uk/~sarahk/




Dr Sarah Keeley
Climatic Research Unit
University of East Anglia
Norwich
NR4 7TJ
UK

tel: +44 (0) 1603 592721

web: www.cru.uea.ac.uk/~sarahk/


Change History (3)

comment:1 Changed 12 years ago by jeff

  • Status changed from new to assigned

comment:2 Changed 12 years ago by jeff

Hi Sarah

You can find FINDPTR1.dk, in directory $UMDIR/vn4.5/source/umpl.dir for 4.5 or $UMDIR/vn6.1/normal/source/umpl for 6.1 on hpcx I assume its the same on your system. Or you can try looking at the source code browser here, http://ncas-cms.nerc.ac.uk/content/view/49/172/. If you don't want to search using all the variables in the subroutine, then set them to be = IMDI.

Jeff.

comment:3 Changed 12 years ago by jeff

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.