--
RicardoVazquezGomez - 2015-07-20
Stripping23 FAQ
If you want to create a new stripping line, you should look
here. The general way of testing the lines is described
here. Below follows a more detailed explanation for specific S23 testing.
How to deal with Vertex and PVRefit in the Stripping
The inclusion of PVRefit and Vertex fitters inside the stripping is detailed in this
link.
How to run the tests for timing/retention in S23?
In order to perform any test related to S23 you should use the DV v36r7p7 (
DaVinci v37r2p2 for S23c). To set up the environment do
lb-dev DaVinci v36r7p7
cd DaVinciDev_v36r7p7
getpack Phys/StrippingSelections head
After getting the head of the Phys/StrippingSelections package, do
cd Phys/StrippingSelections/tests/users
Inside the folder you will find the script
TestMyStrippingLine.py that is used to evaluate the retention and timing of the required stripping lines. Inside the script you will need to modify the line that sets the name of the
StrippingLine.
For lines going to DST the retention MUST BE 0.05%, while for lines going to mDST the retention MUST BE 0.5%. The timing per line needs to be under 1ms/event.
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
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.
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