[Rivet] AGILe

[Andy Buckley]

On 07/06/10 17:11, Sparsh Navin wrote:
>> I think that GSL 1.10 is available for SLC5 platforms.
> 
> Found it. Thanks!
> 
>> Can you try doing this in place of (or after) all those explicit path
> settings:
> 
>> export
> PATH=/afs/cern.ch/sw/lcg/external/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig:$PATH
>> source /afs/cern.ch/sw/lcg/contrib/gcc/4.3/x86_64-slc5-gcc43-opt/setup.sh
> 
>> This is all that I do on a fresh SLC5 machine before running
>> rivet-bootstrap and it works fine. I suspect that the gcc 4.3 setup
>> script is setting the same sort of paths as you are doing by hand, but
>> it gets them self-consistent... I'm not sure what the mistake is in your
>> paths, but it looks like somehow 32 bit libraries are being tried for
>> linking on a 64 bit system.
> 
> The rivet-bootstrap script works but I still can't list the generators
> in agile.
> 
> [pcalicebhm09] /home/snavin/my_work/rivet_test >
> PATH=/afs/cern.ch/sw/lcg/extern
> al/swig/1.3.40/x86_64-slc5-gcc43-opt/bin/swig:$PATH
> [pcalicebhm09] /home/snavin/my_work/rivet_test > source
> /afs/cern.ch/sw/lcg/cont
> rib/gcc/4.3/x86_64-slc5-gcc43-opt/setup.sh
> [pcalicebhm09] /home/snavin/my_work/rivet_test > ./rivet-bootstrap
> --no-install-
> rivet --install-agile --dev-mode on
> Checking for developer mode programs
> Updating AGILe SVN working copy
> LCG area available: using LCG-built packages
> Using LCG platform tag = x86_64-slc5-gcc43-opt
> Boost's headers are not installed properly in
> /afs/cern.ch/sw/lcg/external/Boost/1.42.0_python2.5/x86_64-slc5-gcc43-opt
> Configuring in /home/snavin/my_work/rivet_test/build/agile: ./configure
> --prefix=/home/snavin/my_work/rivet_test/local 
> --with-lcgtag=x86_64-slc5-gcc43-opt
> --with-hepmc=/afs/cern.ch/sw/lcg/external/HepMC/2.05.00/x86_64-slc5-gcc43-opt
> --with-boost=/afs/cern.ch/sw/lcg/external/Boost/1.42.0_python2.5/x86_64-slc5-gcc43-opt
> --with-boost-incpath=/afs/cern.ch/sw/lcg/external/Boost/1.42.0_python2.5/x86_64-slc5-gcc43-opt/include/boost-1_42
> Building in /home/snavin/my_work/rivet_test/build/agile: make -j2 &&
> make -j2 install
> 
> All done. Now set some variables in your shell:
> 
> In sh shell:
> export PATH=/home/snavin/my_work/rivet_test/local/bin:$PATH
> export
> TEXMFHOME=/home/snavin/my_work/rivet_test/local/share/Rivet/texmf:$TEXMFHOME
> export
> HOMETEXMF=/home/snavin/my_work/rivet_test/local/share/Rivet/texmf:$HOMETEXMF
> export
> LD_LIBRARY_PATH=/home/snavin/my_work/rivet_test/local/lib:/afs/cern.ch/sw/lcg/external/HepMC/2.05.00/x86_64-slc5-gcc43-opt/lib:/afs/cern.ch/sw/lcg/external/fastjet/2.4.2/x86_64-slc5-gcc43-opt/lib:$LD_LIBRARY_PATH
> export
> PYTHONPATH=/home/snavin/my_work/rivet_test/local/lib/python2.6/site-packages:$PYTHONPATH
> . /home/snavin/my_work/rivet_test/local/share/Rivet/rivet-completion
> . /home/snavin/my_work/rivet_test/local/share/AGILe/agile-completion
> 
> In csh shell:
> setenv PATH /home/snavin/my_work/rivet_test/local/bin:$PATH
> setenv TEXMFHOME
> /home/snavin/my_work/rivet_test/local/share/Rivet/texmf:$TEXMFHOME
> setenv HOMETEXMF
> /home/snavin/my_work/rivet_test/local/share/Rivet/texmf:$HOMETEXMF
> setenv LD_LIBRARY_PATH
> /home/snavin/my_work/rivet_test/local/lib:/afs/cern.ch/sw/lcg/external/HepMC/2.05.00/x86_64-slc5-gcc43-opt/lib:/afs/cern.ch/sw/lcg/external/fastjet/2.4.2/x86_64-slc5-gcc43-opt/lib:$LD_LIBRARY_PATH
> setenv PYTHONPATH
> /home/snavin/my_work/rivet_test/local/lib/python2.6/site-packages:$PYTHONPATH
> 
> These can be used by sourcing, e.g.
> source rivetenv.sh
> or
> source rivetenv.csh
> [pcalicebhm09] /home/snavin/my_work/rivet_test > source rivetenv.sh
> [pcalicebhm09] /home/snavin/my_work/rivet_test > agile-runmc --list-gens
> AGILe.Loader: WARN  LHAPDF is not available

Ok, well we are getting somewhere. In your paths file, you were setting
AGILE_GEN_PATH... does the value that you're setting it to contain any
generator libraries? And if so, are they under paths that AGILe can
find? (i.e. more LCG platform tag problems?)

I suggest that you try "unset AGILE_GEN_PATH" and then "agile-runmc
--list-gens" again. This will now look for the Genser builds of
generators in the /afs/cern.ch/sw/lcg/external/MCGenerators directory.

If that works (fingers crossed!), then try to get your own generator
installations working by installing them with Genser's bootstrap script
or agile-genser-bootstrap (note that this latter has been recently
updated, so you may need to download it again. Running agile-runmc with
the "-lTRACE" flag will spit out a huge number of paths that are being
tried for generator library searches: you can use that for debugging
your local generator lib searches.

Andy

-- 
Dr Andy Buckley
SUPA Advanced Research Fellow
Particle Physics Experiment Group, University of Edinburgh

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