27 os <<
"Read " << rhs.
rctEm()->size() <<
" RCT EM candidates\n"
28 <<
"Read " << rhs.
rctCalo()->size() <<
" RCT Calo Regions\n";
std::vector< L1CaloEmCand > L1CaloEmCollection
~RctUnpackCollections()
Destructor - the last action of this object is to put the rct collections into the event provided on ...
RctUnpackCollections(edm::Event &event)
Construct with an event. The collections get put into the event when the object instance goes out of ...
L1CaloRegionCollection *const rctCalo() const
Input calo regions from the RCT to the RCT.
std::auto_ptr< L1CaloRegionCollection > m_rctCalo
Input calo regions.
L1CaloEmCollection *const rctEm() const
Input electrons from the RCT to the RCT.
std::ostream & operator<<(std::ostream &out, const ALILine &li)
OrphanHandle< PROD > put(std::auto_ptr< PROD > product)
Put a new product.
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
std::auto_ptr< L1CaloEmCollection > m_rctEm
Input electrons.
std::vector< L1CaloRegion > L1CaloRegionCollection
edm::Event & m_event
The event the collections will be put into on destruction of the RctUnpackCollections instance...