[Rivet] Build of beta version

[Andy Buckley]

Hi Sara,

You're right... we overlooked this. Probably we should update our YAML
reader to use the 0.5 version of the interface, but that involves work!

I'll see if I can add some sort of check to the Rivet2 configure script
to write out a helpful warning. One reason that it's missing right now
is that we anticipated most users taking a look via the pre-installed
version at /afs/cern.ch/sw/lcg/experimental/rivet ... which contains a
simple build script that explicitly downloads yaml-cpp 0.3 ;-) So I
think you're probably the first non-author to have built it from scratch
so far!

This feedback is very helpful, thanks. We'd be particularly interested
to hear your thoughts on the YODA histos and other changes, and anything
else we can do to improve the API: a jets overhaul is next! Please be
aware that we don't have "automatic" scripts to do YODA run-merging yet,
but all the necessary data is in the files and hopefully the Python
interface to YODA will make the merging quite straightforward, even if
you want to weight the different runs... let us know if you hit any
problems and we'll try to help. Thanks again for getting in touch :-)

Andy


On 19/04/13 15:02, Sara Alderweireldt wrote:
> Hi,
> 
> I've been using Rivet from time to time for a long time now, compiled
> many different versions on many different systems, and am quite happy to
> see the new beta available. I'm curious what the YODA histogramming will
> bring...
> 
> I don't know whether there's a proper location for this, hence this
> e-mail, but I thought I'd share my build issues. Just one actually,
> though it took me half a day to realise what the problem was.
> 
> The yaml-cpp tool has two different branches, with a different API
> (0.3.0and 0.5.1 currently, if I'm up to date). I was getting tons and
> tons of YAML error trying to compile Rivet, after the configure told me
> it was happy with the yaml-cpp lib and header it found. Turns out I had
> the 0.5.1 yaml-version installed, while Rivet requires old API. I
> switched versions and Rivet compiled like a charm.
> 
> Would it maybe be an option to add a check to the configure script that
> warns the user that the yaml-cpp version is relevant? As in Boost > 1.40
> required but then yaml-cpp < 0.5 required? Or some page/document to go
> with the beta version that lists things like this?
> Or is this information already available somewhere and I overlooked it?
> 
> 
> Best regards,
> Sara
> 
> 
> 
> -- 
> 
> Sara Alderweireldt        sara.alderweireldt at cern.ch
> <mailto:sara.alderweireldt at cern.ch>
> Universiteit Antwerpen    Phone: +32 (0)3 265 3577
> CGB.U.237 - Physics       Skype: sara.alderweireldt
> Groenenborgerlaan 171
> 2020 Antwerpen            http://www.ua.ac.be/edf
> Belgium
> 
> 
> 
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> http://www.hepforge.org/lists/listinfo/rivet
> 


-- 
Dr Andy Buckley, Royal Society University Research Fellow
Particle Physics Expt Group, University of Edinburgh

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.