MEG Software Status and Prospects

1
MEG SoftwareStatus and Prospects

• MEG Software group

2
Contents

• Software documentation
• MC updates
• WF simulation and analysis tool updates
• Computing
• MEG software release
• MEG data challenge

3
Software documentation
4
MEGWiki
Installation
MC introduction
Users guide
Developers guide
Source code browsing
FAQ
5
Document generation
HTML
Source

• HTML docs are generated from C source code
• Guide lines to write comment http//root.cern.ch
  /root/Conventions.html
• Generated docs from the HEAD version available on
  
• http//meg.web.psi.ch/restricted/software/meganaly
  zer_htmldoc/ClassIndex.html
• 
  and
• http//meg.web.psi.ch/restricted/software/meganaly
  zer_htmldoc/ClassIndex.html

6
MC updates
7
MC updates

• Event generation
• More calibrations
• Radiative decay
• Cosmic ray (preliminary)
• More precise DCH hits
• TICP/TICZ output to be digitized
• Updates and fixes in geometries
• LXe outer wall 846 PMTs in total
• Upstream/downstream beam elements
• DCH dimension
• TICZ/TICP
• TC beam test MC

8
Items ready for production

• Event generator
• Signal
• e g from radiative decay
• e from Michel decay
• e from radiative decay
• g from radiative decay
• Calibrations
• Alpha
• Ni
• ee- pair from W converter
• Cosmic ray (preliminary)
• ZEBRA output to be digitized in megbartender
• All the sub-detectors are ready LXe, DC,
  TC(Phi), TC(Z)
• Preliminary trigger simulation

9
Good level of sophistication, but items to be
done still exist

• Event generator
• AIF
• Calibrations
• LED
• Li(p,g)
• p0
• Cosmic ray
• Preliminary zenith angle distribution is ready
• To be done azimuth angle distribution, energy
  spectrum
• Neutron backgrounds for LXe
• Background from beam
• Crosscheck with beam test
• Timing counter
• Drift chamber

10
Waveform simulation and analysis tool updates
11
Event display

• More displays tracks and energy deposits

12
Xe Waveform display

• Expected To be used also for online

13
DCH 2D display
14
MEGWaveform class

• Reorganization of waveform analysis/simulation
  class
• Each sub-detector/analysis/simulation was using
  its own waveform class

( )
MEGDRSWaveform
MEGXECDRSWaveform
MEGWaveform
MEGTriggerWaveform
MEGXECTriggerWaveform

• Basic operations
• adding/subtracing
• Draw
• Print

• Detector independent operations
• ADC/TDC
• Frequency filtering
• Reflection
• Moving average
• Splitter response
• DRS simulation

• Detector specific operations
• If needed
• PMT/APD/Wire/Pad sim.
• Fitting

15
Standard system of units

• Discussed and decided the standard units for MC
  and offline analysis
• Defines internal expression in programs
• constant values
• global variable and Fortran common blocks
• return value and arguments of functions/subroutine
  s/methods
• Data file (ZEBRA, MIDAS, ROOT, )
• Any unit for human interface
• histograms, plots
• Configuration in GUI panel
• Warning messages
• Units based on GEANT3

16
Xe analysis updates schedules

• Updates
• Linear fit MINUIT fit reconstruction were
  implemented (by Giovanni)
• Pattern recognition (both time and space) for
  pile-up events (by Yasuko)
• To be done
• Qsum-based reconstruction
• Waveform spectrum analysis in progress
• Timing reconstruction
• Calibration monitoring w/ alpha, LED, pi0,
  proton, RD, and neutrion
• Schedule
• Finish items listed above before starting MC mass
  production
• Validate analysis tools in August-September

17
DC offline updates and To-dos

• Analyzer
• Kalman filter reconstruction
• COBRA 3D B-field based on measurement
• Bartender
• Implemented most physical effects in wire signal
  simulation
• Drift electron arrival times, avalanche and
  current pulse shape, charge division, preamp,
  cable propagation and reflection, DRS response
• To be checked against 55Fe Source
• To be done
• Pad simulation was just started
• Precise charge integration of induced charge
• Signal electronic transformation
• Compare analytic formula for reflected signal w/
  measured data

18
DC Wire output
right
left
19
Status of TC

• Analysis
• Very preliminary stage - No algorithms
  implemented
• Analysis of test beams (_at_Frascati _at_PSI) are
  underway? MC should be validated
• Bartender
• TC(Phi) waveform - some physical effects
  implemented
• Need tuning and corrections to mach with
  electronics
• Code copied from LXe differences in electronics
  chain
• TC(Z) waveform simulation not started yet
• New TC organization
• Coordination P.W. Cattaneo
• MEG MC simulation (GEM) S. Dussoni
• MEG Digitization (Bartender) A. Barchiesi
• MEG Analysis (Analyzer) P.W. Cattaneo, D.
  Zanello
• Test Beam MC simulation S. Dussoni
• Test Beam Analysis A. Barchiesi, D. Zanello

20
Status of trigger simulation

• µ?e? mode partly implemented
• Missing items
• TICP waveform
• TICZ waveform
• Coming soon
• Xe trigger waveform and discrimination
• Xe and TC timing matching ( Earliest TICP hit
  is used as TC timing )
• Xe and TC direction matching ( Earliest TICP hit
  is used as TC position )

Should be replaced with PMT/APD output
21
Computing
22
Merlin3 cluster _at_ PSI

• Merlin3 54 Cores 14TBytes Disk batch (SGE
  Sun Grid Engine)
• No modification needed for MEG software
• Write a script for SGE and submit a job
• Potentiality of use of GRID
• No modification needed for MEG software
• Successfully tested for MC production (only 10
  events)
• GRID access is limited to Virtual Organizations
  (VOs) cms, atlas, gilda,
• Need more tests

!/bin/bash Change to the current working
directory -cwd Job name -N
simple_array MY_HOSThostname MY_DATEdate ech
o "Running on MY_HOST at MY_DATE" echo "Running
environment" env echo "
" Put your single-CPU script
here ./Linux/gem gem.cards
23
Offline cluster for MEG
15 x 500 GB SATA
Sun Fire x4100 quad core 4 GB
Sun Fire x4100 quad core 4 GB
Fiber Channel Switch
Sun Fire x4100 quad core 4 GB
GBit Ethernet
Sun Fire x4100 quad core 4 GB
Sun Fire x4100 quad core 4 GB

• Ordered on June 14th 20 cores 30 TB disk?
  MEG requirements 64 cores 100 TB disk in
  total
• Easily extensible
• Redundancy through GFS/GPFS file systems
• GBit link to online cluster requested

24
Database

• Two databases MySQL and sqlite3
• MySQL needs network
• sqlite3 for stand-alone environment
• Easy conversion from MySQL to sqlite3
• Test database is available inside PSI
• Run table
• LXe
• Geometry
• cable configuration
• PMT test result
• Linear-fit parameter
• Requested tables for TC, DC and DRS
• Discussions continuing on ELOG/Offline
• DB mirroring
• MC run table
• Trigger configuration

25
MEG software release
26
On June 19th meg-1.0.0 released

• Released even though couple items left behind-
  We cannot wait for everything being
  ready?Perform MEG Data Challenge
• Feedbacks are welcome
• Bug reports
• Requests
• Questions
• Next release (meg-1.1.0 ?)
• To be used for MC mass production
• Release by the end of July
• ? Start MC mass production from August

27
Release strategy
MEG Repository
ROME Repository
MEG
ROME
Online
MEGMC
MEGBartender
MEGAnalyzer

• Release independent of MEG

• All the MEG software are tagged together
• Release early, release often
• When detector setup changed
• When data structure changed
• When interface changed
• ROME, ROOT, CERNLIB, MySQL, etc
• Some amount of bug fixes/new feature accumulated
• Accumulate for one month?
• Announcement posted 1week in advance
• Responsible persons have to make sure the
  subproject is in a good shape at that date

28
Retaining compatibility Data structure

• Compatibilities btw. MC, Bartender and Analyzer
• Most probable point to screw up the analysis
• Changing data structure implies changes to all
  code using that data
• Make sure that newer Bartender/Analyzer can read
  old MC data
• unrealistic to perform MC production for every
  different data structure
• Append new data into ZEBRA is less problematic
• Removing from/changing order of/inserting data
  ZEBRA are problematic

29
MEG data challenge
30
MEG data challenge

• Test throughout MC production, Bartender, and
  Analyzer
• Test meg-1.0.0 find out unknown missing items,
  problems,
• Realistic estimate of CPU/Disk
• ASAP
• Perform before MC mass production
• Start with event samples available
• Signal, e from Michel, RD, Calibrations, CR,
• 104-105 events/event type
• ?1.5GBytes/104event for signal event
• ? 1day/104event for signal event
• Available resources at moment merlin3 cluster _at_
  PSI
• CPU 4core Opterons x14, 2.4GHz
• Disk 14TBytes

31
End of Slides
32
Storage needed for this year

• Data
• µ?e? trigger 2Hz 20days 4M events ? 3TB
• Calibration
• Alpha, LED 200MB/run 4times/day ? 50GB
• Pi0, RD, neutron, proton
• DAQ w/o LXe in late summer
• Need discussion for the amount of calibration
  data(10Hz 20days 15TB, too big !!)
• MC
• RD 4M event ? 4.5TB
• Michel 1M event ? 1TB
• Michel 1M event ? 1TB
• µ?e? 1M events ? 1TB
• Calibration 2TB

( low intensity )
3 TB calibration
( w/o waveform )
20 TB ?
10 TB
33
CPU estimate

• MC production digitizing 20 CPUs
• 6-8 seconds/event 9M event 625-833 days
• Low intensity beam single RD is dominant
• Waveform fitting 2 CPUs
• fitting 0.5msec600 wf/event 0.3sec/event
• 0.3 sec/event 1.2 M event 1.4 days
• Reduction of 1/10 by pre-selection assumed
• Analysis 6
  CPUs
• Parameter training (Linear fit)
• Calibration
• Pre-selection
• Waveform fast analysis (T,Q conversion) 0.5
  event/sec
• Reconstruction 0.5 sec/event ?
• To be considered
• Time for submitting job negligible?
• Time for tape access
• MC and analysis do not run simultaneously