TOF issues¶

July 13, 2017¶

Issues¶

• Calibrations & efficiencies:
  • #1912
  • Action: SW to upload new calibrations after verifying. Estimate ~end of this week
  • What is the TOF2 efficiency now with improved calibration?
  • What is the status of the deltaT offset with the new calibrations?
  • Action: SW to look at expanding the data structure to include an e.g. tof0/1/2_all_spacepoints structure

• MC-vs-data
  • SW noted MC truth and reco agree now, there remains a small (??? ps) discrepancy in TOF1-2
  • Action: SW to add plots showing MC true vs reco
  • Action: SW to verify that the TOF0-1-2 distances in the calibration cards are consistent with survey geometry
  • Action: SW to compare MC and data for 140, 240 MeV to benchmark level of discrepancy between MC and data
  • Action: Try to add path length information to MC. the PathLength data member is currently unfilled in MAUS.

• TOF-tracker discrepancy
  • Reported discrepancy of ~100ps (?) between TOF and tracker? [ any plots to show this? CR? ]
    • CR noted it's not clear whether this is from tof or tracker, there is a ~3 MeV discrepancy in just trackers
    • Issue parked for now. Will revisit after vetting TOF MC

• System performance paper

Dial-in:¶

• We'll try http://mice.iit.edu/phonebridge.html
  • If already taken, Chris please advise re alternate dial-in code

---

Notes from meeting of June 13, 2017¶

• Attendance: Rogers, Wilbur, Rajaram

• Efficiency
  • SW has new experimental calibrations which improve the coverage
  • 6% failed calibration (now) vs 15% (before)
  • SW is checking the calibrations before uploading
  • DR: Suggestions to improve coverage:
    • combine data from May and March runs
    • do timewalk calibration from a large sample (run conditions don't matter) and use this instead of doing tw calib each time
  • CR asks about the 500ps cut in spacepoint reconstruction -- notes it cuts out ~1% of events. Can it be expanded?
  • CR: can we have a new spacepoint structure to include the events which failed the cut?
  • Action: SW to look at expanding the data structure to include an e.g. tof0/1/2_all_spacepoints structure
  • Action: SW to upload new calibrations after verifying. Estimate ~end of this week

• TOF tracker discrepancy
  • CR: Not clear if this is from tof or tracker, there is a ~3 MeV discrepancy in just trackers
  • Issue parked for now. Will revisit after vetting TOF MC

• MC
  • SW: MC truth and reco agree now, there remains a small (??? ps) discrepancy in TOF1-2
  • Action: SW to add plots showing MC true vs reco
  • Action: SW to verify that the TOF0-1-2 distances in the calibration cards are consistent with survey geometry
  • Action: SW to compare MC and data for 140, 240 MeV to benchmark level of discrepancy between MC and data
  • Action: Try to add path length information to MC. the PathLength data member is currently unfilled in MAUS.
    • SW notes GEANT4 calculates the path length each time, which is potentially computationally intensive.
    • DR: Can we turn this on and do some test MC to see what the MC path length is and how it compares with the straightline distance?

• Calibration systematics
  • TOF2 dt offset: SW notes that he still sees this with his new calibrations. It is not from fits to the 'wrong peak'. To be understood

• Date of next meeting: