Opened 5 years ago
Closed 5 years ago
#2325 closed defect (duplicate)
[MuonGun] Exclude stochastic losses outside active volume in Track::GetEnery()
Reported by: | Jakob van Santen | Owned by: | Jakob van Santen |
---|---|---|---|
Priority: | normal | Milestone: | Autumnal Equinox 2019 |
Component: | combo simulation | Keywords: | |
Cc: | Jan Soedingrekso |
Description
MuonGun::Track assumes that all daughters attached to a muon in I3MCTree are stochastic losses in the active volume, and uses the the difference between the sum of daughter energies and I3MMCTrack::GetElost?() as an estimate of the continuous loss rate. PROPOSAL now seems to attach muon decay products to I3MCTree even if they are outside the volume. In the attached example from jsoedingrekso, an up-going muon decays in low Earth orbit at 180 TeV. This makes the estimated continuous loss rate negative, and MuonGun::Track() claims that the muon _gains_ energy as it propagates.
This could be fixed by only including stochastic losses between Ti and Tf.
Attachments (2)
Change History (6)
Changed 5 years ago by Jakob van Santen
Changed 5 years ago by Jakob van Santen
comment:1 Changed 5 years ago by Alex Olivas
- Milestone set to Autumnal Equinox 2019
comment:2 Changed 5 years ago by Alex Olivas
It's time to start thinking about the next milestone. Going to try something new, since waiting until the code sprints to attack tickets hasn't provided the results we were hoping for.
If you're the owner of this ticket, please acknowledge you're at least receiving email updates by 'accept'ing this ticket in 3 easy steps.
1) Click "Modify Ticket"
2) Click "accept"
3) Click "Submit changes"
comment:3 Changed 5 years ago by Alex Olivas
To the owner of this ticket. Signal you're aware if this ticket, by 'accept'ing it.
comment:4 Changed 5 years ago by Alex Olivas
- Resolution set to duplicate
- Status changed from new to closed
These are all moving to smartsheets 'projects'
muon perpetual motion machine