[Rivet] Rivet in athena

[Andy Buckley]

Hi Ulla,

I'm not sure about a CVMFS path, but 1.8.3 is installed in the
MCGenerators_lcgcmt* directories: the MCGenerators_hepmc* ones have not
been updated for some time, I think, since we moved to using Genser
trees based on fixed external lib versions for the full LCGCMT suite
(e.g. things like FastJet) rather than just for HepMC.

Andy


On 03/11/13 21:21, Ulla Blumenschein wrote:
> Dear all,
> 
> Since we are discussng setups:
> What is the correct cvmfs path for a reasonably recent and stable
> Rivet version?
> On SLC5, I have so far been using 1.8.2 from afs:
> /afs/cern.ch/sw/lcg/external/MCGenerators_hepmc2.06.05/rivet/1.8.2/
> 
> Cheers, Ulla
> 
> 
> 
> 
> On Sun, Nov 3, 2013 at 11:34 AM, Andy Buckley <andy.buckley at cern.ch> wrote:
>> Hi Liron,
>>
>> For some reason you are setting up an Athena Rivet environment *and* a
>> standalone one. My guess is that they are not compatible and ROOT is the
>> first thing to fall over. You are also mixing HepMC / LCGCMT versions in
>> the versions of Rivet and AGILe that you are sourcing -- that will cause
>> problems, too.
>>
>> If you want to run Rivet in Athena, just run asetup: nothing else is
>> needed. You shouldn't need to explicitly set the --cmtconfig flag
>> either, unless you are running on SLC6 but really want to run an SLC5
>> ATLAS build (why?)
>>
>> If you want to run the Rivet standalone scripts, i.e. without Athena
>> involved, then your setup script is probably ok, except for the AGILe
>> part which introduces a clashing version of HepMC. The MCGenerators_XXXX
>> dir in the paths should contain the same XXXX in all cases otherwise you
>> will pick up inconsistent library copies and who knows what will happen.
>>
>> A problem with Rivet in Athena is that we've not yet managed to get the
>> scripts (rivet, rivet-mkanalysis, rivet-buildplugin, rivet-mkhtml, ...)
>> into the Athena PATH in a fully consistent way. If you use recent
>> nightlies you will be able to run some of them on lxplus: rivet,
>> rivet-mkanalysis, and rivet-buildplugin should all work. But the
>> plotting scripts don't yet work from Athena -- because the Python
>> packages aren't installed into the Athena install area: Thomas Balestri
>> is working on solving that at the moment -- so to plot your output files
>> you will need to open a separate terminal with the standalone setup.
>>
>> Hope that helps,
>> Andy
>>
>>
>> On 03/11/13 00:00, Liron Barak wrote:
>>> Dear Experts,
>>>
>>> I'm not sure what is the right mailing list, so I've tried both...
>>> Starting from Thursday night, I have problems running rivet in athena, I do:
>>> asetup --cmtconfig=x86_64-slc5-gcc43-opt 17.2.11.9,here OR asetup
>>> --cmtconfig=x86_64-slc5-gcc43-opt 17.2.11.12,here (tried with both options)
>>> cd /tmp/ChargedPOWHEG1/
>>> source setupRivet.sh
>>> athena JO_rivet_mine.py
>>>
>>>
>>> I get:
>>> Traceback (most recent call last):
>>>   File
>>> "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc5-gcc43-opt/17.2.11/AtlasProduction/17.2.11.9/InstallArea/jobOptions/AthenaCommon/Preparation.py
>>> <http://atlas.cern.ch/repo/sw/software/x86_64-slc5-gcc43-opt/17.2.11/AtlasProduction/17.2.11.9/InstallArea/jobOptions/AthenaCommon/Preparation.py>",
>>> line 86, in <module>
>>>     import PyCintex
>>>   File
>>> "/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc5-gcc43-opt/17.2.11/sw/lcg/app/releases/ROOT/5.30.05/x86_64-slc5-gcc43-opt/root/lib/PyCintex.py
>>> <http://atlas.cern.ch/repo/sw/software/x86_64-slc5-gcc43-opt/17.2.11/sw/lcg/app/releases/ROOT/5.30.05/x86_64-slc5-gcc43-opt/root/lib/PyCintex.py>",
>>> line 21, in <module>
>>>     import libPyROOT
>>> ImportError:
>>> /cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc5-gcc43-opt/17.2.11/sw/lcg/app/releases/ROOT/5.30.05/x86_64-slc5-gcc43-opt/root/lib/libPyROOT.so
>>> <http://atlas.cern.ch/repo/sw/software/x86_64-slc5-gcc43-opt/17.2.11/sw/lcg/app/releases/ROOT/5.30.05/x86_64-slc5-gcc43-opt/root/lib/libPyROOT.so>:
>>> undefined symbol: _ZN7TObject11ShowMembersER16TMemberInspector, ROOT
>>> version or setup problem?
>>>
>>> It worked last Monday....
>>> The setupRivet.sh is;
>>> test -n "$LCGTAG" || LCGTAG=x86_64-slc5-gcc43-opt
>>>
>>> export PATH=/afs/cern.ch/sw/lcg/external/Python/2.6.5/$LCGTAG/bin:$PATH
>>> <http://cern.ch/sw/lcg/external/Python/2.6.5/$LCGTAG/bin:$PATH>
>>> export
>>> LD_LIBRARY_PATH=/afs/cern.ch/sw/lcg/external/Python/2.6.5/$LCGTAG/lib:$LD_LIBRARY_PATH
>>> <http://cern.ch/sw/lcg/external/Python/2.6.5/$LCGTAG/lib:$LD_LIBRARY_PATH>
>>> export PATH=/afs/cern.ch/sw/lcg/external/swig/1.3.40/$LCGTAG/bin:$PATH
>>> <http://cern.ch/sw/lcg/external/swig/1.3.40/$LCGTAG/bin:$PATH>
>>> source /afs/cern.ch/sw/lcg/contrib/gcc/4.3/$LCGTAG/setup.sh
>>> <http://cern.ch/sw/lcg/contrib/gcc/4.3/$LCGTAG/setup.sh>
>>> source
>>> /afs/cern.ch/sw/lcg/external/MCGenerators/professor/1.3.1/$LCGTAG/setup.sh
>>> <http://cern.ch/sw/lcg/external/MCGenerators/professor/1.3.1/$LCGTAG/setup.sh>
>>> source
>>> /afs/cern.ch/sw/lcg/external/MCGenerators_lcgcmt64/rivet/1.8.1/$LCGTAG/rivetenv.sh
>>> <http://cern.ch/sw/lcg/external/MCGenerators_lcgcmt64/rivet/1.8.1/$LCGTAG/rivetenv.sh>
>>> source
>>> /afs/cern.ch/sw/lcg/external/MCGenerators_hepmc2.06.05/agile/1.4.0/$LCGTAG/agileenv.sh
>>> <http://cern.ch/sw/lcg/external/MCGenerators_hepmc2.06.05/agile/1.4.0/$LCGTAG/agileenv.sh>
>>>
>>> export LATEXINPUTS=$LATEXINPUTS:$TEXMFHOME//
>>> export TEXINPUTS=$TEXINPUTS:$TEXMFHOME//
>>>
>>> export RIVET_ANALYSIS_PATH=$PWD:$RIVET_ANALYSIS_PATH
>>> mkfifo /tmp/$USER/hepmc.fifo%
>>>
>>>
>>> Any idea?
>>>
>>> Thanks a lot
>>> Liron
>>
>>
>> --
>> Dr Andy Buckley, Royal Society University Research Fellow
>> Particle Physics Expt Group, University of Glasgow / PH Dept, CERN
> 
> 
> 


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