http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/api.php?action=feedcontributions&feedformat=atom&user=Lguez LMDZPedia - Contributions de l’utilisateur [fr] 2026-06-13T14:12:08Z Contributions de l’utilisateur MediaWiki 1.27.7 http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=HowTo:_debug_the_quality_control&diff=517 HowTo: debug the quality control 2025-10-28T15:58:58Z <p>Lguez : </p> <hr /> <div>As explained on the page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité], a number of quality control checks of the code are run every night to ensure that nothing was broken by the most recent commits to the svn depository (note that only the trunk version of the code is tested by this procedure).<br /> <br /> This note explains what to do if those regular tests reveal that the code is broken.<br /> <br /> The checks are launched by the script [https://web.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://web.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh], which actually launches the quality checks. The results of the tests are synthesized in one line and recorded in the file [https://web.lmd.jussieu.fr/~lmdz/pub/src_archives/Readme Readme]. Each line of this file (besides the comments) gives the version of the code being tested, its corresponding svn revision number and the results of the different checks (as explained in the file and the page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité]). The results are in:<br /> <br /> &lt;nowiki&gt;lmdz-cq:/u/lmdz/WWW/RESUBENCH/trunk/gfortran/latest&lt;/nowiki&gt;<br /> <br /> <br /> === How to debug a failed quality check ===<br /> <br /> Once a failed quality check is established, one should look in the file [https://web.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk] to find out which version of the code caused a problem (for example 20211105.trunk). One can then find the output of the quality control check in the directory:<br /> <br /> lmdz-cq:/home/lmdz/tmp/LMDZ[version_number]<br /> <br /> with the actual output file of the check_version.sh script in<br /> <br /> lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.[version_number]<br /> <br /> ('''''lmdz-cq:/tmp/lmdz/LMDZ20211105.trunk''''' and '''''lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.20211105.trunk''''' respectively in our example). This output file is also [https://lmdz.lmd.jussieu.fr/Distrib/WORK accessible on internet].<br /> <br /> One can then go through the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh] comparing with the different output to find out what went wrong. Tests of correction can actually be done in the <br /> lmdz-cq:/home/lmdz/tmp/LMDZ[version_number]<br /> directory.<br /> <br /> [[Category:HowTo]]<br /> [[Category:ExpertDev]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=511 Peau de l'océan 2024-11-14T07:49:00Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects of cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional NetCDF variables can be output in history files when the parameterization is activated:<br /> <br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> <br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> <br /> - s_int: interface salinity, in ppt<br /> <br /> - t_int: interface temperature, in K<br /> <br /> - dter: ocean-air interface temperature minus subskin temperature, in K<br /> <br /> - dser: ocean-air interface salinity minus subskin salinity, in ppt<br /> <br /> - tkt: thickness of cool skin (microlayer), in m<br /> <br /> - tks: thickness of mass diffusion layer (microlayer), in m<br /> <br /> - taur: momentum flux due to rain, in Pa<br /> <br /> - delta_SST: ocean-air interface temperature minus bulk SST, in K<br /> <br /> - delta_sal: ocean-air interface salinity minus bulk salinity, in ppt<br /> <br /> - SSS: bulk sea-surface salinity, in ppt<br /> <br /> Use the XML files to control this output.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=510 Peau de l'océan 2024-11-14T07:48:48Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects of cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional NetCDF variables can be output in history files when the parameterization is activated:<br /> <br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> <br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> <br /> - s_int: interface salinity, in ppt<br /> <br /> - t_int: interface temperature, in K<br /> <br /> - dter: ocean-air interface temperature minus subskin temperature, in K<br /> <br /> - dser: ocean-air interface salinity minus subskin salinity, in ppt<br /> <br /> - tkt: thickness of cool skin (microlayer), in m<br /> <br /> - tks: thickness of mass diffusion layer (microlayer), in m<br /> <br /> - taur: momentum flux due to rain, in Pa<br /> <br /> - delta_SST: ocean-air interface temperature minus bulk SST, in K<br /> <br /> - delta_sal: ocean-air interface salinity minus bulk salinity, in ppt<br /> <br /> - SSS: bulk sea-surface salinity, in ppt<br /> <br /> Use the XMl files to control this output.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=509 Peau de l'océan 2024-10-26T10:50:10Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects of cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional NetCDF variables can be output in history files when the parameterization is activated:<br /> <br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> <br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> <br /> - s_int: interface salinity, in ppt<br /> <br /> - t_int: interface temperature, in K<br /> <br /> - dter: ocean-air interface temperature minus subskin temperature, in K<br /> <br /> - dser: ocean-air interface salinity minus subskin salinity, in ppt<br /> <br /> - tkt: thickness of cool skin (microlayer), in m<br /> <br /> - tks: thickness of mass diffusion layer (microlayer), in m<br /> <br /> - taur: momentum flux due to rain, in Pa<br /> <br /> - delta_SST: ocean-air interface temperature minus bulk SST, in K<br /> <br /> - delta_sal: ocean-air interface salinity minus bulk salinity, in ppt<br /> <br /> - SSS: bulk sea-surface salinity, in ppt</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=508 Peau de l'océan 2024-10-25T15:42:51Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects of cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional NetCDF variables can be output in history files when the parameterization is activated:<br /> <br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> <br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> <br /> - s_int: interface salinity, in ppt<br /> <br /> - t_int: interface temperature, in K<br /> <br /> - dter: ocean-air interface temperature minus subskin temperature, in K<br /> <br /> - dser: ocean-air interface salinity minus subskin salinity, in ppt<br /> <br /> - tkt: thickness of cool skin (microlayer), in m<br /> <br /> - tks: thickness of mass diffusion layer (microlayer), in m<br /> <br /> - taur: momentum flux due to rain, in Pa<br /> <br /> - delta_SST: ocean-air interface temperature minus bulk SST, in K<br /> <br /> - delta_sal: ocean-air interface salinity minus bulk salinity, in ppt<br /> <br /> - SSS: bulk sea-surface salinity, in ppt<br /> <br /> Keywords: ocean skin</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=507 Peau de l'océan 2024-10-25T14:52:45Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects of cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional NetCDF variables can be output in history files when the parameterization is activated:<br /> <br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> <br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> <br /> Keywords: ocean skin<br /> <br /> - s_int: interface salinity, in ppt<br /> <br /> - t_int: interface temperature, in K<br /> <br /> - dter: ocean-air interface temperature minus subskin temperature, in K<br /> <br /> - dser: ocean-air interface salinity minus subskin salinity, in ppt<br /> <br /> - tkt: thickness of cool skin (microlayer), in m<br /> <br /> - tks: thickness of mass diffusion layer (microlayer), in m<br /> <br /> - taur: momentum flux due to rain, in Pa<br /> <br /> - delta_SST: ocean-air interface temperature minus bulk SST, in K<br /> <br /> - delta_sal: ocean-air interface salinity minus bulk salinity, in ppt<br /> <br /> - SSS: bulk sea-surface salinity, in ppt</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=506 Peau de l'océan 2024-10-25T14:48:39Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional NetCDF variables can be output in history files when the parameterization is activated:<br /> <br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> <br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> <br /> Keywords: ocean skin<br /> <br /> - s_int: interface salinity, in ppt<br /> <br /> - t_int: interface temperature, in K<br /> <br /> - dter: ocean-air interface temperature minus subskin temperature, in K<br /> <br /> - dser: ocean-air interface salinity minus subskin salinity, in ppt<br /> <br /> - tkt: thickness of cool skin (microlayer), in m<br /> <br /> - tks: thickness of mass diffusion layer (microlayer), in m<br /> <br /> - taur: momentum flux due to rain, in Pa<br /> <br /> - delta_SST: ocean-air interface temperature minus bulk SST, in K<br /> <br /> - delta_sal: ocean-air interface salinity minus bulk salinity, in ppt<br /> <br /> - SSS: bulk sea-surface salinity, in ppt</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=505 Peau de l'océan 2024-10-25T14:47:51Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional NetCDF variables can be output in history files when the parameterization is activated:<br /> <br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> <br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> <br /> - s_int: interface salinity, in ppt<br /> <br /> - t_int: interface temperature, in K<br /> <br /> - dter: ocean-air interface temperature minus subskin temperature, in K<br /> <br /> - dser: ocean-air interface salinity minus subskin salinity, in ppt<br /> <br /> - tkt: thickness of cool skin (microlayer), in m<br /> <br /> - tks: thickness of mass diffusion layer (microlayer), in m<br /> <br /> - taur: momentum flux due to rain, in Pa<br /> <br /> - delta_SST: ocean-air interface temperature minus bulk SST, in K<br /> <br /> - delta_sal: ocean-air interface salinity minus bulk salinity, in ppt<br /> <br /> - SSS: bulk sea-surface salinity, in ppt</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=504 Peau de l'océan 2024-10-25T14:44:58Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional variables can be output in history NetCDF files when the parameterization is activated:<br /> <br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> <br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> <br /> - s_int: interface salinity, in ppt<br /> <br /> - t_int: interface temperature, in K<br /> <br /> - dter: ocean-air interface temperature minus subskin temperature, in K<br /> <br /> - dser: ocean-air interface salinity minus subskin salinity, in ppt<br /> <br /> - tkt: thickness of cool skin (microlayer), in m<br /> <br /> - tks: thickness of mass diffusion layer (microlayer), in m<br /> <br /> - taur: momentum flux due to rain, in Pa</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=503 Peau de l'océan 2024-10-25T14:26:57Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.<br /> <br /> Some additional variables can be output in history NetCDF files when the parameterization is activated:<br /> - ds_ns: subskin salinity minus foundation salinity, in ppt<br /> - dt_ns: subskin temperature minus foundation temperature, in K<br /> - s_int: interface salinity, in ppt<br /> - t_int: interface temperature, in K<br /> - dter<br /> - dser<br /> - tkt<br /> - tks<br /> - taur</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=502 Peau de l'océan 2024-10-25T14:02:21Z <p>Lguez : </p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects cool skin, warm layer and fresh water lenses, in this order. The default value is 3.<br /> <br /> The variable depth_1 can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. depth_1 should be set to a real positive value. It is the depth, in m, at which the temperature and salinity are input. It could be the depth at the middle of the first layer of an ocean model (half the depth of the first layer). Setting depth_1 to any value &gt;= 3 has the same effect as setting depth_1 to 3. The default value is 20.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Peau_de_l%27oc%C3%A9an&diff=501 Peau de l'océan 2024-10-25T13:56:41Z <p>Lguez : Page créée avec « The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (paramete... »</p> <hr /> <div>The parameterization of the ocean skin of Bellenger et al. (2017) can be activated by setting: activate_ocean_skin = 1 or 2 in physiq.def. The default value is 0 (parameterization not activated). If activate_ocean_skin = 1 then the parameterization is activated in diagnostic mode only: it has no retroaction on LMDZ. If activate_ocean_skin = 2 then the parameterization is activated with retroaction on LMDZ.<br /> <br /> The variable flag_ocean_skin can be set in physiq.def. This variable is only read if activate_ocean_skin &gt;= 1. flag_ocean_skin can be set to an integer value between 1 and 3, for cumulative effects cool skin, warm layer and fresh water lenses, in this order. The default value is 3.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=444 Strataer 2024-04-10T17:47:49Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportés, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Une exécution de LMDZ avec Strataer peut partir de fichiers restart d'une exécution sans Strataer.<br /> <br /> Références :<br /> * https://doi.org/10.5194/gmd-10-3359-2017<br /> * https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Strataer est activé avec l'option &lt;code&gt;-strataer true&lt;/code&gt; de &lt;code&gt;makelmdz_fcm&lt;/code&gt;.<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=443 Strataer 2024-04-10T17:46:23Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportés, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ.<br /> <br /> Une exécution de LMDZ avec Strataer peut partir de fichiers restart d'une exécution sans Strataer.<br /> <br /> Références :<br /> * https://doi.org/10.5194/gmd-10-3359-2017<br /> * https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Strataer est activé avec l'option &lt;code&gt;-strataer true&lt;/code&gt; de &lt;code&gt;makelmdz_fcm&lt;/code&gt;.<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=440 Strataer 2024-01-19T14:33:08Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ.<br /> <br /> Une exécution de LMDZ avec Strataer peut partir de fichiers restart d'une exécution sans Strataer.<br /> <br /> Références :<br /> * https://doi.org/10.5194/gmd-10-3359-2017<br /> * https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Strataer est activé avec l'option &lt;code&gt;-strataer true&lt;/code&gt; de &lt;code&gt;makelmdz_fcm&lt;/code&gt;.<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=439 Strataer 2024-01-19T06:06:20Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ.<br /> <br /> Références :<br /> * https://doi.org/10.5194/gmd-10-3359-2017<br /> * https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Strataer est activé avec l'option &lt;code&gt;-strataer true&lt;/code&gt; de &lt;code&gt;makelmdz_fcm&lt;/code&gt;.<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=437 Strataer 2023-11-22T15:13:35Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Références :<br /> * https://doi.org/10.5194/gmd-10-3359-2017<br /> * https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Strataer est activé avec l'option &lt;code&gt;-strataer true&lt;/code&gt; de &lt;code&gt;makelmdz_fcm&lt;/code&gt;.<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=436 Strataer 2023-11-22T15:13:17Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Références :<br /> * https://doi.org/10.5194/gmd-10-3359-2017<br /> * https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Strataer est activé avec l'option &lt;code&gt;-strataer true&lt;/code&gt; de &lt;code&gt;makelmdz_fcm&lt;code/&gt;.<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=435 Strataer 2023-11-22T14:55:52Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Références :<br /> * https://doi.org/10.5194/gmd-10-3359-2017<br /> * https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=434 Strataer 2023-11-22T14:54:38Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Références :<br /> - https://doi.org/10.5194/gmd-10-3359-2017<br /> - https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=433 Strataer 2023-11-22T14:53:49Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics. Les aérosols générés par Strataer sont intégrés comme des traceurs dans LMDZ : ils passent par les routines de LMDZ pour la convection, le lessivage, etc.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Références :<br /> https://doi.org/10.5194/gmd-10-3359-2017<br /> https://doi.org/10.5194/acp-21-3317-2021<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=432 Strataer 2023-11-22T14:38:09Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.<br /> <br /> Mots-clefs : aérosol, aerosol</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=431 Strataer 2023-11-22T14:16:19Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnostics.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=430 Strataer 2023-11-22T14:07:25Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnotics.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes de taille d'aérosols sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=429 Strataer 2023-11-22T14:06:49Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnotics.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. À partir de cette climatologie, Strataer calcule un niveau de fond des aérosols.<br /> <br /> En outre, on peut, via le fichier &lt;code&gt;physiq.def&lt;/code&gt;, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes d'aérosols en taille sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=428 Strataer 2023-11-22T14:03:04Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols soufrés. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnotics.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. Ceci permet d’avoir un niveau de fond des aérosols. Ensuite on peut, via le fichier physiq.def, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes d'aérosols en taille sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=427 Strataer 2023-11-22T14:02:14Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols du soufre. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnotics.<br /> <br /> En entrée on a un fichier avec la climatologie des rapports de mélange dans l'air et des durées de vie des espèces OCS, SO2 et H2SO4. Cette climatologie est générée avec un modèle de chimie complète. Les espèces OCS, SO2 et H2SO4 sont des précurseurs des aérosols. Ceci permet d’avoir un niveau de fond des aérosols. Ensuite on peut, via le fichier physiq.def, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes d'aérosols en taille sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=426 Strataer 2023-11-22T13:30:53Z <p>Lguez : </p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols du soufre. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnotics.<br /> <br /> En entrée on a un fichier avec les climatologies sur une période des précurseurs des aérosols OCS, SO2 et H2SO5 + leur durée de vie moyenne (générées avec un modèle de chimie complète). Ceci permet d’avoir un niveau de fond des aérosols. Ensuite on peut, via le fichier physiq.def, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.<br /> <br /> Le nombre et les bornes des classes d'aérosols en taille sont pilotables. C'est pourquoi la routine de calcul de Mie est internalisée à StratAer et non en pre-processing comme c'est le cas pour les aérosols troposphériques.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Strataer&diff=425 Strataer 2023-11-22T13:29:51Z <p>Lguez : Page créée avec « StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols du soufre. En gros il prend des sources de soufre en entrée (climatologie plus injecti... »</p> <hr /> <div>StratAer (anciennement S3A) est un modèle de chimie stratosphérique des aérosols du soufre. En gros il prend des sources de soufre en entrée (climatologie plus injection) et calcule la chimie du soufre pour former des aérosols soufrés, répartis en plusieurs tailles (bin), qui vont être transportées, former d’autres molécules jusqu’à sédimenter. Les propriétés optiques de ces aérosols sont calculées au passage, ainsi que d’autres diagnotics.<br /> <br /> En entrée on a un fichier avec les climatologies sur une période des précurseurs des aérosols OCS, SO2 et H2SO5 + leur durée de vie moyenne (générées avec un modèle de chimie complète). Ceci permet d’avoir un niveau de fond des aérosols. Ensuite on peut, via le fichier physiq.def, définir des injections de soufre à certaines dates pour représenter des éruptions volcaniques ou des shoots induits par géo-ingénérie. StratAer calcule les réactions chimiques induites et génère les aérosols jusqu’à leur sédimentation.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Radiative_transfer_schemes&diff=421 Radiative transfer schemes 2023-10-17T03:41:45Z <p>Lguez : </p> <hr /> <div>There are different radiative schemes that can be used in LMDZ:<br /> <br /> * The &quot;legacy&quot; (oldest) radiative scheme is available regardless of the makelmdz options used. May be selected using the '''iflag_rrtm=0''' option in physiq.def. Note that this schemes also requires using 2 bands in the SW (Short Wave, i.e. visible wavelengths), i.e. setting '''NSW=2''' in physiq.def. This is the radiative code that was used in LMDZ4. It was written by Foucart and Morcrette at ECMWF. The description of the solar part of the spectrum, in particular, is not satisfying.<br /> * RRTM, selected with '''iflag_rrtm=1''' (and requiring that '''NSW=6'''), which is available if makelmdz has been run with the '''-rad rrtm''' option (see [[WhatIs: The makelmdz fcm script]]).<br /> * ECRAD (implementation is ongoing at the time of writing this) , selected with '''iflag_rrtm=2''', which is available if makelmdz has been run with the '''-rad ecrad''' option.<br /> <br /> ECRad has three sub-options for the treatment of clouds:<br /> * McICA : Monte Carlo Independent Column Approximation. Assez rapide, comme si on faisait des sondages, on tire une dizaine de sous-colonnes.<br /> * Tripleclouds : trois colonnes par maille : ciel clair, nuageux compact, nuageux intermédiaire. Le plus proche de RRTM.<br /> * Tripleclouds avec Spartacus : effet 3D des nuages, multiplie par 5 le temps d'exécution du rayonnement.<br /> <br /> ECRad also has two sub-options for the treatment of the gas phase:<br /> * RRTMG (Rapid Radiative Transfer Model for GCMs). 16 longwave bands and 14 shortwave bands.<br /> * ECCKD (ECMWF correlated k-distribution scheme)</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Radiative_transfer_schemes&diff=420 Radiative transfer schemes 2023-10-16T14:18:21Z <p>Lguez : </p> <hr /> <div>There are different radiative schemes that can be used in LMDZ:<br /> <br /> * the &quot;legacy&quot; (oldest) radiative scheme: available regardless of the makelmdz options used. May be selected using the '''iflag_rrtm=0''' option in physiq.def. Note that this schemes also requires using 2 bands in the SW (Short Wave, i.e. visible wavelengths), i.e. setting '''NSW=2''' in physiq.def<br /> * RRTM, selected with '''iflag_rrtm=1''' (and requiring that '''NSW=6'''), which is available if makelmdz has been run with the '''-rad rrtm''' option (see [[WhatIs: The makelmdz fcm script]]).<br /> * ECRAD (implementation is ongoing at the time of writing this) , selected with '''iflag_rrtm=2''', which is available if makelmdz has been run with the '''-rad ecrad''' option.<br /> <br /> ECRad has three sub-options for the treatment of clouds:<br /> * McICA : Monte Carlo Independent Column Approximation. Assez rapide, comme si on faisait des sondages, on tire une dizaine de sous-colonnes.<br /> * Tripleclouds : trois colonnes par maille : ciel clair, nuageux compact, nuageux intermédiaire. Le plus proche de RRTM.<br /> * Tripleclouds avec Spartacus : effet 3D des nuages, multiplie par 5 le temps d'exécution du rayonnement.<br /> <br /> ECRad also has two sub-options for the treatment of the gas phase:<br /> * RRTMG (Rapid Radiative Transfer Model for GCMs). 16 longwave bands and 14 shortwave bands.<br /> * ECCKD (ECMWF correlated k-distribution scheme)</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Radiative_transfer_schemes&diff=419 Radiative transfer schemes 2023-09-28T14:26:08Z <p>Lguez : </p> <hr /> <div>There are different radiative schemes that can be used in LMDZ:<br /> <br /> * the &quot;legacy&quot; (oldest) radiative scheme: available regardless of the makelmdz options used. May be selected using the '''iflag_rrtm=0''' option in physiq.def. Note that this schemes also requires using 2 bands in the SW (Short Wave, i.e. visible wavelengths), i.e. setting '''NSW=2''' in physiq.def<br /> * RRTM, selected with '''iflag_rrtm=1''' (and requiring that '''NSW=6'''), which is available if makelmdz has been run with the '''-rad rrtm''' option (see [[WhatIs: The makelmdz fcm script]]).<br /> * ECRAD (implementation is ongoing at the time of writing this) , selected with '''iflag_rrtm=2''', which is available if makelmdz has been run with the '''-rad ecrad''' option.<br /> <br /> ECRad has three sub-options for the treatment of clouds:<br /> * McICA : Monte Carlo Independent Column Approximation. Assez rapide, comme si on faisait des sondages, on tire une dizaine de sous-colonnes.<br /> * Tripleclouds : trois colonnes par maille : ciel clair, nuageux compact, nuageux intermédiaire. Le plus proche de RRTM.<br /> * Tripleclouds avec Spartacus : effet 3D des nuages, multiplie par 5 le temps d'exécution du rayonnement.<br /> <br /> ECRad also has two sub-options for the treatment of the gas phase:<br /> * RRTMG (Rapid Radiative Transfer Model for GCMs)<br /> * ECCKD (ECMWF correlated k-distribution scheme)</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=The_netCDF_library&diff=409 The netCDF library 2023-05-16T13:19:06Z <p>Lguez : </p> <hr /> <div>== the NetCDF library ==<br /> The model reads and writes input and output files in NetCDF (Network Common Data Form) format (developed and maintained by Unidata: https://www.unidata.ucar.edu/software/netcdf/ ) and therefore a NetCDF library must be at hand when compiling and running LMDZ6.<br /> <br /> As this library is not quite standard, chances are that you might need to install it yourself on your system (note that the [[WhatIs: The install lmdz.sh script|install_lmdz.sh]] default behavior is to download and install that library), hence this page with some indications on how to do so.<br /> <br /> == Checking if a NetCDF library is already available ==<br /> It is possible that the library, including its Fortran component, is already available. An easy way to check this is to see if the related utilities like '''ncdump''' are available, i.e. that <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> which ncdump<br /> &lt;/syntaxhighlight&gt;<br /> returns a positive answer.<br /> <br /> Note that this does not suffice as the full library, including its Fortran component, and not just the related utilities are required. A neat way to check this is to use the '''nf-config'''<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> returns something meaningful. If not, you probably need to take some action along the lines of what is indicated in the following sections.<br /> <br /> == Various ways to install the NetCDF library ==<br /> === Install from the package repository of your Linux distribution ===<br /> <br /> This is the easiest and fastest (and recommended) way. For example, if your distribution is Ubuntu or Linux Mint (and you have admin, i.e. ''sudo'' rights), open a terminal and type:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt install netcdf-bin libnetcdff-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> If you want to use XIOS with LMDZ then you need the parallel-enabled version of NetCDF. In addition to the previous '''apt install''' command, under Ubuntu or Linux Mint, type:<br /> <br /> sudo apt install libnetcdf-mpi-dev libhdf5-mpi-dev<br /> <br /> <br /> === Personal installation ===<br /> One can always download the source code and compile the NetCDF library (see https://docs.unidata.ucar.edu/netcdf-c/current/faq.html#HowdoIgetthenetCDFsoftwarepackage ). You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf<br /> cd netcdf<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5_seq.bash<br /> chmod u=rwx install_netcdf4_hdf5_seq.bash<br /> ./install_netcdf4_hdf5_seq.bash &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5_seq.bash&quot; script in a &quot;netcdf&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation of an advanced NetCDF4-HDF5 library with MPI enabled ===<br /> This specific version is useful especially if running with the XIOS library.<br /> A prerequisite is to have an MPI library installed and available.<br /> You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf4hdf5<br /> cd netcdf4hdf5<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5.bash<br /> chmod u=rwx install_netcdf4_hdf5.bash<br /> ./install_netcdf4_hdf5.bash -CC mpicc -FC mpif90 -CXX mpiCC -MPI /path/to/your/MPI/install &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> You should of course adapt the command line, especially the ''-MPI /path/to/your/MPI/install'' part to your settings. <br /> <br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf4hdf5/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5.bash&quot; script in a &quot;netcdf4hdf5&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> 03/01/2022<br /> <br /> [[Category:HowTo]]<br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=The_netCDF_library&diff=408 The netCDF library 2023-05-16T13:17:14Z <p>Lguez : </p> <hr /> <div>== the NetCDF library ==<br /> The model reads and writes input and output files in NetCDF (Network Common Data Form) format (developed and maintained by Unidata: https://www.unidata.ucar.edu/software/netcdf/ ) and therefore a NetCDF library must be at hand when compiling and running LMDZ6.<br /> <br /> As this library is not quite standard, chances are that you might need to install it yourself on your system (note that the [[WhatIs: The install lmdz.sh script|install_lmdz.sh]] default behavior is to download and install that library), hence this page with some indications on how to do so.<br /> <br /> == Checking if a NetCDF library is already available ==<br /> It is possible that the library, including its Fortran component, is already available. An easy way to check this is to see if the related utilities like '''ncdump''' are available, i.e. that <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> which ncdump<br /> &lt;/syntaxhighlight&gt;<br /> returns a positive answer.<br /> <br /> Note that this does not suffice as the full library, including its Fortran component, and not just the related utilities are required. A neat way to check this is to use the '''nf-config'''<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> returns something meaningful. If not, you probably need to take some action along the lines of what is indicated in the following sections.<br /> <br /> == Various ways to install the NetCDF library ==<br /> === Install from the package repository of your Linux distribution ===<br /> <br /> This is the easiest (and recommended) way. For example, if your distribution is Ubuntu or Linux Mint (and you have admin, i.e. ''sudo'' rights), open a terminal and type:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt install netcdf-bin libnetcdff-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> If you want to use XIOS with LMDZ then you need the parallel-enabled version of NetCDF. In addition to the previous '''apt install''' command, under Ubuntu or Linux Mint, type:<br /> <br /> sudo apt install libnetcdf-mpi-dev libhdf5-mpi-dev<br /> <br /> <br /> === Personal installation ===<br /> One can always download the source code and compile the NetCDF library (see https://docs.unidata.ucar.edu/netcdf-c/current/faq.html#HowdoIgetthenetCDFsoftwarepackage ). You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf<br /> cd netcdf<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5_seq.bash<br /> chmod u=rwx install_netcdf4_hdf5_seq.bash<br /> ./install_netcdf4_hdf5_seq.bash &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5_seq.bash&quot; script in a &quot;netcdf&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation of an advanced NetCDF4-HDF5 library with MPI enabled ===<br /> This specific version is useful especially if running with the XIOS library.<br /> A prerequisite is to have an MPI library installed and available.<br /> You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf4hdf5<br /> cd netcdf4hdf5<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5.bash<br /> chmod u=rwx install_netcdf4_hdf5.bash<br /> ./install_netcdf4_hdf5.bash -CC mpicc -FC mpif90 -CXX mpiCC -MPI /path/to/your/MPI/install &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> You should of course adapt the command line, especially the ''-MPI /path/to/your/MPI/install'' part to your settings. <br /> <br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf4hdf5/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5.bash&quot; script in a &quot;netcdf4hdf5&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> 03/01/2022<br /> <br /> [[Category:HowTo]]<br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=The_netCDF95_library&diff=407 The netCDF95 library 2023-05-16T13:09:58Z <p>Lguez : </p> <hr /> <div>== The NetCDF95 library ==<br /> This is essentially a wrapper on top of the &quot;regular&quot; [[The netCDF library|NetCDF library]].<br /> Added, and thus required, since April 2023 (revision 4489 of LMDZ).<br /> <br /> It is freely available from https://lguez.github.io/NetCDF95/<br /> <br /> Along with installation instructions: https://lguez.github.io/NetCDF95/installation/ <br /> <br /> <br /> <br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Radiative_transfer_schemes&diff=388 Radiative transfer schemes 2023-04-24T11:51:53Z <p>Lguez : </p> <hr /> <div>There are different radiative schemes that can be used in LMDZ:<br /> <br /> * the &quot;legacy&quot; (oldest) radiative scheme: available regardless of the makelmdz options used. May be selected using the '''iflag_rrtm=0''' option in physiq.def. Note that this schemes also requires using 2 bands in the SW (Short Wave, i.e. visible wavelengths), i.e. setting '''NSW=2''' in physiq.def<br /> * RRTM, selected with '''iflag_rrtm=1''' (and requiring that '''NSW=6'''), which is available if makelmdz has been run with the '''-rad rrtm''' option (see [[WhatIs: The makelmdz fcm script]]).<br /> * ECRAD (implementation is ongoing at the time of writing this) , selected with '''iflag_rrtm=2''', which is available if makelmdz has been run with the '''-rad ecrad''' option.<br /> <br /> ECRad has three sub-options for the treatment of clouds:<br /> * McICA : Monte Carlo Independent Column Approximation. Assez rapide, comme si on faisait des sondages, on tire une dizaine de sous-colonnes.<br /> * triple cloud : trois colonnes par maille : ciel clair, nuageux compact, nuageux intermédiraire. Le plus proche de RRTM.<br /> * triple cloud avec Spartacus : effet 3D des nuages, multiplie par 5 le temps d'exécution du rayonnement.<br /> <br /> ECRad also has two sub-options for the treatment of the gas phase:<br /> * RRTMG<br /> * ECCKD</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Radiative_transfer_schemes&diff=387 Radiative transfer schemes 2023-04-24T11:50:21Z <p>Lguez : </p> <hr /> <div>There are different radiative schemes that can be used in LMDZ:<br /> <br /> * the &quot;legacy&quot; (oldest) radiative scheme: available regardless of the makelmdz options used. May be selected using the '''iflag_rrtm=0''' option in physiq.def. Note that this schemes also requires using 2 bands in the SW (Short Wave, i.e. visible wavelengths), i.e. setting '''NSW=2''' in physiq.def<br /> * RRTM, selected with '''iflag_rrtm=1''' (and requiring that '''NSW=6'''), which is available if the GCM has been compiled with the '''-rad rrtm''' option (see [[WhatIs: The makelmdz fcm script]]).<br /> * ECRAD (implementation is ongoing at the time of writing this) , selected with '''iflag_rrtm=2''', which is available if the GCM has been compiled with the '''-rad ecrad''' option.<br /> <br /> ECRad has three sub-options for the treatment of clouds:<br /> * McICA : Monte Carlo Independent Column Approximation. Assez rapide, comme si on faisait des sondages, on tire une dizaine de sous-colonnes.<br /> * triple cloud : trois colonnes par maille : ciel clair, nuageux compact, nuageux intermédiraire. Le plus proche de RRTM.<br /> * triple cloud avec Spartacus : effet 3D des nuages, multiplie par 5 le temps d'exécution du rayonnement.<br /> <br /> ECRad also has two sub-options for the treatment of the gas phase:<br /> * RRTMG<br /> * ECCKD</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Radiative_transfer_schemes&diff=382 Radiative transfer schemes 2023-04-03T12:31:09Z <p>Lguez : </p> <hr /> <div>There are different radiative schemes that can be used in LMDZ:<br /> <br /> * the &quot;legacy&quot; (oldest) radiative scheme: always available. May be selected using the '''iflag_rrtm=0''' option in physiq.def. Note that this schemes also requires using 2 bands in the SW (Short Wave, i.e. visible wavelengths), i.e. setting '''NSW=2''' in physiq.def<br /> * RRTM, selected with '''iflag_rrtm=1''' (and requiring that '''NSW=6'''), which is available if the GCM has been compiled with the '''-rad rrtm''' option (see [[WhatIs: The makelmdz fcm script]]).<br /> * ECRAD (implementation is ongoing at the time of writing this) , selected with '''iflag_rrtm=2''', which is available if the GCM has been compiled with the '''-rad ecrad''' option.<br /> <br /> ECRad has three sub-options for the treatment of clouds:<br /> * McICA : Monte Carlo Independent Column Approximation. Assez rapide, comme si on faisait des sondages, on tire une dizaine de sous-colonnes.<br /> * triple cloud : trois colonnes par maille : ciel clair, nuageux compact, nuageux intermédiraire. Le plus proche de RRTM.<br /> * triple cloud avec Spartacus : effet 3D des nuages, multiplie par 5 le temps d'exécution du rayonnement.<br /> <br /> ECRad also has two sub-options for the treatment of the gas phase:<br /> * RRTMG<br /> * ECCKD</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Radiative_transfer_schemes&diff=324 Radiative transfer schemes 2023-03-06T17:23:40Z <p>Lguez : </p> <hr /> <div>There are different radiative schemes that can be used in LMDZ:<br /> <br /> * the &quot;legacy&quot; (oldest) radiative scheme: always available. May be selected using the '''iflag_rrtm=0''' option in physiq.def. Note that this schemes also requires using 2 bands in the SW (Short Wave, i.e. visible wavelengths), i.e. setting '''NSW=2''' in physiq.def<br /> * RRTM, selected with '''iflag_rrtm=1''' (and requiring that '''NSW=6'''), which is available if the GCM has been compiled with the '''-rad rrtm''' option (see [[WhatIs: The makelmdz fcm script]]).<br /> * ECRAD (implementation is ongoing at the time of writing this) , selected with '''iflag_rrtm=2''', which is available if the GCM has been compiled with the '''-rad ecrad''' option. Three sub-options:<br /> ** McICA : Monte Carlo Independent Column Approximation. Assez rapide, comme si on faisait des sondages, on tire une dizaine de sous-colonnes.<br /> ** triple cloud : trois colonnes par maille : ciel clair, nuageux compact, nuageux intermédiraire. Le plus proche de RRTM.<br /> ** triple cloud avec Spartacus : effet 3D des nuages, multiplie par 5 le temps d'exécution du rayonnement.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=Cosp&diff=320 Cosp 2023-01-27T15:19:52Z <p>Lguez : Page créée avec « Le répertoire cosp correspond à la version cospv1 que nous avons utilisée pour les simulations CMIP6. Le répertoire cospv2 correspond à la version récente cospv2 de... »</p> <hr /> <div>Le répertoire cosp correspond à la version cospv1 que nous avons utilisée pour les simulations CMIP6.<br /> Le répertoire cospv2 correspond à la version récente cospv2 de Cosp. La différence entre les 2 versions est la réécriture avec du fortran récent et l'ajout de nouveaux diagnostics.<br /> Le répertoire cosp2 est une version intermédiaire avec des développement d'un doctorant de Jean-Louis qu'on voulait conserver et qui n'est pas maintenue.</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=The_netCDF_library&diff=305 The netCDF library 2023-01-03T14:34:29Z <p>Lguez : </p> <hr /> <div>== the NetCDF library ==<br /> The model reads and writes input and output files in NetCDF (Network Common Data Form) format (developed and maintained by Unidata: https://www.unidata.ucar.edu/software/netcdf/ ) and therefore a NetCDF library must be at hand when compiling and running LMDZ6.<br /> <br /> As this library is not quite standard, chances are that you might need to install it yourself on your system (note that the [[WhatIs: The install lmdz.sh script|install_lmdz.sh]] default behavior is to download and install that library), hence this page with some indications on how to do so.<br /> <br /> == Checking if a NetCDF library is already available ==<br /> It is possible that the library, including its Fortran component, is already available. An easy way to check this is to see if the related utilities like '''ncdump''' are available, i.e. that <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> which ncdump<br /> &lt;/syntaxhighlight&gt;<br /> returns a positive answer.<br /> <br /> Note that this does not suffice as the full library, including its Fortran component, and not just the related utilities are required. A neat way to check this is to use the '''nf-config'''<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> returns something meaningful. If not, you probably need to take some action along the lines of what is indicated in the following sections.<br /> <br /> == Various ways to install the NetCDF library ==<br /> === Install from the package repository of your Linux distribution ===<br /> This is the easiest (and recommended) way. For example, if your distribution is Ubuntu or Linux Mint (and you have admin, i.e. ''sudo'' rights), open a terminal and type:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt install netcdf-bin libnetcdff-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation ===<br /> One can always download the source code and compile the NetCDF library (see https://docs.unidata.ucar.edu/netcdf-c/current/faq.html#HowdoIgetthenetCDFsoftwarepackage ). You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf<br /> cd netcdf<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5_seq.bash<br /> chmod u=rwx install_netcdf4_hdf5_seq.bash<br /> ./install_netcdf4_hdf5_seq.bash &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5_seq.bash&quot; script in a &quot;netcdf&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation of an advanced NetCDF4-HDF5 library with MPI enabled ===<br /> This specific version is useful especially if running with the XIOS library.<br /> A prerequisite is to have an MPI library installed and available.<br /> You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf4hdf5<br /> cd netcdf4hdf5<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5.bash<br /> chmod u=rwx install_netcdf4_hdf5.bash<br /> ./install_netcdf4_hdf5.bash -CC mpicc -FC mpif90 -CXX mpiCC -MPI /path/to/your/MPI/install &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> You should of course adapt the command line, especially the ''-MPI /path/to/your/MPI/install'' part to your settings. <br /> <br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf4hdf5/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5.bash&quot; script in a &quot;netcdf4hdf5&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> 03/01/2022<br /> <br /> [[Category:HowTo]]<br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=The_netCDF_library&diff=304 The netCDF library 2023-01-03T14:34:05Z <p>Lguez : </p> <hr /> <div>== the NetCDF library ==<br /> The model reads and writes input and output files in NetCDF (Network Common Data Form) format (developed and maintained by Unidata: https://www.unidata.ucar.edu/software/netcdf/ ) and therefore a NetCDF library must be at hand when compiling and running LMDZ6.<br /> <br /> As this library is not quite standard, chances are that you might need to install it yourself on your system (note that the [[WhatIs: The install lmdz.sh script|install_lmdz.sh]] default behavior is to download and install that library), hence this page with some indications on how to do so.<br /> <br /> == Checking if a NetCDF library is already available ==<br /> It is possible that the library, including its Fortran component, is already available. An easy way to check this is to see if the related utilities like '''ncdump''' are available, i.e. that <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> which ncdump<br /> &lt;/syntaxhighlight&gt;<br /> returns a positive answer.<br /> <br /> Note that this does not suffice as the full library, including its Fortran component, and not just the related utilities are required. A neat way to check this is to use the '''nf-config'''<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> returns something meaningful. If not, you probably need to take some action along the lines of what is indicated in the following sections.<br /> <br /> == Various ways to install the NetCDF library ==<br /> === Install from the package repository of your Linux distribution ===<br /> This is the easiest (and recommended) way. For exemple, if your distribution is Ubuntu or Linux Mint (and you have admin, i.e. ''sudo'' rights), open a terminal and type:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt install netcdf-bin libnetcdff-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation ===<br /> One can always download the source code and compile the NetCDF library (see https://docs.unidata.ucar.edu/netcdf-c/current/faq.html#HowdoIgetthenetCDFsoftwarepackage ). You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf<br /> cd netcdf<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5_seq.bash<br /> chmod u=rwx install_netcdf4_hdf5_seq.bash<br /> ./install_netcdf4_hdf5_seq.bash &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5_seq.bash&quot; script in a &quot;netcdf&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation of an advanced NetCDF4-HDF5 library with MPI enabled ===<br /> This specific version is useful especially if running with the XIOS library.<br /> A prerequisite is to have an MPI library installed and available.<br /> You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf4hdf5<br /> cd netcdf4hdf5<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5.bash<br /> chmod u=rwx install_netcdf4_hdf5.bash<br /> ./install_netcdf4_hdf5.bash -CC mpicc -FC mpif90 -CXX mpiCC -MPI /path/to/your/MPI/install &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> You should of course adapt the command line, especially the ''-MPI /path/to/your/MPI/install'' part to your settings. <br /> <br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf4hdf5/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5.bash&quot; script in a &quot;netcdf4hdf5&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> 03/01/2022<br /> <br /> [[Category:HowTo]]<br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=The_netCDF_library&diff=303 The netCDF library 2023-01-03T14:29:36Z <p>Lguez : </p> <hr /> <div>== the NetCDF library ==<br /> The model reads and writes input and output files in NetCDF (Network Common Data Form) format (developed and maintained by Unidata: https://www.unidata.ucar.edu/software/netcdf/ ) and therefore a NetCDF library must be at hand when compiling and running LMDZ6.<br /> <br /> As this library is not quite standard, chances are that you might need to install it yourself on your system (note that the [[WhatIs: The install lmdz.sh script|install_lmdz.sh]] default behavior is to download and install that library), hence this page with some indications on how to do so.<br /> <br /> == Checking if a NetCDF library is already available ==<br /> It is possible that the library, including its Fortran component, is already available. An easy way to check this is to see if the related utilities like '''ncdump''' are available, i.e. that <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> which ncdump<br /> &lt;/syntaxhighlight&gt;<br /> returns a positive answer.<br /> <br /> Note that this does not suffice as the full library, including its Fortran component, and not just the related utilities are required. A neat way to check this is to use the '''nf-config'''<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> returns something meaningful. If not, you probably need to take some action along the lines of what is indicated in the following sections.<br /> <br /> == Various ways to install the NetCDF library ==<br /> === Install from the package repository of your Linux distribution ===<br /> This is the easiest (and recommended) way. If your distribution is Ubuntu or Linux Mint (and you have admin, i.e. ''sudo'' rights), open a terminal and type:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt install netcdf-bin libnetcdff-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation ===<br /> One can always download the source code and compile the NetCDF library (see https://docs.unidata.ucar.edu/netcdf-c/current/faq.html#HowdoIgetthenetCDFsoftwarepackage ). You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf<br /> cd netcdf<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5_seq.bash<br /> chmod u=rwx install_netcdf4_hdf5_seq.bash<br /> ./install_netcdf4_hdf5_seq.bash &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5_seq.bash&quot; script in a &quot;netcdf&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation of an advanced NetCDF4-HDF5 library with MPI enabled ===<br /> This specific version is useful especially if running with the XIOS library.<br /> A prerequisite is to have an MPI library installed and available.<br /> You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf4hdf5<br /> cd netcdf4hdf5<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5.bash<br /> chmod u=rwx install_netcdf4_hdf5.bash<br /> ./install_netcdf4_hdf5.bash -CC mpicc -FC mpif90 -CXX mpiCC -MPI /path/to/your/MPI/install &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> You should of course adapt the command line, especially the ''-MPI /path/to/your/MPI/install'' part to your settings. <br /> <br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf4hdf5/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5.bash&quot; script in a &quot;netcdf4hdf5&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> 03/01/2022<br /> <br /> [[Category:HowTo]]<br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=The_netCDF_library&diff=302 The netCDF library 2023-01-03T14:19:16Z <p>Lguez : </p> <hr /> <div>== the NetCDF library ==<br /> The model reads and writes input and output files in NetCDF (Network Common Data Form) format (developed and maintained by Unidata: https://www.unidata.ucar.edu/software/netcdf/ ) and therefore a NetCDF library must be at hand when compiling and running LMDZ6.<br /> <br /> As this library is not quite standard, chances are that you might need to install it yourself on your system (note that the [[WhatIs: The install lmdz.sh script|install_lmdz.sh]] default behavior is to download and install that library), hence this page with some indications on how to do so.<br /> <br /> == Checking if a NetCDF library is already available ==<br /> It is possible that the library, including its Fortran component, is already available. An easy way to check this is to see if the related utilities like '''ncdump''' are available, i.e. that <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> which ncdump<br /> &lt;/syntaxhighlight&gt;<br /> returns a positive answer.<br /> <br /> Note that this does not suffice as the full library, including its Fortran component, and not just the related utilities are required. A neat way to check this is to use the '''nf-config'''<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> returns something meaningful. If not, you probably need to take some action along the lines of what is indicated in the following sections.<br /> <br /> == Various ways to install the NetCDF library ==<br /> === Install via a system manager ===<br /> This is the easiest (and recommended) way. If on Ubuntu (and with admin, i.e. ''sudo'' rights) you can try<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> sudo apt install netcdf-bin libnetcdff-dev<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation ===<br /> One can always download the source code and compile the NetCDF library (see https://docs.unidata.ucar.edu/netcdf-c/current/faq.html#HowdoIgetthenetCDFsoftwarepackage ). You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf<br /> cd netcdf<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5_seq.bash<br /> chmod u=rwx install_netcdf4_hdf5_seq.bash<br /> ./install_netcdf4_hdf5_seq.bash &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5_seq.bash&quot; script in a &quot;netcdf&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Personal installation of an advanced NetCDF4-HDF5 library with MPI enabled ===<br /> This specific version is useful especially if running with the XIOS library.<br /> A prerequisite is to have an MPI library installed and available.<br /> You can use the following home-made &quot;install_netcdf4_hdf5_seq.bash&quot; script to do so. For this, ensure that you are in your home directory and:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> mkdir netcdf4hdf5<br /> cd netcdf4hdf5<br /> wget -nv --no-check-certificate http://www.lmd.jussieu.fr/~lmdz/pub/import/install_netcdf4_hdf5.bash<br /> chmod u=rwx install_netcdf4_hdf5.bash<br /> ./install_netcdf4_hdf5.bash -CC mpicc -FC mpif90 -CXX mpiCC -MPI /path/to/your/MPI/install &gt; netcdf.log 2&gt;&amp;1<br /> &lt;/syntaxhighlight&gt;<br /> You should of course adapt the command line, especially the ''-MPI /path/to/your/MPI/install'' part to your settings. <br /> <br /> Compiling the library and dependencies can take a while (&gt;&gt;15 minutes; be patient).<br /> Once this is done, check file netcdf.log to verify that all went well.<br /> You may want to also add its &quot;bin&quot; directory to your PATH environment variable by adding in your .bashrc a line of:<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> export PATH=$PATH:$HOME/netcdf4hdf5/bin<br /> &lt;/syntaxhighlight&gt;<br /> The assumption here is that you have run the &quot;install_netcdf4_hdf5.bash&quot; script in a &quot;netcdf4hdf5&quot; subdirectory of your home directory. Adapt accordingly if not.<br /> <br /> Check that the installation was successfully installed :-)<br /> Again, a neat way to do that is to run and check the output of<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> nf-config --all<br /> &lt;/syntaxhighlight&gt;<br /> <br /> 03/01/2022<br /> <br /> [[Category:HowTo]]<br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=WhatIs:_The_tracer.def_input_file&diff=299 WhatIs: The tracer.def input file 2023-01-03T12:01:00Z <p>Lguez : </p> <hr /> <div>== The tracer.def input file ==<br /> This file contains information on the tracers that will be advected in the dynamics. It should be used instead of the now deprecated [[WhatIs: The traceur.def input file|traceur.def]] input file.<br /> <br /> == Simple example of a ''tracer.def'' file ==<br /> In this example there are 4 tracers: 3 for water (one for each of its phases, gas, liquid or solid) and one called ''Aga'' (age of air)<br /> &lt;pre&gt;<br /> &amp;version=1.0<br /> &amp;lmdz<br /> default type=tracer phases=g hadv=10 vadv=10 parent=air<br /> H2O hadv=14 vadv=14<br /> H2O phases=ls<br /> Aga<br /> &lt;/pre&gt;<br /> * The mandatory first line ''&amp;version'' is there to handle (potential) versioning of these file and their format<br /> * The mandatory second line ''&amp;lmdz'' is there to specify the scope of the following lines, i.e. that all that follow is relevant for the LMDZ lon-lat dynamical core.<br /> * The mandatory third line starting with ''default'' specifies the default attributes for all the tracers. In this example that they are of type ''tracer'' (as opposed to type ''tag'' for tagging), that there phase is ''g'' (gas), that they are advected using advection schemes hadv and vadv ''10'' (Van Leer advection scheme) and that their parent (i.e. carrier fluid) is ''air''.<br /> * Then one should specify on successive lines the tracer names and optionally their properties such as phases (g: gas, l: liquid, s:solid). Note that one may condense information about phases using a mix of letters g/l/s rather than specifying the information for each on a separate line. In practice the lines<br /> &lt;pre&gt;<br /> H2O hadv=14 vadv=14<br /> H2O phases=ls<br /> &lt;/pre&gt;<br /> From the example above which specifies there are 3 H2O phases (gas, liquid and solid), where the gas phase is advected with the hadv and vadv ''14'' dedicated scheme could also be written more explicitly as:<br /> &lt;pre&gt;<br /> H2O phases=g hadv=14 vadv=14<br /> H2O phases=l<br /> H2O phases=s<br /> &lt;/pre&gt;<br /> <br /> <br /> == A more advanced example of a ''tracer.def file'' ==<br /> The following example includes water isotopes (identified by the fact that their ''parent'' is not ''air'' but the tracer ''H2O'')<br /> with two tags (''con'' and ''oce'')<br /> &lt;pre&gt;<br /> &amp;version=1.0<br /> &amp;lmdz<br /> default hadv=10 vadv=10 phases=g parent=air type=tracer<br /> H2O hadv=14 vadv=14<br /> H2O phases=ls<br /> RN,PB<br /> H2[18]O,H[2]HO,H2[16]O phases=gls parent=H2O<br /> con,oce phases=gls parent=H2[18]O,H[2]HO,H2[16]O type=tag<br /> &lt;/pre&gt;<br /> <br /> As LMDZ runs it outputs the detailed information about all tracers and their dependencies to one another. For the example above one would get:<br /> &lt;pre&gt;<br /> readTracersFiles: RAW CONTENT OF SECTION &quot;lmdz&quot;:<br /> readTracersFiles: iq | hadv | vadv | name | parent | phase<br /> readTracersFiles: ----+------+------+------------------------+------------------------+-------<br /> readTracersFiles: 1 | 14 | 14 | H2O | air | g<br /> readTracersFiles: 2 | 10 | 10 | H2O | air | ls<br /> readTracersFiles: 3 | 10 | 10 | RN,PB | air | g<br /> readTracersFiles: 4 | 10 | 10 | H2[18]O,H[2]HO,H2[16]O | H2O | gls<br /> readTracersFiles: 5 | 10 | 10 | con,oce | H2[18]O,H[2]HO,H2[16]O | gls<br /> readTracersFiles:<br /> readTracersFiles: EXPANDED CONTENT OF SECTION &quot;lmdz&quot;:<br /> readTracersFiles: iq | hadv | vadv | name | parent | igen | phase<br /> readTracersFiles: ----+------+------+---------------+-----------+------+-------<br /> readTracersFiles: 1 | 14 | 14 | H2O_g | air | 0 | g<br /> readTracersFiles: 2 | 10 | 10 | H2O_l | air | 0 | l<br /> readTracersFiles: 3 | 10 | 10 | H2O_s | air | 0 | s<br /> readTracersFiles: 4 | 10 | 10 | RN | air | 0 | g<br /> readTracersFiles: 5 | 10 | 10 | PB | air | 0 | g<br /> readTracersFiles: 6 | 10 | 10 | H2[18]O_g | H2O_g | 1 | g<br /> readTracersFiles: 7 | 10 | 10 | H2[18]O_l | H2O_l | 1 | l<br /> readTracersFiles: 8 | 10 | 10 | H2[18]O_s | H2O_s | 1 | s<br /> readTracersFiles: 9 | 10 | 10 | H[2]HO_g | H2O_g | 1 | g<br /> readTracersFiles: 10 | 10 | 10 | H[2]HO_l | H2O_l | 1 | l<br /> readTracersFiles: 11 | 10 | 10 | H[2]HO_s | H2O_s | 1 | s<br /> readTracersFiles: 12 | 10 | 10 | H2[16]O_g | H2O_g | 1 | g<br /> readTracersFiles: 13 | 10 | 10 | H2[16]O_l | H2O_l | 1 | l<br /> readTracersFiles: 14 | 10 | 10 | H2[16]O_s | H2O_s | 1 | s<br /> readTracersFiles: 15 | 10 | 10 | H2[18]O_g_con | H2[18]O_g | 2 | g<br /> readTracersFiles: 16 | 10 | 10 | H2[18]O_l_con | H2[18]O_l | 2 | l<br /> readTracersFiles: 17 | 10 | 10 | H2[18]O_s_con | H2[18]O_s | 2 | s<br /> readTracersFiles: 18 | 10 | 10 | H2[18]O_g_oce | H2[18]O_g | 2 | g<br /> readTracersFiles: 19 | 10 | 10 | H2[18]O_l_oce | H2[18]O_l | 2 | l<br /> readTracersFiles: 20 | 10 | 10 | H2[18]O_s_oce | H2[18]O_s | 2 | s<br /> readTracersFiles: 21 | 10 | 10 | H[2]HO_g_con | H[2]HO_g | 2 | g<br /> readTracersFiles: 22 | 10 | 10 | H[2]HO_l_con | H[2]HO_l | 2 | l<br /> readTracersFiles: 23 | 10 | 10 | H[2]HO_s_con | H[2]HO_s | 2 | s<br /> readTracersFiles: 24 | 10 | 10 | H[2]HO_g_oce | H[2]HO_g | 2 | g<br /> readTracersFiles: 25 | 10 | 10 | H[2]HO_l_oce | H[2]HO_l | 2 | l<br /> readTracersFiles: 26 | 10 | 10 | H[2]HO_s_oce | H[2]HO_s | 2 | s<br /> readTracersFiles: 27 | 10 | 10 | H2[16]O_g_con | H2[16]O_g | 2 | g<br /> readTracersFiles: 28 | 10 | 10 | H2[16]O_l_con | H2[16]O_l | 2 | l<br /> readTracersFiles: 29 | 10 | 10 | H2[16]O_s_con | H2[16]O_s | 2 | s<br /> readTracersFiles: 30 | 10 | 10 | H2[16]O_g_oce | H2[16]O_g | 2 | g<br /> readTracersFiles: 31 | 10 | 10 | H2[16]O_l_oce | H2[16]O_l | 2 | l<br /> readTracersFiles: 32 | 10 | 10 | H2[16]O_s_oce | H2[16]O_s | 2 | s<br /> &lt;/pre&gt;<br /> <br /> 03/01/2023<br /> <br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=WhatIs:_The_tracer.def_input_file&diff=298 WhatIs: The tracer.def input file 2023-01-03T12:00:06Z <p>Lguez : </p> <hr /> <div>== The tracer.def input file ==<br /> This file contains information on the tracers that will be advected in the dynamics. It should be used instead of the now deprecated [[WhatIs: The traceur.def input file|traceur.def]] input file.<br /> <br /> == Simple example of a ''tracer.def'' file ==<br /> In this example there are 4 tracers: 3 for water (one for each of its phases, gas, liquid or solid) and one called ''Aga''<br /> &lt;pre&gt;<br /> &amp;version=1.0<br /> &amp;lmdz<br /> default type=tracer phases=g hadv=10 vadv=10 parent=air<br /> H2O hadv=14 vadv=14<br /> H2O phases=ls<br /> Aga<br /> &lt;/pre&gt;<br /> * The mandatory first line ''&amp;version'' is there to handle (potential) versioning of these file and their format<br /> * The mandatory second line ''&amp;lmdz'' is there to specify the scope of the following lines, i.e. that all that follow is relevant for the LMDZ lon-lat dynamical core.<br /> * The mandatory third line starting with ''default'' specifies the default attributes for all the tracers. In this example that they are of type ''tracer'' (as opposed to type ''tag'' for tagging), that there phase is ''g'' (gas), that they are advected using advection schemes hadv and vadv ''10'' (Van Leer advection scheme) and that their parent (i.e. carrier fluid) is ''air''.<br /> * Then one should specify on successive lines the tracer names and optionally their properties such as phases (g: gas, l: liquid, s:solid). Note that one may condense information about phases using a mix of letters g/l/s rather than specifying the information for each on a separate line. In practice the lines<br /> &lt;pre&gt;<br /> H2O hadv=14 vadv=14<br /> H2O phases=ls<br /> &lt;/pre&gt;<br /> From the example above which specifies there are 3 H2O phases (gas, liquid and solid), where the gas phase is advected with the hadv and vadv ''14'' dedicated scheme could also be written more explicitly as:<br /> &lt;pre&gt;<br /> H2O phases=g hadv=14 vadv=14<br /> H2O phases=l<br /> H2O phases=s<br /> &lt;/pre&gt;<br /> <br /> <br /> == A more advanced example of a ''tracer.def file'' ==<br /> The following example includes water isotopes (identified by the fact that their ''parent'' is not ''air'' but the tracer ''H2O'')<br /> with two tags (''con'' and ''oce'')<br /> &lt;pre&gt;<br /> &amp;version=1.0<br /> &amp;lmdz<br /> default hadv=10 vadv=10 phases=g parent=air type=tracer<br /> H2O hadv=14 vadv=14<br /> H2O phases=ls<br /> RN,PB<br /> H2[18]O,H[2]HO,H2[16]O phases=gls parent=H2O<br /> con,oce phases=gls parent=H2[18]O,H[2]HO,H2[16]O type=tag<br /> &lt;/pre&gt;<br /> <br /> As LMDZ runs it outputs the detailed information about all tracers and their dependencies to one another. For the example above one would get:<br /> &lt;pre&gt;<br /> readTracersFiles: RAW CONTENT OF SECTION &quot;lmdz&quot;:<br /> readTracersFiles: iq | hadv | vadv | name | parent | phase<br /> readTracersFiles: ----+------+------+------------------------+------------------------+-------<br /> readTracersFiles: 1 | 14 | 14 | H2O | air | g<br /> readTracersFiles: 2 | 10 | 10 | H2O | air | ls<br /> readTracersFiles: 3 | 10 | 10 | RN,PB | air | g<br /> readTracersFiles: 4 | 10 | 10 | H2[18]O,H[2]HO,H2[16]O | H2O | gls<br /> readTracersFiles: 5 | 10 | 10 | con,oce | H2[18]O,H[2]HO,H2[16]O | gls<br /> readTracersFiles:<br /> readTracersFiles: EXPANDED CONTENT OF SECTION &quot;lmdz&quot;:<br /> readTracersFiles: iq | hadv | vadv | name | parent | igen | phase<br /> readTracersFiles: ----+------+------+---------------+-----------+------+-------<br /> readTracersFiles: 1 | 14 | 14 | H2O_g | air | 0 | g<br /> readTracersFiles: 2 | 10 | 10 | H2O_l | air | 0 | l<br /> readTracersFiles: 3 | 10 | 10 | H2O_s | air | 0 | s<br /> readTracersFiles: 4 | 10 | 10 | RN | air | 0 | g<br /> readTracersFiles: 5 | 10 | 10 | PB | air | 0 | g<br /> readTracersFiles: 6 | 10 | 10 | H2[18]O_g | H2O_g | 1 | g<br /> readTracersFiles: 7 | 10 | 10 | H2[18]O_l | H2O_l | 1 | l<br /> readTracersFiles: 8 | 10 | 10 | H2[18]O_s | H2O_s | 1 | s<br /> readTracersFiles: 9 | 10 | 10 | H[2]HO_g | H2O_g | 1 | g<br /> readTracersFiles: 10 | 10 | 10 | H[2]HO_l | H2O_l | 1 | l<br /> readTracersFiles: 11 | 10 | 10 | H[2]HO_s | H2O_s | 1 | s<br /> readTracersFiles: 12 | 10 | 10 | H2[16]O_g | H2O_g | 1 | g<br /> readTracersFiles: 13 | 10 | 10 | H2[16]O_l | H2O_l | 1 | l<br /> readTracersFiles: 14 | 10 | 10 | H2[16]O_s | H2O_s | 1 | s<br /> readTracersFiles: 15 | 10 | 10 | H2[18]O_g_con | H2[18]O_g | 2 | g<br /> readTracersFiles: 16 | 10 | 10 | H2[18]O_l_con | H2[18]O_l | 2 | l<br /> readTracersFiles: 17 | 10 | 10 | H2[18]O_s_con | H2[18]O_s | 2 | s<br /> readTracersFiles: 18 | 10 | 10 | H2[18]O_g_oce | H2[18]O_g | 2 | g<br /> readTracersFiles: 19 | 10 | 10 | H2[18]O_l_oce | H2[18]O_l | 2 | l<br /> readTracersFiles: 20 | 10 | 10 | H2[18]O_s_oce | H2[18]O_s | 2 | s<br /> readTracersFiles: 21 | 10 | 10 | H[2]HO_g_con | H[2]HO_g | 2 | g<br /> readTracersFiles: 22 | 10 | 10 | H[2]HO_l_con | H[2]HO_l | 2 | l<br /> readTracersFiles: 23 | 10 | 10 | H[2]HO_s_con | H[2]HO_s | 2 | s<br /> readTracersFiles: 24 | 10 | 10 | H[2]HO_g_oce | H[2]HO_g | 2 | g<br /> readTracersFiles: 25 | 10 | 10 | H[2]HO_l_oce | H[2]HO_l | 2 | l<br /> readTracersFiles: 26 | 10 | 10 | H[2]HO_s_oce | H[2]HO_s | 2 | s<br /> readTracersFiles: 27 | 10 | 10 | H2[16]O_g_con | H2[16]O_g | 2 | g<br /> readTracersFiles: 28 | 10 | 10 | H2[16]O_l_con | H2[16]O_l | 2 | l<br /> readTracersFiles: 29 | 10 | 10 | H2[16]O_s_con | H2[16]O_s | 2 | s<br /> readTracersFiles: 30 | 10 | 10 | H2[16]O_g_oce | H2[16]O_g | 2 | g<br /> readTracersFiles: 31 | 10 | 10 | H2[16]O_l_oce | H2[16]O_l | 2 | l<br /> readTracersFiles: 32 | 10 | 10 | H2[16]O_s_oce | H2[16]O_s | 2 | s<br /> &lt;/pre&gt;<br /> <br /> 03/01/2023<br /> <br /> [[Category:WhatIs]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=HowTo:_debug_the_quality_control&diff=290 HowTo: debug the quality control 2022-12-16T11:17:10Z <p>Lguez : </p> <hr /> <div>As explained on the page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité], a number of quality control checks of the code are run every night to ensure that nothing was broken by the most recent commits to the svn depository (note that only the trunk version of the code is tested by this procedure).<br /> <br /> This note explains what to do if those regular tests reveal that the code is broken.<br /> <br /> The checks are launched by the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh], which actually launches the quality checks. The results of the tests are synthesized in one line and recorded in the file [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk]. Each line of this file (besides the comments) gives the version of the code being tested, its corresponding svn revision number and the results of the different checks (as explained in the file and the page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité]).<br /> <br /> === How to debug a failed quality check ===<br /> <br /> Once a failed quality check is established, one should look in the file [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk] to find out which version of the code caused a problem (for example 20211105.trunk). One can then find the output of the quality control check in the directory:<br /> <br /> lmdz-cq:/tmp/lmdz/LMDZ[version_number]<br /> <br /> with the actual output file of the check_version.sh script in<br /> <br /> lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.[version_number]<br /> <br /> ('''''lmdz-cq:/tmp/lmdz/LMDZ20211105.trunk''''' and '''''lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.20211105.trunk''''' respectively in our example). This output file is also [https://lmdz.lmd.jussieu.fr/Distrib/WORK accessible on internet].<br /> <br /> One can then go through the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh] comparing with the different output to find out what went wrong. Tests of correction can actually be done in the <br /> lmdz-cq:/tmp/lmdz/LMDZ[version_number]<br /> directory.<br /> <br /> [[Category:HowTo]]<br /> [[Category:ExpertDev]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=HowTo:_debug_the_quality_control&diff=289 HowTo: debug the quality control 2022-12-16T11:15:16Z <p>Lguez : </p> <hr /> <div>As explained on the page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité], a number of quality control checks of the code are run every night to ensure that nothing was broken by the most recent commits to the svn depository (note that only the trunk version of the code is tested by this procedure).<br /> <br /> This note explains what to do if those regular tests reveal that the code is broken.<br /> <br /> The checks are launched by the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh], which actually launches the quality checks. The results of the tests are synthesized in one line and recorded in the file [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk]. Each line of this file (besides the comments) gives the version of the code being tested, its corresponding svn revision number and the results of the different checks (as explained in the file and the page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité]).<br /> <br /> === How to debug a failed quality check ===<br /> <br /> Once a failed quality check is established, one should look in the file [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk] to find out which version of the code caused a problem (for example 20211105.trunk). One can then find the output of the quality control check in the<br /> <br /> lmdz-cq:/tmp/lmdz/LMDZ[version_number]<br /> <br /> directory with the actual output file of the check_version.sh script in<br /> <br /> lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.[version_number]<br /> <br /> ('''''lmdz-cq:/tmp/lmdz/LMDZ20211105.trunk''''' and '''''lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.20211105.trunk''''' respectively in our example). This output file is also [https://lmdz.lmd.jussieu.fr/Distrib/WORK accessible on internet].<br /> <br /> One can then go through the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh] comparing with the different output to find out what went wrong. Tests of correction can actually be done in the <br /> lmdz-cq:/tmp/lmdz/LMDZ[version_number]<br /> directory.<br /> <br /> [[Category:HowTo]]<br /> [[Category:ExpertDev]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=HowTo:_debug_the_quality_control&diff=288 HowTo: debug the quality control 2022-12-16T11:13:44Z <p>Lguez : </p> <hr /> <div>As explained on the page [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite Contrôle qualité], a number of quality control checks of the code are run every night to ensure that nothing was broken by the most recent commits to the svn depository (note that only the trunk version of the code is tested by this procedure).<br /> <br /> This note explains what to do if those regular tests reveal that the code is broken.<br /> <br /> The checks are launched by the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh creation_modipsl.sh] which prepares the distribution version of the code and then lauches [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh], which actually launches the quality checks. The results of the tests are synthesized in one line and recorded in the file [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk]. Each line of this file (besides the comments) gives the version of the code being tested, its corresponding svn revision number and the results of the different checks (as explained in the file and the webpage given above [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite]<br /> <br /> === How to debug a failed quality check ===<br /> <br /> Once a failed quality check is established, one should look in the file [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk] to find out which version of the code caused a problem (for example 20211105.trunk). One can then find the output of the quality control check in the<br /> <br /> lmdz-cq:/tmp/lmdz/LMDZ[version_number]<br /> <br /> directory with the actual output file of the check_version.sh script in<br /> <br /> lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.[version_number]<br /> <br /> ('''''lmdz-cq:/tmp/lmdz/LMDZ20211105.trunk''''' and '''''lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.20211105.trunk''''' respectively in our example). This output file is also [https://lmdz.lmd.jussieu.fr/Distrib/WORK accessible on internet].<br /> <br /> One can then go through the script [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh] comparing with the different output to find out what went wrong. Tests of correction can actually be done in the <br /> lmdz-cq:/tmp/lmdz/LMDZ[version_number]<br /> directory.<br /> <br /> [[Category:HowTo]]<br /> [[Category:ExpertDev]]</div> Lguez http://lmdz-forge.lmd.jussieu.fr/mediawiki/LMDZPedia/index.php?title=HowTo:_debug_the_quality_control&diff=287 HowTo: debug the quality control 2022-12-12T17:42:58Z <p>Lguez : </p> <hr /> <div>As explained on https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite, a number of quality control checks of the code are run every night to ensure that nothing was broken by the most recent commits to the svn depository (note that only the trunk version of the code is tested by this procedure).<br /> <br /> This note explains what to do if those regular tests reveal that the code is broken.<br /> <br /> The checks are launched by the [https://www.lmd.jussieu.fr/~lmdz/Distrib/creation_modipsl.sh following script] which prepares the distribution version of the code and then lauches the [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh script] that actually launches the quality checks. The results of the tests are synthesized in one line and recorded in the following file https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk. Each line of this file (besides the comments) gives the version of the code being tested, its corresponding svn revision number and the results of the different checks (as explained in the file and the webpage given above [https://lmdz.lmd.jussieu.fr/le-coin-des-developpeurs/controle-qualite]<br /> <br /> === How to debug a failed quality check ===<br /> <br /> Once a failed quality check is established, one should look in the [https://www.lmd.jussieu.fr/~lmdz/pub/LISMOI.trunk LISMOI.trunk file] to find out which version of the code caused a problem (for example 20211105.trunk). One can then find the output of the quality control check in the<br /> <br /> lmdz-cq:/tmp/lmdz/LMDZ[version_number]<br /> <br /> directory with the actual output file of the check_version.sh script in<br /> <br /> lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.[version_number]<br /> <br /> ('''''lmdz-cq:/tmp/lmdz/LMDZ20211105.trunk''''' and '''''lmdz-cq:~lmdz/WWW/Distrib/WORK/check.out.20211105.trunk''''' respectively in our example). This output file is also [https://lmdz.lmd.jussieu.fr/Distrib/WORK accessible on internet].<br /> <br /> One can then go through the [https://www.lmd.jussieu.fr/~lmdz/Distrib/check_version.sh check_version.sh script] comparing with the different output to find out what went wrong. Tests of correction can actually be done in the <br /> lmdz-cq:/tmp/lmdz/LMDZ[version_number]<br /> directory.<br /> <br /> [[Category:HowTo]]<br /> [[Category:ExpertDev]]</div> Lguez