Multiprocessing Task Interfaces

The following describes ‘type interfaces.’ See Type Interfaces for more info on what that is.

The following are type interfaces that allow the creation of several instances of a task, possibly reporting intermediate status, and collecting results in the end.

Such interfaces are required, for example, to run parallel tasks with the OMP task dispatcher, Tomographer::MultiProc::OMP::TaskDispatcher, which is itself a TaskDispatcher Interface compliant type.

In the future, I hope we can also write an MPI implementation using the same interfaces. (Hopefully everything works fine if ResultType and TaskCData is serializable)

A task is implemented by a Task Interface. It may refer to some global, constant data (the parameters of the problem) stored in a struct (referred to as TaskCData in the following docs). Each Task must also conform to the Resultable Interface and generates a result, which is then collected and returned by the task dispatcher. The task manager exposes an API to interact with the Task objects: it is the TaskManagerIface Interface. This interface may be used for example in order to submit intermediate status reports.

Since

Changed in Tomographer 5.0: removed the ResultsCollector type interface; the tasks must now themselves conform to the Resultable Interface.

Type interfaces which are used by the task dispatcher:

• TaskCData Interface
• Task Interface
• TaskManagerIface Interface

The type interface which the task dispatcher itself obeys:

• TaskDispatcher Interface