Revision as of 09:16, 14 April 2011

Agenda

• Announcements
  • New controls meeting Thurs 9:30am, mail list "halld-controls", and Controls wiki page
• Review of minutes from 30-Mar-2011 meeting

• Counting house UPS and Telecom - Elliott
  • VOIP only, use fibers instead of copper to connect to telecom room
  • UPS outlets in hall, telecom room
  • what to connect, how long will it run, when to use portable UPS's?

• P3E Online tasks - Elliott
  • Possible tasks for DAQ group and others
    • self-configuring readout list with database storage of crate configuration
    • farm manager CODA component
    • top-level AFECS experiment control supervisor and GUI
    • CLARA-enable DANA framework
    • convert Hall D facilities into CLARA services
    • readout/control libraries for Hall D specific modules (do we have any?)
    • implement EPICS driver using ASYN framework, e.g. for Anagate CAN gateway (Nerses?)
    • implement EPICS JavaIOC and driver using Port Driver framework (Nerses?)
    • design and prototype conditions database (Dmitry?)
    • other tasks that do not need DAQ expertise, just good programming skills
  • list of tasks and outside group expertise
  • Excel spreadsheet
  • Mantis tasks

• Online database strategy - Mark, Dave, Elliott
  • unlike calibration database, conditions database needs many searchable columns
  • should it be run-based or time-based?
  • should we use MySql replication or clustering?
  • how to interoperate with other databases, esp. EPICS archiver database, elog, etc?
  • Proposal for an online conditions database

• Coil test update - Elliott, Yi
  • schedule
  • VME fast DAQ system
  • Auxiliary tests

• Other Tests - Chris, Beni
  • Multi-crate trigger test
  • FDC cosmic ray test

• Controlling CAN systems - Elliott, Hovanes
  • FCAL bases - Anagate gateway
  • c-based IOC, JavaIOC, PCAS, ASYN framework, separate controller task?

• Raw event format - Dave, Carl
• Event display - Elliott, Andrew
• Java coda object framework - Elliott
• Controls test station - Elliott, Hovanes
• Electronics, trigger and DAQ status reports - Chris, Alex, Dave, Fernando, Ben, Ed, William, Bryan
• Mantis Task Tracker
• wallet card

Time/Location

1:30 PM Wed 30-Mar-2011 CC F326

Announcements

Next Meeting

1:30 PM Wed 27-Apr-2011 CC F326

Minutes

Present: Elliott W, Simon T, Bryan M, Alex S, Hovanes E, Mark I, Chris C, Carl T, Vardan G.

Telecom

Elliott reported on the status of working with the Networking and Civil groups. We'll only have VOIP phone service, and for safety the switches must be on UPS's. Telecom goes in before our big UPS arrives so temporary rack-mount UPS's will be used until the big UPS is installed and we run circuits to them.

P3E tasks

Elliott presented a number of possible Hall D specific tasks that DAQ group membes and others might do for us. See the list above. Many of the P3E database tasks cannot be done until the conditions database is designed, see below.

Conditions database

Mark presented a concept for the conditions database, see his note above.

• data will be stored in a single table with an id telling which type of data it is.
• this allows for adding new types of data to the DB at will without having to modify table structures.
• aggregation of data prior to entry is not required, as it usually is when you need to fill a single row with many columns.
• Mark believes a "DAQ status" tag for each entry will allow for much faster access, others think a time index is all that is needed.
• there was much discussion concerning what should go into the conditions DB.
• major discussion point was whether configurations should be stored a priori in the DB, whether they get used or not.
• many thought the conditions DB was not a good place to store all possible hardware configurations, rather let detector groups figure out for themselves how to create and store such configurations.
• this important topic will be revisited.

Coil test

Other tests

CAN control

EMU progress

CNU students

Electronics

Mantis task tracker