tauRec: fix flag check
Hello, There was a recent jump in CPU for the first tau algorithm we run, while there was no change in any tool: https://atlaspmb.web.cern.ch/atlaspmb/arch-mon-fullchain_mc16_ttbar_valid_13tev_25ns_mu40/?test=cpu/master__x86_64-centos7-gcc8-opt#RAWtoESD/tau I suspect it's due to atlas/athena!37904 (diffs) where rec.doESD should rather be rec.doESD(). As the check fails, we might not be using the cached track-calo extrapolation, which may cause the CPU increase. I'm running some test to verify this. Results in a few minutes. Cheers, Bertrand
Loading
Please register or sign in to comment