|
[Rivet] More Rivet problemsDominic Hirschbuehl dhirsch at mail.cern.chMon Sep 8 08:12:30 BST 2014
Hi Andy, thanks a lot. > > sorry for bothering you again. > > Unfortuntly our "private" top routines are still for Rivet 1.X and > > therefore I wanted to compile and run them within Athena. > > However either I am too stupid or something is screwed up. > > I am running on a CentOS 6.5 machine using Athena 17.2.12.5 > > > > As soon as I try to build our routines, I get the attached error > > message. I tried with different option like -m32 or setting > > asetup 17.2.12.5,here,slc5 > > > > Nothing helped. > > I had a look at the message. Very strange -- you have the same version > of gcc as in 17.2.X.Y but getline() seems not to exist. That's very odd: > I wonder if SLC5 has a slightly modified version of gcc relative to > CentOS (or vice versa)? This is now also my impression. I had also an exchange with Roman Lysak and we found event more inconsistencies. I'll try to get something run on a SLC machine. > > > During my investigation I found also the following: > > [hirsch at electron routines]$ rivet --version > > rivet v1.8.3 > > > > [hirsch at electron routines]$ rivet-config --prefix > > /afs/.cern.ch/sw/lcg/external/MCGenerators_lcgcmt61f/rivet/1.9.0/i686-slc5-gcc43-opt > > > > [hirsch at electron routines]$ rivet-config --version > > 1.9.0 > > > > Is this intended, that rivet-config has a different version number, than rivet itself? > > I don't see that on my local lxplus build: > > $ asetup r6,17.2.X.Y,32,slc5,here > $ rivet --version > rivet v1.9.0 > $ rivet-config --version > 1.9.0 > > but without the "here" and local packages, the rivet command doesn't > work properly. I'll look into that, but for now maybe try checking out > External/Rivet and Generators/Rivet_i. > > Generally, though, it would be much better to get those routines updated > to Rivet 2. It should be more or less just a matter of replacing > > bookHistogram1D -> bookHisto1D > AIDA::IHistogram1D* -> Histo1DPtr > AIDA::IProfile1D* -> Profile1DPtr > > and then you can use the nice new features in v2 as well. I see there > was some attempt to start a v1 -> v2 migration, but none have been > converted so far. I completely agree and to be honest I am really disappointed that everytime we do these kick-off or organisation meetings half a dozen people show up and tell that they work on it and afterwards they disappear. > I/we can help if manpower can be found... is there any > OTP available for this work? Or maybe it could be a final project for > Thomas Balestri's qualification, which ends this month. I also think it > would be good to make a general ATLAS physics validation routine archive > rather than keeping it internal to the top group, which is in line with > Thomas' work. Agreed. I would suggest, that we migrate all our routines to Rivet2, check that they are useful and complete and then give them to Christian for central validation. Thanks Dominic -- /---------------------------------------------------------------------\ | Dr. Dominic Hirschbuehl | \ Bergische Universitaet Wuppertal - Exp. Elementarteilchenphysik / / hirsch at physik.uni-wuppertal.de / dominic.hirschbuehl at cern.ch \ | office : D.09.22 phone : 0049 - 202 - 439 - 3751 | \---------------------------------------------------------------------/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 230 bytes Desc: not available URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20140908/a6fb0e50/attachment.pgp>
More information about the Rivet mailing list |