Comment 10 for bug 1334014

Revision history for this message
Azar Mustafayev (azar) wrote : Re: [Bug 1334014] Re: crash at Compiling MCatNLO

Hi Marco,

Yes, I did get a number for Herwing run and it was 8787pb. But there
also was an error stamp atthis run, so I wasn't sure how reliable that
number was.
When I switched to pythia6Q, as Paolo suggested, the shower worked
without problems.

Best,
   Azar

On 07/14/2014 08:27 PM, marco zaro wrote:
> Hi Azar,
> i don't understand one thing: also by selecting HW6 as a shower, you should
> get a number for the total cross-section before showering the events, right?
> does the shower work ok with pythia6?
> Cheers,
>
> Marco
>
>
> Marco Zaro
>
>
> On Tue, Jul 15, 2014 at 1:56 AM, Azar Mustafayev <email address hidden>
> wrote:
>
>> Hi Paolo,
>>
>> I tried to generate events with PYTHIA6Q as you suggested and it did go
>> through returning cross esction of 8903 pb. This is close to 9.7e3 pb
>> you have for Z+j at NLO in Table 1 of your paper. I guess the difference
>> can be attributed different PDFs and scale used.
>>
>> In running the code I received multiple messages of the following type,
>> but I guess they are harmless:
>> Exception AttributeError: AttributeError("'_DummyThread' object has no
>> attribute '_Thread__block'",) in <module 'threading' from
>> '/usr/lib64/python2.7/threading.pyc'> ignored
>>
>> As for the StdHEP compilation, I used the install command from MG and
>> presume it used the same compliers for all. Here is my configuration
>> file, just in case.
>>
>> Best,
>> Azar
>>
>>
>> On 07/14/2014 12:02 AM, Paolo Torrielli wrote:
>>> Hi Azar,
>>>
>>> could you also try to generate and shower a sample with PYTHIA6Q instead
>> of HERWIG6, and see if you get the
>>> same kind of problem?
>>>
>>> Another question: are you sure that while compiling StdHEP you use the
>> same fortran and c++ compilers that you
>>> use to compile HERWIG6 in the shower phase? Normally this is the case,
>> unless you specify some particular compiler
>>> in the input/mg5_configuration.txt file.
>>> If you use different compilers, there may be some compilation conflict
>> or something similar.
>>> Cheers.
>>> Paolo
>>>
>>
>> ** Attachment added: "mg5_configuration.txt"
>>
>> https://bugs.launchpad.net/bugs/1334014/+attachment/4152648/+files/mg5_configuration.txt
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1334014
>>
>> Title:
>> crash at Compiling MCatNLO
>>
>> Status in MadGraph5_aMC@NLO Generator:
>> New
>>
>> Bug description:
>> Hello,
>>
>> I am trying to learn how to generate NLO events and decided to
>> reproduce Z+j results from your paper, but MG crashed compiling
>> MCatNLO. Here is the relevant screen output
>>
>> INFO: Events generated
>> decay_events -from_cards
>> INFO: Prepairing MCatNLO run
>> INFO: Compiling MCatNLO for HERWIG6...
>> ../lib/libstdhep.a(luntmp.o): In function `luntmp_':
>> luntmp.F:(.text+0x82): undefined reference to `pyerrm_'
>> luntmp.F:(.text+0x5bc): undefined reference to `pyerrm_'
>> luntmp.F:(.text+0x61c): undefined reference to `pycomp_'
>> luntmp.F:(.text+0xaa6): undefined reference to `pyerrm_'
>> luntmp.F:(.text+0xee6): undefined reference to `pycomp_'
>> luntmp.F:(.text+0xfee): undefined reference to `pyerrm_'
>> ../lib/libstdhep.a(lutran.o): In function `lutran_':
>> lutran.F:(.text+0x2a8): undefined reference to `pyerrm_'
>> lutran.F:(.text+0x2e2): undefined reference to `pyerrm_'
>> lutran.F:(.text+0x30d): undefined reference to `pyerrm_'
>> lutran.F:(.text+0xaf4): undefined reference to `pyerrm_'
>> collect2: error: ld returned 1 exit status
>> make: *** [HW_EXE_DEFAULT] Error 1
>> mv: cannot stat ‘HW_EXE_DEFAULT’: No such file or directory
>>
>> Then there are some lengthy fortran compiler lines and the program
>> crashes suggesting to report the error.
>> Could you tell what went wrong and how to fix this?
>>
>> Thanks,
>> Azar
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/mg5amcnlo/+bug/1334014/+subscriptions
>>