|
[Rivet] Rivet in ATLAS: loading dllJames Monk jmonk at hep.ucl.ac.ukThu Jul 21 15:41:15 BST 2011
Hi Alan, When running inside Athena I always had trouble with it deciphering the RIVET_ANALYSIS_PATH env variable (I don't know if Athena sets up a new environment or what...). In any case, there is an option for Rivet_i such that you can add to your job options rivet.AnalysisPath=/home/barra/susy/multijets/w which should cause Rivet_i to search there rather than try and use the (possibly not set by Athena) RIVET_ANALYSIS_PATH. Let me know if that works... (if it doesn't there is also a rivet.OutputLevel=VERBOSE option, which should tell you where it thinks it is looking for libs) cheers, James On 21 Jul 2011, at 15:20, Alan Barr wrote: > To Rivet experts on ATLAS. > > I’m trying to run my first home-made rivet routine through Athena. Mostly it’s been going very smoothly – congratulations on making such a clear package. Unfortunatly I’ve failed to convince it to pick up my own Analysis, and help would be appreciated/ > > I’ve been following the instructions on: > https://projects.hepforge.org/rivet/rivet-tutorial-140.pdf > And those on RivetForAtlas, I have a setup which can run my own EVGEN file through the standard analyses to create an aida file with projections and then make some visualisations. > > My setup is: > > [barra at pplxint5]data/w100-fives-6% which rivet > /afs/cern.ch/sw/lcg/external/MCGenerators/rivet/1.5.0/i686-slc5-gcc43-opt/bin/rivet > [barra at pplxint5]data/w100-fives-6% which athena.py > /afs/cern.ch/atlas/software/releases/16.6.7/AtlasCore/16.6.7/InstallArea/share/bin/athena.py > Target: x86_64-unknown-linux-gnu > Configured with: /build/LCG/work/gcc-4.3.2/configure --prefix=/afs/.cern.ch/sw/lcg/contrib/gcc/4.3.2/x86_64-slc5-gcc34-opt --with-mpfr=/afs/.cern.ch/sw/lcg/external/mpfr/2.3.1/x86_64-slc5-gcc34-opt --with-gmp=/afs/.cern.ch/sw/lcg/external/gmp/4.2.2/x86_64-slc5-gcc34-opt --enable-languages=c,c++,fortran > Thread model: posix > gcc version 4.3.2 (GCC) > > athena myrivet.py > > which has inside it a reference to my own analysis. > > rivet = Rivet_i() > rivet.Analyses += [ 'AJB_WJETS' ] > > I built the analysis using the commands: rivet-mkanalysis and rivet-buildplugin and came up with analysis files > > AJB_WJETS.plot > AJB_WJETS.lo > AJB_WJETS.info > AJB_WJETS.cc > RivetAJBTest.so > > I now set the RIVET_ANALYSIS_PATH to the directory containing the files above > [barra at pplxint5]data/w100-fives-6% echo $RIVET_ANALYSIS_PATH > /home/barra/susy/multijets/w > > Change into another directory: > /home/barra/susy/multijets/w/data/w100-fives-6 > > I now run the program, but it seemingly fails to load the “.so” file: > > athena rivet.w100-fives-6.py > > Rivet.AnalysisLoader: WARN Ignoring duplicate plugin analysis called 'MC_JETS' > Rivet.AnalysisLoader: WARN Ignoring duplicate plugin analysis called 'MC_GENERIC' > Rivet.AnalysisLoader: WARN Ignoring duplicate plugin analysis called 'EXAMPLE' > Rivet.Analysis.Handler: WARN Analysis 'AJB_WJETS' not found. > ------------------------------------------------------------------------------------- > Core dump from CoreDumpSvc on pplxint5.physics.ox.ac.uk at Thu Jul 21 14:52:00 2011 > > Do I need to ask Athena to dynamically load the .so in a different way to standard rivet? > > [sorry if this is a dumb question] > _______________________________________________ > Rivet mailing list > Rivet at projects.hepforge.org > http://www.hepforge.org/lists/listinfo/rivet
More information about the Rivet mailing list |