Configuration Database David Forrest 15th January 2009 CM23, HIT, Harbin.

Slides:



Advertisements
Similar presentations
JQuery MessageBoard. Lets use jQuery and AJAX in combination with a database to update and retrieve information without refreshing the page. Here we will.
Advertisements

19/05/2011 CSTS File transfer service discussions CSTS-File Transfer service discussions (2) CNES position.
File Server Organization and Best Practices IT Partners June, 02, 2010.
March 24-28, 2003Computing for High-Energy Physics Configuration Database for BaBar On-line Rainer Bartoldus, Gregory Dubois-Felsmann, Yury Kolomensky,
Project Perfect Pty Ltd Project Administrator Overview of Software.
Software Summary Database Data Flow G4MICE Status & Plans Detector Reconstruction 1M.Ellis - CM24 - 3rd June 2009.
1 Databases in ALICE L.Betev LCG Database Deployment and Persistency Workshop Geneva, October 17, 2005.
Grid and CDB Janusz Martyniak, Imperial College London MICE CM37 Analysis, Software and Reconstruction.
Beamline Takashi Kobayashi 1 Global Analysis Meeting Nov. 29, 2007.
Data Quality Assurance Linda R. Coney UCR CM26 Mar 25, 2010.
1 Configuration Database David Forrest University of Glasgow MICO Meeting 13/10/2008
Online Reconstruction Update Linda R. Coney UCR Mar 25, 2010.
1 Configuration Database Review David Forrest University of Glasgow RAL :: 1 st June 2009.
Computing Panel Discussion Continued Marco Apollonio, Linda Coney, Mike Courthold, Malcolm Ellis, Jean-Sebastien Graulich, Pierrick Hanlet, Henry Nebrensky.
Online Reconstruction Update Linda R. Coney UCR Dec 17, 2009.
1 Analysis code for KEK Test-Beam M. Ellis Daresbury Tracker Meeting 30 th August 2005.
Software Parallel Intro 1M.Ellis - CM23 - Harbin - 15th January 2009  Focus this CM continues to be on needs for analysis of data and use of G4MICE online.
1Malcolm Ellis - Software Meeting - 31st May 2006 Data Challenge Requirements  First list of requirements, based on Yagmur’s document: u
1 G4MICE Analysis of KEK Test Beam Aron Fish Malcolm Ellis CM15 10th June 2006.
1Paul Kyberd - CM17 - February 2007 Database(s) for MICE  It is clear that we will need some sort of data base to hold information such as: u Geometry.
1 G4MICE TOF Reconstruction & KEK Test Beam Analysis Update Aron Fish Tracker Phone Conference May 25, 2006.
Objectives of the Lecture :
Software Summary 1M.Ellis - CM23 - Harbin - 16th January 2009  Four very good presentations that produced a lot of useful discussion: u Online Reconstruction.
1M. Ellis - MICE Video Conference - 15th March 2007 Software Report  New G4MICE Users  TOF Simulation and Digitisation  SciFi Reconstruction  Tracker.
HPS Online Software Discussion Jeremy McCormick, SLAC Status and Plans.
Software & Computing 1M.Ellis - CM th July 2010  Announcement  Software u Current Status u Open Issues u Roles u Next Steps  Computing u Status.
© IGD 2011 For subscribers who usually log in via a company intranet link.
Conditions DB in LHCb LCG Conditions DB Workshop 8-9 December 2003 P. Mato / CERN.
Offline Software Summary 1M.Ellis - CM25 - 6th November 2009  Release Schedule  Simulation and Analysis Update  Detector software: u CKOV u EMR u KL.
Hello We are looking for a coder to code the following We have a network that has different sites: we need an application that will scan the network and.
Configuration Database MICE Collaboration Meeting 28, Sofia David Forrest University of Glasgow Antony Wilson Science and Technology Facilities Council.
André Augustinus 10 September 2001 DCS Architecture Issues Food for thoughts and discussion.
ATLAS and GridPP GridPP Collaboration Meeting, Edinburgh, 5 th November 2001 RWL Jones, Lancaster University.
Event Data History David Adams BNL Atlas Software Week December 2001.
Configuration Database Antony Wilson MICE CM February 2011 RAL 1.
Tracker data quality monitoring based on event display M.S. Mennea – G. Zito University & INFN Bari - Italy.
Software Status  Last Software Workshop u Held at Fermilab just before Christmas. u Completed reconstruction testing: s MICE trackers and KEK tracker.
Some Thoughts about Hits, Geometry etc Rob Kutschke, Hans Wenzel Fermilab March 13, 2007.
G4MICE Status and Plans 1M.Ellis - CM24 - RAL - 31st May 2009  Firstly, a correction to the agenda:  I failed to spot a mistake in the agenda that I.
Online Reconstruction 1M.Ellis - CM th October 2008.
1 KEK test-beam software progress Malcolm Ellis MICE Video Conference 4 th May 2005.
This presentation shall describe; The motivation to design a new system How the new system works and user interaction Current work/results Future work.
Linda R. Coney – 5 November 2009 Online Reconstruction Linda R. Coney 5 November 2009.
9 Copyright © 2009, Oracle. All rights reserved. Deploying and Reporting on ETL Jobs.
MICE CM28 Oct 2010Jean-Sebastien GraulichSlide 1 Detector DAQ o Achievements Since CM27 o DAQ Upgrade o CAM/DAQ integration o Online Software o Trigger.
G4MICE’s DataQualityCheck application G4MICE’s DataQualityCheck application: Preliminary thoughts Mark Rayner 23 rd February 2010.
Alberto Colla - CERN ALICE off-line week 1 Alberto Colla ALICE off-line week Cern, May 31, 2005 Table of contents: ● Summary of requirements ● Description.
Database David Forrest. What database? DBMS: PostgreSQL. Run on dedicated Database server at RAL Need to store information on conditions of detector as.
Oct HPS Collaboration Meeting Jeremy McCormick (SLAC) HPS Web 2.0 OR Web Apps and Databases (Oh My!) Jeremy McCormick (SLAC)
CS 350 – Software Design A Problem That Cries Out for Flexible Code – Chapter 3 Imagine you want to extract information from a CAD system to feed an expert.
M. Oldenburg GridPP Metadata Workshop — July 4–7 2006, Oxford University 1 Markus Oldenburg GridPP Metadata Workshop July 4–7 2006, Oxford University ALICE.
A. De Caro for the ALICE TOF Offline Group (University of Salerno and INFN)
Software Overview 1M. Ellis - CM21 - 7th June 2008  Simulation Status  Reconstruction Status  Unpacking Library  Tracker Data Format  Real Data (DATE)
Configuration & Management for Joachim Flammer Integration Team EGEE is a project funded by the European Union under contract IST JRA1 all-hands-meeting,
1 Configuration Database David Forrest University of Glasgow RAL :: 31 May 2009.
Database Issues Peter Chochula 7 th DCS Workshop, June 16, 2003.
AliRoot Classes for access to Calibration and Alignment objects Magali Gruwé CERN PH/AIP ALICE Offline Meeting February 17 th 2005 To be presented to detector.
The Database Project a starting work by Arnauld Albert, Cristiano Bozza.
Configuration Database David Forrest University of Glasgow.
Monitoring Dynamic IOC Installations Using the alive Record Dohn Arms Beamline Controls & Data Acquisition Group Advanced Photon Source.
Database High-Level Overview
PyBAR Firmware Structure and Operation Experience
Software Session Introduction
MICE Collaboration Meeting Saturday 22nd October 2005 Malcolm Ellis
Data Management and Database Framework for the MICE Experiment
Configuration Database
Off-line weekly meeting
APE EAD3 introduction - DARIAH - Brussels
Offline framework for conditions data
Multi VO Rucio Andrew Lister.
Presentation transcript:

Configuration Database David Forrest 15th January 2009 CM23, HIT, Harbin

Contents Scope Design Concepts Implementation Remote Access Way Forward

Scope Configuration Database By configuration I mean everything that is related to the geometry of all components, and the calibration and cabling of sub detectors useful for reconstructing the conditions of a run Plus a wee bit of metadata associated with a run There should be very little overlap with DAQ etc

Design Concepts (1) Since CM22 a note has been written with some detailed draft of the design. This is intended in parts to inform and to prompt into action. There remains a clear need for more information from subdetector groups on what they anticipate requiring access to. You don’t have to be infallible, or a database expert (or know anything at all about databases) 228/MICE0228.pdf I provide this link here free of charge, all I ask for in return is feedback 228/MICE0228.pdf

Design for an Alien Spacecraft

Design Concepts (3) The point is, there is something called a ‘Run’. A run includes some meta data and has one or more configurations A configuration is the geometry (position, dimensions, rotation, etc) + Calibrations for detectors (not all shown here) + Cabling information

Design Concepts (4) So a run has a configuration, and many calibrations and cablings for each subdetector I need to know what form the calibrations take. For example I understand that each PMT in the TOF will have some vector of no more than ten floating point numbers, Malcolm has info re: tracker Would love to hear more from people, particularly regards other detectors

Design (5) : Temporal Access Use Case: “Give me a configuration for a specific time” There may be more than one configuration relevant for a given time Imagine a calibration valid only in May but improved later in July. We now have two calibrations valid for May (VALID TIME) Default behaviour – take the one that was updated the most recently, whilst maintaining the ability to view the old one (indexed by TRANSACTION TIME) So we have two timestamps: Valid time and transaction time This kind of idea is stolen from temporal databases and attached to relational, our db management system is well suited for this.

Implementation - I have scripts which generate the database structure and I make throwaway databases hosted at RAL for development, resembling that in slide 5 - The database is ‘relational’ and implemented using PostgreSQL 8.3 (open source) - There are access accounts for myself, Malcolm, Paul Kyberd and G4MICE

Remote Access We want to be able to reconstruct configurations in G4MICE Code has been written to read and write from the database from behind RAL firewall, has worked, awaiting some action by RAL to open a port for proper remote access using virtually identical program G4MICE application in development (awaiting RAL opening of port) to load VLPC data into G4MICE

Remote Access (2) - Access will need to support a variety of users with different versions of G4MICE and associated libraries. - There may be some version of G4MICE on the Grid, some other on my laptop, some other on yours, software in the control room etc etc - If something significant changes about the structure of the database I would rather not have to change code in all those places - In addition, it is not feasible to give RAL firewall access to all these addresses - So I imagine this being done through an API

Remote Access (3) (envisioned) RAL Firewall Grid Users DB API DB G4MICE Dev Control Room Apps* *Automatic Recording processes in the control room. Obviously has firewall access already. Direct access could be arranged. May also include Tom Roberts’ GUI

Future Work I want to read and write full geometries in the database using G4MICE I would like to hear even the most seemingly obvious things from det groups. Have heard something from TOF and Tracker but more appreciated