You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
----- Begin Fatal Exception 01-Nov-2013 06:29:50 CET-----------------------
An exception of category 'BadToken' occurred while
[0] Processing run: 138924 lumi: 1 event: 1572
[1] Running path 'dqmoffline_step'
[2] Calling event method for module BTagPerformanceAnalyzerOnData/'pfbTagAnalysis'
Exception Message:
A get using a EDGetToken with the C++ type 'edm::AssociationVector,std::vector,edm::RefToBase,unsigned int,edm::helper::AssociationIdenticalKeyReference>' was made using a token with a value 1702130277 which is beyond the range used by this module.
Please check that the variable is being initialized from a 'consumes' call from this module.
You can not share EDGetToken values between modules.
----- End Fatal Exception -------------------------------------------------
The text was updated successfully, but these errors were encountered:
Hi,
I think I get the problem.
This is an indirect effect from moving the booking the histograms from the constructor to the beginRun.
Basically we are filling a vector of inputTag for the taggers we want to look at using push_back. When running on several runs, the vector increase each time (the original code was supposed to be ran only one time). The error rise as we use the size of this vector to run over the tagger list in the analyser (loop on which we do the getByToken).
I suspect #1206 is missing some consumes tag somewhere. @acaudron @deguio, can you look at it? It happens in step 3 of workflow 4.6:ù
https://cmssdt.cern.ch/SDT/cgi-bin/buildlogs/slc5_amd64_gcc481/CMSSW_7_0_X_2013-11-01-0200/pyRelValMatrixLogs/run/4.6_MinimumBias2010A+MinimumBias2010A+RECOSKIM+HARVESTD/step2_MinimumBias2010A+MinimumBias2010A+RECOSKIM+HARVESTD.log
The text was updated successfully, but these errors were encountered: