Title: Using Jupiter and Satellites
1UsingJupiter and Satellites
- Akiya Miyamoto
- KEK
- Feb 2007
2Target of Jupiter/Satellites/Uranus
- Jupiter and Satellites are tools for detector
optimization based on Geant4 Full detector
simulation. - Implement an ideal GLD geometry in Jupiter(
other geometry is also possible ) - Study PFA performances by an ultimate condition
- Implement tower calorimeter
- Develop analysis tools
- Study physics performance vs. detector choice.
- Not for simulation studies for beam test studies
- A study by detector simulation is also crucial
for the design of the IR design of ILC.
3Jupiter/Satellites Concepts
For real data
Tools for simulation Tools
Satellites
URANUS
JUPITER
METIS
Input/Output module set
IO
JLC Unified Particle Interaction and Tracking
EmulatoR
Unified Reconstructionand ANalysis Utility Set
Monte-Calro Exact hits To Intermediate Simulated
output
LEDA
Library Extention forData Analysis
Geant4 based Simulator
JSF/ROOT based Framework
MC truth generator
Event Reconstruction
JSF the analysis flow controller based on ROOT
The release includes event generators,
Quick Simulator, and simple event display
4Jupiter Directory Structure
Jupiter
bin
doc
include
config
lib
macros
scripts
sources
tmp
Linux-g
Readme
Sample G4scripts
Jupiter
common.gmk
bd
cal
cdc
ct
vtx
kern
lcexp
sol
main
tpc
it
ir
Jupiter.cc
src
include
Detector components to use are switched by CPP
flags in Jupiter.cc or parameters in JSFJ4
Sub-Detector files
5Standalone Jupiter
- Jupiter options g4macro file
-  options    -v N N is a message level.
          gt 10 Write message every time new
geometry is created. Â Â Â Â Â Â Â Â Â Â 5-10 Write
message of geometry whose rank is less than N-4.
          lt 5 No message is written at
geometry creation. Â Â Â -f FILE Read parameters
from the file FILE Â Â Â Â Â Â Â Â Â Â Â Â Â More than one
-f option can be specified. In this case
             a value in the first file is used.
   -w     Write default parameters defined
in the program              to the file,
jupiter.defaults    -help  Print help
message
Useful to display events and debug
6G4macro file
- Commands to Geant4 and Jupiter are provided as a
g4macro file. A list of commands can be found
at - When Jupiter is executed as a standalone
application interactively, help command can be
used to get help information.
http//www-jlc.kek.jp/miyamoto/Jupiter/html/_.htm
l
7Jupiter parameter list file
- Parameters for detector configuration can be
modified by a parameter file given by f option. - JUPITERROOT/doc/HowToRun for more details
- Standard configuration file as of Jan 2006 is at
http//ilcphys.kek.jp/soft/samples_dod/dec05/inde
x.html
8Satellites/Uranus
9JSFJ4
- Interface to run Jupiter in JSF environment.
- Allows to write
- Jupiter output by ROOT or LCIO
- Use generators in JSF or StdHep format file.
- Satellites package reads ROOT file created by
JSFJ4
10Metis package
- Metis is a collection of reconstruction tools for
Jupiter data. - Current aim is to prepare a minimum set of Metis
modules for studies of Particle Flow Algorithm. - Novice users will be able to do physics analysis
using information of PFO classes. - As a first step, a cheated track finder and a
cluster maker, etc are in preparation in order to
know ultimate performance. - Each module is independent, thus shall be easy to
implement different reconstruction algorithm
according to interests? Development of a real
clustering code begins recently
11Metis Analysis Flow
make smeared TPC hits from exact hit
make tracks from TPC
make hybrid tracks ( TPCITVTX)
make smeared/merged CAL hits from exact hit
make cluster from CAL hits
make Particle Flow Objects
jet clustering
12Satellites Directory Structure
Satellites
Run Jupiter in JSFto create a ROOT file
io
jsfj4
kern
bin
examples
include
mctruth
cal
S4xxxExactHit class J4xxxHit class
vtx
cdc
lib
.
src
Output LCIO data
j42lcio
test
examples
Leda
macro
metis
13Metis Directory Structure
metis
(JSFs) Modules for MC data analysis
tpc
hitmaker
make smeared TPC hits from exact hit
make tracks from TPC
trackmaker
hybt
hybtmaker
make hybrid tracks ( TPCITVTX)
cal
hitmaker
make smeared/merged CAL hits from exact hit
clustermaker
make cluster from CAL hits
pfo
pfomaker
make Particle Flow Objects
jet
jetmaker
make jet Objects
14Uranus Directory Structure
Uranus
Packages for real data analysis
data
kern
include
lib
VTX
detconfig
src
hitmaker
IT
trackmaker
TPC
hybt
15Relation among TrackHits
U4VTrack
double fChi2 U4VTrackMaker fU4V JSFHelicalTrack
fHT
S4XXXHit
S4XXXTrackHit
S4XXXTrack
double fError S4XXXExactHit Hit
16Relation among CAL Hits
TObject
TAttLockable
S4VHit
S4VExactHit
GetExactHitsPtr() GetAddress() GetHitPosition()
GetAddressPtr() GetSmearedHitPtr()
S4CALHit
S4CALExactHit
GetCALType() GetClusterType()
GetPreHitPtr()
17Typical results
18Momentum resolution
Exact hit points created by single m were fitted
by Kalman filter package
spt/pt2 (GeV -1)
By A.Yamaguchi(Tsukuba)
19EM Cal Performance
By A.L.C.Sanchez (Niigata U.)
Linearity is good, but to get energy resolution
similar to beam test results, Randge cut of O(1)
mm is required. It is very small and we dont
know why we need O(1) mm.
20Cheated Particle Flow Analysis
A sample detector signal
- Key point of PFA is use Cal. signals only for
neutral particles - Remove CAL signal if connected to a track
- Use Simulation information to connect track and
cal. signals ? Cheated PFA - What affects jet energy resolution
- Signal sampling fluctuation in Cal.
- Tracker resolution
- Treatment of V0, decays,and interactions before
Cal. - more
- ? Understand factors which affect resolution
21Cheated PFO analysis
ZH event at Ecm500 GeV
- - Exact hit points of TPC and CAL
- are displayed.
- Hits belong to the same PFO are shown with the
same color - A framework of event display
- in JSF is used.
By K.Fujii(KEK), S.Yamamoto(GUAS),
A.Yamaguchi(Tsukuba)
22X3D
ROOTs X3d view of the same event
23X3D-Jet
Same event, after a forced 4-jet clustering on
PFObjects
24Jet energy resolution
ee- ? Z ? q qbar at sqrt(E)91.1GeV
By Sumie Yamamoto
25DE for Perfect CAL./Tracker
By Sumie Yamamoto
Jet energy resolution when resolution of CAL and
tracker are perfect.
Contribution of each detector Total 2.7
GeV HD Cal 2.0 EM Cal 1.2 Tracker
0.4 Others 1.4 (under investigation)
GeV/c2
26Satellites examples
- Exam01
- Exam02
- Exam03
- Exam04
- Exam05
- Exam06
- Exam07
- Exam08
- Exam09
- Analysis code examples