Input - Revision history

Admin 3 at 12:40, 7 April 2025

2025-04-07T12:40:08Z

← Older revision		Revision as of 14:40, 7 April 2025
Line 179:		Line 179:
	\| '''transport'''		\| '''transport'''
	\| character		\| character
	\| ~~stdaero, stdchem, ...~~, off		\| hadv52aero, off
	\| choice of transport template		\| choice of transport template
	\|-		\|-
Line 437:		Line 437:
	\| '''transport'''		\| '''transport'''
	\| character		\| character
	\| ~~stdaero, stdchem, ...~~, off		\| hadv52aero, off
	\| choice of transport template		\| choice of transport template
	\|-		\|-

Admin 3: /* Initial and boundary conditions from CAM-Chem output */

2025-01-24T00:16:59Z

Initial and boundary conditions from CAM-Chem output

← Older revision		Revision as of 02:16, 24 January 2025
Line 1,569:		Line 1,569:
	= Initial and boundary conditions from CAM-Chem output =		= Initial and boundary conditions from CAM-Chem output =

	~~'''~~CAM-Chem data~~'''~~		===CAM-Chem data===

	The Community Atmosphere Model with Chemistry (CAM-Chem) is a component of the Community Earth System Model (CESM) used for simulations of global tropospheric and stratospheric atmospheric composition. The chemistry in CAM-Chem is based on the Model for Ozone and Related Chemical Tracers (MOZART) mechanism. The latest release is CESM2, using the MOZART-T1 mechanism detailed in [Emmons, 2020].		The Community Atmosphere Model with Chemistry (CAM-Chem) is a component of the Community Earth System Model (CESM) used for simulations of global tropospheric and stratospheric atmospheric composition. The chemistry in CAM-Chem is based on the Model for Ozone and Related Chemical Tracers (MOZART) mechanism. The latest release is CESM2, using the MOZART-T1 mechanism detailed in [Emmons, 2020].
Line 1,584:		Line 1,584:
	''Gas phase chemistry in ICON-ART uses the atmospheric chemistry module MECCA (Module Efficiently Calculating the Chemistry of the Atmosphere). In the current version (MECCA 4.0) only an older version (MOZART-4 [Emmons, 2010]) of the MOZART chemical mechanism is implemented, while its latest expansion, MOZART-T1, is not. However, one can simply add the MOZART-T1 chemical mechanism to the base version of MECCA by specifying new chemical species, reactions and rate coefficients. This allows the use of CAM-Chem output data as described above.''		''Gas phase chemistry in ICON-ART uses the atmospheric chemistry module MECCA (Module Efficiently Calculating the Chemistry of the Atmosphere). In the current version (MECCA 4.0) only an older version (MOZART-4 [Emmons, 2010]) of the MOZART chemical mechanism is implemented, while its latest expansion, MOZART-T1, is not. However, one can simply add the MOZART-T1 chemical mechanism to the base version of MECCA by specifying new chemical species, reactions and rate coefficients. This allows the use of CAM-Chem output data as described above.''

	<details>
	<summary>Table with species available in CAM-Chem output</summary>		<summary>Table with species available in CAM-Chem output</summary>

Line 1,731:		Line 1,730:
	</details>		</details>

	~~'''~~Pre-processing~~'''~~		=== Pre-processing ===

	This subsection is based on [Aubet, 2021].

	Throughout we assume that the chemistry data is provided by CAM-Chem output (MOZART chemistry). We will lay out the pre-processing steps needed to merge the chemical with the meteorological fields, as required when using the Online Emission Module (OEM) in ICON-ART. The chemistry data is given on 56 vertical levels, while the meteorological fields are defined on 137 levels. Thus, vertical interpolation of the chemical fields has to be performed. Moreover, the chemistry data is contained in one single file with a time step of 6 hours. One has to separate the file into multiple files containing one single time step each and subsequently interpolate the data to obtain the same time resolution as for the meteorological variables.		Throughout we assume that the chemistry data is provided by CAM-Chem output (MOZART chemistry). We will lay out the pre-processing steps needed to merge the chemical with the meteorological fields, as required when using the Online Emission Module (OEM) in ICON-ART. The chemistry data is given on 56 vertical levels, while the meteorological fields are defined on 137 levels. Thus, vertical interpolation of the chemical fields has to be performed. Moreover, the chemistry data is contained in one single file with a time step of 6 hours. One has to separate the file into multiple files containing one single time step each and subsequently interpolate the data to obtain the same time resolution as for the meteorological variables.

Admin 3: /* Running a Limited Area Mode (LAM) Simulation */

2025-01-24T00:14:05Z

Running a Limited Area Mode (LAM) Simulation

Show changes

Admin 3: /* All input data required for ART standard configurations */

2025-01-23T23:57:47Z

All input data required for ART standard configurations

← Older revision		Revision as of 01:57, 24 January 2025
Line 1,568:		Line 1,568:
	If you want to generate a finer grid (e.g. R2B10) you might have to increase the allocated memory (-m 64000).		If you want to generate a finer grid (e.g. R2B10) you might have to increase the allocated memory (-m 64000).

	== All input data required for ART standard configurations ==		= All input data required for ART standard configurations =
	=== XML files are [https://gitlab.dkrz.de/icon/icon-model/-/tree/release-2024.10-public/externals/art/runctrl%20examples/xml%20ctrl?ref%20type=heads here] ===		=== XML files are [https://gitlab.dkrz.de/icon/icon-model/-/tree/release-2024.10-public/externals/art/runctrl%20examples/xml%20ctrl?ref%20type=heads here] ===

Admin 3: /* Perturbation of the Lateral Boundary Tracer Conditions */

2025-01-23T23:56:47Z

Perturbation of the Lateral Boundary Tracer Conditions

← Older revision		Revision as of 01:56, 24 January 2025
Line 1,465:		Line 1,465:
	== Perturbation of the Lateral Boundary Tracer Conditions ==		== Perturbation of the Lateral Boundary Tracer Conditions ==

	As described in the section ~~[https://gitlab.empa.ch/abt503/user-guides/-/wikis/OEM_User_Guide#perturbation-of-tracer-boundary-conditions '''~~Perturbation of Tracer Boundary Conditions~~''']~~, adding the XML tag oem_bg_ens of type string to an ensemble member and setting it to the name of the background tracer (e.g., <oem_bg_ens type="char">CH4_BG</oem_bg_ens>) includes the background tracer field in the ensemble member. The background is scaled using the scaling factors provided in boundary_lambda_nc = 'background_lambdas.nc' based on the region mask defined in boundary_regions_nc = 'boundary_mask.nc'.		As described in the section Perturbation of Tracer Boundary Conditions, adding the XML tag oem_bg_ens of type string to an ensemble member and setting it to the name of the background tracer (e.g., <oem_bg_ens type="char">CH4_BG</oem_bg_ens>) includes the background tracer field in the ensemble member. The background is scaled using the scaling factors provided in boundary_lambda_nc = 'background_lambdas.nc' based on the region mask defined in boundary_regions_nc = 'boundary_mask.nc'.

	Technically, the background field is added to the ensemble member in the routine art_oem_add_bg_ens (from the module mo_art_oem_ensemble). The background tracer concentrations are scaled with the corresponding perturbation scaling factors. During the simulation, only the tendencies of the background field at the boundary grid cells are scaled. For the first lateral boundary timestep, this occurs synchronously in the subroutine art_oem_emissions (on the variable p_nh_state%diag%grf_tend_tracer()), while for subsequent timesteps, it happens asynchronously in the subroutine compute_boundary_tendencies (from the module mo_async_latbc_utils()).		Technically, the background field is added to the ensemble member in the routine art_oem_add_bg_ens (from the module mo_art_oem_ensemble). The background tracer concentrations are scaled with the corresponding perturbation scaling factors. During the simulation, only the tendencies of the background field at the boundary grid cells are scaled. For the first lateral boundary timestep, this occurs synchronously in the subroutine art_oem_emissions (on the variable p_nh_state%diag%grf_tend_tracer()), while for subsequent timesteps, it happens asynchronously in the subroutine compute_boundary_tendencies (from the module mo_async_latbc_utils()).

Admin 3: /* Technical Implementation of OEM */

2025-01-23T23:54:38Z

Technical Implementation of OEM

← Older revision		Revision as of 01:54, 24 January 2025
Line 1,456:		Line 1,456:

	<math> F_i = \sum_{c=1}^{n} F_{i,cat}^{gridded} \times \lambda_{cat,c}^{hour-of-day} \times \lambda_{cat,c}^{day-of-week} \times \lambda_{cat,c}^{month-of-year} \times \lambda_{i,c}^{vertical} </math>		<math> F_i = \sum_{c=1}^{n} F_{i,cat}^{gridded} \times \lambda_{cat,c}^{hour-of-day} \times \lambda_{cat,c}^{day-of-week} \times \lambda_{cat,c}^{month-of-year} \times \lambda_{i,c}^{vertical} </math>

			== Generation of a Flux Ensemble ==

			The flux ensemble is computed online within the routine art_oem_compute_emissions, which also handles the "regular" online emissions. For each OEM emission tracer, the routine checks if an ensemble with perturbed fluxes is to be generated. If so, it loops through all ensemble members associated with the tracer and applies an additional scaling factor to compute the tracer's emissions at each grid cell:

			<math> F_i = \sum_{c=1}^{n} F_{i,cat}^{gridded} \times \lambda_{cat,c}^{hour-of-day} \times \lambda_{cat,c}^{day-of-week} \times \lambda_{cat,c}^{month-of-year} \times \lambda_{i,cat}^{vertical} \times \color{red} \lambda_{i,cat}^{perturbation} </math>

			== Perturbation of the Lateral Boundary Tracer Conditions ==

			As described in the section [https://gitlab.empa.ch/abt503/user-guides/-/wikis/OEM_User_Guide#perturbation-of-tracer-boundary-conditions '''Perturbation of Tracer Boundary Conditions'''], adding the XML tag oem_bg_ens of type string to an ensemble member and setting it to the name of the background tracer (e.g., <oem_bg_ens type="char">CH4_BG</oem_bg_ens>) includes the background tracer field in the ensemble member. The background is scaled using the scaling factors provided in boundary_lambda_nc = 'background_lambdas.nc' based on the region mask defined in boundary_regions_nc = 'boundary_mask.nc'.

			Technically, the background field is added to the ensemble member in the routine art_oem_add_bg_ens (from the module mo_art_oem_ensemble). The background tracer concentrations are scaled with the corresponding perturbation scaling factors. During the simulation, only the tendencies of the background field at the boundary grid cells are scaled. For the first lateral boundary timestep, this occurs synchronously in the subroutine art_oem_emissions (on the variable p_nh_state%diag%grf_tend_tracer()), while for subsequent timesteps, it happens asynchronously in the subroutine compute_boundary_tendencies (from the module mo_async_latbc_utils()).

	= Running a Limited Area Mode (LAM) Simulation =		= Running a Limited Area Mode (LAM) Simulation =

Admin 3: /* Boundary Data */

2025-01-23T23:51:21Z

Boundary Data

← Older revision		Revision as of 01:51, 24 January 2025
Line 1,481:		Line 1,481:

	------		------
	[[#Aerosol Tracers]]

	== Creating A Nested ICON-Grid ==		== Creating A Nested ICON-Grid ==

Admin 3: /* Online emission module (OEM) */

2025-01-23T23:50:33Z

Online emission module (OEM)

@@ Line 1,384: / Line 1,384: @@
     * `ens`: number of ensemble members (i.e., number of tracers with the `oem_type` set to `ens`)
     * `reg`: number of scaling regions (same as in `boundary_mask.nc`)
 = Running a Limited Area Mode (LAM) Simulation =

Admin 3: /* Running a Limited Area Mode (LAM) Simulation */

2025-01-23T23:47:07Z

Running a Limited Area Mode (LAM) Simulation

← Older revision		Revision as of 01:47, 24 January 2025
Line 1,385:		Line 1,385:
	* `reg`: number of scaling regions (same as in `boundary_mask.nc`)		* `reg`: number of scaling regions (same as in `boundary_mask.nc`)

	== Running a Limited Area Mode (LAM) Simulation ==		= Running a Limited Area Mode (LAM) Simulation =

	=== General ===		=== General ===

Admin 3: /* Online emission module (OEM) */

2025-01-23T23:46:07Z

Online emission module (OEM)

← Older revision		Revision as of 01:46, 24 January 2025
Line 1,230:		Line 1,230:
	* In any case, double check if all emission tags have been assigned to the correct tracer		* In any case, double check if all emission tags have been assigned to the correct tracer

	== Online emission module (OEM) ==		= Online emission module (OEM) =
	=== Introduction ===		=== Introduction ===