Simulation v0.1 - PowerPoint PPT Presentation

1 / 10
About This Presentation
Title:

Simulation v0.1

Description:

Names in multimap refer to primary particle all from same primary have same name ... Names for multimap are identical to those in IceTopParticleMap ... – PowerPoint PPT presentation

Number of Views:45
Avg rating:3.0/5.0
Slides: 11
Provided by: tycede
Category:

less

Transcript and Presenter's Notes

Title: Simulation v0.1


1
Simulation v0.1
  • IceCube Collaboration Meeting
  • Uppsala, Sweden

2
Overview
  • Goal is to simulate cosmic ray muon events
  • Development release not for serious physics
    analysis
  • Verify that offline tools work
  • Establish a baseline for continuing simulation
    development
  • Provide starting point for development of
    reconstruction tools (at a pre-physics level)
  • Allow preliminary comparisons to amasim

3
Generator
  • Corsika file reader
  • No attempt to incorporate corsika itself into
    IceTray at this time
  • Cosmic ray spectrum on the atmosphere
  • EM air shower particles at ground level
  • Muons at ground level
  • Output is I3Particles in IceTopParticleMap
  • Names in multimap refer to primary particle all
    from same primary have same name
  • Particle parentID and primaryID are set
  • Primary particle is recorded in PrimaryMap with
    same name as in IceTopParticleMap
  • Ready now?

4
IceTop Simulation
  • Bartol is responsible for generating IceTop
    response from records in the IceTopParticleMap
  • Peters status report
  • Trigger records?

5
Propagator
  • MMC for muon propagation
  • Takes particles from IceTopParticleMap, checks
    for muon particle type
  • Propagates muons through active volume, writes
    particles as they exist InIce in InIceParticleMap
  • ParentID refers to version of particle in
    IceTopParticleMap
  • Names for multimap are identical to those in
    IceTopParticleMap
  • Mainly ready now, but possibly bug in Java/C
    interface?

6
Hit Constructor
  • Takes muon tracks from InIceParticleMap as input
  • Uses geometry records read in by I3DB
  • Writes photons reaching surface of PMT based on
    results provided by PSI service
  • Glass/gel effects included in table efficiency
    files, but not quantum/collection efficiencies
  • Written to I3MCPhotonVect in I3OMResponse
  • ParentID is taken from muon particleID
  • Provides time series (possibly extra info such as
    wavelength?)
  • Ready now but may need some physics-level
    tweaks (IR cutoff, etc.)

7
ROMEO
  • Uses photon time series from I3OMResponse for
    input
  • Will write a photoelectron series to
    I3MCHitSeries as an intermediate result
  • Writes a PMT waveform to an as-yet-nonexistent
    field in I3MCOMResponse as output
  • Interface is a whole function? a value given a
    time?
  • Will not include effects like saturation at this
    stage of development
  • Relative geometry of track, OM available, but not
    actual flight path or actual emission point of
    photon
  • Released, needs integration into IceTray

8
DOMSimulator
  • Will use voltage series from ROMEO as input
  • Output is a DataReadout consisting of one or more
    Launches
  • IsRaw will return true
  • Responsible for controlling execution of ROMEO?
  • End of October

9
(Simple) InIce Trigger
  • Will look at the OMResponses and form a trigger
  • Output will be written to TriggerDict
  • Will be written regardless, with a DidPass field
  • Algorithm still TBD?

10
Feature Extraction
  • Will provide a DataReadout representing
    synthesized DOM output
  • Based on raw DOM DataReadout
  • IsRaw will be false
Write a Comment
User Comments (0)
About PowerShow.com