[Rivet] Work for Rivet 2.4.0 release: call for contributions!

[Andy Buckley]

Hi Xavier,

We're trying to work out what had happened to to that one. In fact I 
don't see it in our contrib area *or* in my email inbox, so maybe it 
just didn't come into our queue as planned. Could you send us the 
tarball again, just in case there was some submission problem?


I have another issue with a CMS submitted analysis -- I just started 
doing the work to integrate the CMS_2014_I1305624 analysis, only to find 
that it depends on a secondary source file of event shape calculations 
based on CLHEP types. We can't accept that into the Rivet repository 
because it would add CLHEP as an unacceptable extra dependency. Even 
without the CLHEP issue it would be strongly preferable to use the 
existing event shape routines (and vector dot products!) in Rivet, since 
we will have to maintain this code ~forever.

Can you please get someone to migrate the event shape logic in this 
analysis from the EventShape_rivet.* files into the analysis .cc file as 
private methods, replacing the CLHEP and hand-made dot product etc. with 
the Rivet 4-vectors? This should just be a technical transformation -- 
ideally the existing projections would also be used in place of this, 
but I appreciate that would be more work.

Thanks,
Andy



On 11/09/15 12:27, Xavier Janssen wrote:
> Hi Andy,
>
> Wrt the list of analysis of new CMS plugins you are quoting, I’d like to understand what happened with CMS_2013_I1122847
> that was submitted (by Lars/Albert before I took over from them) in February and was not included in 2.3.0.
>
> Cheers, Xavier.
>
>> On 10 Sep 2015, at 18:19, Andy Buckley <andy.buckley at cern.ch> wrote:
>>
>> Hey everyone,
>>
>> A reminder that we agreed to increase the Rivet release frequency, and that the next analysis update release should happen before the end of this month.
>>
>> If we hadn't done any other development in the last couple of months, that release would be 2.3.1, but we have actually changed enough (in a stable and complete way) to justify version 2.4.0.
>>
>> Unless there are pressing bugfixes or developments that I'm not aware of, all that remains to be done before validation is to hook up the 8 new analysis codes in the contrib directory:
>>
>> ATLAS_2014_I1326641.tar.gz
>> ATLAS_2014_I1327229.tar.gz
>> ATLAS_2015_I1387176.tar.gz
>> CMS_2014_I1305624.tgz
>> CMS_2015_I1310737.new.tgz
>> CMS_2015_I1310737.orig.tgz
>> CMS_2015_I1327224.tgz
>> CMS_2015_I1346843.tgz
>> D0_2000_I503361.tar.gz
>> (note that two of these are "new" and "orig" versions of the same analysis)
>>
>> We also said that we would distribute the work, to make new analysis releases unintimidating for developers... so, who wants to integrate which analysis codes? ;-) Add the new analyses on the release-2-3-x branch, and I will sync them into default before we make the release (cf. earlier discussions about what sorts of changes go on which branches.)
>>
>> Volunteers please... thanks in advance.
>>
>> Andy
>>
>> PS. Holger/David, the contrib dir needs some umask or similar permissions set so that the tarballs are group-writeable. Several of these new ones aren't, so intervention from root will needed to move them to the pre2.4.0 dir when we make it. Also, the email notifications about new tarballs seem to be broken (right?)
>>
>> --
>> Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
>> Particle Physics Expt Group, University of Glasgow
>> _______________________________________________
>> Rivet mailing list
>> Rivet at projects.hepforge.org
>> https://www.hepforge.org/lists/listinfo/rivet
>


-- 
Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
Particle Physics Expt Group, University of Glasgow