What is ecflow

ECFLOW is a client/server workflow package that enables users to run a large number of programs (with dependencies on each other and on time) in a controlled environment. It provides reasonable tolerance for hardware and software failures, combined with restart capabilities.
ECFLOW submits tasks (jobs) and receives acknowledgments from the tasks when they change status and when they send events, using child commands embedded in your scripts. ECFLOW stores the relationships between tasks, and is able to submit tasks dependant on triggers, such as when a given task changes its status, for example when it finishes. Users communicate with ECFLOW server using:

ECFLOW runs as a server receiving requests from clients. CLI, ecflowview and the suite jobs are the clients. Communication is based on TCP/IP. Note that ECFLOW is a scheduler and is not a queuing system such as NQS, SGE, Load leveller or PBS. However, it can submit to queuing systems.

History

ECFLOW is a product of the European Centre for Medium-range Weather Forecasts (ECMWF) and was written by the Meteorological Applications (MetApps) section.

ECFLOW is a complete replacement of SMS. It has been written using an object oriented language. It provides most of the functionality that is available in SMS.

Differences with SMS

Ecflow excecutables

 

ECFLOW functionality is provided by the following executables and shared libraries

  • ecflow_client: This executable is a command line program; it is used for all communication with the server. This executable implements the Command Level Interface (CLI). The bulk of this functionality is also provided by the python API
  • ecflowview: This is a specialised GUI client that monitors and visualises the node tree hierarchy.
  • ecflow_server: This executable is the server. It is responsible for scheduling the jobs and responding to ecflow_client requests.
  • ecflow.so : These shared libraries provide the python API for creating the suite definition and communication with the server.