7. Glossary Terms
Here are some definitions of the specific terms used in the PyMoDAQ documentation:
Any instrument with a controllable varying parameter
Any instrument generating data to be recorded
- Control Modules
GUI for actuators and detectors, with subsequent classes:
DAQ_Viewer, see Control Modules
XML file containing the number and type of control modules to be used for a given experiment. You can create, modify and load a preset from the Dashboard
Enum informing about the source of the data object, for instance raw from a detector or processed from mathematical functions (from ROI, …)
Enum for the dimensionality representation of the data object, for instance scalars have a dimensionality Data0D, waveforms or vectors have Data1D dimensionality, camera’s data are Data2D, and hyperspectral (or other) are DataND
Enum for the distribution type of the data object. Data can be stored on linear grid (think about an oscilloscope trace having a fixed time interval, or camera having a regular grid of pixels) or stored on non uniform and non linear “positions”, for instance data taken at random time intervals. Data can therefore have two distributions: uniform or spread.
Signal and Navigation is a term taken from the hyperspy package vocabulary. It is useful when dealing with multidimensional data. Imagine data you obtained from a camera (256x1024 pixels) during a linear 1D scan of one actuator (100 steps). The final shape of the data would be (100, 256, 1024). The first dimension corresponds to a Navigation axis (the scan), and the rest to Signal axes (the real detector’s data). The corresponding data has a dimensionality of DataND and a representation of (100|256,1024).
Short name for
Short name for
A plugin is a python package whose name is of the type: pymodaq_plugins_apluginname containing functionalities to be added to PyMoDAQ
A plugin may contains added functionalities such as:
Classes to add a given instrument: allows a given instrument to be added programmatically in a Control Modules graphical interface
Instrument drivers located in a hardware folder: contains scripts/classes to ease communication with the instrument. Could be third party packages such as Pymeasure
PID models located in a models folder: scripts and classes defining the behaviour of a given PID loop including several actuators or detectors, see The PID Model
Extensions located in a extensions folder: scripts and classes allowing to build extensions on top of the DashBoard
Entry points python mechanism is used to let know PyMoDAQ of installed Instrument, PID models or extensions plugins
A module in the python sense is an importable object either a directory containing an __init__.py file or a python file containing data, functions or classes.
If there is code that can be executed within your module but you don’t want it to be executed when importing,
make sure to protect the execution using a :
if __name__ == '__main__': clause.