Marco Cattaneo, Milano, 27th September 20001 Brunel status and plans Status of commissioning Forthcoming improvements Conventions.

Slides:



Advertisements
Similar presentations
28 Feb 2006Digi - Paul Dauncey1 In principle change from simulation output to “raw” information equivalent to that seen in real data Not “reconstruction”,
Advertisements

25/03/2003Simulation Application for the LHCb Experiment CHEP March 2003 Presented by: W. Pokorski / CERN Authors: I. Belyaev, Ph. Charpentier,
VELO Testbeam 2006 Tracking and Triggering Jianchun (JC) Wang Syracuse University VELO Testbeam and Software Review 09/05/2005 List of tasks 1)L0 trigger.
GAUDI Framework. Conventions QuantityUnit Lengthmillimetre Timenanosecond EnergyMeV Electic chargePositron charge TemperatureKelvin Amout of substancemole.
29 Mar 2007Tracking - Paul Dauncey1 Tracking/Alignment Status Paul Dauncey, Michele Faucci Giannelli, Mike Green, Anne-Marie Magnan, George Mavromanolakis,
L3 Filtering: status and plans D  Computing Review Meeting: 9 th May 2002 Terry Wyatt, on behalf of the L3 Algorithms group. For more details of current.
Marco Cattaneo, 23rd February Status of the software migration  Migration strategy: Where we should be  Status: Where we are  Plans.
Introduction Multi-jets final states are of major interest for the LC Physics EFlow : An essential test to design the foreseen detector Software (Algorithms)
Event Data Model in ATLAS Edward Moyse (CERN) On behalf of the ATLAS collaboration CHEP 2004, Interlaken.
David N. Brown Lawrence Berkeley National Lab Representing the BaBar Collaboration The BaBar Mini  BaBar  BaBar’s Data Formats  Design of the Mini 
Bookkeeping Tutorial. Bookkeeping & Monitoring Tutorial2 Bookkeeping content  Contains records of all “jobs” and all “files” that are created by production.
The BESIII Offline Software Weidong Li Institute of High Energy Physics, Beijing Workshop on the cooperation of PRC-US in HEP 16 June 2006.
Event Data History David Adams BNL Atlas Software Week December 2001.
5 May 98 1 Jürgen Knobloch Computing Planning for ATLAS ATLAS Software Week 5 May 1998 Jürgen Knobloch Slides also on:
Fabiola Gianotti, 31/8/’99 PHYSICS and SOFTWARE ATLAS Software Week 31/8/’99 Fabiola Gianotti Software requirements of physics groups What should Detector.
17-Aug-00 L.RistoriCDF Trigger Workshop1 SVT: current hardware status CRNowFinal Hit Finders64242 Mergers31616 Sequencers2312 AMboards4624 Hit Buffers21212.
Postgraduate Computing Lectures Applications I: Overview 1 Applications: Overview Symbiosis: Theory v. Experiment Theory –Build models to explain existing.
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.
Reconstruction Configuration with Python Chris Jones University of Cambridge.
LHCb Lausanne Workshop, 21st March /12 Tracking Software for DC’06 E. Rodrigues, NIKHEF LHCb Tracking and Alignment Workshop  To do list, and done.
AMB HW LOW LEVEL SIMULATION VS HW OUTPUT G. Volpi, INFN Pisa.
1 Calorimeter in G4MICE Berkeley 10 Feb 2005 Rikard Sandström Geneva University.
Marco Cattaneo, Aleph plenary, 23rd April Long term archive of LEP data  LEPC working group report Purpose Assumptions Conclusions  Physics goals.
Marco Cattaneo, 15-Sep OO software plans  Major milestone (presented last June) Fully functional SICB replacement by mid-2000  How to get there?
Status of OPAL data Matthias Schröder
Online Reconstruction 1M.Ellis - CM th October 2008.
Refitting Tracks from DST E. Rodrigues, NIKHEF LHCb Tracking and Alignment Workshop, Lausanne, 8-9th November 2006  Motivations  Step-by-step …  Current.
David Adams ATLAS DIAL: Distributed Interactive Analysis of Large datasets David Adams BNL August 5, 2002 BNL OMEGA talk.
Simulation Commissioning, Validation, Data Quality A brain dump to prompt discussion Many points applicable to any of LHCb software but some simulation.
CBM ECAL simulation status Prokudin Mikhail ITEP.
GAUDI Muon Software  Algorithms : Muon Digitization MuonL0Trigger MuonIdentification  Detector Description Database  Transient Detector Store  Detector.
1 SICBDST and Brunel Migration status and plans. 2 Migration Step 1: SICBMC/SICBDST split  Last LHCb week: Split done but not tested  Software week.
Bookkeeping Tutorial. 2 Bookkeeping content  Contains records of all “jobs” and all “files” that are produced by production jobs  Job:  In fact technically.
Computing R&D and Milestones LHCb Plenary June 18th, 1998 These slides are on WWW at:
23/2/2000Status of GAUDI 1 P. Mato / CERN Computing meeting, LHCb Week 23 February 2000.
BES III Software: Overview, Status and Plan Weidong Li Representing BES III Software Group BES Annual Meeting, Beijing 1 st June 2005.
Claudio Grandi INFN-Bologna CHEP 2000Abstract B 029 Object Oriented simulation of the Level 1 Trigger system of a CMS muon chamber Claudio Grandi INFN-Bologna.
April 6, 2000 LHCb Event Data Model Pavel Binko, Gloria Corti LHCb / CERN 1 LHCb Software week LHCb Event Data Model Pavel Binko Gloria Corti LHCb / CERN.
1 Software tools in Asia Akiya Miyamoto KEK 18-March-2005 Simulation and Reconstruction Session LCWS2005 Representing acfa-sim-j activity M.C.Chang 1,K.Fujii.
Prospects for Integrating Veloroot into GAUDI D. Steele - 24/11/1999.
25th Nov, 1999 LHCb Event Data Model Pavel Binko, LHCb / CERN 1 LHCb Software Week LHCb Event Data Model Pavel Binko LHCb / CERN.
Object Oriented reconstruction of the CMS muon chambers CHEP February, Padova Annalina Vitelli - INFN Torino.
Software Week - 8/12/98G. Poulard - CERN EP/ATC1 Status of Software for Physics TDR Atlas Software Week 8 December 1998 G. Poulard.
Marco Cattaneo, 6-Apr Issues identified in sub-detector OO software reviews Calorimeters:18th February Tracking:24th March Rich:31st March.
Follow-up to SFT Review (2009/2010) Priorities and Organization for 2011 and 2012.
Tau31 Tracking Efficiency at BaBar Ian Nugent UNIVERSITY OF VICTORIA Sept 2005 Outline Introduction  Decays Efficiency Charge Asymmetry Pt Dependence.
Marco Cattaneo, 3-June Event Reconstruction for LHCb  What is the scope of the project?  What are the goals (short+medium term)?  How do we organise.
Object-Oriented Track Reconstruction in the PHENIX Detector at RHIC Outline The PHENIX Detector Tracking in PHENIX Overview Algorithms Object-Oriented.
21/5/03J.E Campagne Opera Framework: Status Report.
MAUS Status A. Dobbs CM43 29 th October Contents MAUS Overview Infrastructure Geometry and CDB Detector Updates CKOV EMR KL TOF Tracker Global Tracking.
David Lange Lawrence Livermore National Laboratory
Marco Cattaneo, 20-May Event Reconstruction for LHCb  What is the scope of the project?  What are the goals (short+medium term)?  How do we organise.
LHCb Software Week 25/11/99 Gonzalo Gracia Abril 1 r Status of Geant4 in LHCb. r Ideas on how to populate the LHCb Detector Description Data Base (LHCb.
LHCb Simulation LHCC Computing Manpower Review 3 September 2003 F.Ranjard / CERN.
Migration of reconstruction and analysis software to C++
The LHCb Software and Computing NSS/IEEE workshop Ph. Charpentier, CERN B00le.
Status of Brunel team and next steps
Physical Units Event Data Model Access to MonteCarlo truth
Vincenzo Innocente CERN/EP/CMC
What’s new in version 5 of GAUDI
Search for coincidences and study of cosmic rays spectrum
Muon Group Software Report
2 Getting Started.
2 Getting Started.
What’s new in version 4 of GAUDI
And plan for SICBDST retirement
2 Getting Started.
Summary Computing Model SICb Event Model Detector Description
Agenda SICb Session Status of SICb software migration F.Ranjard
MC production plans : 1/08/ /03/2001
Presentation transcript:

Marco Cattaneo, Milano, 27th September Brunel status and plans Status of commissioning Forthcoming improvements Conventions

2 Verification status  Brunel v1r3 corresponds to SICBDST v235 i.e. Steering, I/O done by Gaudi, reconstruction done by wrapped Fortran algorithms from SICBDST  dst1 and dst2 samples produced with both programs, starting from same RAWH input 100 events DST1 B->pi+pi- 500 events DST2 B->pi+pi-  Outputs compared using new data quality tool (See Agnieszka’s talk) Detailed checks also by many sub-detectors DST1 identical DST2 fully compatible within statistics (pileup in Gaudi uses different random number sequence)  Brunel functionally identical to SICBDST

3 DST1 comparison

4 DST2 comparison

5 Brunel Commissioning  Goal: Use current Brunel version (wrapped SICBDST algorithms) in production INSTEAD of SICBDST  Benefit: New functionality (spillover, tracking) can be verified in production environment, and quickly integrated if physics criteria are fulfilled.  Commissioning plan: Use Brunel v1r3 to produce events on PCSF Adapt scripts, verify program stability vs. SICBDST Status: started last week Packaging and distribution Current Brunel executable uses shared libraries from AFS Produce static linked, self-contained executables for Linux and NT Status: start next week Review status at next software week (1-3 November)

6 Forthcoming improvements (timescale of one month) Infrastructure for Spillover events C++ Track Fit

7 Spillover events  Definitions: Pileup: several events from same beam crossing Combination done by simply adding MC Hits of underlying events to the physics event Requires no changes to digitisation code Implemented in both Brunel and SICB Spillover: events from previous or subsequent beam crossing Combination must preserve 25ns timing offset Digitisation must know what to do with hits that are 25nd early/late  Sub-detector specific Not implemented in SICB or Brunel  I/O for additional events easy with Gaudi  Sub-detector digitisation code must be rewritten (if spillover is relevant)

8  SpilloverSelector in next Gaudi release (November 1st)  First xxDigi: tracking Spillover events in Gaudi Transient Event Data /Event /MC /MCNext /MCNextNext /MCPrev /MCPrevPrev /Raw /Rec EventSelector SpilloverSelector xxDigi SpilloverSelector.TimeOffsetNext = 25*ns; SpilloverSelector.TimeOffsetNextNext = 50*ns; SpilloverSelector.TimeOffsetPrev = -25*ns; SpilloverSelector.TimeOffsetPrevPrev = -50*ns;

9 C++ Tracking  C++ track fit runs in Brunel now Comparison possible (in Gaudi) between Fortran and C++ fits Similar results  By end October: Feed fit results back to AXTK  Links to RAWH? Possibility to abandon Fortran track fit in production version First release of pattern recognition Probably not yet production quality, BUT Pattern recognition results available (in AXTK) for private studies by other sub-detectors

10 SICBDST retirement  By 1st November it should be possible to: Run current Brunel version in production, on Linux and NT Identical algorithms as SICBDST, different steering main program Optionally, AND if required by the physics groups: Use C++ track fit in production INSTEAD of Fortran track fit Begin studies of effect of pattern recognition Begin studies of effect of spillover events  Can we use Brunel.exe instead of SICBDST.exe in official productions as from November? In a configuration to be decided by physics meeting Subject to fulfilment of commissioning plan

11 Brunel Conventions  Conventions needed for: Uniformity Maintainability  Request at last software week: Proposals to come from Brunel manager  Current proposals: Discussed and approved at computing meetings   Mandatory after today for code accepted into Brunel But review always possible!  Conventions on: Physical Units Event Data Model Access to MonteCarlo truth

12 Physical Units All quantities in Gaudi data stores shall conform to the CLHEP system of units. All dimensioned quantities shall be defined by multiplying by the units in CLHEP/Units/SystemOfUnits.h : Output of dimensioned quantities shall be converted to the required units by dividing by the units in CLHEP/Units/SystemOfUnits.h Physical constants should not be defined in LHCb code. They should be taken directly from CLHEP/Units/PhysicalConstants.h my_hist = histoSvc()->book( "/stat/diet", "corpulence (kg/m**2)",30,10.,40.); double my_corpulence = my_weight / (my_height*my_height); my_hist->fill( my_corpulence/(kg/m2), 1. ); const double my_height = 170*cm; // = 1700 const double my_weight = 75*kg; // = 4.68e+26 float my_rest_energy = my_weight * c_squared;

13 Event Data Model  Glossary MC Event: output of the event generator step.  e.g. MC Particles and MC Vertices MC Hits: output of the GEANT tracking step.  e.g. detector entrance and exit point, energy loss etc. FE data: simulated output of the detector front end,  as seen by the hardware triggers, when different from Raw data. Raw data: output of the digitisation step of the detector simulation, and output of the data acquisition system for real data.  e.g. ADC and TDC counts. Coordinates: output of reconstruction program when applied to detector hits.  e.g. hit coordinates, calorimeter clusters etc. (is there a better name?) Reconstructed data: final output of the reconstruction program.  e.g. tracks, particle ID, energy flow objects etc.  Naming convention Agree on basic names. E.g. CaloDigit and OTDigit.  To be extended, please send me requests.... MC classes that derive from a real data base class have the same name as the base class, prefixed by "MC”. E.g. MCCaloDigit

14 Event Data Model Relationship between Raw data and MC Hits MCParticle Attributes Operations MCCaloDigit MCCalo SummedDeposit Attributes Operations 1 MCCalo Deposit Attributes Operations 1..N CaloDigit Attributes Operations 1  Implemented by inheritance:

15 Information Track segments Reconstructed space points Track candidates Monte Carlo Raw data Hits Digits Particles Dis-integrated Detector response Processing Comparison Generic Data-MC comparison

16 Event Data Model Generic relationship between reconstructed data and MC Hits No other explicit links between reconstructed data and MC truth Navigation always by associator tool in dedicated monitor algorithms Associators may save their AssociationTables to persistent storage to optimise subsequent analyses  Transparent to applications MCParticle Attributes Operations MCTrackingHit Attributes Operations TrTrack Attributes Operations 1 OTHit TrMeasurement Attributes Operations MCOTDigi OTDigi Attributes Operations N MCHitBase TrTrackMCParticleAssociator

17 Associator example: CaloDigitMCSumDepAsct IAssociator* pAsct; std::string m_asctCalo = "CaloDigitMCSumDepAsct"; StatusCode sa = m_toolSvc->retrieveTool( m_asctCalo, pAsct ); for(CaloDigitVector::iterator it=Digs->begin(); Digs->end()!=it; ++it ){ MCCaloSummedDeposit* pMC = 0; StatusCode sas = pAsct->retrieveDirect( *it, pMC ); } CaloClusterCaloDigitPair CaloDigit MCCaloSumDeposit MCCaloDigitMCCaloDepositMCParticle SmartDataPtr Digs(eventSvc(),"/Event/Raw/Ecal/Digits_0");

18 Conclusions  Current Brunel version gives identical results to SICBDST  We could decide NOW to use Brunel for production As soon as it is packaged for production enviroment  Would allow rapid deployment of new features In particular, tracking improvements  Brunel now mature We must adopt conventions

19 Let’s take the plunge!