Software Plans for 04

1
Software Plans for 04

• Shuichi Kunori
• U of Maryland
• 17-Oct-2003
• Database
• VCR (virtual control room)

2
Introduction

• Goal
• To build a coherent database system for HCAL, EMU
  and PIXEL detectors in CMS.
• The system covers both online and offline.
• The system also covers hardware information from
  the construction phase.
• The system is expandable to other detectors in
  CMS.
• To build a virtual control room for remote
  monitoring, operation and analysis.
• The system provides an environment for
  information exchange and a framework for
  monitoring.
• We expect a framework for operation will be
  provided by the DAQ group.
• Plan
• Build a prototype for the slice
  test/TB2004/(DC04) in 2004 and evaluate.
• Upgrade the prototype to fully functional product
  in 2005/2006.

3
CMS Database types
? Now called Equipment Management DB
4
Conditions/Calibration DB
(David Stickland LHCC CR, 23-Sep-03)
5
Brief History of HCAL DB
Parameters stored at manufacturing/construction
sites (1996-2003) e.g. Absorber geometry
AutoCad FNAL HPD
(web) Minnesota Tiles,
optical cables ASCII files FNAL
PMT mySQL Iowa
channel map Excel Notre
Dame Calibration runs in the H2
testbeam at CERN (TB2002/TB2003)
runDB mySQL CERN
configuration ASCII files
CERN gain (output)
ASCII files FNAL Calibration DB prototype
using ORACLE (2003 spring)
gain/pedestal (from TB2002) data model
close to CDF by
J.Damgov/J.Cranshaw with help from the FNAL
CD. Survey activities at CERN (20003 summer)
a mini workshop at CERN (July 2003)
HCAL, Glege, Liendle
(conditions), Wynhoff(ORCA), Valassi (LCG)
CMS week (September 2003) Form a joint
working group with EMU (Summer 2003)
bi-weekly meetings PIXEL group joined in
September, 2003
6
2002 HCAL Calibration Prototype DBData Structure
(J.Damgov J.Cranshaw, FNAL CD)
7
2002 HCAL Calibration Prototype DBAPI
8
Next Step
Current Situation No infrastructure /
framework / clear guideline on DB in CMS.
Unclear situation of conditions DB in LCG. Our
next step Coordinate ourselves
(HCAL/EMU/PIXEL) Look for global/common
solution for hardware/online/offline. Two
strategies Bottom-up expand our current
prototype. from
calibration domain to hardware/online
from HCAL to EMU PIXEL
(vise versa) Top-down define DB
system architecture and interfaces, and build
infrastructure, and
then implement detector specific part. HELP
needed A technical coordinator for the
HCAL/EMU/PIXEL DB project. DB data modeling
/ OO experts for top-down approach. DB
experts for consulting for bottom-up approach.
9
Manpower (as of today)
HCAL S.Kunori (HCAL coordinator)
J.Cranshaw, J.Damgov FNAL
S.Sergueev (DCS) CERN

A.Oulianov, V.Ladygin Moscow
students/CS Iowa, Texas tech, EMU
R.Clare (EMU coordinator)
V.Sytnik(DCS), I.Vorobiev(Construction)
CERN PIXEL U.Joshi FNAL CAS
R.Clare (L2 manager) (US-CMS) M.Case
UC Davis
Other parties CMS CCS, DAQ,
Integration LCG CERN-IT
10
Request to CD( CD Briefing on 6-Oct-03 )

• For the HCAL/EMU/PIXEL DB development.
• A technical coordinator for the
  HCAL/EMU/PIXEL DB team.
• We will find a deputy from the
  detector groups to help the coordinator.
• Top-down DB (software) system design.
• Including evaluation of new
  technologies/standards and implementation.
• Consulting for developers from three
  detector groups for their
• bottom-up approach.
• For the CMS wide DB develoment.
• Exploring a possibility of taking a
  leading role in CMS wide DB
• development.
• We suggest a few people from CD
  visit CERN in very near future (November
• or December) to explore the
  possibility, and also to collect information
• needed for the top-down design
  work and consulting.

11
VCR
TB2003 operation. - Three months data
taking. - Experts visited CERN for 12
weeks ( a little longer) to install and
commission their detector components, e.g.
electronics, DAQ etc. - People
(non-expert) at CERN operated the system.
- Experts debugged and fixed problems, remotely.
- Some people monitored quality of data,
remotely. We used some tools for remote
capability. - web pages. E.g.
http//hpslweb.cern.ch/frame/java/1.1/view110-ja
va.html - e-logbook (provided by the
HEPBook development team at Fermilab). -
24h/7d VRVS connection. - 100
Logitech camera Polycom speaker/microphone in
an analysis room. - a wireless
head set and a wireless camera in a control
room. ? daily meeting with experts in
Boston, Princeton, Maryland, Texas, Fermilab
etc. ? debug electronics/DAQ in the
control room with experts. Missing
- remote capability of detector slow control and
monitoring. ? Plan to add these for TB2004
and the slice test.
12
Operation of CMS
Operation Coordination - shift coordinator
VCR (Fermilab)
Expert (Fermilab)
miniVCR
Expert (Maryland)
CERN Meyrin
US
Expert (Boston)
expert
Point5
expert
Expert (Princeton)
Main Control Room (ground level) - shifters
(D0-7, CDF-4, BELL-2, CMS-?)
VCR
Electronics Room (100 meters underground) -
experts during commissioning/debugging phase

(miniVCR)
Country X
Expert
Detector (100 meters underground)
Expert
13
CMS Control Room
an operation console
Capable to operate and monitor whole system by
two people. (Boeing777)
14
Operation Console
Operation console (for up to two people)

• Multi-displays/windows in console.
• Work/Control
• Instruction
• Communication control and status
• Video View
• Oscilloscope view
• DAQ/Trigger status
• Alarm (detector monitor/event monitor)
• Monitor 1 (detector monitor)
• Monitor 2 (event monitor 1)
• Monitor 3 (event monitor 2)
• Monitor 4 (event display)
• Accelerator/beam monitor
• Accelerator logbook/ATLAS logbook

• Design/build an operation console which is
  capable for one person (or two) to operate and
  monitor whole system.
• Install multiple copies of the console in the
  main CR VCR.
• Install a scaled down version of the console in
  various location as needed.

15
Online Event Monitoring
16
(No Transcript)
17
VCR People and Tasks
HCAL Stefan Piperov
Jordan Damgov Seguei
Segueev USCMS Hans Wenzel
(framework, monitoring) (FNAL) Umesh
Joshi (video/audio) CD Data
com. network group (FNAL) HepBook
(Logbook) group
Tasks Design CMS operation console.
Develop a framework for monitoring. Deploy
communication system. Improve develop
logbook and HEPbook. Develop and/or
integrate HCAL monitoring software.
18
Conclusions

• We plan to develop and deploy a database system
  and a prototype VCR for slice test and testbeam
  in 2004.
• 2 FTE start working on DB and VCR soon.
• On DB
• We have established a collaboration on DB with
  the EMU and Pixel groups.
• We requested the Fermilab CD to provide
  significant support for CMS DB development
  project(s).
• On VCR
• We are working with the Fermilab CD on
  communication and networking.
• We are also working with the Fermilab CD to
  improve e-logbook and to extend it to HEPBook.
• We need close collaboration with ORCA team and
  DAQ group to build a fully integrated system.