HowTo

Region sets

Region sets (or specific regions thereof) need to be specified for various purposes, such as:

Postprocessing: Spatial integration of fluxes into time series (parameter pp_regionset).
Postprocessing: Forward transport model runs with fluxes from a certain geographical region only (parameter tm_MaskoutReg).
Set-up: Definition of Sigma_region for uncertainty normalization.
Diagnosis: Calculation of a-priori sigma intervals for spatial integrals of fluxes (parameter sigmas_region).

Region sets are specified by a string 'REGION' that can have one of the following meanings (whichever is recognized first):

Hard-wired region set: Various region sets of general interest are hard-wired in the code, such as:

Name	Number of regions	Region(s)
`''`, `'global'`, `'Global'`	1	Entire domain
`'NH20'`	1	Northern hemisphere (north of 20N)
`'Tr20'`	1	Tropics (20N-20S)
`'SH20'`	1	Southern hemisphere (south of 20S)
`'3Bands15e'`	6+3	3 latitudinal bands for land and ocean cut at 15N and 15S
`'3Bands20e'`	6+3	3 latitudinal bands for land and ocean cut at 20N and 20S
`'3Bands25e'`	6+3	3 latitudinal bands for land and ocean cut at 25N and 25S
`'5Bands1545e'`	10+3	5 latitudinal bands for land and ocean cut at 45N, 15N, 15S, and 45S
`'TransCom3'`	22+3	11 land and 11 ocean regions as defined by the TransCom3 project
`'Aggreg6Eu02'`	6+3	6 European subregions

There are further hard-wired region sets, in particular various other latitudinal bands. For a complete overview in the current version, see the more or less self-explanatory code in "~/INVERSION/RUN/src/mask.f90".
Region sets reading n+3 in the 2nd column additionally contain 3 global regions (total land, total ocean, and global total).
All these hard-wired region sets are available for any grid. For non-global grids, any regions (or part of regions) outside the domain of the grid are zero.

Region file: If a region file "reg_REGION_gridtag.d" exists, it is read in to define the region set. As the region files are specific to a given grid gridtag and need follow a strict syntax, they are not recommended any more.
Map file:
Cutout file:

In addition, the 'REGION' string can be appended by the following modifiers (to be applied in this order when being combined):

'REGIONoo', 'REGIONoo400', or 'REGIONoo1km' restricts all ocean regions in the set to the open ocean defined in different ways (by ocean fraction, by ocean areas deeper than 400m, or by ocean areas deeper than 1km, respectively).
'REGION@gridtag' restricts all regions to the domain of the grid gridtag (supposed to be a non-global grid). For example, '5OceanBands1545ePAIA66@stilt04' denotes the regions of the set '5OceanBands1545ePAIA66' restricted to the domain of the 'stilt04' grid around Europe. All regions outside the domain are just zero.
In particular, by appending it to the empty string ('') for the global region, this modifier can be used to specify the single region comprising the domain of the grid gridtag (example: '@stilt04').
'REGION:index' denotes the single region having the given index in the original set. A negative index means the entire domain except that region (example: 'TransCom3:-22' denotes everything except TransCom3's Southern Ocean, '@stilt04:-1' denotes everything except the 'stilt04' domain).