You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
For diagnostics and eventually for data analysis, we need to have the option to use the panda's position capture (PCAP) within Hyperion's grid scans. Note that until bluesky/ophyd-async#90 is merged, we can only capture data manually.
Acceptance Criteria
A separate panda config yaml file is created in /dls_sw/i03/software/daq_configuration/panda_configs, which wires up the PCAP so that: Its trigger and gate inputs are wired to the CLOCK1 output, and the trigger is set to the rising edge. This will allow us to get the MIN/MAX/MEAN values of the X value for each trigger point.
This file should specify that we capture MIN/MAX/MEAN of the INENC1, the time at which the PCAP is triggered, as well as TTLIN1 (This is the signal sent by PPMAC when we start a new row)
If the PCAP config is selected, Hyperion should enable and arm the PCAP block during panda setup, and disarm and disable it during tidy-up. Config choice can be hardcoded for now since we can only capture data manually
The text was updated successfully, but these errors were encountered:
For diagnostics and eventually for data analysis, we need to have the option to use the panda's position capture (PCAP) within Hyperion's grid scans. Note that until bluesky/ophyd-async#90 is merged, we can only capture data manually.
Acceptance Criteria
/dls_sw/i03/software/daq_configuration/panda_configs
, which wires up the PCAP so that: Its trigger and gate inputs are wired to the CLOCK1 output, and the trigger is set to the rising edge. This will allow us to get the MIN/MAX/MEAN values of the X value for each trigger point.The text was updated successfully, but these errors were encountered: