11
10th May 2007 SLAC-PPA Summit 1 Mike Whalley Mike Whalley Durham University Durham University [email protected] [email protected] .uk .uk

The Durham HEP Database Group

  • Upload
    maris

  • View
    59

  • Download
    0

Embed Size (px)

DESCRIPTION

The Durham HEP Database Group. HEPDATA. Mike Whalley Durham University [email protected]. The Durham HEP Database Group. We are a small group based in the IPPP at Durham University in the UK, whose primary mission is the compilation of : HEP Reaction/Scattering Data - PowerPoint PPT Presentation

Citation preview

Page 1: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 1

Mike WhalleyMike Whalley

Durham UniversityDurham University

[email protected]@durham.ac.uk

Page 2: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 2

We are a small group based in the IPPP at Durham University in the UK, whose primary mission is the compilation of:

HEP Reaction/Scattering Data Reaction Data Database & Data Reviews

Personnel involved:

Mike Whalley – DBM/Project ManagerJoanne Bentham – Database Assistant

Funded by PPARC(UK) STFC(UK)

The Durham HEP Database Group

PLUS……. UK Mirror Sites of…..

SLAC-SPIRES – (hep etc…) + LBNL Review of Particle Physics

Since ~ 1975 – originally mainly 2 body final state data …now….to compile ALL published data on HEP scattering cross sections etc..

“Products”

Page 3: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 3

Types of Particle Physics Data

Particle Properties Reaction (scattering)Bibliographic

MassesLifetimesSpin etc…

LBNL PDGSLAC spires/hep & arXiv archives

Cross SectionsPolarizationsEvent Shapesetc…. a b c d …

Durham “Reaction Data”

Database

Experimental and Theory papers

CDF (Fermilab) jet cross section

H1 (DESY) low-x F2 measurements

Page 4: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 4

SPIRESHEP

SPIRESHEP

PDG

PDG

ExperimentsJournals arXiv

Durham Data Compilers

Users

ReactionDatabase

Mirror

BDMS

UKMirrors

Reaction Data

Database

BDMS

Present

SLACBerkeley

Durham HEPDATA

DESYKeywords

Page 5: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 5

Reaction/Scattering Data - The Durham Database Group

~10,000 records(papers) -1970s-present data – currently ~150/year

WHY?Large amounts of money are spent on experiments to collect the data therefore efforts should be made to make sure it is not lost and available in the long term.

Such a data store is essential if, for example, earlier and maybe lower energy data, as well as current data, are to be used in data/theory comparisons, tuning Monte Carlos and in designing new experiments.

To provide an easy, and consistent, way of locating data.

Strengths & WeaknessesStrengths:•Long term commitment•Done by physicists•Comprehensive coverage

Weaknesses:•Old DBMS•Limited output formats•Complicated search syntax•Lack of modern networking•Lack of personnel

(see future ….)

Data from Journals – peer reviewed – (not prelim. or conf.) – direct fromexperiments if only in plot form – verified by authors.

Page 6: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 6

Data Reviews Data Reviews• Since 1984 the HEPDATA group

has produced and published reviews of “timely and topical” subsets of the data in the HEPDATA database.

• Published in IoP Journal of Physics G and also since ~1995 on-line as web pages.

• Enlist the help of experts in the particular subject.

• The purpose is to provide a comprehensive “one place” archive of the data.

• The on-line version is kept up-to-date as new data appear.

• The process of producing the review also audits the database ensuring that it contains all the data on a particular topic.

Page 7: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 7

The Durham-SPIRES connection< 1984 ppfs/ppas received as paper copies + QSPIRES (email) + STAIRS (at RAL) 1984 Durham HEPDATA group produced a database – using BDMS, - weekly ppfs and merging in the ppas. Accessible by logging into remote machines (with guest account) .

~1993 Moved to web based front end. Updating weekly, then eventually nightly – but just the ppf/ppa subset of the data. Added conference, hepnames, …

1999 Full mirror service developed – the cut-down version was not enough.

2006 Full rsync of all spires databases nightly.

Uses ‘IRN’ as the link

Page 8: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 8

BDMS

SPIRESHEP

SPIRESHEP

PDG

PDG

Experiments

NewReactionDatabase

Journals arXiv

Durham Data Compilers

Users

Users

JetWeb

CEDARMC validation

Monte Carlosgenerate observeddistributions

ReactionDatabase

BDMS

MySQL

UKMirrors

OldReactionDatabase

Future

Java codeddata model

asciirootaidaxml

Page 9: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 9

CEDAR

+Combined E-science DAta Resource for HEP=

HEPDATA - Durham JETWEB - UCL

HEPDATA – archive ofHEP data.

JETWEB – a “tool” developedto facilitate the comparison andtuning of Monte Carlo programs(eg) PYTHIA, HERWIG etc.. withreal data

£350K over 3 years from the PPARC E-Science call to update and join these two together to make a powerful data/MC tuning resource for the start of the LHC

Page 10: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 10

JETWEB

CEDAR workplan

HEPDATA

MC programsExperiments

Inputting data directly

USERS

CEDAR

Design new (relational)DB schema.

Migrate data to the new DBMS – MySQL

Network new DB to JETWEB (or to any user’s programme!)

Develop direct entry andmaintenance of data bythe experiments.

Modify JETWEBto take data directlyfrom the new HEPDATA DB

Re-write HZTOOL in C++ to handle new MCs for LHC

Develop the GRID accessiblility

JETWEB uses Gridtechnology to runfitting jobs remotely

publicationsnetwork/grid

Page 11: The Durham HEP Database Group

10th May 2007 SLAC-PPA Summit 11

The Durham HEP Databse Group - Summary

• Since 1975 – Data Compilation of all types of HEP scattering data

• Products:

Reaction Data Database Data Reviews

• Maintain the UK Mirror sites of

SLAC/SPIRES LBNL PDG web pages

• Future:

1. New Reaction Database – MySQL with Java based model.2. Expand output types : graphics, ascii, root, aida, xml, etc…3. Improve input methods (eg direct maintainence by expts(?)…4. Involvement with CEDAR (MC validation) project.