Simulating a Point Source - Revision history

Editor 2: Some minor changes

2023-10-26T08:18:38Z

Some minor changes

← Older revision		Revision as of 10:18, 26 October 2023
Line 1:		Line 1:
	In this tutorial, the steps to simulate a volcanic eruption via a point source are given.		In this tutorial, the steps to simulate a volcanic eruption via a point source are given.

	<gallery mode="slideshow">
	File:Pointsource.gif ~~\| Pointsource simulation of the Raikoke eruption in June 2019.~~		[[File:Pointsource.gif]]
	</gallery>
	== Setting up ICON-ART ==		== Setting up ICON-ART ==

Line 19:		Line 18:
	== Setting up the Runscript ==		== Setting up the Runscript ==

	The function of the runscript is to set up the directory structure,link the relevant files and create the namelists.		The function of the runscript is to set up the directory structure, link the relevant files and create the namelists, which are grouped into several namelist files.

	== Setting up the .xml's ==		== Setting up the .xml's ==
Line 134:		Line 133:


	Now, the external parameters and chemistry files are linked into the output directory, so that ~~after~~ ~~running~~ the ~~simulation it~~ can be ~~identified~~ ~~which~~ ~~run specific settings have~~ ~~been~~ ~~used.~~		Now, the external parameters and chemistry files are linked into the output directory, so that ICON and the user can find it in the output directory
	<syntaxhighlight line lang=bash class="mw-collapsible-content">		<syntaxhighlight line lang=bash class="mw-collapsible-content">
	ln -sf ${DATADIR}/icon_grid_0024_R02B06_G.nc ${OUTDIR}/iconR2B06-DOM01.nc		ln -sf ${DATADIR}/icon_grid_0024_R02B06_G.nc ${OUTDIR}/iconR2B06-DOM01.nc
Line 167:		Line 166:
	In the next step, namelist files are created. They contain the individual namelists which control the settings of the different modules of icon. They are written into the output directory and read by icon during a run.		In the next step, namelist files are created. They contain the individual namelists which control the settings of the different modules of icon. They are written into the output directory and read by icon during a run.
	First the master namelist is created, which most importantly contains the start and stop date, as well as the possibility to restart a run.		First the master namelist is created, which most importantly contains the start and stop date, as well as the possibility to restart a run.
	The next namelist created is called "NAMELIST_Raikoke-June-2019". Here a lot of the model setup is taking place. It is subdivided into different ~~smaller namelist parts~~, which all do their part to set up a different part of the model.		The next namelist file created is called "NAMELIST_Raikoke-June-2019". Here a lot of the model setup is taking place. It is subdivided into different namelists, which all do their part to set up a different part of the model.
	Some important namelists for this simulation are:		Some important namelists for this simulation are:
	* grid_nml (line 35): Here the grid on which the simulation is taking place is given		* grid_nml (line 35): Here the grid on which the simulation is taking place is given
Line 428:		Line 427:
	</syntaxhighlight>		</syntaxhighlight>

	With the namelists set, we can now prepare the simulation for running. Since a lot of setup is required for running, this is also prepared within the runscript and then later executed. The following part is highly dependant on the HPC system configuration. The following setup works on the DKRZ Levante HPC system:		With the namelists set, we can now prepare the simulation for running. Since a lot of setup is required for running, this is also prepared within the runscript and then later executed. The following part is highly dependant on the HPC system configuration. The following setup works on the DKRZ Levante HPC system (July 2023):

	<syntaxhighlight line lang=bash class="mw-collapsible-content">		<syntaxhighlight line lang=bash class="mw-collapsible-content">
Line 490:		Line 489:
	$ ./myrunfile		$ ./myrunfile
	</syntaxhighlight>		</syntaxhighlight>
	This will then create all the ~~Namelists~~ and the runscript job_ICON. To submit the icon run, go to the output directory, make the runscript executable, and run it:		This will then create all the Namelist files and the runscript job_ICON. To submit the icon run, go to the output directory, make the runscript executable, and run it:
	<syntaxhighlight lang=bash class="mw-collapsible-content">		<syntaxhighlight lang=bash class="mw-collapsible-content">
	$ cd /path/to/your/output		$ cd /path/to/your/output

Editor 2: fixed some typos and wording, added plot for pythonscripts and instructions how to run it

2023-10-18T08:13:03Z

fixed some typos and wording, added plot for pythonscripts and instructions how to run it

← Older revision		Revision as of 10:13, 18 October 2023
Line 1:		Line 1:
	___ Work in Progress ___

	In this tutorial, the steps to simulate a volcanic eruption via a point source are given.		In this tutorial, the steps to simulate a volcanic eruption via a point source are given.
	<gallery mode="slideshow">		<gallery mode="slideshow">
Line 7:		Line 5:
	== Setting up ICON-ART ==		== Setting up ICON-ART ==

	The first thing to do is having a working installation of ICON-~~art~~. To check if your icon version has been built correctly, you can check if		The first thing to do is having a working installation of ICON-ART. To check if your icon version has been built correctly, you can check if
	your_icon_folder/bin/icon.exe		your_icon_folder/bin/icon.exe
	exists.		exists.
Line 36:		Line 34:
	This can be adapted as needed.		This can be adapted as needed.

	In this example, the Raikoke eruption on 21 of June 2019 is simulated, as can be seen in the following .xml:		In this example the Raikoke eruption on 21 of June 2019 is simulated, as can be seen in the following .xml:

	<syntaxhighlight line lang=xml class="mw-collapsible-content">		<syntaxhighlight line lang=xml class="mw-collapsible-content">
Line 104:		Line 102:
	The first step is to set the relevant directories, so that the XML data we provide as well as the path to the ICON model can be found and accessed easily.		The first step is to set the relevant directories, so that the XML data we provide as well as the path to the ICON model can be found and accessed easily.
	In this simulation, external data such as a grid containing external parameter data is required. The directory containing the data is set as DATADIR.		In this simulation, external data such as a grid containing external parameter data is required. The directory containing the data is set as DATADIR.
	The output directory is where the model will write the output into, as well as linking a lot of relevant files used in the simulation.		The output directory is where the model will write the output NetCDF files into, as well as linking a lot of relevant files used in the simulation.

	<syntaxhighlight line lang=bash class="mw-collapsible-content">		<syntaxhighlight line lang=bash class="mw-collapsible-content">
Line 136:		Line 134:


	Now, the external parameters and chemistry files are linked into the output directory, so that after running the simulation it can be identified which have been used.		Now, the external parameters and chemistry files are linked into the output directory, so that after running the simulation it can be identified which run specific settings have been used.
	<syntaxhighlight line lang=bash class="mw-collapsible-content">		<syntaxhighlight line lang=bash class="mw-collapsible-content">
	ln -sf ${DATADIR}/icon_grid_0024_R02B06_G.nc ${OUTDIR}/iconR2B06-DOM01.nc		ln -sf ${DATADIR}/icon_grid_0024_R02B06_G.nc ${OUTDIR}/iconR2B06-DOM01.nc
Line 167:		Line 165:
	</syntaxhighlight>		</syntaxhighlight>

	In the next step, we ~~create~~ the namelists. They are written into the output directory.		In the next step, namelist files are created. They contain the individual namelists which control the settings of the different modules of icon. They are written into the output directory and read by icon during a run.
	First the master namelist is created, which most importantly contains the start and stop date, as well as the possibility to restart a run.		First the master namelist is created, which most importantly contains the start and stop date, as well as the possibility to restart a run.
	The next namelist created is called "NAMELIST_Raikoke-June-2019". Here a lot of the model setup is taking place. It is subdivided into different smaller namelist parts, which all do their part to set up a different part of the model.		The next namelist created is called "NAMELIST_Raikoke-June-2019". Here a lot of the model setup is taking place. It is subdivided into different smaller namelist parts, which all do their part to set up a different part of the model.
Line 487:		Line 485:
	</syntaxhighlight>		</syntaxhighlight>
	This concludes the runfile.		This concludes the runfile.
	The Job_ICON-file that has been produced in the last step can then be executed. For that, ~~firstly~~ the runfile hast to be run using bash:		The Job_ICON-file that has been produced in the last step can then be executed. For that, the runfile hast to be run using bash:
	<syntaxhighlight lang=bash class="mw-collapsible-content">		<syntaxhighlight lang=bash class="mw-collapsible-content">
	$ chmod +x myrunfile		$ chmod +x myrunfile
	$ ./myrunfile		$ ./myrunfile
	</syntaxhighlight>		</syntaxhighlight>
	This will then create all the Namelists and the runscript job_ICON. To ~~then~~ submit the icon run, go to the output directory, make the runscript executable, and run it:		This will then create all the Namelists and the runscript job_ICON. To submit the icon run, go to the output directory, make the runscript executable, and run it:
	<syntaxhighlight lang=bash class="mw-collapsible-content">		<syntaxhighlight lang=bash class="mw-collapsible-content">
	$ cd /path/to/your/output		$ cd /path/to/your/output
Line 498:		Line 496:
	$ sbatch job_ICON		$ sbatch job_ICON
	</syntaxhighlight>		</syntaxhighlight>
	~~with that,~~ the Job should be submitted. The submission status can be seen with		Now the Job should be submitted. The submission status can be seen with
	<syntaxhighlight lang=bash class="mw-collapsible-content">		<syntaxhighlight lang=bash class="mw-collapsible-content">
	$ squeue --user your_username		$ squeue --user your_username
	</syntaxhighlight>		</syntaxhighlight>

	If everything went well, in the ~~Output~~ directory there will be output files generated with names like Raikoke-June-2019-forecast_mode-remap_DOM01_ML_0001.nc		If everything went well, in the output directory there will be output files generated with names like Raikoke-June-2019-forecast_mode-remap_DOM01_ML_0001.nc
	== Inspecting the Output ==		== Inspecting the Output ==
	In this example, the output is created in the form of several NetCDF4 (.nc) files. To avoid having one giant file, it is subdivided into several files containing a fixed amount of timesteps. The quickest way to inspect a NetCDF file is with [https://code.mpimet.mpg.de/projects/cdo CDO]:		In this example, the output is created in the form of several NetCDF4 (.nc) files. To avoid having one giant file, it is subdivided into several files containing a fixed amount of timesteps. The quickest way to inspect a NetCDF file is with [https://code.mpimet.mpg.de/projects/cdo CDO]:
Line 519:		Line 517:
	import matplotlib.pyplot as plt # Library to produce Plots		import matplotlib.pyplot as plt # Library to produce Plots
	import xarray as xr # reading in of netCDF data, optimized for large datasets		import xarray as xr # reading in of netCDF data, optimized for large datasets
			from glob import glob
	import cartopy.crs as ccrs # plotting things on a map		import cartopy.crs as ccrs # plotting things on a map

Line 549:		Line 548:
	# in this simulation there are 144 timesteps and 144 files each containing one timestep		# in this simulation there are 144 timesteps and 144 files each containing one timestep
	# To produce a plot for each timestep, you can also loop the rest of this file over i		# To produce a plot for each timestep, you can also loop the rest of this file over i
	i = 1		i = 30

	#load the NetCDF file containing the timestep		#load the NetCDF file containing the timestep
Line 588:		Line 587:

	</syntaxhighlight>		</syntaxhighlight>
			To run the script, you need a working python version and the packages listed in the beginning of the script. Dont forget to make the file executable in order to run it using <code> chmod +x plotscript </code>.
			The resulting Plot will look something like this: [[File:Example SO2 130.png]]

Admin 2: Small correction of some typos

2023-10-17T14:07:06Z

Small correction of some typos

Editor 2: updated draft

2023-10-12T09:04:34Z

updated draft

Show changes

Luca R: Syntaxhighlighting

2023-09-07T08:32:39Z

Syntaxhighlighting

← Older revision		Revision as of 10:32, 7 September 2023
Line 38:		Line 38:
	In this example, the Raikoke eruption on 21. of June 2019 is Simulated, as can be seen in the following .xml:		In this example, the Raikoke eruption on 21. of June 2019 is Simulated, as can be seen in the following .xml:

	<~~pre~~ class="mw-collapsible-content">		<syntaxhighlight line lang=xml class="mw-collapsible-content">

	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
Line 95:		Line 95:
	</pntSrc>		</pntSrc>
	</sources>		</sources>
			</syntaxhighlight>
	</pre>

	== Running the Simulation ==		== Running the Simulation ==

Editor 2: added work in Progress disclaimer for now

2023-06-30T10:07:41Z

added work in Progress disclaimer for now

← Older revision		Revision as of 12:07, 30 June 2023
Line 1:		Line 1:
			___ Work in Progress ___

	In this Tutorial, the steps to simulate a Volcanic Eruption via a point source are given.		In this Tutorial, the steps to simulate a Volcanic Eruption via a point source are given.
	<gallery mode="slideshow">		<gallery mode="slideshow">

Editor 2: added Raikoke.gif

2023-06-30T10:03:54Z

added Raikoke.gif

← Older revision		Revision as of 12:03, 30 June 2023
Line 1:		Line 1:
	In this Tutorial, the steps to simulate a Volcanic Eruption via a point source are given.		In this Tutorial, the steps to simulate a Volcanic Eruption via a point source are given.
			<gallery mode="slideshow">

			File:Pointsource.gif \| Pointsource simulation of the Raikoke eruption in June 2019.
			</gallery>
	== Setting up ICON-ART ==		== Setting up ICON-ART ==

Editor 2: /* Setting up the .xml's */ added raikoke .xml

2023-06-28T13:13:02Z

Setting up the .xml's: added raikoke .xml

← Older revision		Revision as of 15:13, 28 June 2023
Line 20:		Line 20:

	== Setting up the .xml's ==		== Setting up the .xml's ==
			Here the .xml
			pntSRC.xml
			is set up. It contains all the necessary information to describe the emission of the here defined aerosols into the atmosphere.
			The following information is contained:
			* where is the Pointsource
			* when is it emitting
			* what substances are emitted
			* how much of each substance is emitted
			* what size are the emitted substances (median and standard deviation)

			This can be adapted as needed.

			In this example, the Raikoke eruption on 21. of June 2019 is Simulated, as can be seen in the following .xml:

			<pre class="mw-collapsible-content">

			<?xml version="1.0" encoding="UTF-8"?>
			<!DOCTYPE tracers SYSTEM "sources_selTrnsp.dtd">

			<sources>
			<pntSrc id="Raikoke-SO2">
			<lon type="real">153.24</lon>
			<lat type="real">49.29</lat>
			<substance type="char">TRSO2</substance>
			<source_strength type="real">46300.0</source_strength>
			<height type="real">14000</height>
			<height_bot type="real">600</height_bot>
			<unit type="char">kg s-1</unit>
			<startTime type="char">2019-06-21T13:00:00</startTime>
			<endTime type="char">2019-06-21T22:00:00</endTime>
			</pntSrc>
			<pntSrc id="Raikoke-ashacc">
			<lon type="real">153.24</lon>
			<lat type="real">49.29</lat>
			<substance type="char">ash_insol_acc</substance>
			<dg3_emiss type="real">0.8E-6</dg3_emiss>
			<sigma_emiss type="real">1.4</sigma_emiss>
			<source_strength type="real">19700.0</source_strength>
			<height type="real">14000</height>
			<height_bot type="real">600</height_bot>
			<unit type="char">kg s-1</unit>
			<startTime type="char">2019-06-21T13:00:00</startTime>
			<endTime type="char">2019-06-21T22:00:00</endTime>
			</pntSrc>
			<pntSrc id="Raikoke-ashcoa">
			<lon type="real">153.24</lon>
			<lat type="real">49.29</lat>
			<substance type="char">ash_insol_coa</substance>
			<dg3_emiss type="real">2.98E-6</dg3_emiss>
			<sigma_emiss type="real">1.4</sigma_emiss>
			<source_strength type="real">19700.0</source_strength>
			<height type="real">14000</height>
			<height_bot type="real">600</height_bot>
			<unit type="char">kg s-1</unit>
			<startTime type="char">2019-06-21T13:00:00</startTime>
			<endTime type="char">2019-06-21T22:00:00</endTime>
			</pntSrc>
			<pntSrc id="Raikoke-ashgiant">
			<lon type="real">153.24</lon>
			<lat type="real">49.29</lat>
			<substance type="char">ash_giant</substance>
			<dg3_emiss type="real">11.35E-6</dg3_emiss>
			<sigma_emiss type="real">1.4</sigma_emiss>
			<source_strength type="real">19700.0</source_strength>
			<height type="real">14000</height>
			<height_bot type="real">600</height_bot>
			<unit type="char">kg s-1</unit>
			<startTime type="char">2019-06-21T13:00:00</startTime>
			<endTime type="char">2019-06-21T22:00:00</endTime>
			</pntSrc>
			</sources>
			</pre>

	== Running the Simulation ==		== Running the Simulation ==

Editor 2 at 11:18, 28 June 2023

2023-06-28T11:18:38Z

← Older revision		Revision as of 13:18, 28 June 2023
Line 16:		Line 16:

	== Setting up the Runscript ==		== Setting up the Runscript ==

			The function of the runscript is to set up the directory structure,link the relevant files and create the namelists.

	== Setting up the .xml's ==		== Setting up the .xml's ==

Editor 2: Created Structure /first draft

2023-06-28T10:41:33Z

Created Structure /first draft

New page

In this Tutorial, the steps to simulate a Volcanic Eruption via a point source are given.

== Setting up ICON-ART ==

The first thing to do is having a working installation of ICON-art. To check if your icon version has been built correctly, you can check if
your_icon_folder/bin/icon.exe
exists.

== Setting up Directories ==

Now a directory structure has to be set up. Usually the following directories are used:
* '''Working Directory''': Here the files that are needed for an individual run are saved. This usually includes the runscript and the relevant .xml files.
* '''Icon Code directory''': This is where the Icon code is stored.
* '''External Data directory''': Here external files which are needed for a run are stored. For example, to parametrize the optical properties of clouds a files like ECHAM6_CldOptProps.nc is used. These files of course can be switched out for others, however in most applications the same ones are used. A list of the used files is given in the Runscript, which then creates a link of these files in the Output directory.
* '''Output directory''': This is where the new Simulation data will be stored. Since most of the time large amounts of data are produced, this is stored in the work or scratch partitions on most HPC Systems. The Namelists produced by the runfile are also stored here.

== Setting up the Runscript ==

== Setting up the .xml's ==

== Running the Simulation ==

== Inspecting the Output ==

== Making a Plot of the Simulation Data ==

← Older revision		Revision as of 16:07, 17 October 2023
Line 1:		Line 1:
	___ Work in Progress ___		___ Work in Progress ___

	In this ~~Tutorial~~, the steps to simulate a ~~Volcanic~~ ~~Eruption~~ via a point source are given.		In this tutorial, the steps to simulate a volcanic eruption via a point source are given.
	<gallery mode="slideshow">		<gallery mode="slideshow">
	File:Pointsource.gif \| Pointsource simulation of the Raikoke eruption in June 2019.		File:Pointsource.gif \| Pointsource simulation of the Raikoke eruption in June 2019.
Line 16:		Line 16:
	* '''Working Directory''': Here the files that are needed for an individual run are saved. This usually includes the runscript and the relevant .xml files.		* '''Working Directory''': Here the files that are needed for an individual run are saved. This usually includes the runscript and the relevant .xml files.
	* '''Icon Code directory''': This is where the Icon code is stored.		* '''Icon Code directory''': This is where the Icon code is stored.
	* '''External Data directory''': Here external files which are needed for a run are stored. For example, to parametrize the optical properties of clouds a files like ECHAM6_CldOptProps.nc is used. These files of course can be switched out for others, however in most applications the same ones are used. A list of the used files is given in the ~~Runscript~~, which then creates a link of these files in the ~~Output~~ directory.		* '''External Data directory''': Here external files which are needed for a run are stored. For example, to parametrize the optical properties of clouds a files like ECHAM6_CldOptProps.nc is used. These files of course can be switched out for others, however in most applications the same ones are used. A list of the used files is given in the runscript, which then creates a link of these files in the output directory.
	* '''Output directory''': This is where the new ~~Simulation~~ data will be stored. Since most of the time large amounts of data are produced, this is stored in the work or scratch partitions on most HPC ~~Systems~~. The ~~Namelists~~ produced by the runfile are also stored here.		* '''Output directory''': This is where the new simulation data will be stored. Since most of the time large amounts of data are produced, this is stored in the work or scratch partitions on most HPC systems. The namelists produced by the runfile are also stored here.

	== Setting up the Runscript ==		== Setting up the Runscript ==
Line 36:		Line 36:
	This can be adapted as needed.		This can be adapted as needed.

	In this example, the Raikoke eruption on 21. of June 2019 is ~~Simulated~~, as can be seen in the following .xml:		In this example, the Raikoke eruption on 21 of June 2019 is simulated, as can be seen in the following .xml:

	<syntaxhighlight line lang=xml class="mw-collapsible-content">		<syntaxhighlight line lang=xml class="mw-collapsible-content">
Line 98:		Line 98:

	== Running the Simulation ==		== Running the Simulation ==
	The setup of the model for the ~~Simulation~~ happens with a runscript. It contains all the different control parameters, such as time ~~Control~~ of the ~~Simulation~~, what equations are going to be used, whether ART is active, and a lot more.		The setup of the model for the simulation happens with a runscript. It contains all the different control parameters, such as time control of the simulation, what equations are going to be used, whether ART is active, and a lot more.
	The ~~Runscript~~ itself is just a text file, which is run via bash to start the simulation. Usually a template file is used and adapted to the specific needs of the ~~User~~ running the ~~Simulation~~.		The runscript itself is just a text file, which is run via bash to start the simulation. Usually a template file is used and adapted to the specific needs of the user running the simulation.
	Here we will go through the runscript for our ~~Pointsource~~ ~~Simulation~~.		Here we will go through the runscript for our pointsource simulation.

	The first step is to set the relevant directories, so that the XML data we provide as well as the path to the ICON model can be found and accessed easily.		The first step is to set the relevant directories, so that the XML data we provide as well as the path to the ICON model can be found and accessed easily.
Line 122:		Line 122:
	</syntaxhighlight>		</syntaxhighlight>

	In the next step, the previously defined ~~Output~~ directory is created, if not already there, and the icon executable is linked into it for easier ~~acces~~ and overview.		In the next step, the previously defined output directory is created, if not already there, and the icon executable is linked into it for easier access and overview.

	<syntaxhighlight line lang=bash class="mw-collapsible-content">		<syntaxhighlight line lang=bash class="mw-collapsible-content">
Line 136:		Line 136:


	Now, the external ~~Parameters~~ and chemistry files are linked into the ~~Output~~ directory, so that after running the simulation it can be identified which have been used.		Now, the external parameters and chemistry files are linked into the output directory, so that after running the simulation it can be identified which have been used.
	<syntaxhighlight line lang=bash class="mw-collapsible-content">		<syntaxhighlight line lang=bash class="mw-collapsible-content">
	ln -sf ${DATADIR}/icon_grid_0024_R02B06_G.nc ${OUTDIR}/iconR2B06-DOM01.nc		ln -sf ${DATADIR}/icon_grid_0024_R02B06_G.nc ${OUTDIR}/iconR2B06-DOM01.nc
Line 167:		Line 167:
	</syntaxhighlight>		</syntaxhighlight>

	In the next step, we create the ~~Namelists~~. They are written into the ~~Output~~ directory.		In the next step, we create the namelists. They are written into the output directory.
	First the ~~Master~~ ~~Namelist~~ is created, which most importantly contains the start and stop date, as well as the possibility to restart a run.		First the master namelist is created, which most importantly contains the start and stop date, as well as the possibility to restart a run.
	The next namelist created is called "NAMELIST_Raikoke-June-2019". Here a lot of the model setup is taking place. It is subdivided into different smaller namelist parts, which all do their part to set up a different part of the model.		The next namelist created is called "NAMELIST_Raikoke-June-2019". Here a lot of the model setup is taking place. It is subdivided into different smaller namelist parts, which all do their part to set up a different part of the model.
	Some important namelists for this simulation are:		Some important namelists for this simulation are:
	* grid_nml (line 35): Here the grid on which the ~~Simulation~~ is taking place is given		* grid_nml (line 35): Here the grid on which the simulation is taking place is given
	* run_nml (line 3): Contains the switch to turn on ICON-ART, as well as set model height levels and timestep length.		* run_nml (line 49): Contains the switch to turn on ICON-ART, as well as set model height levels and timestep length.
	* output_nml (line 225): Defines which variables at which intervals are written in the ~~Output~~ directory		* output_nml (line 225): Defines which variables at which intervals are written in the output directory
	* art_nml (line 238): Contains the switches relevant for ~~icon~~-~~-art~~, see [[Namelist]] for more details. Most importantly, the xml file for the point source emission is linked here		* art_nml (line 238): Contains the switches relevant for ICON-ART, see [[Namelist]] for more details. Most importantly, the xml file for the point source emission is linked here

	<syntaxhighlight line lang=bash class="mw-collapsible-content">		<syntaxhighlight line lang=bash class="mw-collapsible-content">
Line 430:		Line 430:
	</syntaxhighlight>		</syntaxhighlight>

	With the namelists set, we can now prepare the ~~Simulation~~ for running. Since a lot of setup is required for running, this is also prepared within the runscript and then later executed. The following part is highly dependant on the HPC system configuration. The following setup works on the DKRZ Levante HPC system:		With the namelists set, we can now prepare the simulation for running. Since a lot of setup is required for running, this is also prepared within the runscript and then later executed. The following part is highly dependant on the HPC system configuration. The following setup works on the DKRZ Levante HPC system:

	<syntaxhighlight line lang=bash class="mw-collapsible-content">		<syntaxhighlight line lang=bash class="mw-collapsible-content">
Line 512:		Line 512:

	== Making a Plot of the Simulation Data ==		== Making a Plot of the Simulation Data ==
	In order to gain insight into the ~~Simulation~~, as well as an overview, the most common way is to create some plots of different variables of interest. In our case, we want to know what happens to the ash emitted from the Raikoke eruption.		In order to gain insight into the simulation, as well as an overview, the most common way is to create some plots of different variables of interest. In our case, we want to know what happens to the ash emitted from the Raikoke eruption.
	A quick and easy way to create ~~Plots~~ is using python and a reference script to produce a plot similar to the Pointsource animation is given here:		A quick and easy way to create plots is using python and a reference script to produce a plot similar to the Pointsource animation is given here:
	<syntaxhighlight line lang=python class="mw-collapsible-content">		<syntaxhighlight line lang=python class="mw-collapsible-content">
	# first we import the following packages:		# first we import the following packages: