build based on 5650d7f3

previews/PR980/.documenter-siteinfo.json

@@ -1 +1 @@
-{"documenter":{"julia_version":"1.9.4","generation_timestamp":"2023-12-02T12:03:46","documenter_version":"1.0.1"}}
+{"documenter":{"julia_version":"1.9.4","generation_timestamp":"2023-12-04T11:14:52","documenter_version":"1.0.1"}}

previews/PR980/Build/Build_with_makeup/index.html

@@ -79,4 +79,4 @@
 
 # or not to mess up the output, use just one process for compilations
 
-gmake NPES=1 -i</code></pre><h3 id="Creating-precompiled-installation"><a class="docs-heading-anchor" href="#Creating-precompiled-installation">Creating precompiled installation</a><a id="Creating-precompiled-installation-1"></a><a class="docs-heading-anchor-permalink" href="#Creating-precompiled-installation" title="Permalink"></a></h3><p>If you want to provide precompiled libraries, objects, source code to other users so that they do not have to start compilation from scratch, then make a distribution or precompiled installation as follows:</p><pre><code class="language-bash hljs">gmake PRECOMPILED=/a/precompiled/rootdir precompiled</code></pre><p>After this the stuff you just compiled ends up in directory <code>/a/precompiled/rootdir</code> with two subdirectories : <code>src/</code> and <code>util/</code>. All executables are currently removed.</p><p>You can repeat this call, and it will just <code>rsync</code> the modified bits.</p><h3 id="Update/check-your-interface-blocks-outside-configure"><a class="docs-heading-anchor" href="#Update/check-your-interface-blocks-outside-configure">Update/check your interface blocks outside <code>configure</code></a><a id="Update/check-your-interface-blocks-outside-configure-1"></a><a class="docs-heading-anchor-permalink" href="#Update/check-your-interface-blocks-outside-configure" title="Permalink"></a></h3><p>The <code>configure</code> has options -c or -g to check up or enforce for (re-)creation of interface blocks of projects <code>arp</code> and <code>ald</code>. To avoid full and lengthy <code>configure</code>-run, you can just do the following:</p><pre><code class="language-bash hljs">gmake intfb</code></pre></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../Build_with_cmake/">« CMake</a><a class="docs-footer-nextpage" href="../../System/MFaccess/">MF Access »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="auto">Automatic (OS)</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.0.1 on <span class="colophon-date" title="Saturday 2 December 2023 12:03">Saturday 2 December 2023</span>. Using Julia version 1.9.4.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html>
+gmake NPES=1 -i</code></pre><h3 id="Creating-precompiled-installation"><a class="docs-heading-anchor" href="#Creating-precompiled-installation">Creating precompiled installation</a><a id="Creating-precompiled-installation-1"></a><a class="docs-heading-anchor-permalink" href="#Creating-precompiled-installation" title="Permalink"></a></h3><p>If you want to provide precompiled libraries, objects, source code to other users so that they do not have to start compilation from scratch, then make a distribution or precompiled installation as follows:</p><pre><code class="language-bash hljs">gmake PRECOMPILED=/a/precompiled/rootdir precompiled</code></pre><p>After this the stuff you just compiled ends up in directory <code>/a/precompiled/rootdir</code> with two subdirectories : <code>src/</code> and <code>util/</code>. All executables are currently removed.</p><p>You can repeat this call, and it will just <code>rsync</code> the modified bits.</p><h3 id="Update/check-your-interface-blocks-outside-configure"><a class="docs-heading-anchor" href="#Update/check-your-interface-blocks-outside-configure">Update/check your interface blocks outside <code>configure</code></a><a id="Update/check-your-interface-blocks-outside-configure-1"></a><a class="docs-heading-anchor-permalink" href="#Update/check-your-interface-blocks-outside-configure" title="Permalink"></a></h3><p>The <code>configure</code> has options -c or -g to check up or enforce for (re-)creation of interface blocks of projects <code>arp</code> and <code>ald</code>. To avoid full and lengthy <code>configure</code>-run, you can just do the following:</p><pre><code class="language-bash hljs">gmake intfb</code></pre></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../Build_with_cmake/">« CMake</a><a class="docs-footer-nextpage" href="../../System/MFaccess/">MF Access »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="auto">Automatic (OS)</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.0.1 on <span class="colophon-date" title="Monday 4 December 2023 11:14">Monday 4 December 2023</span>. Using Julia version 1.9.4.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html>

previews/PR980/DataAssimilation/CHKEVO/index.html

@@ -20,4 +20,4 @@
  CHKEVO :   1.3677546254375832       0.22965677860570116     
  CHKEVO :   1.1506125378848564       0.20575065246468008     
  CHKEVO :  0.98597708942270756       0.19299583141063531
-.....</code></pre><ul><li>The first column contains the string <code>CHKEVO :</code></li><li>Second column contains the RMS of dps/dt averaged over the domain.</li><li>Second column contains the AVG of dps/dt averaged over the domain.</li></ul><p>The RMS of dps/dt alone can be extracted with:</p><pre><code class="language-bash hljs">grep &quot;^ CHKEVO : &quot; HM_Date_2013041118.html | tail -n +2 | awk &#39;{print $3}&#39;</code></pre></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../MTEN/">« MTEN</a><a class="docs-footer-nextpage" href="../NWECHKEVO/">NWECHKEVO »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="auto">Automatic (OS)</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.0.1 on <span class="colophon-date" title="Saturday 2 December 2023 12:03">Saturday 2 December 2023</span>. Using Julia version 1.9.4.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html>
+.....</code></pre><ul><li>The first column contains the string <code>CHKEVO :</code></li><li>Second column contains the RMS of dps/dt averaged over the domain.</li><li>Second column contains the AVG of dps/dt averaged over the domain.</li></ul><p>The RMS of dps/dt alone can be extracted with:</p><pre><code class="language-bash hljs">grep &quot;^ CHKEVO : &quot; HM_Date_2013041118.html | tail -n +2 | awk &#39;{print $3}&#39;</code></pre></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../MTEN/">« MTEN</a><a class="docs-footer-nextpage" href="../NWECHKEVO/">NWECHKEVO »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="auto">Automatic (OS)</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.0.1 on <span class="colophon-date" title="Monday 4 December 2023 11:14">Monday 4 December 2023</span>. Using Julia version 1.9.4.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html>

previews/PR980/DataAssimilation/DaAlgorithms/index.html

@@ -13,4 +13,4 @@
 NSIMU4D=15,20                           # Maximum number of cost function simulations in 4D-Var outer loops
 CH_RES_SPEC=yes                         # yes => change of resolution of the increment spectrally; no => by FULLPOS
 FORCE1=no                               # yes => tendency increment; no => analysis increment in loop 1
-FORCE2=no                               # yes =&gt; tendency increment; no =&gt; analysis increment in loop 2</code></pre><h3 id="Schematic-work-flow-of-4D-Var"><a class="docs-heading-anchor" href="#Schematic-work-flow-of-4D-Var">Schematic work flow of 4D-Var</a><a id="Schematic-work-flow-of-4D-Var-1"></a><a class="docs-heading-anchor-permalink" href="#Schematic-work-flow-of-4D-Var" title="Permalink"></a></h3><p><img src="../../assets/smsanua.png" alt/></p><ul><li>After the screening <code>4DVscreen</code> for the default 3h observation window (2h before and 1h after the start of the main forecast), </li><li><code>4DVprolog</code> prepares the initial conditions at the appropriate resolution (<code>ILRES</code> settings) for the forecasts used in minimization. The input here is the background <code>BGHR (ICMSHHARM+0001</code> fields of the former cycle supplemented with some surface fields). </li><li>Subsequently <code>4DVminim</code> produces initially the low resolution at the beginning of the observation  window (<code>an_lowres_$loop</code>), which is then (<code>CH_RES_SPEC=yes</code> in <code>config_exp.h</code>) transformed to the field at forecast resolution (<code>an_hr_begwin</code>). </li><li>This field is complemented in <code>Blendhr</code> with necessary surface fields and the resulting field  (<code>anb_hr_begwin</code>) acts as the initial condition for the trajectory run <code>4DVtraj</code>. </li><li>From the 2h forecast of <code>4DVtraj</code> (<code>ICMSHTRAJ+0002</code> fields) the main forecast is started.</li></ul><h2 id="Cloudingest-Cloud-Initialization"><a class="docs-heading-anchor" href="#Cloudingest-Cloud-Initialization">Cloudingest - Cloud Initialization</a><a id="Cloudingest-Cloud-Initialization-1"></a><a class="docs-heading-anchor-permalink" href="#Cloudingest-Cloud-Initialization" title="Permalink"></a></h2><p>The cloud initialization modifies temperature and humidity fields with help of MSGcloudYYYYMMDDHH.grib file, which contains 2-d fields of cloudtop-temperature [K], cloudmask [0-1] and cloudbase [m].  Pre cy46h the Cloudingest happened within MASTERODB in <code>src/arpifs</code> specifically in <code>src/arpifs/phys_dmn/msginit.F90</code> routine. Since cy46h the Cloudingest uses pysurfex and gl to do the job. </p><h3 id="Settings-3"><a class="docs-heading-anchor" href="#Settings-3">Settings</a><a class="docs-heading-anchor-permalink" href="#Settings-3" title="Permalink"></a></h3><p>Enable Cloudingest in <code>ecf/config_exp.h</code>:</p><pre><code class="nohighlight hljs">USE_MSG=yes                              # Use MSG data for adjustment of inital profiles, EXPERIMENTAL! (no|yes), expects MSGcloudYYYYMMDDHH.grib in $OBDIR</code></pre><p>And in src/include.ass:</p><pre><code class="nohighlight hljs">export CLOUD_BASE=1                # 1 and USE_MSG=true (ecf/config_exp.h) =&gt; msginit</code></pre><p>to replace the cloudbase field in MSGcloudYYYYMMDDHH.grib with an OI interpolated field of SYNOP observations of CloudBaseHeights and postprocessed field of cloudbases of the first-guess file.</p><h3 id="Schematic-work-flow-of-Cloudingest"><a class="docs-heading-anchor" href="#Schematic-work-flow-of-Cloudingest">Schematic work flow of Cloudingest</a><a id="Schematic-work-flow-of-Cloudingest-1"></a><a class="docs-heading-anchor-permalink" href="#Schematic-work-flow-of-Cloudingest" title="Permalink"></a></h3><p>In case of 3DVar assimilation, the ecflow AnUA family should look like this:</p><p><img src="../../assets/CloudIngest_scheme.png" alt/></p></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../StructureFunctions/">« Structure functions</a><a class="docs-footer-nextpage" href="../DigitalFilterInitialization/">Digital Filter Initialization »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="auto">Automatic (OS)</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.0.1 on <span class="colophon-date" title="Saturday 2 December 2023 12:03">Saturday 2 December 2023</span>. Using Julia version 1.9.4.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html>
+FORCE2=no                               # yes =&gt; tendency increment; no =&gt; analysis increment in loop 2</code></pre><h3 id="Schematic-work-flow-of-4D-Var"><a class="docs-heading-anchor" href="#Schematic-work-flow-of-4D-Var">Schematic work flow of 4D-Var</a><a id="Schematic-work-flow-of-4D-Var-1"></a><a class="docs-heading-anchor-permalink" href="#Schematic-work-flow-of-4D-Var" title="Permalink"></a></h3><p><img src="../../assets/smsanua.png" alt/></p><ul><li>After the screening <code>4DVscreen</code> for the default 3h observation window (2h before and 1h after the start of the main forecast), </li><li><code>4DVprolog</code> prepares the initial conditions at the appropriate resolution (<code>ILRES</code> settings) for the forecasts used in minimization. The input here is the background <code>BGHR (ICMSHHARM+0001</code> fields of the former cycle supplemented with some surface fields). </li><li>Subsequently <code>4DVminim</code> produces initially the low resolution at the beginning of the observation  window (<code>an_lowres_$loop</code>), which is then (<code>CH_RES_SPEC=yes</code> in <code>config_exp.h</code>) transformed to the field at forecast resolution (<code>an_hr_begwin</code>). </li><li>This field is complemented in <code>Blendhr</code> with necessary surface fields and the resulting field  (<code>anb_hr_begwin</code>) acts as the initial condition for the trajectory run <code>4DVtraj</code>. </li><li>From the 2h forecast of <code>4DVtraj</code> (<code>ICMSHTRAJ+0002</code> fields) the main forecast is started.</li></ul><h2 id="Cloudingest-Cloud-Initialization"><a class="docs-heading-anchor" href="#Cloudingest-Cloud-Initialization">Cloudingest - Cloud Initialization</a><a id="Cloudingest-Cloud-Initialization-1"></a><a class="docs-heading-anchor-permalink" href="#Cloudingest-Cloud-Initialization" title="Permalink"></a></h2><p>The cloud initialization modifies temperature and humidity fields with help of MSGcloudYYYYMMDDHH.grib file, which contains 2-d fields of cloudtop-temperature [K], cloudmask [0-1] and cloudbase [m].  Pre cy46h the Cloudingest happened within MASTERODB in <code>src/arpifs</code> specifically in <code>src/arpifs/phys_dmn/msginit.F90</code> routine. Since cy46h the Cloudingest uses pysurfex and gl to do the job. </p><h3 id="Settings-3"><a class="docs-heading-anchor" href="#Settings-3">Settings</a><a class="docs-heading-anchor-permalink" href="#Settings-3" title="Permalink"></a></h3><p>Enable Cloudingest in <code>ecf/config_exp.h</code>:</p><pre><code class="nohighlight hljs">USE_MSG=yes                              # Use MSG data for adjustment of inital profiles, EXPERIMENTAL! (no|yes), expects MSGcloudYYYYMMDDHH.grib in $OBDIR</code></pre><p>And in src/include.ass:</p><pre><code class="nohighlight hljs">export CLOUD_BASE=1                # 1 and USE_MSG=true (ecf/config_exp.h) =&gt; msginit</code></pre><p>to replace the cloudbase field in MSGcloudYYYYMMDDHH.grib with an OI interpolated field of SYNOP observations of CloudBaseHeights and postprocessed field of cloudbases of the first-guess file.</p><h3 id="Ecflow-and-schematic-work-flow-of-Cloudingest"><a class="docs-heading-anchor" href="#Ecflow-and-schematic-work-flow-of-Cloudingest">Ecflow and schematic work flow of Cloudingest</a><a id="Ecflow-and-schematic-work-flow-of-Cloudingest-1"></a><a class="docs-heading-anchor-permalink" href="#Ecflow-and-schematic-work-flow-of-Cloudingest" title="Permalink"></a></h3><p>In case of 3DVar assimilation, the ecflow AnUA family should look like this:</p><p><img src="../../assets/CloudIngest_scheme.png" alt/></p><p>And a schematic work-flow of tasks and files involved: <img src="../../assets/Cloudingest_mermaid-diagram.png" alt/></p></article><nav class="docs-footer"><a class="docs-footer-prevpage" href="../StructureFunctions/">« Structure functions</a><a class="docs-footer-nextpage" href="../DigitalFilterInitialization/">Digital Filter Initialization »</a><div class="flexbox-break"></div><p class="footer-message">Powered by <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> and the <a href="https://julialang.org/">Julia Programming Language</a>.</p></nav></div><div class="modal" id="documenter-settings"><div class="modal-background"></div><div class="modal-card"><header class="modal-card-head"><p class="modal-card-title">Settings</p><button class="delete"></button></header><section class="modal-card-body"><p><label class="label">Theme</label><div class="select"><select id="documenter-themepicker"><option value="documenter-light">documenter-light</option><option value="documenter-dark">documenter-dark</option><option value="auto">Automatic (OS)</option></select></div></p><hr/><p>This document was generated with <a href="https://github.com/JuliaDocs/Documenter.jl">Documenter.jl</a> version 1.0.1 on <span class="colophon-date" title="Monday 4 December 2023 11:14">Monday 4 December 2023</span>. Using Julia version 1.9.4.</p></section><footer class="modal-card-foot"></footer></div></div></div></body></html>