experimentor.models.devices.cameras.basler package¶
Submodules¶
experimentor.models.devices.cameras.basler.basler module¶
-
class
experimentor.models.devices.cameras.basler.basler.
BaslerCamera
(camera, initial_config=None)[source]¶ Bases:
experimentor.models.devices.cameras.base_camera.BaseCamera
-
ROI
¶
-
acquisition_mode
¶
-
auto_exposure
¶ Off, Once, Continuous
Type: Auto exposure can take one of three values
-
auto_gain
¶ Off, Once, Continuous
Type: Auto Gain must be one of three values
-
binning_x
¶
-
binning_y
¶
-
buffer_size
¶
-
ccd_height
¶
-
ccd_width
¶
-
exposure
¶ The exposure of the camera, defined in units of time
-
finalize
()[source]¶ Finalizes the model. It only takes care of closing the publisher. Child classes should implement their own finalize methods (they get called automatically), and either close the publisher explicitly or use this method.
-
frame_rate
¶
-
gain
¶ Gain is a float
-
height
¶
-
initialize
¶ Decorator for methods in models. Actions are useful when working with methods that run once, and are normally associated with pressing of a button. Actions are multi-threaded by default, using a single executor that returns a future.
Even though Actions (intended as the method in a model) can take arguments, it may be a better approach to store the parameters as attributes before triggering an action. In this way, triggering an action would be equivalent to pressing a button. In the same way, actions can store return values as attribute in the model itself, avoiding the need to keep track of the future returned by the action. Be aware of potential racing conditions that may arise when using shared memory to exchange information.
Todo
Define a clear protocol for exchanging information with models. Should it be state-based (i.e. storing parameters as attributes in the class) or statement based (i.e. passing parameters as arguments of methods).
-
new_image
¶ Base signal which implements the common pattern for defining, emitting and connecting a signal
-
pixel_format
¶ Pixel format must be one of Mono8, Mono12, Mono12p
-
start_free_run
()[source]¶ Starts a free run from the camera. It will preserve only the latest image. It depends on how quickly the experiment reads from the camera whether all the images will be available or only some.
-
stop_camera
¶ Decorator for methods in models. Actions are useful when working with methods that run once, and are normally associated with pressing of a button. Actions are multi-threaded by default, using a single executor that returns a future.
Even though Actions (intended as the method in a model) can take arguments, it may be a better approach to store the parameters as attributes before triggering an action. In this way, triggering an action would be equivalent to pressing a button. In the same way, actions can store return values as attribute in the model itself, avoiding the need to keep track of the future returned by the action. Be aware of potential racing conditions that may arise when using shared memory to exchange information.
Todo
Define a clear protocol for exchanging information with models. Should it be state-based (i.e. storing parameters as attributes in the class) or statement based (i.e. passing parameters as arguments of methods).
-
stop_free_run
¶ Decorator for methods in models. Actions are useful when working with methods that run once, and are normally associated with pressing of a button. Actions are multi-threaded by default, using a single executor that returns a future.
Even though Actions (intended as the method in a model) can take arguments, it may be a better approach to store the parameters as attributes before triggering an action. In this way, triggering an action would be equivalent to pressing a button. In the same way, actions can store return values as attribute in the model itself, avoiding the need to keep track of the future returned by the action. Be aware of potential racing conditions that may arise when using shared memory to exchange information.
Todo
Define a clear protocol for exchanging information with models. Should it be state-based (i.e. storing parameters as attributes in the class) or statement based (i.e. passing parameters as arguments of methods).
-
width
¶
-