Acquisitions

The Acquisition class is a powerful abstraction that can be used for a wide range of microscopy workflows. The only requirement for running an acquisition is to use one of several possible mechanisms for Specifying data to acquire

More advanced functionality can be implemented through the use of Acquisition hooks, which are used to modify acquisition control on-the-fly or synchrnoize hardware outside of micro-manager with acquisition, or with Image processors, which can be used to modify images during before saving/display or to divert images away from display/saving to custom endpoints.

The Acquisition class can also be used for Fast acquisition with hardware triggering.

Reading acquired data describes how to read the data acquired by an Acquisition as a numpy or dask array.

The figure figure below gives an overview of all of the features this class provides.

Overview figure of pycro-manager Acquisitions

Overview of pycro-manager Acquisitions. The blue boxes show acquisitions starting with some source of ”acquisition events”, instructions for image collection and associated hardware changes. Green boxes represent acquisition events that are optimized, then used to move hardware and collect images. ”Acquisition hooks” can be used to execute arbitrary code synchronously or modify/delete instructions on-the-fly. Magenta boxes represent acquired images going straight to the default image saving and display, or being diverted through ”image processors”, which allow for modification of images or diversion to external saving and visualization.