[Rivet] Bug/change in RIVET IdentifiedFinalState()?

[David Grellscheid]

Hi Marco,

can you please send a minimal analysis and a short HepMC file that shows
the problem? Also, which Rivet version are you using?

Thanks,

  David


On 08/07/15 09:27, Marco Delmastro wrote:
> Hello,
> 
> Andy Buckley suggested that I report this bug (?) I encountered when using Rivet within the ATLAS Athena framework.
> 
> I'm writing the RIVET routines for the ATLAS 8 TeV inclusive diphoton and diphoton + jet analyses. In the first tests I made, running on a Pythia diphoton samples, I noticed something strange: only photons with eta > 1 were used, and the initial pT selection was not applied. I tracked down the problem to this method:
> 
> IdentifiedFinalState photonfs(Cuts::abseta < 2.37 && Cuts::pT > 30.*GeV); // 30 GeV cut on subleading photon
> 
> Apparently the 30 GeV cut on the photon pT is not applied, and or some reason only objects with eta > 1 are kept. From some conversation on the ATLAS MC Generator mailing list, it seems that the problem might be related to the handling of the && operator. If I change the line to:
> 
> IdentifiedFinalState photonfs(-2.37,2.37,30.*GeV); // etamin, etamax, ptmin
> 
> everything seems to work fine. I'm using rivet 2.2.0 from Athena 19.2.1:
> 
> [mdelmast at lxplus0157 Rivet]# which rivet
> /cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.1/AtlasSimulation/19.2.1/InstallArea/share/bin/rivet
> 
> [mdelmast at lxplus0157 Rivet]# rivet
> Rivet 2.2.0 running on machine lxplus0157.cern.ch (x86_64)
> 
> Thanks for your help!
> 
> Ciao, M.
> 
> 
> 
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> https://www.hepforge.org/lists/listinfo/rivet
>