1 / 37

Jupiter and Satellites

Jupiter and Satellites. Akiya Miyamoto KEK June 2005. Target 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 )

peyton
Download Presentation

Jupiter and Satellites

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Jupiter and Satellites Akiya Miyamoto KEK June 2005

  2. Target 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.

  3. Jupiter/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

  4. Jupiter feature - 1 • Based on Geant4 7.0p1 • Modular organization of source codes for easy installation of sub-detectors • Geometry • parameters ( size, material, etc ) can be modified by input ASCII file. • Only simple geometries are implemented ( OK for the detector optimization ) • Input: • StdHep file(ASCII), HepEvt, CAIN, or any generators implemented in JSF. • Binary StdHep file interface was implemented.Need some more tests.

  5. Jupiter feature - 2 • Run mode: • A standalone Geant4 application • JSF application to output a ROOT file. • Output: • Exact Hits of each detectors (Smearing in Satellites) • Pre- and Post- Hits at before/after Calorimeter • Used to record true track information which enter CAL. • Format: ROOT (standard), ASCII(debug), LCIO • Physics List • LCPhysicsList • QGSP, LHEP, … • Calorimeter resolution : Depends on physics list, and not as good as we expected for single particle

  6. Geometry in Jupiter Muon/Iron Solenoid TPC Hadron Calorimeter VTX Elemag. Calorimeter QC1 IT Forward Cal.

  7. Detector Parameters • GLD_V1: as an initial set of detector parameters • Beam Pipe : 1.8cmf, Be 500mmt • VTX : 4 layers from R=2.4cm to 6.0cm, Si 330mmt, |cosq|<0.9srj=sz=4mm, Cylindrical shape, not FPCCD geometry yet • IT : 4 layers from R=9cm to 30cm, Si 600mmt, |cosq|<0.9srj=sz=10mm, Cylindrical shape • TPC : R=40cm to 206cm, |Z|<235cm, # of sampling 200srj=150mm, sz=500mm, Gas P10 • Solenoid : 3T • Muon : Barrel : 4 mud layers, total 270cmt Fe Endcap : 5 mud layers, total 260cmt Fe Signals are smeared in Satellites All parameters needs to be optimized

  8. 210 cm Full One Tower EM + HD 40 cm 270 cm 6.1λ 27 X0 Calorimeter Geometry • Default sensor size: • EM: 4cmx4cmx1mm, 38 layers • HD:12cmx12cmx2mm, 130 layers • Replica • Phi direction : Tower and mini-tower • Sandwich structure of X/Y scinti structure can be defined.

  9. Documents Documents are available at http://www-jlc.kek.jp/subg/offl/lib/docs/Jupiter • Jupiter in general: • Jupiter.pdf : “JUPITER”, the latest manual (June 6, 2004, in Japanese ), by K.Hoshina • Hoshina-appi2002.pdf : “Simulator status of Jupiter and Satelliets”,The proceedings of APPI2002, by K.Hoshina • Stereo Geometry for CDC • J4TwistedTubs.pdf: K.H, K.F and O.N., CPC 153 (2003)373-391, • Hoshina-appi2003.pdf: “Status of Jupiter and Satellites”,the proceedings of APPI2003 by K.Hoshina • Thesis • Hoshina-D.pdf: Doctor Thesis by K.Hoshina (in Japanese) • Nakashima-M.pdf: Master Theses by Y.Nakashima (in Japanese)About Kalman Filter Track Fitting package

  10. Meetings & ML • Since last July, • We had two Jupiter developers workshop • Each about ~ 1 week • Participants : A.Miyamoto, K.Fujii (KEK), and students from Kobe, Niigata, Tsukuba, GUAS • Regular TV meetings in Tuesday afternoon • Create a mailing list, acfa-sim-j@jlcux1.kek.jp • To discuss technical details ( in Japanese )

  11. Sources • The host system for developments is jlclogin.kek.jp • CVS Master repository : jlclogin:/proj/soft/CVSMASTER Note: CVS repository of Jupiter and Satellites are updated very frequently • A set of libs/execs : jlclogin:/proj/soft/Release/x.xx ( x.xx=1.00 as of June 1, new set will be created soon ) • For a remote user, • Daily snap shots of CVS repository: http://jlccvs.kek.jp/snapshots/ • The Web interface to CVS, http://jlccvs.kek.jp/ • Remote access to the CVS repository • CVS access is out of order, due to a security problem.We will restart after the system update, if there is a request. • Or use CVSup ( see http://jlccvs.kek.jp/cvsup/ )

  12. Jupiter Directory Structure Jupiter bin config doc include lib macros scripts sources tmp Linux-g++ Readme Sample G4scripts Jupiter common.gmk main sol lcexp kern cal cdc ct vtx bd 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

  13. How to build and run Jupiter • You will need, • ROOT, JSF, Geant4, CLHEP, …(?) • Get JUPITER source from CVS • Set environment parameters, such as JUPITERROOT • See jlclogin:/proj/soft/Release/x.xx/setup.bash for example • Then do “make” at the Jupiter top director. • To run, type $ Jupiter … prompt> /run/beamOn 100 Read pythia_event.data and hit information is written in a file, hit.dat

  14. Standalone Jupiter $ Jupiter [options] [g4macro file]   options:     -v N : N is a message level.            > 10 ; Write message every time new geometry is created.            5-10 ; Write message of geometry whose rank is less than N-4.            < 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

  15. G4macro 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/_.html

  16. Jupiter parameter list file • Parameters for detector configuration can be modified by a parameter file given by –f option. • Default parameters defined in the program is prepared in $JUPITERROOT/doc/gld_v1.dat • $JUPITERROOT/doc/HowToRun for more details

  17. HepStd and LCIO • Interface module to HepStd and LCIO are provided as JSF modules. • HepStd • ASCII format : using LCHEP package • Binary format : using MCFIO package ( implemented very recently, needs more study ) • LCIO • Exact hit points and MCParticle data can be written as LCIO file. • Links between Exact hits and MCParticle are not perfect yet.

  18. Satellites/Uranus

  19. JSFJ4 • 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

  20. Metis 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

  21. Metis Analysis Flow Jupiter result Physics study make smeared TPC hits from exact hit make tracks from TPC make hybrid tracks ( TPC+IT+VTX) make smeared/merged CAL hits from exact hit make cluster from CAL hits make Particle Flow Objects jet clustering

  22. Satellites 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

  23. Metis Directory Structure metis (JSF’s) Modules for MC data analysis tpc hitmaker make smeared TPC hits from exact hit make tracks from TPC trackmaker hybt hybtmaker make hybrid tracks ( TPC+IT+VTX) 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

  24. Uranus Directory Structure Uranus Packages for real data analysis data kern include lib VTX detconfig src hitmaker IT trackmaker TPC hybt

  25. Relation among TrackHits U4VTrackHit double fResidual double fT0 U4VHit *fHitPointer TObjArray U4XXXTrackHit U4XXXTrack U4XXXHit U4VTrack double fChi2 U4VTrackMaker* fU4V JSFHelicalTrack* fHT S4XXXHit S4XXXTrackHit S4XXXTrack double fError S4XXXExactHit *Hit

  26. Relation among CAL Hits TObject TAttLockable S4VHit S4VExactHit +GetExactHitsPtr() +GetAddress() +GetHitPosition() GetAddressPtr() GetSmearedHitPtr() S4CALHit S4CALExactHit + GetCALType() +GetClusterType() + GetPreHitPtr()

  27. Typical results

  28. Momentum resolution Exact hit points created by single m were fitted by Kalman filter package spt/pt2 (GeV -1) By A.Yamaguchi(Tsukuba)

  29. EM 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 don’t know why we need O(1) mm.

  30. Cheated 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

  31. Cheated PFO analysis ZH event at Ecm=500 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)

  32. X3D ROOT’sX3d view of the same event

  33. X3D-Jet Same event, after a forced 4-jet clustering on PFObjects

  34. e+e- Z  q qbar at sqrt(E)=91.1GeV Jet energy resolution By Sumie Yamamoto

  35. DE 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

  36. Satellites examples • Exam01 • Exam02 • Exam03 • Exam04 • Exam05 • Exam06 • Exam07 • Analysis code examples

  37. Summary • Full detector simulator, Jupiter, has been developed based on Geant4. • Cheated PFA has been implemented in Satellites and a study of jet mass resolution in progress. • Other studies in progress includes • Development of realistic PFA • Study of TPC performance • Backgrounds studies • There are many untouched topics. Contributions are highly welcomed.

More Related