Common recipes¶

Set liquid clouds (clwc) and liquid ice (ciwc) to 0¶

It is possible to drop liquid clouds and ice variables and assign them to a custom value, including 0. The benefit is often huge, as we can drop two variables (single nudging file) or two NetCDF files (multi-file setup). Furthermore, some of the analysis performed by the IPSL-CM-LAM team show little impact of 0 value on the final simulation.

Remove uneccessary data¶

In the case of a single nudging_forcing.nc file, there is nothing to do as the clwc and ciwc variables will be skipped. However, you can also remove them and prepare a thinner nudging file.

On the other hand, with a multi-file setup you should modify the COMP/dynamico.card, so that the clwc.nc and ciwc.nc files (or other names) are not copied anymore. Copying them is not a problem, however it takes precious simulation time:

 [BoundaryFiles]
 List = (${config_UserChoices_ForcingDataDir}/q_${year}.nc, q.nc), \
-       (${config_UserChoices_ForcingDataDir}/clwc_${year}.nc, clwc.nc), \
-       (${config_UserChoices_ForcingDataDir}/ciwc_${year}.nc, ciwc.nc), \
        (${config_UserChoices_ForcingDataDir}/r_${year}.nc, r.nc), \
        (${config_UserChoices_ForcingDataDir}/sp_${year}.nc, sp.nc), \
        (${config_UserChoices_ForcingDataDir}/t2m_${year}.nc, t2m.nc), \

Lastly, we edit nudging_dynamico.xml to remove any references to these variables inside input file definitions, in <file id="nudging_in" .../>:

       <field id="H2O_g_nudged_read" name="q" />
-      <field id="H2O_l_nudged_read" name="clwc" />
-      <field id="H2O_s_nudged_read" name="ciwc" />
       <field id="H2O_b_nudged_read" name="cbwc" enabled="false" />

and, in <file id="nudging_in0" ... />:

       <field id="H2O_g_nudged_read0" name="q" />
-      <field id="H2O_l_nudged_read0" name="clwc" />
-      <field id="H2O_s_nudged_read0" name="ciwc" />
       <field id="H2O_b_nudged_read0" name="cbwc" enabled="false" />

Set values to 0¶

Once, the uneccessary data is out of our way we can setup the variables to 0. In order to so, we will use an XIOS trick where we convert data of conforming size, from an existing variable, to 0 at each timestep. The q variable of specific humidity is perfect for this task as it has the required size (surface variables z and sp would not work here).

All required changes are applied inside <field_definition> tag in the nudging_dynamico.xml file.

 <field id="H2O_l_nudged_horiz_interp"
-       field_ref="H2O_l_nudged_read"
+       field_ref="H2O_g_nudged_read"
        domain_ref="from_nudged"
        axis_ref="axis_nudged"
-/>
+>this*0.</field>
 <field id="H2O_s_nudged_horiz_interp"
-       field_ref="H2O_s_nudged_read"
+       field_ref="H2O_g_nudged_read"
        domain_ref="from_nudged"
        axis_ref="axis_nudged"
-/>
+>this*0.</field>
 <field id="H2O_l_nudged_horiz_interp0"
-       field_ref="H2O_l_nudged_read0"
+       field_ref="H2O_g_nudged_read0"
        domain_ref="from_nudged"
        axis_ref="axis_nudged"
-/>
+>this*0.</field>
 <field id="H2O_s_nudged_horiz_interp0"
-       field_ref="H2O_s_nudged_read0"
+       field_ref="H2O_g_nudged_read0"
        domain_ref="from_nudged"
        axis_ref="axis_nudged"
-/>
+>this*0.</field>

Every nudging-forcing variable must go through the interpolation process. This is where we inject the zeros. The H2O_l and H2O_s represent liquid clouds (clwc) and liquid ice (ciwc), respectively. First, we make sure these fields take data from the specific humidity variable q (here H2O_g) by setting the field_ref to H2O_g_nudged_read or H2O_g_nudged_read0.

Finally, we convert the incoming humidity data into 0, by taking a current timestep value this and multiplying it by 0.. If you want a constant value C instead, you could write this*0.+C, but is there even a reason to try that?

Running simulations beyond year 2014¶

...