Difference between revisions of "OWG Meeting 23-Apr-2014"

From GlueXWiki
Jump to: navigation, search
(Created page with "= Location and Time = '''Room:''' CC F326-327 '''Time:''' 1:30pm-2:30pm =Connection= (if problems, call phone in conference room: 757-269-6460) # To join via Polycom room syst...")
 
m (Text replacement - "/halldweb1.jlab.org/" to "/halldweb.jlab.org/")
 
(2 intermediate revisions by one other user not shown)
Line 22: Line 22:
 
#* Monitoring
 
#* Monitoring
 
#* Controls
 
#* Controls
−
# [http://halldweb1.jlab.org/mantisbt Mantis Task Tracker]
+
# DAQ system Configuration
 +
# [http://halldweb.jlab.org/mantisbt Mantis Task Tracker]
  
  
Line 30: Line 31:
 
= Minutes =
 
= Minutes =
 
==Attendees==
 
==Attendees==
−
David L., Curtis M., Simon T., Sergey F., Bryan M., Chris C., Beni Z., Nerses G., Verdan G., Sean D., Sergey P., Dave A., Alex S., Mark D., Hovanes E., Dmitry R.
+
David L., Bryan M., Sergey F., Simon T., Alex S., HOvanes E., Dmitry R., Beni Z., Vanik, Serguei P., Curtis M., Eugene C., Mark I., Michael S., Dave A., Vardan G., Nerses G.
 +
 
 +
== Announcements ==
 +
* Fiber (for networking) is installed
 +
** CC will connect to switches.
 +
** Can do this without disrupting network service (in principle)
 +
** Preliminarily planned for May 5th.
 +
* Wiki update is scheduled for this evening
 +
* New detector-specific accounts have been created on gluon cluster
 +
** hdcdcops
 +
** hdfdcops
 +
** hdfcalops
 +
** hdbcalops
  
 
== Trigger ==
 
== Trigger ==
−
* Synchronized timing of 4 CDC crates
+
* Working on BCAL Cosmic Trigger
−
* Synchronization for FDC waiting for Beni to finish some work
+
** 3 crates (1 BCAL and 2 trigger crates)
−
* Debugging cosmic trigger using full TS, GTP/SSP, CTP system
+
** Pulser feeding into fADC modules in BCAL crate
−
** Using output of SSP plugged into TS (bypassing GTP)
+
** Have done one test with entire chain (trigger originating from BCAL and going through TS back to BCAL to trigger event)
−
* Continuing the debugging of the Mast TI issues with William
+
* Revised the front-end configuration to use 3 files
−
** seems to randomly switch to internal pulser
+
** One is the global level settings
−
* Chris would like to use playback to test certain features
+
** Second is crate-level configurations
−
* Chris has posted final drawing of fibers
+
** Third is optional user supplied configurations that can be used to mask channels or disable entire boards
−
* There was some discussion on the firmware version and disagreement as to what is installed
+
** Will implement read back of register values to confirm they were correctly set
−
** Bryan and Alex S. will discuss offline
+
  
 
== DAQ ==
 
== DAQ ==
−
* Online CCDB has been installed by Dmitry at Beni's request who is using it for DAC values in the FADC125 modules
+
* 5 flash modules changed in FCAL
−
** This is an alternate system to the one developed by the trigger group
+
* FCAL has noticed 3 failure modes in individual fADC250 channels (not always same channels)
−
* Network fibers are being installed
+
** pedestal shifted by some amount (bad DAC setting?)
−
** Possibly done by the end of next week
+
** time shifted by some fixed amount
−
** Mark D. is the contact person
+
** channel value locks at single value.
−
* Started testing run conf. DB with DAQ system
+
** Not yet verifying DAC values set are actually set. (will do soon)
−
** Currently writing to separate SQLite files so subsystems don't interfere
+
** Bryan Moffit noted that Hai has narrowed down the location of one of the problems to a small portion of the FPGA code. They may even have a fix.
−
*Some issues with BCAL N
+
** Bryan would like to look at the ROL to confirm the initialization sequencing so that can be eliminated as a possible cause.
−
** certain config files give junk or empty data
+
* One of the TOF crates is missing the TI module (Alex thinks it's in his office )
−
* Run Control command line interface is now available
+
* TOF DAQ:
−
** This ''plask'' but with some significant enhancements
+
** Someone needs to take responsibility for the TOF dedicated DAQ (Sergey F. was nominated twice for this role)
−
 
+
** Some discussion about using TOF as cosmic trigger for other detector systems
 +
** The trigger algorithm for the TOF is not ready and not being worked at the moment. It is lower on priority list
 +
** May be possible to use BCAL simple sum algorithm for trigger
 +
 
== Monitoring ==
 
== Monitoring ==
−
* RootSpuy development continues
+
* Work continues, but nothing significant to report
−
** TTree passing is now working and coupled into the Solenoid fast-DAQ system
+
  
 
== Controls ==
 
== Controls ==
−
* Working w/ BCAL group on voltage controls
+
* Nerses is working on BCAL GUI problems
−
* Some issues require Vanik who will arrive in a couple of weeks
+
* Vanik is here and working on motor applications
−
* Orlando is working on GUI for pulser controls
+
* Dave Butler continues work on gas system
−
* Nerses working on setup of Voltage alarms
+
* Mike S. working on EPICS guis that will be used by shift personnel
−
** MPODs, CAENs, ... (CAEN first)
+
* Orlando is working on scripts for running pulser sequence for BCAL
−
** Testing in next week or two
+
* Accelerator group is working on developing some guis for us to control magnets and other beam line devices
−
* Issue with configuring BCAL voltage boards
+
*CDC voltage controls are now operational
−
** This slipped through the cracks (Fernando's group and Hovanes thought the other was doing it)
+
−
** Maintainer of this configuration is still not determined
+
−
* Backup/Restore scheme for boards
+
−
** Any change (including rebooting crate) requires voltages be downloaded prior to turning voltage on
+
−
** Policy is what prevents someone from turning on voltage potentially damaging hardware
+
  
−
== DAQ software organization ==
+
== DAQ system Configuration ==
−
Sergey F. presented some plans on organizing the DAQ software (CODA mainly) and files to allow versioning.
+
An open discussion was had on some of the technical details on how to organize the configuration information for the DAQ system and related components. The Trigger Group has developed a nearly complete system. It could incorporate other items (e.g. monitoring) but that would couple the systems. Several ideas were discussed though unanimous consent was not reached on any particular plan. One significant agreement was that we can use a file-based config system for all detectors providing it is coupled to a database system that provides a full history mechanism.  
  
 
== Action Items ==
 
== Action Items ==
−
* Create separate accounts on the gluon cluster for different detectors (David L. will ask Paul Letta)
 
−
* Setup a wiki page with instructions on how to checkout and use his subversion-backed DAQ setups.
 

Latest revision as of 06:29, 1 April 2015

Location and Time

Room: CC F326-327

Time: 1:30pm-2:30pm

Connection

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

  1. To join via Polycom room system go to the IP Address: 199.48.152.152 (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.

Agenda

  1. Announcements
  2. Collaboration Meeting May 12-14
  3. Major systems reports
    • Trigger
    • DAQ
    • Monitoring
    • Controls
  4. DAQ system Configuration
  5. Mantis Task Tracker


Previous Meeting

Minutes

Attendees

David L., Bryan M., Sergey F., Simon T., Alex S., HOvanes E., Dmitry R., Beni Z., Vanik, Serguei P., Curtis M., Eugene C., Mark I., Michael S., Dave A., Vardan G., Nerses G.

Announcements

  • Fiber (for networking) is installed
    • CC will connect to switches.
    • Can do this without disrupting network service (in principle)
    • Preliminarily planned for May 5th.
  • Wiki update is scheduled for this evening
  • New detector-specific accounts have been created on gluon cluster
    • hdcdcops
    • hdfdcops
    • hdfcalops
    • hdbcalops

Trigger

  • Working on BCAL Cosmic Trigger
    • 3 crates (1 BCAL and 2 trigger crates)
    • Pulser feeding into fADC modules in BCAL crate
    • Have done one test with entire chain (trigger originating from BCAL and going through TS back to BCAL to trigger event)
  • Revised the front-end configuration to use 3 files
    • One is the global level settings
    • Second is crate-level configurations
    • Third is optional user supplied configurations that can be used to mask channels or disable entire boards
    • Will implement read back of register values to confirm they were correctly set

DAQ

  • 5 flash modules changed in FCAL
  • FCAL has noticed 3 failure modes in individual fADC250 channels (not always same channels)
    • pedestal shifted by some amount (bad DAC setting?)
    • time shifted by some fixed amount
    • channel value locks at single value.
    • Not yet verifying DAC values set are actually set. (will do soon)
    • Bryan Moffit noted that Hai has narrowed down the location of one of the problems to a small portion of the FPGA code. They may even have a fix.
    • Bryan would like to look at the ROL to confirm the initialization sequencing so that can be eliminated as a possible cause.
  • One of the TOF crates is missing the TI module (Alex thinks it's in his office )
  • TOF DAQ:
    • Someone needs to take responsibility for the TOF dedicated DAQ (Sergey F. was nominated twice for this role)
    • Some discussion about using TOF as cosmic trigger for other detector systems
    • The trigger algorithm for the TOF is not ready and not being worked at the moment. It is lower on priority list
    • May be possible to use BCAL simple sum algorithm for trigger

Monitoring

  • Work continues, but nothing significant to report

Controls

  • Nerses is working on BCAL GUI problems
  • Vanik is here and working on motor applications
  • Dave Butler continues work on gas system
  • Mike S. working on EPICS guis that will be used by shift personnel
  • Orlando is working on scripts for running pulser sequence for BCAL
  • Accelerator group is working on developing some guis for us to control magnets and other beam line devices
  • CDC voltage controls are now operational

DAQ system Configuration

An open discussion was had on some of the technical details on how to organize the configuration information for the DAQ system and related components. The Trigger Group has developed a nearly complete system. It could incorporate other items (e.g. monitoring) but that would couple the systems. Several ideas were discussed though unanimous consent was not reached on any particular plan. One significant agreement was that we can use a file-based config system for all detectors providing it is coupled to a database system that provides a full history mechanism.

Action Items

Retrieved from "https://halldweb.jlab.org/wiki/index.php?title=OWG_Meeting_23-Apr-2014&oldid=65774"