Skip to content

Releases: PyMoDAQ/pymodaq_plugins_basler

Use of config files to create specific configs for all camera models

15 Dec 13:32
fb0fe95

Choose a tag to compare

Previously, a difficulty was that different camera models had different accessible attributes and attribute names.
Instead of making a plugin that handles all those cases, the plugin now relies on model-specific config files, in which the user can easily choose the attributes they want to expose.

For a given camera model, if no config file is present, the plugin will offer to create a new config file (eg in .pymodaq/config_acA645-100gm.json) with basic attributes (exposure and gain), whose names will be automatically adapted to the available attributes. The style of the .json configuration files follows the usual pymodaq config files.

What's Changed

New Contributors

Full Changelog: 1.0.1...5.1.0

1.0.1

20 Mar 19:58
88c8c68

Choose a tag to compare

What's Changed

  • apply the pyproject packaging layout by @seb5g in #17

New Contributors

  • @seb5g made their first contribution in #17

Full Changelog: 1.0.0...1.0.1

Provide compatibility with different cameras

20 Mar 16:21
ecf48b6

Choose a tag to compare

  • The plugin will now check for various attribute names available, making it compatible with more cameras from Basler. Changes are mainly on the Gain and Exposure parameters.
  • The plugin can now emit image axes as real life units (e.g. microns). Either the pixel size is known already (hardcoded in the plugin), or can be specified by the user in the interface.
  • Now follows more recent templates.

v0.1.1

25 Jan 16:26

Choose a tag to compare

[0.1.1] - 2024-01-25

Fixed

  • Fixed type hints to be compatible with older python versions (#6)

Full Changelog: v0.1.0...v0.1.1

v0.1.0

25 Jan 10:59

Choose a tag to compare

CHANGELOG

[0.1.0] - 2024-01-25

Initial version

Full Changelog: https://github.com/BenediktBurger/pymodaq_plugins_basler/commits/v0.1.0