[Halld-online] Online meeting minutes

[David Lawrence]

Hi All,

  Minutes from yesterday’s Online Meeting are now posted on the wiki and copied below.

https://halldweb1.jlab.org/wiki/index.php/OWG_Meeting_27-Jan-2016

Regards,
-David

Minutes[edit]

Attendees: David L. (chair), Sergey F., Simon T., Curtis M., Sean D., Naomi J., Bryan M., Dmitry R., Alex S., Carl T., Mark I.
Announcements[edit]

New Run Period will be implemented tomorrow with corresponding change of run number to 10000
Gluon work disk is scheduled for delivery this week. No other word on it.
gluon48 will have RHEL6 reinstalled this week to address spontaneous reboot problems
gluon49 has been reverted to RHEL6 is is currently in use. Stability is not yet known.
Collaboration Meeting[edit]

Copied agenda from last collaboration meeting.
Speakers invited to adjust times as appropriate
Run Number -> 10000[edit]

see announcements
Run Preparations[edit]

RCDB[edit]
RCDB entries are now being updated continuously (~once per minute) while DAQ is active. This uses a new RC feature that can run periodic jobs.
Entires are updated for the current run, not inserted so RCDB size stays reasonably small
Run crashes are currently detected by lack of End of Run entry
Sean provided request for information that should be included in the RCDB. These have not yet been implemented
C++ interface to RCDB has been implemented that will allow easy access from offline
We discussed using RCDB to implement tags for runs. Because the outward facing interface is based on a replica, changes can't be made through the web. They will need to be made in the counting house where the definitive version of RCDB is maintained.
fADC125 Modes[edit]
Naomi brought up that the new f125 firmware has more modes than the traditional "mode 7" and "mode 8". This can be confusing for humans to keep track of what each of these numbers means. 
The automated e-log entries (HDRUN logbook) have copies of the configuration files which currently list only these numbers.
We agreed to place comments in the config. files with the map of number to name so it will be easy for people to identify the meaning of the mode number.
Identifying Cosmic Runs[edit]
Naomi brought up the issue of how best to identify COSMIC runs. 
Dmitry demonstrated how to select cosmic run configurations using the "Run Config" filter in the RCDB website here:
http://halldweb.jlab.org/rcdb/runs
Beginning of Run (BOR) record[edit]
The BOR mechanism has now been implemented in both online and offline.
Values read back from modules are written to data stream (except F1TDC where this is not possible so best accessible data is written).
Data structures for digitization modules can be seen here:
https://halldsvn.jlab.org/repos/trunk/online/daq/vme/src/rcm/monitor/bor_roc.h
DAQ[edit]

System seems to be working and expect to get achieve ~30kHz
ROL Status (SYNC events)[edit]

Sascha is still working on SYNC events. The intent is to check current module configurations against those set at beginning of run to ensure they are still correct
Sascha is currently implementing checks on pedestal settings at beginning of run. The intent is to identify bad settings that could cause the trigger system to lock after one or two events. This will then post an error condition to the run log forcing the sift workers to address the problem.
TAGM VBias recording
There has been a request from the tagger microscope group to provide a mechanism to insert information on the voltage bias into the data stream. This is needed for calibration runs of the TAGM.
Richard J. has provided an example ROL that implements a solution that have used previously
Sascha had some concerns about including this in our standard ROL. He suggested an alternative method using the scalers
It was decided that Sascha and Richard needed to come to a consensus offline
L3/Event Tagging[edit]

Nothing new to report


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-online/attachments/20160128/b8685cec/attachment-0001.html>