v0.0.5 - Timing Operations Overhaul
v0.0.5 - Timing Operations Overhaul
We're excited to announce the release of v0.0.5, which includes a significant overhaul of our data acquisition card timing operations.
What's Changed?
In previous versions, the data acquisition card executed tasks based on the cycle time, which included the exposure time plus any additional delays. These delays were inherently determined by the camera exposure time as a percent. For example, the flyback time was previously set as ~10% of the exposure time. Nonetheless, the flyback time, which typically involves a galvo or a piezo, should not depend upon the exposure time but rather the amplitude of the movement, and should be a fixed value.
New Improvements
With v0.0.5, we've revamped this approach to allow for more precise and faster imaging, with significantly reduced dwell times. This enhancement means that our timing operations are now more efficient and better suited to the needs of high-speed imaging.
We look forward to your feedback on these improvements!
Contributors
- @BingyingChen made their first contribution in #224
- @HoneybeeATc made their first contribution in #337
- @JinlongL made their first contribution in #505
- @3vwylie made their first contribution in #539
- @mehr0096 made their first contribution in #557
- @EvoleneP made their first contribution in #672
- @conorhughmcfadden made their first contribution in #699
Full Changelog: v0.0.1-alpha...v0.0.5
