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
Figure how to handle EPICS events. The Hall A analyzer does have some code for EPICS. Need to determine if this can be reused for the way Hall C puts EPICS events into the data stream and how the analysis uses the EPICS events.
The text was updated successfully, but these errors were encountered:
Could make a new list of variables called gHcEPICS and update this list with each EPICS event. Or could put the epics variables into an existing list like gHcParms, but put a prefix such as "ep:" in front of each epics name to avoid name collisions with parameters.
There is EPICS decoding in PODD. hana_decode/THaEPICS.C saves EPICS data in an STL map so that EPICS signal values are retrievable by tag. It looks like EPICS events are hardwired to be event type 131, while Hall C uses, 131, 132, ... depending on how many different epics logging intervals are used.
Figure how to handle EPICS events. The Hall A analyzer does have some code for EPICS. Need to determine if this can be reused for the way Hall C puts EPICS events into the data stream and how the analysis uses the EPICS events.
The text was updated successfully, but these errors were encountered: