File: operational-suite.rst

package info (click to toggle)
ecflow 5.15.2-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 51,868 kB
  • sloc: cpp: 269,341; python: 22,756; sh: 3,609; perl: 770; xml: 333; f90: 204; ansic: 141; makefile: 70
file content (35 lines) | stat: -rw-r--r-- 1,042 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
.. _tutorial-operational-suite:

Operational Suite
-----------------

* 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 forecasts results as they become available. 

What do:

1. Write a :term:`suite definition` for this suite.
2. How should the :term:`ecf script`\ s be organised? 


Useful pointers:

    * :ref:`tutorial-add-trigger`  
    * :ref:`tutorial-add-meter` 
    * :ref:`tutorial-add-variable` 
    * :ref:`tutorial-using-python-scripting`
    * :ref:`tutorial-file-location` for ECF_FILES  
    * :ref:`python_based_suite_definition`
    
One possible :ref:`tutorial-operational_suite_soln`