Difference between revisions of "OWG Meeting 12-Feb-2014"

From GlueXWiki
Jump to: navigation, search
(Created page with "= Location and Time = '''Room:''' CC F326-327 '''Time:''' 1:30pm-2:30pm = Remote Connection = '''ESNet:''' 8542553 (if problems, call phone in conference room: 757-269-6460) ...")
 
m (Text replacement - "/halldweb1.jlab.org/" to "/halldweb.jlab.org/")
 
(2 intermediate revisions by 2 users not shown)
Line 17: Line 17:
 
* [[Spring_2014_Online_Data_Challenge| Online Data Challenge May 2014]]
 
* [[Spring_2014_Online_Data_Challenge| Online Data Challenge May 2014]]
 
* [[GlueX-Collaboration-Feb-2014|Feb. Collaboration Meeting]]
 
* [[GlueX-Collaboration-Feb-2014|Feb. Collaboration Meeting]]
 +
* EPICS alarms: making a list (Mark I.)
 
* Major systems reports
 
* Major systems reports
 
** Trigger
 
** Trigger
Line 22: Line 23:
 
** DAQ
 
** DAQ
 
** Monitoring
 
** Monitoring
−
* [http://halldweb1.jlab.org/mantisbt Mantis Task Tracker]
+
* [http://halldweb.jlab.org/mantisbt Mantis Task Tracker]
−
 
+
  
 
=Minutes=
 
=Minutes=
−
Attendees: ''David L.(chair), Sascha S., Hovanes E., Mark D., Beni Z., Graham H., Dave A., Dmitry R., Mark I., Bryan M., Curtis M., Sean D., Eugene C., Chris C., Sergey F.''
+
Attendees: ''David L.(chair), Sascha S., Mark D., Graham H., Dmitry R., Mark I., Bryan M., Curtis M., Eugene C., Sergey F., Simon T., Dmitry R., Sergey P., Vardan G.''
  
−
== Discussion of the Future of Online Meetings ==
+
==Announcements==
−
There was some discussion about whether to continue the broad-based online meetings and if so, in what format. There were concerns that since we are now in the implementation phase for many online systems in Hall-D, that it is more efficient to discuss details in small groups. There were others arguing that the online meetings provided a forum for discussion that is not appropriate for the bi-weekly collaboration meetings, but would allow the various subgroups to keep abreast of each others activities. There were mixed opinions on whether an online meeting would be an overall efficient use of everyone's time.
+
* There will be a meeting of some of the Hall-D physicists immediately after the meeting to discuss activity schedule
  
−
There was consensus that we would continue the online meetings for a while longer, but with a streamlined agenda. Status reports will be brief and special discussion topics added to the agenda only as needed on a meeting-by-meeting basis. David Lawrence will chair the meetings.
+
== EPICS Alarms ==
−
 
+
* Mark I. is compiling list of EPICS variables that will need to have alarms set on them.
−
=== Online Data Challenge 2014 ===
+
* These are informational alarms for shift workers. Not interlocked with safety systems.
−
David reported that he and Mark D. continue to work on the ODC2014 document. Some details on the requirements of relevant subsystems are being added and will be circulated for review and comment by the people responsible for those subsystems.
+
* PLC variables of interest will be copied into EPICS variables and alarms placed on those. (Mark and Hovanes will take care of these)
−
 
+
* Graham noted that Hall-A recently reviewed the non-human-danger-causing stuff
−
=== Collaboration Meeting Agenda ===
+
* The alarms may have multiple levels set that can alert shift workers before the level of an interlock is reached so that they may take action to prevent this.
−
The collaboration meeting agenda was discussed. The following changes were agreed upon:
+
* Some things in our EPICS installation ins Hall-D
−
* Add a talk on the f125 by Cody
+
** CAEN HV
−
* Add a DAQ status update talk by Mark D.
+
** Magnets power supplies
−
* Move Chris' talk to the previous session
+
** Gas systems
−
* Add a Controls talk by Hovanes
+
** Beamline Devices
−
* Add a Monitoring talk by David
+
** DAQ systems
−
 
+
** Trigger
−
=== Major Systems Reports ===
+
** MPOD
−
====Trigger====
+
−
Alex S. reported:
+
−
* Currently able to read out 6 crates in FCAL
+
−
**Using one of the TI's in an FCAL crate as the master and pulser trigger
+
−
* Working on getting 3 BCAL crates set up
+
−
* It's possible to setup a trigger from the CTP in a single crate without the use of SSP, GTP, or TS
+
−
**(this was in answer to an inquiry regarding the self triggering ability available for the ODC2014)
+
−
 
+
−
Chris C. reported:
+
−
* 3 long trunk lines have been delivered
+
−
* installation of the GTP crate will be done once the the trunk lines (144 fibers each) have been installed
+
−
 
+
−
====Controls====
+
−
Hovanes reported:
+
−
* A request has been put out to all detector groups to submit their interlock requirements by beginning of March
+
−
* Dave Butler is working on the FCAL interlock system
+
  
−
====DAQ ====
+
== Trigger ==
−
Eugene/Dave A. reported:
+
* Pedestal readout for FCAL (6 crates at a time) is complete
−
* Remaining CPUs (single board computers) will be shipped on Feb 12th
+
* Changes required to the FADC250 firmware for triggering cosmics
−
** vendor has option to ship earlier if available
+
*# baseline (per channel)
−
** minimal acceptance testing will be done before distribution
+
*# threshold (common to all channels in module)
−
* CODA 3.0.1 is expected next week
+
*The ability to allow opposing module coincidences in BCAL is being added to the CTP programming
−
** user configuration files
+
* Chris: GTP will be moved into hall next week
−
** fixed ids for CODA components
+
−
*** Originally, the coda component id for a crate might be different for different CODA configurations. This was going to make offline translation difficult since a configuration-dependent translation table would be required. JCedit was modified to allow the id for a specific component to be set and persist across CODA configurations.
+
  
−
Hovanes reported:
+
== Controls ==
−
* ethernet fibers will be pulled in the middle of Feb.
+
* PLC - Dave Butler working on BCAL safety interlocks
−
**(currently, the switches in the hall are daisy chained)
+
** FDC requirements look simple (no PLC required for interlocks)
 +
** BCAL requires PLC implementation
 +
* Orlando has collected information for set points of BCAL biases and (preliminarily) populated a DB
  
−
====Monitoring====
+
== Monitoring ==
−
Sean D. reported:
+
* Dave will provide state transition script for starting monitoring
−
* Some minor improvements have been made to RootSpy.
+
  
−
====Other Topics====
+
== DAQ ==
−
* E-log
+
−
There was some discussion on which e-log to use. We currently have two e-logs in use. One made and supported by the Accelerator Division and the other, the MIDAS e-log. There was some discussion about e-logs in general and the appropriate role for the two we have.
+
  
−
It was agreed that for online operations (including the L1 trigger/DAQ development currently being done) shall be reported in the accelerator-base e-log.
+
== Misc. ==
 +
The Controls and Monitoring reports as well of anything that Graham and Chris may not necessarily be interested in should be moved to the bottom of the agenda in order to save their time.
  
 
== Next Meeting ==
 
== Next Meeting ==
−
Next meeting is scheduled for Feb. 12th
+
Next meeting is scheduled for Feb. 26th

Latest revision as of 04:01, 1 April 2015

Location and Time

Room: CC F326-327

Time: 1:30pm-2:30pm

Remote Connection

ESNet: 8542553

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

Previous Meeting

Agenda

Minutes

Attendees: David L.(chair), Sascha S., Mark D., Graham H., Dmitry R., Mark I., Bryan M., Curtis M., Eugene C., Sergey F., Simon T., Dmitry R., Sergey P., Vardan G.

Announcements

  • There will be a meeting of some of the Hall-D physicists immediately after the meeting to discuss activity schedule

EPICS Alarms

  • Mark I. is compiling list of EPICS variables that will need to have alarms set on them.
  • These are informational alarms for shift workers. Not interlocked with safety systems.
  • PLC variables of interest will be copied into EPICS variables and alarms placed on those. (Mark and Hovanes will take care of these)
  • Graham noted that Hall-A recently reviewed the non-human-danger-causing stuff
  • The alarms may have multiple levels set that can alert shift workers before the level of an interlock is reached so that they may take action to prevent this.
  • Some things in our EPICS installation ins Hall-D
    • CAEN HV
    • Magnets power supplies
    • Gas systems
    • Beamline Devices
    • DAQ systems
    • Trigger
    • MPOD

Trigger

  • Pedestal readout for FCAL (6 crates at a time) is complete
  • Changes required to the FADC250 firmware for triggering cosmics
    1. baseline (per channel)
    2. threshold (common to all channels in module)
  • The ability to allow opposing module coincidences in BCAL is being added to the CTP programming
  • Chris: GTP will be moved into hall next week

Controls

  • PLC - Dave Butler working on BCAL safety interlocks
    • FDC requirements look simple (no PLC required for interlocks)
    • BCAL requires PLC implementation
  • Orlando has collected information for set points of BCAL biases and (preliminarily) populated a DB

Monitoring

  • Dave will provide state transition script for starting monitoring

DAQ

Misc.

The Controls and Monitoring reports as well of anything that Graham and Chris may not necessarily be interested in should be moved to the bottom of the agenda in order to save their time.

Next Meeting

Next meeting is scheduled for Feb. 26th

Retrieved from "https://halldweb.jlab.org/wiki/index.php?title=OWG_Meeting_12-Feb-2014&oldid=65612"