[Rivet] WFinder does not keep charged particle cuts

Daniel Weyh weyh at physik.hu-berlin.de
Thu May 26 21:16:13 BST 2011


Hi all,

I'd guess it's in these lines
----WFinder.cc-------L103-----------
    // FS for non-signal bits of the event
    VetoedFinalState remainingFS;
    remainingFS.addVetoOnThisFinalState(signalFS);
    addProjection(remainingFS, "RFS");
--------------------------------------------
By now I don't know pretty much about when projections are evaluated.
But given as far is I (think I have) seen, these lines do a veto on the global event.
For maintaining cuts made earlier, second line would maybe have to be changed to
--------------------------------------------
    VetoedFinalState remainingFS(fs_l);
--------------------------------------------
where fs_l is the input final state.

But here again the question about inteded behaviour...

Cheers,
Daniel

PS @ Holger: In our MC_EVENTSHAPES I think I solved the problem by using some veto-juggling... (therefore no recompilation of rivet/Sherpa is needed). 
Look into the git repo (git pull) ;-)

Am 26.05.2011 um 18:03 schrieb Holger Schulz:

> Hi guys,
> 
> we realised that when constructing a WFinder with a ChargedFinalState
> as first argument in the constructor, the pT cuts for instance as applied
> on the ChargedFinalState are ignored when asking for the WFinder's
> remainingFinalState.
> 
> Is this the intended behaviour?
> 
> Cheers,
> Holger
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> http://www.hepforge.org/lists/listinfo/rivet



More information about the Rivet mailing list