Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v3.4 alternative #19

Open
wants to merge 8 commits into
base: lumentum-v3
Choose a base branch
from
Open

v3.4 alternative #19

wants to merge 8 commits into from

Conversation

ericonr
Copy link
Member

@ericonr ericonr commented Mar 21, 2025

Replaces #18

liteAlvaroCosta and others added 3 commits March 20, 2025 11:45
The precision of AcquireTime and AcquireTime_RBV is set to 3 by ADBase,
which is not enough to represent the minimum acquire time available
(0.0005). This commit increases the precision of AcquireTime_RBV to 6
decimal places, which is the same value already used by AcquireTime.
There's no need for it to be a class member, it's only used inside a
single function.
@ericonr ericonr mentioned this pull request Mar 21, 2025
liteGabrielAmorim and others added 5 commits March 21, 2025 16:48
The high perf stream sends 16-bit data for 12-bit images, and 32-bit
data for 24-bit images, so updateEpicsFrames needed to be updated to
deal with that.

Accessing PimegaCounterDepth in the zmq callback without locking the
port is safe, because the value can't be updated while an acquisition is
happening, which is when the frames are received.

It's important to note that this change requires changing the
BackendPortFrame argument to pimegaDetectorConfig to match "stream_port"
from backend.json. This breaks the DACCountScan implementation, because
it depends on the port being passed to it having the
"pimega_frame_visualizer" subscription available. This issue isn't dealt
with here, because the DACCountScan implementation in the IOC is already
broken for other reasons.

Co-authored-by: Érico Nogueira <[email protected]>
This is necessary in order to allow building on Ubuntu 24.04, since this
version includes workarounds for issues with FORTIFY_SOURCE.
ADSDKVersion wasn't filled in because pimega-api doesn't provide version
runtime.

We obtain the driver version from git.

Co-authored-by: Érico Nogueira <[email protected]>
Co-authored-by: Henrique F. Simoes <[email protected]>
Tested-by: Henrique F. Simoes <[email protected]>
This function is called by the Capture function and it didn't return
anything. Other GCC versions may ignore this lack of return but on GCC
13.3.0 (Ubuntu 13.3.0-6ubuntu2~24.04) this causes a sigill and crashes
the software.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants