[Rivet] Agile can't find generators

[Andy Buckley]

On 23/04/11 12:56, Gavin Hesketh wrote:
> Hi,
> I've just moved to the new agile 1.2.2 but it can't seem to find my
> locally installed generators.
> 
> I've installed alpge, pythia, herwig, and set AGILE_GEN_PATH, eg:
> 
>> ls $AGILE_GEN_PATH
> agile-genser-bootstrap* alpgen/  downloads/  herwig/  jimmy/  pythia6/
> 
> and:
> $AGILE_GEN_PATH/pythia6/425.2/x86_64-Linux-gcc44-opt
> 
> seems to contain all the right stuff. But:
> 
>> agile-runmc  -l TRACE
> 
> AGILe.Loader: TRACE  Trying to find libs for AlpGenHerwig:HEAD:HEAD
> AGILe.Loader: TRACE  Testing for
> /afs/cern.ch/sw/lcg/external/MCGenerators/herwig/HEAD.3/x86_64-Linux-gcc44-opt/lib/libherwig.so
> 
> AGILe.Loader: TRACE  Testing for
> /afs/cern.ch/sw/lcg/external/MCGenerators/herwig/HEAD.2/x86_64-Linux-gcc44-opt/lib/libherwig.so
> 
> AGILe.Loader: TRACE  Testing for
> /afs/cern.ch/sw/lcg/external/MCGenerators/herwig/HEAD/x86_64-Linux-gcc44-opt/lib/libherwig.so
> 
> AGILe.Loader: TRACE  Testing for
> /afs/cern.ch/sw/lcg/external/MCGenerators/herwig/HEAD.3/lib/libherwig.so
> AGILe.Loader: TRACE  Testing for
> /afs/cern.ch/sw/lcg/external/MCGenerators/herwig/HEAD.2/lib/libherwig.so
> AGILe.Loader: TRACE  Testing for
> /afs/cern.ch/sw/lcg/external/MCGenerators/herwig/HEAD/lib/libherwig.so
> AGILe.Loader: TRACE  Testing for
> /afs/cern.ch/sw/lcg/external/MCGenerators/lib/libherwig.so
> AGILe.Loader: TRACE  Testing for
> /afs/cern.ch/sw/lcg/external/MCGenerators/lib/libherwigHEAD.so
> AGILe.Loader: TRACE  Didn't find herwig:HEAD:libherwig
> 
> 
> (repeated for all other generators).
> 
> So it seems to only be looking for the cern afs area... Haven't looked
> too deeply into the code, but wondered if someone had an idea of the
> problem. With previous versions and installs I've had issues with
> LCG_TAG not be correctly set, but that does not seem to be the case here.

Agreed -- the LCG platform tag seems to be fine. I'm puzzled, because
it's working fine for me! Is your AGILE_GEN_PATH variable exported
properly as opposed to just defined?

If it is defined as far as the AGILe process is concerned, then it
shouldn't try using that Genser fallback at all, cf. the code for the
search path definition in src/Tools/AGILePaths.cc:

  const vector<string> getGenPaths() {
    vector<string> dirs;
    char* env = 0;
    env = getenv("AGILE_GEN_PATH");
    if (env) {
      // Use the AGILe generator path variable if set...
      dirs += split(env);
    } else {
      // ... fallback to Genser AFS path

Andy

PS. Looking into this I also noticed that I wasn't excluding the "." and
".." directory entries from the generator version search. So from
today's svn head version onwards there won't be so much cruft in the
trace output about looking for generator versions called e.g. "...3"!

-- 
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.