Difference: LHCbStripping23 (4 vs. 5)

Revision 52015-07-28 - RicardoVazquezGomez

Line: 1 to 1
 
META TOPICPARENT name="LHCbStripping"
-- RicardoVazquezGomez - 2015-07-20
Line: 30 to 29
 If the requirements are not satisifed, the changes to the configuration dictionary can be done inside the testing script without needing to modify and compile the stripping algorithm. To do so uncomment the line
confs[confname]["CONFIG"]["CutName"] = NewValue
Changed:
<
<
You need to change only CutName and NewValue with the appropriate name and value that you want to test. This will change at the configuration time the value for the selected cut. Remember to update the default_config dictionary inside the stripping algorithm after arriving to the desired configuration.
>
>
You need to change only CutName and NewValue with the appropriate name and value that you want to test. This will change at the configuration time the value for the selected cut. Remember to update the default_config dictionary inside the stripping algorithm after arriving to the desired configuration.
  To evaluate the timing, the script creates a copy of all the lines with the name XXX_TIMING to get the real timing consumption by the lines without taking into account the creation of CommonParticles. This is the time that must be under 1ms/event.
Added:
>
>

How to solve the error ERROR L0DUFromRawAlg:: TCK not recognized.

While running the stripping tests you may encounter the following error:

ToolSvc.L0DUConfig                                             INFO Creating the TEMPLATE configuration tools : ToolSvc.L0DUConfig.Template for time slot :  'T0' 
ToolSvc.L0CondDBProvider                                       INFO Registered RAM(BCID) versions = {} 
ToolSvc.L0DUConfig.Template                                    INFO --------------- TCK = 0x10000------------------ 
ToolSvc.L0DUConfig.Template                                    INFO **** L0DU Config loading : L0TCK = 0x10000 for slot T0 ==> OK  
ToolSvc.L0DUConfig.Template                                    INFO Short description :: NO DESCRIPTION (L0DUConfig.Template) 
ToolSvc.L0DUConfig                                            ERROR L0DUMultiConfigProvider:: The requested TCK = 0xEE63 is not registered  
L0DUFromRaw.L0DUFromRawTool                                 WARNING L0DUFromRawTool::  Unable to load the configuration for tck = 0xEE63 --> Incomplete L0DUReport 
L0DUFromRaw                                                   ERROR L0DUFromRawAlg:: TCK not recognized. Run with L0Conf().EnsureKnownTCK=False to ignore this error StatusCode
=FAILURE 
DataOnDemandSvc                                               ERROR Failed to execute the algorithm:L0DUFromRaw for location:/Event/Trig/L0/L0DUReport

To solve it do

getpack TCK/L0TCK head 
cp /afs/cern.ch/work/m/mvesteri/public/RealData1406/L0DUConfig_June2015_0xEE63.opts TCK/L0TCK/options


And also add the following line

#include "$L0TCK/L0DUConfig_June2015_0xEE63.opts"

to the file

TCK/L0TCK/options/L0DUConfig.opts



 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback