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
It's due to !37904 (diffs) where rec.doESD should rather be rec.doESD(). As the check fails, we are not using the cached track-calo extrapolation, which causes the CPU increase.
I've rerun the data18 RAWtoALL SPOT test.
18:36:08 PMonSD n cpu max@evt vmem max@evt malloc max@evt component
18:36:57 PMonSD [evt] 99 336 840@17 45 1472@1 2713 3928@41 TauCoreBuilderAlg
is, with the fix, back to
18:36:08 PMonSD [evt] 99 124 260@17 45 1472@1 2713 3928@41 TauCoreBuilderAlg
Cheers, Bertrand
Edited by Bertrand Martin Dit Latour