[Rivet] WFinder on VetoedFinalState

[Frank Siegert]

Hi Ulrike,

On 07/09/11 17:12, Ulrike Schnoor wrote:
> trying to upgrade a private rivet analysis to RIVET 1.6.0, I stumbled
> accross the following change with respect to the previous version:
> It used to be possible to define a WFinder with a vetoed final state
> as input with a constructor like this:
> WFinder::WFinder(const FinalState&  fs,
>                     PdgId pid,
>                     double m2_min, double m2_max,
>                     double dRmax)

If I'm not mistaken, then this was a "ChargedFinalState fs_l", as input 
representing the charged lepton, wasn't it? Everything else (i.e. in 
particular the neutrino) was still taken from the global final state. So 
I'm not sure that this should have worked even back then for the case 
that you describe below.

> Am I missing something, or why is this function not available in RIVET
> 1.6.0? What can I do as an alternative? I need to find two Ws which
> can both decay into leptons of the same flavor, so when one W is
> reconstructed, I have to somehow veto it for the next WFinder.

I'm attaching an untested patch (for Rivet trunk, but should also apply 
to Rivet 1.6.0 I think -- otherwise let me know), which allows to 
specify the input FS as extra argument in the WFinder constructors. It 
would be great if you could try out whether this works and does what you 
need, then it could be added for the next version of Rivet.

Cheers,
Frank
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wfinder.patch
Type: text/x-diff
Size: 3856 bytes
Desc: not available
URL: <http://www.hepforge.org/lists-archive/rivet/attachments/20110915/8de9a774/attachment.patch>