<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">There may be some atomic capture of pi- on a nucleus, but I would have guessed<div>the time scale is fractions of a ns. I would also expect the same in both FCAL and</div><div>BCAL<br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div><div>---------</div><div>Curtis A. Meyer<span class="Apple-tab-span" style="white-space: pre; "> </span>MCS Associate Dean for Faculty and Graduate Affairs</div><div>Wean: (412) 268-2745<span class="Apple-tab-span" style="white-space: pre; "> </span>Professor of Physics</div><div>Doherty: (412) 268-3090<span class="Apple-tab-span" style="white-space: pre; "> </span>Carnegie Mellon University</div><div>Fax: (412) 681-0648<span class="Apple-tab-span" style="white-space: pre; "> </span>Pittsburgh, PA 15213</div><div><a href="mailto:curtis.meyer@cmu.edu">curtis.meyer@cmu.edu</a><span class="Apple-tab-span" style="white-space: pre; "> </span>http://www.curtismeyer.com/</div></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On May 30, 2014, at 6:58 PM, Will Levine <<a href="mailto:wilevine@andrew.cmu.edu">wilevine@andrew.cmu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Is there some type of nuclear process that takes place on a time scale of ~5 ns?<br><br>I've looked a little more at some of the problem events and it doesn't<br>seem like the relevant late hits are from pi->mu decays.<br><br>Another way to get info recorded in hdgeant is thru trajectory info<br>(accessed via DMCTrajejectoryPoint). This must be enabled in<br>control.in. I set TRAJECTORIES = 2, which means store birth and death<br>points of all particles. Again, I don't totally understand the<br>information saved, so I might be misinterpreting it, but it looks like<br>the late hits are due to protons and neutrons that just seem to appear<br>a few ns later, which is why I asked about delayed nuclear process. I<br>have atttached the trajectory information for a typical-looking event<br>with my annotations for anyone else to take a look at.<br><br>On Fri, May 30, 2014 at 4:07 PM, Justin Stevens <<a href="mailto:jrsteven@mit.edu">jrsteven@mit.edu</a>> wrote:<br><blockquote type="cite">Hi Will,<br><br>I'm wary of trying to draw too much from a single event (so take this with a grain of salt), but if I assume the event you give below is "typical" in the BCAL TruthCell it looks like there might be 3 classes of hits:<br><br>1) very late in time (2-4 microseconds)<br>2) late in time (30-70 ns),<br>3) close in time (5-10 ns)<br><br>1) doesn't seem very relevant since they're so far away (and happen to be on the timescale of the muon lifetime as Richard suggested). Depending on the source of class 2), they might be able to be removed from the reconstructed shower time calculation by only using hits within XX ns of the first hit. Do you have a requirement that the hits used to calculate the shower time have to be in some XX ns window from the first hit? For class 3) two of the outer layer hits have t = 8 and 10 ns, is that typically expected from propagation or are these hits "late"?<br><br>Maybe you've already tried it, but if you were to form clusters and time averages from these TruthCell hits, similar to the algorithm you use in the offline, it might tell you more about what kinds of hit selection could be useful in offline reconstruction to prune late hits.<br><br>-Justin<br><br>On May 29, 2014, at 6:32 PM, Will Levine wrote:<br><br><blockquote type="cite">Hi offline,<br>Following up on the issue of "late" energy deposition in hadronic<br>showers in the BCAL.<br><br>There are two different ways that BCAL truth information from hdgeant<br>is stored: these can be accessed in JANA from the DBCALTruthShower and<br>the DBCALTruthCell objects. The code that stores this information is<br>in hitBarrelEMcal() in<br>sim-recon/src/programs/Simulation/HDGeant/<a href="http://hitBCal.cc">hitBCal.cc</a><br><br>As I understand the code, DBCALTruthShower records every particle that<br>geant tracks thru the BCAL (with energy greater than 1 MeV). One<br>DBCALTruthShower for each unique particle in the BCAL. This includes<br>all secondary shower particles. The particle type, initial energy, and<br>initial position in the BCAL is recorded for each particle.<br><br>DBCALTruthCell just records the energy deposited in a given BCAL cell<br>without recording which particle was responsible for the energy.<br>(Again this is "truth" information, before any detector resolution or<br>readout effects are incorporated).<br><br>These two sources of information are not always tremendously helpful.<br>For example in one single-pion event that has some characteristic<br>"late hits", we see the following DBCALTruthShower's:<br><br>DBCALTruthShower:<br>ptype: track: primary: phi: r: z: t: p: E:<br>-------------------------------------------------------------------<br> 8 1 1 -1.863 65.042 185.3 4.780 0.571 0.588<br><br>Only the primary pion is recorded. There is no record of any secondary<br>tracks. But when we look at the TruthCell's in the same event:<br><br>DBCALTruthCell [truncated]:<br>module: layer: sector: E: t: zLocal:<br>-----------------------------------------------<br> 34 1 1 0.006 71.31 -6.0<br> 34 1 3 0.027 4.87 -24.4<br> 34 1 4 0.002 4.79 -26.5<br> 34 2 1 0.006 33.59 -16.9<br> 34 2 2 0.018 5.07 -19.6<br> 34 2 3 0.013 4.98 -21.7<br> 34 3 1 0.020 28.91 -15.4<br> 34 3 1 0.005 4301.28 -19.1<br> 34 3 2 0.023 5.19 -16.6<br> 34 4 1 0.029 6.45 -13.1<br> 34 4 1 0.019 73.07 -13.0<br> 34 4 1 0.004 2219.77 -13.3<br> 34 4 1 0.039 4301.12 -15.0<br> 34 5 1 0.017 8.24 -9.6<br> 34 5 1 0.001 4301.19 -17.1<br> 34 7 1 0.011 10.44 -21.4<br><br>The time is in the second-to-last column. The "on-time" hits have t ~<br>5 ns. Where are all the late hits coming from? It is not clear. There<br>must be some tracks that are not recorded in the TruthShower info.<br><br>Even in events with a more extensive record of secondary tracks it's<br>not clear what is responsible for a late hit:<br><br>DBCALTruthShower:<br>ptype: track: primary: phi: r: z: t: p: E:<br>-------------------------------------------------------------------<br> 8 1 1 -2.072 65.042 186.4 4.812 0.572 0.589<br> 13 22 0 -2.083 65.969 188.5 5.185 0.284 0.982<br> 14 21 0 -2.083 65.969 188.5 5.185 0.040 0.939<br> 13 20 0 -2.083 65.969 188.5 5.185 0.173 0.955<br> 3 19 0 -2.081 65.814 188.1 4.879 0.005 0.005<br> 3 19 0 -2.083 65.851 188.2 4.884 0.002 0.002<br> 1 19 0 -2.083 65.852 188.2 4.884 0.001 0.001<br><br>Any ideas?<br><br>Will<br>_______________________________________________<br>Halld-offline mailing list<br><a href="mailto:Halld-offline@jlab.org">Halld-offline@jlab.org</a><br>https://mailman.jlab.org/mailman/listinfo/halld-offline<br></blockquote><br></blockquote><span><trajectories.event_28.txt></span>_______________________________________________<br>Halld-offline mailing list<br><a href="mailto:Halld-offline@jlab.org">Halld-offline@jlab.org</a><br><a href="https://mailman.jlab.org/mailman/listinfo/halld-offline">https://mailman.jlab.org/mailman/listinfo/halld-offline</a></div></blockquote></div><br></div></body></html>