<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [Rivet] AGILe</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>> Ok, well we are getting somewhere. In your paths file, you were setting<BR>
> AGILE_GEN_PATH... does the value that you're setting it to contain any<BR>
> generator libraries? And if so, are they under paths that AGILe can<BR>
> find? (i.e. more LCG platform tag problems?)<BR>
<BR>
I had AGILE_GEN_PATH=/home/snavin/my_work/genser<BR>
[pcalicebhm09] /home/snavin/my_work/rivet_test > ls /home/snavin/my_work/genser/<BR>
agile-genser-bootstrap downloads pythia6<BR>
<BR>
> I suggest that you try "unset AGILE_GEN_PATH" and then "agile-runmc<BR>
> --list-gens" again. This will now look for the Genser builds of<BR>
> generators in the /afs/cern.ch/sw/lcg/external/MCGenerators directory.<BR>
<BR>
> If that works (fingers crossed!), then try to get your own generator<BR>
> installations working by installing them with Genser's bootstrap script<BR>
> or agile-genser-bootstrap (note that this latter has been recently<BR>
> updated, so you may need to download it again. Running agile-runmc with<BR>
> the "-lTRACE" flag will spit out a huge number of paths that are being<BR>
> tried for generator library searches: you can use that for debugging<BR>
> your local generator lib searches.<BR>
<BR>
This works! I can see a list of Herwig, Charybdis, AlpGen and Pythia and generate events using<BR>
agile-runmc Pythia6:420 --beams pp:900GeV -o output.hepmc<BR>
<BR>
It generates 10 events. Not sure where this number (and other parameters) is set though.<BR>
I will work with PYTHIA 6 for now and then attempt to install PHOJET.<BR>
<BR>
Thanks for your help.<BR>
<BR>
Sparsh<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>