1 #ifndef DTVDriftCalibration_H
2 #define DTVDriftCalibration_H
67 void add(
const std::vector<const TMax*>& tMaxes);
75 std::vector<dttmaxenums::TMaxCells>
addedCells;
TMaxGranularity theGranularity
cellInfo(const cellInfo &)
Information on each of the four TMax values in a SL.
std::string theVDriftOutputFile
std::map< DTWireId, cellInfo * > theWireIdAndCellMap
edm::ParameterSet theCalibFilePar
void add(const std::vector< const TMax * > &tMaxes)
void analyze(const edm::Event &event, const edm::EventSetup &eventSetup)
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger but the state exists so we define the behavior If all triggers are the negative crieriion will lead to accepting the event(this again matches the behavior of"!*"before the partial wildcard feature was incorporated).The per-event"cost"of each negative criterion with multiple relevant triggers is about the same as!*was in the past
virtual ~DTVDriftCalibration()
Destructor.
DTSegmentSelector select_
DTMeanTimerFitter * theFitter
std::string theCalibChamber
DTVDriftCalibration(const edm::ParameterSet &pset)
Constructor.
std::vector< dttmaxenums::TMaxCells > addedCells
cellInfo(const TString &name)
DTTTrigBaseSync * theSync
edm::InputTag theRecHits4DLabel