Project

General

Profile

Bug #6706

Use RecoHit::MIP() to define MIP-peak in various modules

Added by Christopher Backhouse over 5 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Start date:
07/29/2014
Due date:
% Done:

0%

Estimated time:
Duration:

Description

This was an email, but it didn't get much traction. We shouldn't forget to do this, so make it an Issue...

As discussed in the "All Analysis" meeting on June 23, we're trying to move away from exposing PECorr to the outside world, it's basically a calibration implementation detail, and can change from release to release.

The following packages have cuts on PECorr being used to define a MIP peak:

CAFMaker
Calibration/Mpi0
Filter/CAFFilter
NCAna
NueSandbox
Preselection/NuePresel
RecVarPID

These are probably now mistuned. It would be much better to use a stable calibration quantity. RecoHit::MIP seems tailor-made...

Can we try and determine a good definition of the MIP peak in terms of actual MIP units and alter this code to use it?

History

#1 Updated by Alexander Himmel about 3 years ago

  • Status changed from New to Rejected


Also available in: Atom PDF