OWG Meeting 27-Jan-2016

From GlueXWiki
Jump to: navigation, search

Location and Time

Room: CC F326-327

Time: 1:30pm-2:30pm


You can connect using BlueJeans Video conferencing (ID: 120 390 084). (Click "Expand" to the right for details -->):

(if problems, call phone in conference room: 757-269-6460)

  1. To join via Polycom room system go to the IP Address: (bjn.vc) and enter the meeting ID: 120390084.
  2. To join via a Web Browser, go to the page https://bluejeans.com/120390084.
  3. To join via phone, use one of the following numbers and the Conference ID: 120390084
    • US or Canada: +1 408 740 7256 or
    • US or Canada: +1 888 240 2560
  4. More information on connecting to bluejeans is available.

Previous Meeting


  1. Announcements
    • New Run Period (2016-02)
    • Gluon work disk
      • Estimated Delivery Date on or before 29-Jan-2015
    • gluon49 -> RHEL6
    • gluon48 -> rebuild RHEL6
  2. Collaboration Meeting
  3. Run Number -> 10000
  4. Run Preparations
    • RCDB
    • Beginning of Run (BOR) record
  5. DAQ
  6. ROL status (SYNC events)
  7. L3/event tagging
  8. AOT
  9. Recharge Wednesday: Brownie Sundae


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


  • 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

  • Copied agenda from last collaboration meeting.
  • Speakers invited to adjust times as appropriate

Run Number -> 10000

  • see announcements

Run Preparations


  • 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

  • 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

  • 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:

Beginning of Run (BOR) record


  • System seems to be working and expect to get achieve ~30kHz

ROL Status (SYNC events)

  • 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

  • Nothing new to report