[Rivet] RE : installation problems (It works!)

[Mikhail Kirsanov]

 Hello,
 Do you set the size of HEPEVT by hands or use the Pythia parameter
from common blocks?
                               Mikhail


-------- Message d'origine--------
De: Andy Buckley [mailto:andy.buckley at durham.ac.uk]
Date: mar. 29/07/2008 17:21
À: jmonk at hep.ucl.ac.uk
Cc: Holger Schulz; genser-developers; rivet at projects.hepforge.org
Objet : Re: [Rivet] installation problems (It works!)
 
James Monk wrote:
> I just re-built AGILe against HepMC 2.03.08 and still see the seg  
> fault when running pythia.  The build of HepMC 2.03.08 has not changed  
> (been re-built etc) in the past few months, has it?

There's one way to tell:

abuckley at lxplus218:~$ llt -d LCGExternal/HepMC/2.03.*
drwxrwxrwx  8 root root 2.0K Jul 18 17:11 LCGExternal/HepMC/2.03.09
drwxrwxrwx  7 root root 2.0K Apr 29 01:50 LCGExternal/HepMC/2.03.08
drwxrwxrwx  8 root root 2.0K Mar 12 22:38 LCGExternal/HepMC/2.03.06
drwxrwxrwx  7 root root 2.0K Mar  5 13:40 LCGExternal/HepMC/2.03.05
drwxrwxrwx  8 root root 2.0K Feb  6 02:12 LCGExternal/HepMC/2.03.04

;)

So it's probably not a problem in HepMC - maybe a memory problem in the
Pythia/Herwig HEPEVT common blocks that makes HepMC fall over? Could
this be a problem with common block int sizes etc. again? That was dealt
 with a long time ago, but maybe we accidentally changed something...

Can you try using Rivet HEAD with AGILe 1.1.1, in the interest of
narrowing it down? I'll try the same.

Andy