Differences between revisions 11 and 12
Revision 11 as of 2008-07-15 08:32:59
Size: 2937
Editor: NicoleThomas
Comment:
Revision 12 as of 2008-07-15 09:26:05
Size: 3027
Editor: NicoleThomas
Comment:
Deletions are marked like this. Additions are marked like this.
Line 41: Line 41:
 * add_flightpath.f90:  * add_flightpath.f90: Add positions of a flightpath to a pos file
Line 53: Line 53:
 * pos_flightpath.f90:  * pos_flightpath.f90: Create pos file with positions along flightpath

The package pos

The package pos helps to create an ensemble of n APs. Especially, their initial special positions (described in isentropic coordinates spanned by longitude, latitude and the potential temperature) and their initial times (in Julian seconds) can be created. The geometric properties (positions, Voronoi areas,...) and the dynamical properties (PV, EQLAT, TEMP, PRESS,....) of the APs are derived from the meteorological input files using the pos***-family of the programs.

How to get the source code

The source code of the pos package is under control of the CVS (Concurrent Version System) utility. To get the source code the environment variable CVSROOT must be set to /usr/local/icg/icg1/archive. The command

cvs co -P pos

creates a directory pos in the current working directory and copies the current version of the pos package to this directory.

The directory pos includes the following subdirectories:

  • data: some data files necessary for initialization with a passive tracer

  • doc: latex file for documentation

  • mod: module files

  • obj: object files

  • source: source code

  • templates: templates for the configuration files

Compiling

The programs can be compiled on different platforms with the command

gmake prog_name

leading to an executable file with same name in the pos directory.

To compile programs in package pos the package dynmod must be checked out too.

Available programs

The subdirectory source contains the following programs:

  • add_flightpath.f90: Add positions of a flightpath to a pos file
  • pos_3d.f90: Different 2d or 3d initial configurations

  • pos_area.f90: 2d or 3d initial positions of APs with equal isentropic areas (+ PV_INIT)

  • pos_chem.f90: modifies chemical fields (O3, HCL etc) in init-files on lower and upper bound

  • pos_dyn.f90: This program completes the geometric positions of the APs with their dynamical properties, i.e.~PV, EQLAT, TEMP, PRESS,...

  • pos_example.f90: An easy example how to create the initial positions of APs

  • pos_flightpath.f90: Create pos file with positions along flightpath
  • pos_voronoi.f90: Voronoi areas are calculated and added to the pos/init-file

Output Files

Each pos_* program creates an output file in NetCDF data format. It is named:

  • pos_xxx_yymmddhh.nc

    xxx : prefix, 1-3 characters
    yymmddhh : year, month, day, hour
    e. g.: pos_ABC_99022812.nc

In this file the starting positions of the trajectories (longitudes, latitudes and theta) are stored on the variables LAT, LON and THETA. The corresponding starting times are saved on the variable TIME_INIT. Furthermore, the variables PV_INIT, EQLAT, TEMP, PRESS, TND (density) and VORONOI_AREA can be created.


History of Changes

pos (last edited 2019-07-31 12:28:06 by NicoleThomas)