Closed Zehvogel closed 1 year ago
I can tell the event and run numbers are not set in the edm4hep to lcio conversion?
That is correct. I am also not entirely sure that information is actually available from edm4hep currently. There is an edm4hep::EventHeader
but I am not sure it is filled consistently. DDG4 does fill it, not sure how many others do.
TL;DR: event and run number not set/transferred during edm4hep to lcio conversion? /TL;DR
We received a bug report via email from Emmanuel Perez (original message below) about inconsistencies in the CLIC reconstruction between using Marlin+LCIO, Gaudi+LCIO and Gaudi+EDM4Hep. He noticed a shift in the track pulls when using the edm4hep input, mainly in tanLambda, z0 and d0. I was able to reproduce this following his description.
Digging into this we noticed that there must be an issue already during digitisation as the hit position smearing is non-gaussian.
with edm4hep input:
with slcio input:
which is weird as this part of the code looks to be independent from the input:
However, there is a dependency on the event during the refreshment of the seeds happening for every event and as far as I can tell the event and run numbers are not set in the edm4hep to lcio conversion?
I will check that next...