9 std::vector< Alignable* > updated;
10 std::vector< Alignable* >::const_iterator itAlignable = alignables.begin();
12 while ( itAlignable != alignables.end() )
16 if (
std::find(updated.begin(),updated.end(),*itAlignable) == updated.end() && alignmentParameters != 0 )
21 if ( userVariables != 0 ) userVariables->
update();
23 updated.push_back( *itAlignable );
31 const std::vector< Alignable* >
35 std::vector< Alignable* > alignables;
37 std::vector< AlignableDetOrUnitPtr >::const_iterator itAD;
38 for ( itAD = alignableDets.begin(); itAD != alignableDets.end(); ++itAD )
41 alignables.push_back( ali );
51 std::set< Alignable* >
list;
52 list.insert( ali.begin(), ali.end() );
53 unsigned int ndiff = list.size();
virtual const std::vector< Alignable * > alignablesFromAlignableDets(std::vector< AlignableDetOrUnitPtr > &alignableDets, AlignmentParameterStore *store) const
void updateUserVariables(const std::vector< Alignable * > &alignables) const
Update the AlignmentUserVariables, given that the Alignables hold KalmanAlignmentUserVariables.
void find(edm::Handle< EcalRecHitCollection > &hits, DetId thisDet, std::vector< EcalRecHitCollection::const_iterator > &hit, bool debug=false)
void update(bool enforceUpdate=false)
Call this function in case the associated Alignable was updated by the alignment algorithm.
AlignmentUserVariables * userVariables(void) const
Get pointer to user variables.
unsigned int nDifferentAlignables(const std::vector< Alignable * > &ali) const
Alignable * alignableFromAlignableDet(const AlignableDetOrUnitPtr &alignableDet) const
Obsolete: Use AlignableNavigator::alignableDetFromGeomDet and alignableFromAlignableDet.
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 list("!*","!HLTx*"if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL.It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of"!*"before the partial wildcard feature was incorporated).Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run