Update of the overlap removal and the anti-tau definition
The anti-tau decoration and the overlap removal in the anti-tau region in easyjet is not correctly implemented. In the current implementation, only the highest-pT candidate is decorated with an antiTau flag in cases when the number of taus that pass the tau-ID requirements is less than 1 (2) in the lephad (hadhad) channel.
This should be changed to decorate all taus satisfying the anti-ID requirement with the corresponding flag. Then, anti-tau objects would go through the first part of the overlap removal (all overlaps are removed except between anti-taus and non-b-jets). After that, the correct number of anti-taus should be selected (based on trigger matching and random selection where we don't trigger on taus). After the anti-tau selection, the last part of the overlap removal, between anti-taus and light jets should be performed in favor of anti-taus. Additionally, overlap removal priority for taus and b-jets should be studied with GN2, but that can be defined as a separate task.
We should not forget that all the studies should be performed in both the hadhad and lephad channels. Anti-taus are defined with a lower cut on the RNN score of 0.01, but this should be studied as well.