fluidimage.topologies

Topologies representing asynchronous computations

A topology represents an asynchronous computation as a graph of waiting queues and works. Works take (an) item(s) in (an) input queue(s), process it/them and put the result in (an) output queue(s).

All topologies inherit from a base class fluidimage.topologies.base.TopologyBase, which has methods to define the topology (add_queue and add_work), to represent the computational graph (make_code_graphviz) and finally to execute it (compute).

Users are particularly concerned with the following already defined topologies:

piv

Topology for PIV computation (fluidimage.topologies.piv)

bos

Topology for BOS computation (fluidimage.topologies.bos)

preproc

Topology for image preprocessing (fluidimage.topologies.preproc)

image2image

Topology for image2image preprocessing (fluidimage.topologies.image2image)

surface_tracking

Topology for surface tracking(fluidimage.topologies.surface_tracking)

optical_flow

Topology for optical flow (fluidimage.topologies.optical_flow)

These others modules defined classes and functions useful for developers.

base

Topology base (fluidimage.topologies.base)

log

Parse and analyze logging files (fluidimage.topologies.log)

launcher

Launchers for topologies used for GUI (fluidimage.topologies.launcher)

Functions

prepare_path_dir_result(path_dir_input, …)

Makes new directory for results, if required, and returns its path.