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:
Topology for PIV computation (fluidimage.topologies.piv) |
|
Topology for BOS computation (fluidimage.topologies.bos) |
|
Topology for image preprocessing (fluidimage.topologies.preproc) |
|
Topology for image2image preprocessing |
|
Topology for surface tracking(fluidimage.topologies.surface_tracking) |
|
Topology for optical flow (fluidimage.topologies.optical_flow) |
These others modules defined classes and functions useful for developers.
Topology base (fluidimage.topologies.base) |
|
Parse and analyze logging files (fluidimage.topologies.log) |
|
Launchers for topologies used for GUI (fluidimage.topologies.launcher) |
|
Splitters to split a topology task |
Functions
|
Makes new directory for results, if required, and returns its path. |