Feat/allied vision #279

2026-07-28T10:27:37+02:00

holler commented

2026-07-28 10:27:37 +02:00

No description provided.

holler added 7 commits 2026-07-28 10:27:37 +02:00

feat(devices): add native vmbpy integration for Allied Vision Alvium camera

CI for csaxs_bec / test (push) Successful in 1m41s

Details

f3148c897c

Adds AlliedVisionVmbCamera, talking to the Alvium G1-507m directly over
GigE Vision via vmbpy (Vimba X SDK) instead of the existing dead EPICS
IOC-based AlliedVisionCamera, which is left in place for now. Includes
the low-level Camera wrapper, simulation backend, device config example,
tests, and a README covering setup/testing/vmbpy install steps.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

refactor(devices): swap AlliedVision camera backend from vmbpy to Aravis b644cf786b

Replaces the vendor-SDK-based vmbpy backend with Aravis, an open-source
GenICam/GigE Vision library that implements the network protocol itself,
so no Allied Vision account/license/SDK download is needed - just
PyGObject plus the system-packaged Aravis library. Renames
AlliedVisionVmbCamera -> AlliedVisionAravisCamera (and matching
file/sim/test names) to reflect the new backend; low-level Camera
wrapper keeps the same public interface, only its internals changed.
README rewritten with Aravis install steps and camera-ID discovery via
arv-tool-0.8 / Aravis.get_device_id().

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

fix: include content changes for vmbpy->Aravis swap

CI for csaxs_bec / test (push) Failing after 2m21s

Details

f4bd20e4e8

The prior commit only captured the file renames (a botched `git add`
dropped the actual edits). This commit carries the real diff: Aravis
GObject-introspection backend in base_integration/camera.py, renamed
class/config references, and the rewritten README.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

test config file

CI for csaxs_bec / test (push) Failing after 3m49s

Details

bb643cac4e

fix(devices): use real camera_id, disable auto live-mode, pin pygobject a96d24a3cc

Update the placeholder camera_id in allied_vision_test.yaml/bl_detectors.yaml
to the Aravis device ID discovered on the actual Alvium G1-507m hardware,
and set live_mode back to False (explicit, not deleted) so the camera stays
idle until start_live_mode() is called -- matching every real IDS camera
config, instead of auto-starting its live-mode polling thread as soon as
the device connects.

Pin pygobject<3.52 in pyproject.toml: 3.52+ requires girepository-2.0
(GLib >=2.80/gobject-introspection >=1.80), which this RHEL9 host's system
packages don't provide (only the older girepository-1.0 via
gobject-introspection 1.68) -- unpinned pip install fails at build time.
Document both the camera_id lookup and the pin in the README.

Merge remote-tracking branch 'origin/main' into feat/allied_vision 13326c0985

# Conflicts:
#	csaxs_bec/device_configs/bl_detectors.yaml

feat(devices): add live-mode FPS measurement to AlliedVisionAravisCamera

CI for csaxs_bec / test (push) Failing after 1m42s

Details

CI for csaxs_bec / test (pull_request) Failing after 1m38s

Details

285691b629

Port get_live_fps()/live_mode_poll_interval_s from IDSCamera (added on
main): a rolling deque of the last 10 live-mode push timestamps, exposed
as a measured frame rate rather than assuming the nominal poll interval
is actually achieved -- verified against real hardware, where the
Alvium G1-507m's actual acquisition/readout time brings the achievable
rate to ~3 fps despite the 0.2s (5 Hz) nominal poll interval.

Mirrors the same three unit tests added for IDSCamera's version.

bec_bl_push-gitea added 2 commits 2026-07-28 10:46:58 +02:00

config(devices): drop allied_vision_test.yaml, add commented example to ptycho_omny 2bd161cd63

allied_vision_test.yaml was only ever a scratch config for exercising the
camera during bring-up; the same commented allied_vision_cam example
already lives in bl_detectors.yaml, so keep that one and add the matching
commented block to ptycho_omny.yaml instead of a separate file.

fix(devices): defer Aravis import-guard from Camera.__init__ to on_connect()

CI for csaxs_bec / test (pull_request) Successful in 1m59s

Details

Read the Docs Deploy Trigger / trigger-rtd-webhook (push) Successful in 3s

Details

CI for csaxs_bec / test (push) Successful in 2m0s

Details

c42595922d

Camera.__init__ raised ImportError unconditionally whenever the Aravis
GObject-Introspection library wasn't importable, even with connect=False --
contradicting the module's own "lazy initialization" docstring and
breaking every unit test in CI, since Aravis is a system library (not
pip-installable) that CI never has installed. The test fixture builds a
real AlliedVisionAravisCamera(connect=False) and only mocks camera.cam
afterward, so the raise fired before mocking ever got a chance to run.

Move the guard into on_connect(), mirroring IDSCamera's working pattern
(its equivalent check lives in the object only built by on_connect(),
never at construction time). Construction is now independent of whether
Aravis is installed; on_connect() still raises the same clear error the
moment something actually tries to talk to hardware.

holler merged commit c42595922d into main

2026-07-28 10:59:04 +02:00

holler deleted branch feat/allied_vision

2026-07-28 10:59:04 +02:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bec/csaxs_bec#279