Stripping issueshttps://gitlab.cern.ch/lhcb/Stripping/-/issues2024-01-22T12:08:33+01:00https://gitlab.cern.ch/lhcb/Stripping/-/issues/41Cannot get consistent results for S28r2 and S34r0p1 locally2024-01-22T12:08:33+01:00Nicole SkidmoreCannot get consistent results for S28r2 and S34r0p1 locallyRelates to DV too
## In stripping24r2-28r2-patches
- S24r2 is fine
- S28r2 cannot give consistent counters locally (ie. running the test twice produces different counters). The differences are small and do not affect the rates etc.
`...Relates to DV too
## In stripping24r2-28r2-patches
- S24r2 is fine
- S28r2 cannot give consistent counters locally (ie. running the test twice produces different counters). The differences are small and do not affect the rates etc.
```
PhotonHighSelZ0RareDecay ref) "# Phys/StdLooseAllPhotons" | 797 | 29295 | 36.757 | 17.512 | 1.0000 | 108.00
(PhotonHighSelZ0RareDecay new) "# Phys/StdLooseAllPhotons" | 797 | 29301 | 36.764 | 17.515 | 1.0000 | 108.00
```
Look at the differences in the lines btw S24r2 and S28r2?
## In 2018-patches
- S34 is fine
- S34r0p1 cannot give consistent counters locally
So its not a stack thing and not a rerunning the CALO thing.
Marco suggests it could be uninitialised pointer? Floating point number assigned wrong?
Test `2018-patches` reproducibility by running high statistics tests tests twice:
* S28r2: 60k test no rate difference
* S34r0p1: 100k test no rate difference
* S34: 100k test only 0.001% rate difference in StrippingZVTOP_High_LineEduardo RodriguesFederico Leo RediAravindhan VenkateswaranNathan Allen Griesernathan.allen.grieser@cern.chEduardo Rodrigues2023-08-01https://gitlab.cern.ch/lhcb/Stripping/-/issues/42S21 stripping cache is broken2023-06-08T16:57:00+02:00Nicole SkidmoreS21 stripping cache is brokenWhen trying to build the stripping cache for S21rX or S21rXp2 (using the instructions at
https://gitlab.cern.ch/lhcb-dpa/project/-/blob/master/source/wp5/CoordinatorGuidelines.rst
under "Prepare the StrippingCache") we get errors
```
/cv...When trying to build the stripping cache for S21rX or S21rXp2 (using the instructions at
https://gitlab.cern.ch/lhcb-dpa/project/-/blob/master/source/wp5/CoordinatorGuidelines.rst
under "Prepare the StrippingCache") we get errors
```
/cvmfs/lhcbdev.cern.ch/nightlies/lhcb-stripping21-patches/1012/Phys/InstallArea/x86_64-slc6-gcc49-opt/include/LoKi/ProtoParticles.h:491:7: note: candidate expects 0 arguments, 1 provided
/cvmfs/lhcbdev.cern.ch/nightlies/lhcb-stripping21-patches/1012/Phys/InstallArea/x86_64-slc6-gcc49-opt/include/LoKi/ProtoParticles.h:478:7: note: LoKi::ProtoParticles::HasDetector::HasDetector(const string&)
HasDetector ( const std::string& det ) ;
```
The full error can be found here
https://termbin.com/qilp
This is a new problem in the last 9 months given the MR https://gitlab.cern.ch/lhcb/DaVinci/-/merge_requests/350
NOTE: the strippingcaches for S21rXp2 were not used in production because I forgot to do this. THIS SHOULD BE ADDED TO LEGACY NOTESFederico Leo RediNathan Allen Griesernathan.allen.grieser@cern.chFederico Leo Redi