template<typename DET, PFLayer::Layer Layer, DetId::Detector det, unsigned subdet>
class PFHGCalRecHitCreator< DET, Layer, det, subdet >
Definition at line 26 of file PFHGCalRecHitCreator.h.
template<typename DET , PFLayer::Layer Layer, DetId::Detector det, unsigned subdet>
Implements PFRecHitCreatorBase.
Definition at line 34 of file PFHGCalRecHitCreator.h.
References HCALHighEnergyHPDFilter_cfi::energy, Exception, relativeConstraints::geom, PFHGCalRecHitCreator< DET, Layer, det, subdet >::geomToken_, edm::EventSetup::getHandle(), mps_fire::i, iEvent, runTheMatrix::keep, LogDebug, or, MillePedeFileConverter_cfg::out, edm::ESHandle< T >::product(), PFRecHitCreatorBase::qualityTests_, HI_PhotonSkim_cff::rechits, PFHGCalRecHitCreator< DET, Layer, det, subdet >::recHitToken_, PFHGCalRecHitCreator< DET, Layer, det, subdet >::recHitTools_, hgcal::RecHitTools::setGeometry(), and protons_cff::time.
52 unsigned skipped_rechits = 0;
53 for (
const auto& hgrh :
rechits) {
54 const DET detid(hgrh.detid());
56 if (det != detid.det()
or (subdet != 0 and subdet != detid.subdetId())) {
58 <<
"det expected: " << det <<
" det gotten: " << detid.det() <<
" ; " 59 <<
"subdet expected: " << subdet <<
" subdet gotten: " << detid.subdetId() << std::endl;
62 double energy = hgrh.energy();
63 double time = hgrh.time();
65 auto thisCell =
geom->getSubdetectorGeometry(det, subdet)->getGeometry(detid);
69 LogDebug(
"PFHGCalRecHitCreator") <<
"warning detid " << detid.rawId() <<
" not found in geometry" << std::endl;
76 bool rcleaned =
false;
90 cleaned->push_back(rh);
92 edm::LogInfo(
"HGCalRecHitCreator") <<
"Skipped " << skipped_rechits <<
" out of " <<
rechits.size() <<
" rechits!" 94 edm::LogInfo(
"HGCalRecHitCreator") <<
"Created " <<
out->size() <<
" PFRecHits!" << std::endl;
hgcal::RecHitTools recHitTools_
std::vector< std::unique_ptr< PFRecHitQTestBase > > qualityTests_
SeedingLayerSetsHits::SeedingLayer Layer
T const * product() const
Particle flow rechit (rechit + geometry and topology information). See clustering algorithm in PFClus...
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle e< void, edm::EventID const &, edm::Timestamp const & > We also list in braces which AR_WATCH_USING_METHOD_ is used for those or
ESHandle< T > getHandle(const ESGetToken< T, R > &iToken) const
Log< level::Info, false > LogInfo
edm::ESGetToken< CaloGeometry, CaloGeometryRecord > geomToken_
edm::EDGetTokenT< HGCRecHitCollection > recHitToken_