1. Software and Computing Status of Software development and MC production OpRoot-Fedra MC interface New CVS server Computing resources at CERN: present and future Database group activity D.Duchesneau LAPP, Annecy OPERA collaboration meeting Hamburg, June 5 th 2004

2. New CVS server Collaboration meeting – Hamburg – June 2004 Access Contents One address to remember: cvsopera@cern.ch (please write mail subject as: [CVSOPERA] Your subject) L. Chaussard

3. Access Direct acces for administrators only lxplus login : cvsopera password: ******** Public WEB access for everybody http://isscvs.cern.ch:8180/cgi-bin/cvsweb.cgi/?cvsroot=opera http://isscvs.cern.ch:8180/cgi-bin/viewcvs.cgi/?cvsroot=opera kserver access for Opera users setenv CVSROOT :kserver:isscvs.cern.ch:/local/reps/opera klog.krb –cell cern.ch –pri yourCERNlogin you need to be registered ! send a mail to cvsopera@cern.ch with lxplus login and adm/co/ci requests and subject : [CVSOPERA] bla bla bla Collaboration meeting – Hamburg – June 2004 L. Chaussard

4. Contents Already installed technical packages (OpMath, OpUtils, OpAlgo, CMTI) data model (OpRData, OpData, OpIO) detector description (OpGeom) algorithms (OpNegn, OpRoot, OpTreeConvert, OpDigit, OpRec, MyAna, OpNtuple) Still missing VMC simulation (OpSim) event display (OpDisplay) emulsion analysis interfaces (to SySal and FEDRA) Status of the old server archiving (operacvs.tgz) done and kept on several machines and CD-R no more support on this old server, do not use it anymore Collaboration meeting – Hamburg – June 2004 L. Chaussard

5. LXPLUS is our official computing platform all the code is installed and compiled on /afs/cern.ch/exp/opera area However: batch system was basically impossible to use in April due to LHC computing (Data challenge) : A 8mn job took 1 day to start! The turnaround was so bad that development, test jobs etc…were impossible to do After discussion with CERN, J. Boucrot succeeded to get a period where OPERA gets high priority for a certain number of very long jobs (until end of June) in order to pursue production and development! Computing at CERN D. Duchesneau

6. After that period the situation will be as worse as before: LHC is taking most of the resources and for long time! Solution? Even during production period, OPERA is not taking very large computing resources in total (it will be quantified in term of CPU time after our actual production). My opinion : we should try to get at least a constant computing availability at CERN (with a dedicated batch queue for example!) + some period for official production. Remark: Official production, reconstruction etc… should be done in one center (CERN is a good place, Mass storage system exists). Computing at CERN D. Duchesneau

7. Recently set up Goals: Coordinate DB development work Define what should be an OPERA central Database and/or data repository First meeting held at CERN on April 22nd 2004 The group has a dedicated web page (thanks to J. Goldberg) accessible from the OPERA internal pages It will be used for document exchange, discussion etc… Interested people can subscribe to the opera-db mailing list OPERA Database group D. Duchesneau

8. Local databases BAM Brick Manipulation Management (Storage, Cosmic..) DAQ (raw data from electronic detectors) +Slow control: calibration, environment parameters, beam data OPERA Geometry and alignment Development lab, cosmic exposure CS Emulsion scanning lab Brick Emulsion scanning in Japan Brick Emulsion scanning in Europe What are the systems running or planning a local DB? V. Verguilov D. Duchesneau J. Marteau D. Autiero C. Sirignano N. Savvinov K. Kodama C. Bozza, G. Grella Work progress, technology choice, timescale to be reported regularly

9. The OPERA events have 2 main structures: electronic detector information taken and built online emulsion data obtained after a delayed processing For analysis: The 2 parts should be stored in a common structure with an easy access and in a common Data-MC structure. A central database: for which purpose ? It depends on how we want to manage the OPERA event 1) The central database should contain relevant information copied from the local systems in order to give access to data needed for analysis 2) The Central Database concept should probably be extended to include the Emulsion scanning information at a level permitting exploitation for analysis. Strategy to define soon

10. Next step: June 21st 2004: review the results of the following studies: 1) - define the information which has to be stored in a central DB storage system from emulsion scanning and estimation of the resulting size of these data 2) - complete the list of information (not emulsion) which should be in a general OPERA Database 3) - have a first idea of the general analysis scheme which will be performed in the common OPERA framework: > use of a common format for data and MC > the interface with simulation and reconstruction > bookkeeping of simulated and real data. Autumn 2004: Definition of the OPERA data storage scheme and analysis scheme

11. The end