NOMAD-CAMELS Driver for PyLabLibs Cam-Control
Connects to the server of Cam-Control to save, snap and request frames. Written for the measurement software NOMAD-CAMELS.
More information on how to use it can be found here
Changelog
0.1.4
- Improved frame acquisition. Increased speed and made it more stable.
0.1.3
- Changed
grab_backgroundto wait for the background to be grabbed before continuing. - Changed
get_single_frameandget_background_frameto wait for the frames to actually be available and then read them. - Added device setting that allows you to choose if you want to overwrite the exposure time set in the GUI.
0.1.2
- Removed
read_waitas it is no longer needed. - Changed the end of the file name when using suffixes to be
time.time()and notdatetime.date.today()
0.1.1
Optimized reading of frames into python. Drastically increased reading speed.
0.1.0
Core functions. Not optimized.
Documentation
The backbone of this driver is the cam-control software by PyLabLib. The software must be running and set up to allow server communication. CAMELS then connects to the server and sends requests to the server. You must set up cam-control via its own GUI and you can then use CAMELS to actually save images with the exact settings from the GUI. Currently you can set the exposure time, save snapshots locally and save continuous frames locally as well as save frames into the HDF5 files of CAMELS. You can also save the background image which is currently being subtracted. The direct saving of frames to HDF5 files is quite slow as the server takes some time to answer (about 1 second per frame even for low exposure times of < 100 ms).
For more information and documentation visit our GitHub.io page.
Metadata
Release files for nomad-camels-driver-cam-control-pylablib 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| nomad_camels_driver_cam_control_pylablib-0.1.4.tar.gz | 14.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nomad_camels_driver_cam_control_pylablib-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.3 kB
Release files / nomad_camels_driver_cam_control_pylablib-0.1.4.tar.gz
| Download URL | nomad_camels_driver_cam_control_pylablib-0.1.4.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbd0339dcad48ca27a557bdcda70c7aa0ca94542778aadc9bc3077c304491842
|
|
BLAKE2b-256 checksum How to use checksums |
d726d8ddd687cc6a5fe5f3ff60dc4cd074172e5d6a9e928f0c61a672478387fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / nomad_camels_driver_cam_control_pylablib-0.1.4-py3-none-any.whl
| Download URL | nomad_camels_driver_cam_control_pylablib-0.1.4-py3-none-any.whl |
|---|---|
| Size | 15.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7f63b52361967e07a34e4e54217fbdd3c38d2ccb12cf94efe3f745571f3b8ad
|
|
BLAKE2b-256 checksum How to use checksums |
ad5ddf8954c0c421fb1abd19e3b00f5f5470116b607a41ac8a7edbc79955ab17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for nomad-camels-driver-cam-control-pylablib 0.1.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.