| Horizontal Navigation Bar | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The operational suite contains two cycles named 00 and 12.
Each cycle contains three parts:
o Analysis
- fetch the observations
- run the analysis model
- post-process the data
o Forecast
- Prepare the input data
- Run the forecast model. The forecast model outputs its results every 6 hours up to 24 hours for cycle 00 and up to 240 hours for cycle 12.
o Archive
- Save the analysis results.
- Save the forecast results as they become available.
What do:
- Write a suite definition for this suite.
- How should the ecf script‘s be organised?
Useful pointers:
One possible Operational Suite Solution
| Horizontal Navigation Bar | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
| HTML | ||||||||||||||||||||||||||
|
<div class="section" id="operational-suite">
<span id="index-0"></span><span id="id1"></span>
<ul>
<li><p class="first">The operational suite contains two cycles named 00 and 12.</p>
</li>
<li><dl class="first docutils">
<dt>Each cycle contains three parts:</dt>
<dd><dl class="first last docutils">
<dt>o Analysis</dt>
<dd><ul class="first last simple">
<li>fetch the observations,</li>
<li>run the analysis model,</li>
<li>post-process the data</li>
</ul>
</dd>
<dt>o Forecast</dt>
<dd><ul class="first last simple">
<li>Prepare the input data</li>
<li>Run the forecast model. The forecast model outputs its results every 6 hours up to 24 hours for cycle 00 and up to 240 hours for cycle 12.</li>
</ul>
</dd>
<dt>o Archive</dt>
<dd><ul class="first last simple">
<li>Save the analysis results.</li>
<li>Save the forecasts results as they become available.</li>
</ul>
</dd>
</dl>
</dd>
</dl>
</li>
</ul>
<p>What do:</p>
<ol class="arabic simple">
<li>Write a <a class="reference internal" href="/wiki/display/ECFLOW/Glossary#term-suite-definition"><em class="xref std std-term">suite definition</em></a> for this suite.</li>
<li>How should the <a class="reference internal" href="/wiki/display/ECFLOW/Glossary#term-ecf-script"><em class="xref std std-term">ecf script</em></a>‘s be organised?</li>
</ol>
<p>Useful pointers:</p>
<blockquote>
<div><ul class="simple">
<li><a class="reference internal" href="/wiki/display/ECFLOW/Add+Trigger#add-trigger"><em>Add Trigger</em></a></li>
<li><a class="reference internal" href="/wiki/display/ECFLOW/Add+a+meter#add-meter"><em>Add a meter</em></a></li>
<li><a class="reference internal" href="/wiki/display/ECFLOW/ECF+variables#add-variable"><em>ECF variables</em></a></li>
<li><a class="reference internal" href="/wiki/display/ECFLOW/Using+python+scripting#using-python-scripting"><em>Using python scripting</em></a></li>
<li><a class="reference internal" href="/wiki/display/ECFLOW/File+location#file-location"><em>File location</em></a> for ECF_FILES</li>
<li><a class="reference internal" href="/wiki/display/ECFLOW/ecFlow+Python+Api#python-api"><em>ecFlow Python Api</em></a></li>
</ul>
</div></blockquote>
<p>One possible <a class="reference internal" href="/wiki/display/ECFLOW/Operational+Suite+Solution#operational-suite-soln"><em>Operational Suite Solution</em></a></p>
</div>
|