[Rivet] jetsBySomething

[Frank Siegert]

Hi Hendrik,

On 07/11/11 11:23, Hendrik Hoeth wrote:
> the jetsBySomething() functions return a list of jets sorted by, well,
> Something. So far, so good. It is also possible to pass a pT cut (!!!)
> to those functions, which e.g. in case of jetsByEt() is a bit
> counter-intuitive. The following analyses use jetsByEt() with a cut, and
> looking at the corresponding publications it is clear that they *all*
> want to cut on Et rather than pT:
>
>   D0_1996_S3214044
>   CDF_1998_S3618439
>   CDF_2001_S4517016
>   CDF_2001_S4563131
>   CDF_2008_S7541902
>
> In addition to that, the cuts in the publication for CDF_2001_S4517016
> seem to be meant for raw jets, so I'm not sure this analysis is correct
> at all. Frank, you've read the paper in detail -- am I wrong here?

Hmmm, as far as I understood it, they mention the cuts at detector level 
and then talk about correcting for detector effects without stating any 
other cuts, so I assumed that these were also the particle level cuts. 
But as always with these old Tevatron papers, I find it difficult to 
tell what was really done.

> The other four analyses seem to be okay once we fix the
> jetsBySomething() behaviour. Since this is on the TODO list for 2.0
> anyhow, I don't want to mess with it now. But I wonder whether we should
> set them to UNVALIDATED in the meantime.

Fine with me.
Only CDF_1998_S3618439, CDF_2001_S4517016 and CDF_2001_S4563131 are 
affected by the way (the others are still UNVALIDATED).

Best,
Frank