[Rivet] [Rivet-svn] r1225 - in 2008-10-jetplugins: include/Rivet/Analyses include/Rivet/Projections src/Analyses src/Projections

[Lars Sonnenschein]

Hello Andy

On Wed, 17 Dec 2008, Andy Buckley wrote:

> Lars Sonnenschein wrote:
> > On Wed, 17 Dec 2008, Andy Buckley wrote:
> >> Lars Sonnenschein wrote:
> 
> >>> I assume that such an equivalent switch will be added for the TrackJet
> >>> plugin inside FastJet. Right now for the Rivet Plugin branch the code has 
> >>> to be compiled together with the FastJet plugin libraries
> >>> (Rivet external!) and behaves like the D0 cone plugin inside FastJet
> >> The behaviour sounds good. Can you explain the compilation in a little
> >> more detail? Does the TrackJet code still live in Rivet, but has to be
> >> compiled against the FastJet headers? That's what I was expecting...
> > 
> > Sorry for being imprecise:
> > I deleted already any D0 Cone + TrackJet code inside the Rivet plugin 
> > branch.
> > The TrackJet code is completely outside Rivet (as supposed to).
> > It has been compiled with the FastJet package.
> >>From the Rivet point of view it is coherent in parallel to the other 
> > jet algorithms used from FastJet within Rivet.
> 
> The D0 ILCone alg is obviously an easy one since it's built in to the
> next FastJet. I think one of Jade/Durham is also going to be native to
> FastJet. But the other one (Durham/Jade) and TrackJet need to be
> supplied as plugins by us.
> 
> At the moment we provide Jade/Durham via Hendrik's FastJet patch, but
> almost no-one uses that. Better would be that we use the extended plugin
> API in FastJet 2.4.0 (?) to provide our extra plugins *inside* Rivet.
> That way they will definitely be there, with no patching required.
> 
> 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?


> 
> #include "Rivet/fastjet/TrackJetPlugin.hh"
> ...
> _plugin.reset(new fastjet::TrackJetPlugin());
> 
> Once that is working, we can incorporate Hendrik's Jade or Durham plugin
> (as required) in the same way.
> 
> By the way, note that there was a bug fix to TrackJet in the trunk: the
> sorting order was reversed. That, and any other changes, will need to be
> merged in.

Does that mean that the first jet in the list is now the lowest pT jet?
This is the way the jets are coming from the FastJet plugin,
but I use the reversed order, highest pT jet first to match the same 
ordering with the rivet trackjet projection, based on revision 1065.

	Lars
 
______________________________________
Lars Sonnenschein    
______________________________________
Home Institution:
III. Physikalisches Institut A, 26A204
Physikzentrum RWTH Aachen
52056 Aachen
Germany
--------------------------------------
______________________________________
CERN:
PH 32/2C-07
CH-1211 Geneve 23
Switzerland
Tel.:+41(22)767-9875
--------------------------------------
______________________________________
FNAL:
D0, PK151
Mailstop #352
Fermilab, P.O.Box 500
Batavia, IL 60510-500
USA
Tel.: +1(630)840-8740
______________________________________