d3/d34/CounterChecker_8cc_source.html

 /****************************************************************************

  *

  * This is a part of TOTEM offline software.

  * Authors:

  *   Maciej Wróbel (wroblisko@gmail.com)

  *   Jan Kašpar (jan.kaspar@gmail.com)

  *

  ****************************************************************************/


 #include "EventFilter/CTPPSRawToDigi/interface/CounterChecker.h"


 //-------------------------------------------------------------------------------------------------


 using namespace std;


 //-------------------------------------------------------------------------------------------------


 void CounterChecker::Fill(word counter, TotemFramePosition fr)

 {

   pair<CounterMap::iterator, bool> ret;


   vector<TotemFramePosition> list;

   list.push_back(fr);

   ret = relationMap.insert(pair<word, vector<TotemFramePosition> >(counter, list));

   if (ret.second == false)

     relationMap[counter].push_back(fr);

 }

runTheMatrix.ret
tuple ret
prodAgent to be discontinued
Definition: runTheMatrix.py:279

TotemFramePosition
Definition: TotemFramePosition.h:32

CounterChecker::word
unsigned short word
Definition: CounterChecker.h:31

CounterChecker.h

CounterChecker::Fill
void Fill(word counter, TotemFramePosition fr)
add new value to map, counter takes value of EC or BC number
Definition: CounterChecker.cc:18

counter
static std::atomic< unsigned int > counter
Definition: SharedResourceNames.cc:15

list
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