1 / 10

A Brief History of Glast Release

A Brief History of Glast Release. GR1.1594 (Friday, July 15) Effectively, the first DC-2 2M all-gamma sample Had various problems (no MIP finding, Direct diode deposit all to one face, etc.) GR1.612 (Wednesday, July 27) Why change one thing when you can change 10?

andrew-buckner
Download Presentation

A Brief History of Glast Release

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. A Brief History of Glast Release • GR1.1594 (Friday, July 15) • Effectively, the first DC-2 2M all-gamma sample • Had various problems (no MIP finding, Direct diode deposit all to one face, etc.) • GR1.612 (Wednesday, July 27) • Why change one thing when you can change 10? • 21 packages change between these two runs • Most important to this discussion: • Convert ntuple output from doubles to floats • CalDigi, CalXtalResponse and Trigger packages extensively refactored. Also attempts to raise thresholds to 2 MeV and double the noise • MIP finding turned on (version optimized for speed) • Various bug fixes in CalRecon, Event and AnalysisNtuple related to new Cal output format • All runs use the same seed so can’t be used…

  2. A Brief History of Glast Release • GR1.613 (Friday, July 29) • Fix run seed problem • Notice that energy response appears to have changed significantly • GR1.615 • Six packages modified, including: • CalXtalResponse – fix bug which allowed longitudinal position to be outside hit crystal (and often in another tower…) • CalRecon – fix bug in Last Layer Likelihood tool which caused it to not get called • Still see problem with energy response in recon • GR1.615-mod • Back out CalDigi/CalXtalResponse/Trigger to post GR1.594 versions • This puts thresholds and noise back to “old” versions • But appears to “solve” the energy response problem

  3. Cal Raw Energy SumGR1.594 to GR1.615 all-gamma 180 GeV Blue Histogram: GR1.594 Red Overlay: GR1.615 Was not expecting things to get worse!!!

  4. Cal “PSF”GR1.594 to GR1.615 all-gamma 180 GeV Blue Histogram: GR1.615 Red Overlay: GR1.594 Was not expecting things to get worse!!! MC-Cal Angle (radians)

  5. Look at Input to CalReconCalXtalRecData: GR1.594 to GR1.615 all-gamma 180 GeV Blue Histogram: GR1.594 Red Overlay: GR1.615 Number of CalXtalRecData objects per event (with a nonzero number of CalDigis

  6. Look at Input to CalReconCalXtalRecData: GR1.594 to GR1.615 all-gamma 180 GeV Blue Histogram: GR1.594 Red Overlay: GR1.615 Energy per CalXtalRecData object for all CalXtalRecData objects in each event Close in on range 0-50 MeV

  7. Look at Input to CalReconCalXtalRecData: GR1.594 to GR1.615mod all-gamma 180 GeV Blue Histogram: GR1.594 Red Overlay: GR1.615mod “Old” CalXtalResponse code with raised thresholds and noise Close in on range 0-50 MeV Energy per CalXtalRecData object for all CalXtalRecData objects in each event

  8. Cal Raw Energy SumGR1.594 to GR1.615 all-gamma 180 GeV Blue Histogram: GR1.613 Red Overlay: GR1.594 Was not expecting things to get worse!!!

  9. Cal “PSF”GR1.594 to GR1.613 all-gamma 180 GeV Blue Histogram: GR1.615-mod Red Overlay: GR1.594 This is what I expected! MC-Cal Angle (radians)

  10. Where Are We Now? • Recon appears to be ready for CT studies again • MIP Finding code in place and in output ntuple • Cluster energy and axis appear to be “normal” • Running the “old” CalDigi/CalXtalResponse/Trigger • Can raise thresholds and noise in this code to desired levels • Are we losing something in the updated package that we need for DC-2? • Time frame for studying/fixing the code? • Are there other problems? • Onboard Filter is having a problem too? • Opinions?

More Related