Overview
The top layer in the EHRATM software stack is ehratmworkflow. Underneath this layer there has been no workflow implied in anything that we built.
The underlying layers simply provide a collection of plug and play components that can be arranged in any way that a programmer would like to create a variety of NWP and ATM applications. This is where our targeted top-level ehratmworkflow layer comes in. It relies on the fact that the robust components it needs are available in the underlying ehratm layer and provides the “plumbing” needed to arrange the ehratm components as dictated by a user-supplied workflow namelist (wfnamelist). The ehratmworklow layer contains a large collection of wfnamelists which can be tested all at once in batch mode to ensure that they all work. As each one is invoked, it is providing additional testing of the underlying ehratm and nwpservice layers. The following provides a simple illustration that all of this abstraction has ultimately provided to the user, who simply invokes ehratmwf.py, supplying workflow requirements in a namelist (see Workflow Namelist (wfnamelist) Reference Document).
