Dust Cycle in Mars PCM5 - Revision history

Emillour at 12:55, 21 April 2026

2026-04-21T12:55:51Z

Jbclement: Addition of explanations about Conrath dust

2025-08-26T14:07:25Z

Addition of explanations about Conrath dust

Emillour at 15:24, 22 August 2025

2025-08-22T15:24:48Z

Emillour: Created page with "This page details at different levels how to use and what is featured in the dust cycle in Mars PCM5. == Brief Overview == The reference work leading to the implementation in..."

2025-08-22T14:27:41Z

Created page with "This page details at different levels how to use and what is featured in the dust cycle in Mars PCM5. == Brief Overview == The reference work leading to the implementation in..."

New page

This page details at different levels how to use and what is featured in the dust cycle in Mars PCM5.

== Brief Overview ==
The reference work leading to the implementation in the PCM is the PhD work of J.-B. Madeleine; check out his PhD manuscript and 2011 JGR article
"Revisiting the radiative impact of dust on Mars using the LMD Global Climate Model" https://doi.org/10.1029/2011JE003855

The main features and concepts on how the dust is handled are:
* Dust is modeled as a log-normal population (varying in size), which in the end requires managing only two ''tracers'', the first two moments of the distribution, which are the dust mass mixing ratio and number (tracers ''dust_mass'' and ''dust_number'').
* All the physical processes like large scale advection, mixing by the turbulence in the planetary boundary layer, sedimentation, etc. are modeled.
* How the dust gets injected in the atmosphere (i.e. the details of dust lifting from the surface) is not modeled; instead we use a simple assumption that there is always some injection of dust from the surface (most of it simply falling back down; but some of it, when the conditions are right, propagates)
* In addition, the dust in each column is rescaled so that its column opacity then matches that of a driving dust scenario (typically derived from observations).

== Flags concerning the dust cycle in a PCM version 5 setup ==
A setup including adequate flags and parameters for a PCM5 dust cycle can be found in the reference [[callphys.def.GCM5|https://trac.lmd.jussieu.fr/Planeto/browser/trunk/LMDZ.MARS/deftank/callphys.def.GCM5] reference provided in deftank.

As mentioned above, there should be the 2 dedicated tracers (dust moments) at hand (i.e. in the traceur.def file):
<pre>
dust_mass
dust_number
</pre>

In practice the relevant callphys.def parameters are:
<syntaxhighlight lang="bash">
#Directory where external input files are:
datadir=/users/lmdz/WWW/planets/mars/datadir

## Dust scenario. Used if the dust is prescribed (i.e. if active=F)
## ~~~~~~~~~~~~~
# =1 Dust opt.deph read in startfi; =2 Viking scenario; =3 MGS scenario,
# =4 Mars Year 24 from TES assimilation (old version of MY24; dust_tes.nc file)
# =6 "cold" (low dust) scenario ; =7 "warm" (high dust) scenario
# =8 "climatology" (our best guess of a typical Mars year) scenario
# =24 Mars Year 24 ; =25 Mars Year 25 (year with a global dust storm) ; ...
# =30 Mars Year 30
iaervar = 26
# Dust opacity at 610 Pa (when constant, i.e. for the iaervar=1 case)
tauvis=0.2
# Dust vertical distribution:
# (=0: old distrib. (Pollack90), =1: top set by "topdustref",
# =2: Viking scenario; =3 MGS scenario)
iddist = 3
# Dust top altitude (km). (Matters only if iddist=1)
topdustref = 55.
</syntaxhighlight>
* '''iaervar''' points to the driving dust scenario (daily maps; netcdf files located under '''datadir''') to use: e.g. ''dust_clim.nc'' if <code>iaervar=8</code>, ''dust_MY30.nc'' if <code>iaervar=30</code>, etc. In the special case where <code>iaervar=1</code> then the driving dust column opacity is constant (over space and time) to the value specified by flag '''tauvis'''.
* '''tauvis''' is only used when <code>iaervar=1</code> in which case it is the imposed value of the column dust opacity (at reference pressure of 610Pa).
* '''iddist''' and '''topdustref''' are not used (date back to even simpler setup)
<syntaxhighlight lang="bash">
## Tracer (dust water, ice and/or chemical species) options :
## ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# DUST: Transported dust ? (if >0, use 'dustbin' dust bins)
dustbin = 2
# DUST: Radiatively active dust ? (matters if dustbin>0)
active = .true.
# DUST: use mass and number mixing ratios to predict dust size ?
doubleq = .true.
# DUST: use a small population of dust particules (submicron dust)?
submicron = .false.
# DUST: lifted by GCM surface winds ?
lifting = .true.
# DUST: lifted by dust devils ?
callddevil = .false.
# DUST: Scavenging by H2O/CO2 snowfall ?
scavenging = .true.
</syntaxhighlight>
* '''dustbin''' should be 2, because using the 2-moment scheme (with <code>doubleq=.true.</code>).
* '''active''' should definitely be set to <code>.true.</code>, to account for the radiative effect of dust.
* '''doubleq''' should be <code>.true.</code> (with <code>dustbin=2</code>), to use the two-moment scheme
* '''submicron''' should be <code>.false.</code>; was put there to eventually have a second distribution of small particles around. Not used nor validated.
* '''lifting''' should be <code>.true.</code>, to impose continuous dust injection from the surface into the first atmospheric layer.
* '''callddevil''' should be <code>.false.</code>; was put there to eventually account for dust injection via dust devils. Not used nor validated.
* '''scavenging ''' should be <code>.true.</code> to include scavenging of dust by H2O and or CO2 snowfall (assuming CO2 and/or H2O cycles are also computed). Significant effect in the polar night.
<syntaxhighlight lang="bash">
# SCATTERERS: set number of scatterers. must be compliant with preceding options.
naerkind = 2
</syntaxhighlight>
* '''nearkind ''' is the number of radiatively active scatterers. Dust is one of them (if <code>active=.true.</code>) so nearkind should be at least 1; and if the water cycle is also computed with radiatively active clouds (<code>water=.true.</code> and <code>activice=.true.</code>) then <code>naerkind=2</code>

== More technical stuff, and how/where it is managed in the Mars PCM code ==
....TODO....

[[Category:Mars-Model]]

@@ Line 96: / Line 96: @@
 If one wants to use a very simple scheme for dust instead of the usual 'doubleq' (and 'active') dust, it is possible to use an old parametrization based on '''"Conrath dust"'''. In this case, the dust follows the "Conrath profile" and the radiative effect of dust is still included. This simple parametrization can be useful for some tests under idealized conditions like for the 1D model.
-In "callphys.def", the necessary flags are <code>doubleq = .false.</code> and <code>dustbin = 0</code>. So there is no dust-related tracer in "traceur.def" and <code>naerkind = 1</code>.
+In "callphys.def", the necessary flags are <code>doubleq = .false.</code>, <code>dustbin = 0</code> and <code>active  = .false.</code>. So there is no dust-related tracer in "traceur.def" and <code>naerkind = 1</code>.
 This is actually the default choice for the main scatterer. The "Conrath dust" can be used with different dust scenarios (<code>iaervar</code>) and dust vertical distributions (<code>iddist</code>). In line with the aim to get the simplest case, one can choose <code>iddist = 0</code> to set the old dust vertical distribution function (pollack90) depending only on the dust scenario (for example <code>iaervar = 1</code> to define a simple case).
 [[Category:Mars-Model]]

@@ Line 91: / Line 91: @@
 * '''freedust''' : this parameter should be <code>freedust=.false.</code>, so that there is rescaling of the dust using the "tauscaling" coefficient
 * '''dustscaling_mode''' : this parameter should be <code>dustscaling_mode=1</code>
 [[Category:Mars-Model]]

@@ Line 79: / Line 79: @@
 == More technical stuff, and how/where it is managed in the Mars PCM code ==
 ....TODO....
 [[Category:Mars-Model]]