Skip to content

2024 Aug 22

rrivera747 edited this page Aug 22, 2024 · 1 revision

Agenda:

  1. General TDAQ Project status updates/Schedule review.
  2. Status of DCS and next steps
  3. AOB

Eric -- Establishing spack mpd workflow, which allows for mrb style incremental building (should be much faster for development). Currently cannot include Offline until new patch is applied. Process kicked off by Werror producing warnings, so made jump to spack mpd (from Kyle and artists).

Antonio -- looking at making an ots/DCS poster for an upcoming conference.

Glenn -- On list is to setup rack monitor box in IERC so it is ready to replace rack monitor in rack 1E. Will document procedure so it can be a model for the future. Also, would like to document Archiver usage flow.

Simon -- back

Merrill -- Pheobus working on dcs-01 with alarm trees (for Glenn list) with strip charts and meter displays. Next step is to integrate with Archiver.

Ryan -- Working on adding user friendly/shifter friendly to ots for Mu2e codebase. Waiting for DTC/CFO feedback from VSTs. Caught up on fiber order vendor communication.

Paul -- Server with VOIP on it (ExtMon room not working). 1E rack is likely culprit, TDAQ should not care about reboots there.

Javier -- Helping with Calorimeter VST Sidet server/DTC setup; 3 servers/DTCs are working. On list is Avalanche loopback and timing characterization, but need Windows machine back and drive is dead.

Discussion of next steps for Pheobus and Archiver

Archiver:

  • Currently have Archivers running at IERC and DAQ room.
  • Polling values is read-only, so safe to add multiple readers
  • How do we document passwords?
  • Elog can password protect text files (from previous experiment experience)
  • Elog might be better than private GitHub because it is Fermilab owned.
  • ​​https://dbweb0.fnal.gov/ECL/mu2e
  • If nobody objects, we ask Rob Kutschke to setup a Project
  • Sticky point is how to add Archiver channels?
  • ots utility supports registering the channels in the Archiver
  • Broaden use to not DTC only?
  • Ots philosophy is “dynamic” to add/remove channels at each Configure step
  • Do we want to delete disconnected channels?
  • We could instead use Archiver “engines” which can group channels
  • Could change the engine ID for known disconnected channels
  • Change in Antonio ots utility required (TODO for Antonio)
  • The alternative is someone like Glenn documents the Java utility
  • Pheobus has “Services” tools for connecting/managing Archivers, should not be used? Glenn says no need to do that, because Archiver is already setup.
  • Merrill wants to know the flow for plotting value vs time, Glenn ⇒ Archiver does not need to be aware of any plots.
  • Are we using containers anywhere? For KAFKA? Zookeeper?
  • Merrill has launch by installing and running manually (Status is currently running on mu2e-dcs-01)
  • Lets run screen (?) [This is how Archiver is up, and mongodb is up, and g-2 used]
  • #Start a screen session, On the terminal, type screen.
  • #Detach from screen, Use Ctrl+a + d to detach from the screen session.

Alarm Server:

  • Also run on screen (?)
  • Adding to alarm info requires XML parameters
  • Merrill has made python scripts to build 5-level alarm trees
  • Also can acknowledge alarms
  • Philisophy is Alarm Server is archiver of alarms and allows latching/current/acknowledge/defer(snooze) alarms
  • How do we access Alarm Server?
  • Old way was sql db
  • Ots has way of monitoring Alarms but needs PV specified (does not have all)
  • Mu2e philosophy on acknowledging alarms (undefined plan?)
  • There is a C++ KAFKA library
  • This latching/current/acknowledge/defer(snooze) system needs to “always” be up, so likely should be screen/Pheobus only (?!)

Demonstrate Archiver and Alarm Server at Global Run 3 in DAQ room

  • October 21st week M-F

Final question about CA parameters, could be environment variables, but Pheobus ignores env vars so need to add to Java preference files

Glenn will point Merrill to some instructions