search

JeffersonLab / hcana

Hall C++ Analyzer
7 stars 118 forks source link

EPICS events #12

Open sawjlab opened 10 years ago

sawjlab commented 10 years ago

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.

sawjlab commented 10 years ago

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.