DeepLabCut / DeepLabCut/DeepLabCut-live-GUI
Add Hardware-trigger mode to gentl/basler backends
Open
camera
config
gui
- Dominant language
- Python
- Stars
- 72
- Forks
- 28
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
In certain scenarios its usefull to have the camera(s) run in a hardware - triggered mode instead of freerun.
That way one can exactly control when the cameras record the frames and at the same time enables a synchronization between cameras: all cameras receiving a trigger signal record their frames at the same time.
I would suggest different modes of hardware-trigger:
- fully external hardware-trigger - an external device will provide the TTL-like pulses to control the cameras. Simpler but requires external hardware.
- use one of the cameras as clock: this camera runs in freerun mode and outputs its ExposureActive signal via GPIO, other camera(s) are set in triggered mode and use the clock signal of the main camera.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.