Jack Cranshaw

1
HCAL Database Plans

• General Areas of Effort
• Slice Test Specific Areas
• More Details, Pleeease.
• How to Proceed

2
A. Tasks Clearly Under Our Control

1. Prototype 0 in Oracle at CERN.
2. Prototype 1 development
3. Should we use code generation?
4. Investigate middle tier software
5. What do we do with outside calibration?
   (voltages, ..)
6. Evaluate ConditionsDB interface.
7. Can we handle non-Oracle files transparently?
8. Where do we write for testing? Development?
9. Where do we keep raw data and in what format?

3
B. Tasks Requiring Slice Test Coordination

• Which detectors will be using the database?
• Which software will be in use which needs the DB?
• Who is responsible for the various pieces?
• Which servers are in place?
• Development only?
• At CERN, FNAL, both?
• Do we want to do any basic export/import or
  replication?
• Where is the master?
• Where are the copies?

4
C. Problems Needing a Working Decision

• What is the organization of the CMS database
  efforts?
• Which users in the near future? Far future? When?
• Which environments at which periods?
• How much do we have to fudge because its not
  ready yet?
• How many database formats will be in use?
• Oracle, Text, Root, Xml, Mysql,
• When does the database become non-development?
• Are there any legal or budget issues associated
  with software or licenses?
• Where do we get DBA support from?

5
Slice Test - the Event

• Goals of the Slice Test
• Global goals?
• Timescales? Does HCAL start first then other
  detectors join?
• Who will be there and what will they be working
  on?
• What do we really want to learn?

6
General Structure Databases

• Assume that a single development server is
  sufficient. But where is it?
• How many of the other databases do we need?
• Can we handle mixed database formats ok?
• Is there a way to translate?
• Do we consolidate?
• Is the database needed for DAQ at all?
• What software do we want to have in place and
  test?
• Do we try to distribute?
• How much support from CERN/FNAL computing?

DAQ
Mysql
slow
txt
chips
Crates
Software
xml
geom
Data
oracle
calib
int
7
How to Proceed

• Assume this is a valid subset, and start
  assigning names and dates. Expand or re-order as
  needed.
• Assume at this point that we are free to fudge
  anything that we need from someone else that is
  not going to be available.
• Assume that any software developed is extremely
  useful, but is not the final product.
• Go ahead and start looking past slice test.