|
[Rivet] [Rivet-svn] r1225 - in 2008-10-jetplugins: include/Rivet/Analyses include/Rivet/Projections src/Analyses src/ProjectionsAndy Buckley andy.buckley at durham.ac.ukWed Dec 17 17:39:33 GMT 2008
Lars Sonnenschein wrote: > On Wed, 17 Dec 2008, Andy Buckley wrote: >> So, can you move the TrackJet plugin back into Rivet. Maybe in a >> separate directory from the main Rivet stuff (e.g. "fastjet" at the same >> level as "src", "include", "etc.") to keep the separation clear. We can >> then do something like this in FastJets.hh: > > I can move the TrackJet plugin back into Rivet. > We are not the only users, interested in having the "right" trackjet > algorithm. So if it comes with FastJet anyway, why do we want to have it > inside Rivet? Maybe I have misunderstood again: I wasn't aware that TrackJet was going to be in FastJet. If FastJet has an implementation of their own (which I'd be surprised about, since it's a one-off algorithm, and not IR/C-safe) then obviously we'd rather use that. If that's the case, then we can stop worrying and just implement another enum value in FastJets.hh, as it appears is the case for the D0ILCone. Otherwise, the easiest way to make sure that TrackJet is available in Rivet is to build it *in Rivet* as a FastJet plugin. I'm not aware of anyone else dying to have a TrackJet plugin since the only sensible application of it (other than throwing it away) is to reproduce the Field-Stuart CDF UE analysis. Since we wrote the code, I don't think there's any compelling need for us to make the algorithm available as a separate package! Andy -- Dr Andy Buckley Institute for Particle Physics Phenomenology Durham University 0191 3343798 | 0191 3732613 | www.insectnation.org
More information about the Rivet mailing list |