[Rivet] Herwig problem

[Adam Davison]

Yeah I browsed the source and it was kind of a if (impossible) { throw } 
type error so I agree it's probably some kind of subtle memory 
corruption problem.

This was without JIMMY, so I'm not sure if that applies or not. It was 
Herwig 6.510.2 from the Genser archive but with some modifications to 
the makefile. I had quite a few problems getting fortran things to 
compile 64-bit on osx...

In the end I used the atlas software to get my cross-sections instead.

Adam

On 06/07/2010 12:44, Jonathan Butterworth wrote:
> This error is coming about because of HWHGB1 being called with an 
> illegal argument.
>
> To me, this has the smell of the old fortran common block mismatch.
>
> Are you running with JIMMY? Are you sure that the HEPEVT common block 
> and others are the same length in all the places you use it?
>
> (i.e. which versions of herwig and jimmy do you compile/link against?)
>
> Worth following up since it might affect other processes you run.
>
> Cheers,
> Jon
>
>
>
> Adam Davison wrote:
>> Hi Andy,
>>
>> Just to follow up on this, in Herwig_i if use the standard herwig job 
>> options and just set IPROC to 2800 it runs fine. But of course 
>> there's all sorts of ATLAS stuff going on there so I have no idea 
>> what that tells you :)
>>
>> Either way I got my cross-sections now.
>>
>> Thanks,
>>
>> Adam
>>
>> On 22/06/2010 18:05, Andy Buckley wrote:
>>> On 22/06/10 15:17, Adam Davison wrote:
>>>> Hi,
>>>>
>>>> I'm having a (probably unrelated) Herwig problem. Whenever I choose a
>>>> diboson process, 2800, 2810 etc... then I get a crash:
>>>>
>>>>             NUMBER OF SHOTS    =       10000
>>>>
>>>>    HWWARN CALLED FROM SUBPROGRAM HWHGB1: CODE = 501
>>>>    RUN CANNOT CONTINUE
>>>>
>>>> All I'm running here is:
>>>>
>>>> agile-runmc -p IPROC=2800 Herwig:6.510
>>>>
>>>> I also tried this in an old setup of rivet on a 32-bit slc4 machine at
>>>> UCL and got exactly the same error, which makes me think this isn't a
>>>> problem with my toolchain or architecture any more.
>>>>
>>>> Are there any known issues with rivet here?
>>> You mean AGILe rather than Rivet, I guess... there is nothing do with
>>> Rivet going on in that command.
>>>
>>> I've not been aware of that problem so far, but I've reproduced it on
>>> lxplus5 with a fresh AGILe 1.1.6 installation, so it's certainly
>>> genuine. I don't know anything about HW diboson setup: do e.g. any 
>>> extra
>>> flags need to be set? And does this work fine through the Athena
>>> Herwig_i interface?
>>>
>>> Andy
>>>
>>
>> _______________________________________________
>> Rivet mailing list
>> Rivet at projects.hepforge.org
>> http://www.hepforge.org/lists/listinfo/rivet
>