Explaining the EPICS logging scheme for SBS

From Hall A Wiki
Revision as of 17:32, 23 October 2022 by Rom (Talk | contribs) (Created page with "The EPICS data go to two places 1. HALOG -- both start-of-run and end-of-run. 2. datastream as event type 131 First let me describe the scheme. A script called EpicsToFile...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The EPICS data go to two places

1. HALOG -- both start-of-run and end-of-run.

2. datastream as event type 131

First let me describe the scheme.

A script called EpicsToFile runs continuously, using caget to obtain EPICS variables and put them into text files. 

File to log EPICS data
/adaqfs/home/sbs-onl/logentry_scripts/halla/EpicsToFile

the text files are in /adaqfs/home/sbs-onl/logentry_scripts/halla/epics/halla.epics

Note, halla1.epics is rewritten frequently while halla.epics is a more stable copy that gets put into HALOG and datastream.

For the HV, its similar. A script /adaqfs/home/sbs-onl/logentry_scripts/HV_logging_SBS/EpicsLooper with data in the /Results subdirectory.

Other scripts insert the halla1.epics file into the datastream and into the HALOG.

All the scripts mentioned are in the directory /adaqfs/home/sbs-onl/logentry_scripts/halla/ 

InsertETLoop -- loops forever, puts halla.epics into ET system
as event type 131

getruninfo_bgr_SBS -- inserts EPICS data into HALOG.

and getruninfo_bgr_SBS is called by

start_run_SBS -- runs at the start of a run

end_run_SBS -- runs at the end of a run
Retrieved from "https://hallaweb.jlab.org/wiki/index.php?title=Explaining_the_EPICS_logging_scheme_for_SBS&oldid=43912"