|
TECA
The Toolkit for Extreme Climate Analysis
|
Base class and default implementation for executives. More...
#include <teca_algorithm_executive.h>
Public Member Functions | |
| virtual int | initialize (MPI_Comm comm, const teca_metadata &md) |
| virtual teca_metadata | get_next_request () |
| void | set_verbose (int a_verbose) |
| int | get_verbose () const |
Static Public Member Functions | |
| static p_teca_algorithm_executive | New () |
Protected Member Functions | |
| teca_algorithm_executive (const teca_algorithm_executive &)=default | |
| teca_algorithm_executive (teca_algorithm_executive &&)=default | |
| teca_algorithm_executive & | operator= (const teca_algorithm_executive &)=default |
| teca_algorithm_executive & | operator= (teca_algorithm_executive &&)=default |
Base class and default implementation for executives.
Algorithm executives can control pipeline execution by providing a series of requests. this allows for the executive to act as a load balancer. the executive can for example partition requests across spatial data, time steps, or file names. in an MPI parallel setting the executive could coordinate this partitioning amongst the ranks. However, the only requirement of an algorithm executive is that it provide at least one non-empty request.
The default implementation creates a single request for the first index specified by the "index_initializer_key" using the "index_request_key" with "device_id" set to execute on the CPU or GPU (if GPU's are available).