Topologies representing asynchronous computations

A topology is responsible for the organization of the processing of a succession of input “unit” objects. It contains the description as a “topology” of the processing of one “unit” object (for example the production of 1 PIV field from a couple of images). A topology is formed of a set of unit processes linked by waiting queues.

The Topology object also organizes the “loop” over the input set. It organizes the asynchronous (parallel) calls of the work units of the topology with the correct transfer of data between them.

Users are particularly concerned with the PIV and preprocessing topologies:

piv Topology for PIV computation (fluidimage.topologies.piv) ==================================================================.
bos Topology for BOS computation (fluidimage.topologies.bos) ==================================================================.
preproc Topology for preprocessing images (fluidimage.topologies.preproc) ===========================================================================.
image2image Topology for image processing (fluidimage.topologies.image2image) ===========================================================================.

These others modules defined classes and functions useful for developers.

base Topology base (fluidimage.topologies.base) ====================================================.
waiting_queues Waiting queues (fluidimage.topologies.waiting_queues) ===============================================================.
log Parse and analyze logging files (fluidimage.topologies.log) =====================================================================.
launcher Launchers for topologies used for GUI (fluidimage.topologies.launcher) =============================================================================.


prepare_path_dir_result(path_dir_input, …) Makes new directory for results, if required, and returns its path.