Missing variable definition DUM0 in VBF for v4 models

Bug #1095603 reported by Johan Alwall
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadGraph5_aMC@NLO
Fix Released
High
Olivier Mattelaer

Bug Description

Timlu wrote:

When I ran the process like u d > d u w+ w- $ w+ w- z
It would also induce the error :

Error detected in "generate_events run_01"
write debug file /Users/timlu/Desktop/MadGraph5/2HDM-101/run_01_tag_1_debug.log
If you need help with this issue please contact us on https://answers.launchpad.net/madgraph5
MadGraph5Error : A compilation Error occurs when trying to compile /Users/timlu/Desktop/MadGraph5/2HDM-101/SubProcesses/P0_qq_qqwpwm.
The compilation fails with the following output message:
   gfortran -O -w -ffixed-line-length-132 -w -c -o symmetry.o symmetry.f
   touch qmass.inc
   gfortran -O -w -ffixed-line-length-132 -w -c -o setcuts.o setcuts.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o cuts.o cuts.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o cluster.o cluster.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o myamp.o myamp.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o genps.o genps.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o initcluster.o initcluster.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o setscales.o setscales.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o reweight.o reweight.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o get_color.o get_color.f
   gfortran -O -w -ffixed-line-length-132 -w -c -o matrix1.o matrix1.f
   matrix1.f:393.15:

        $ *2),DUM0,AMP(1))
                  1
   錯誤: 符號「dum0」(位於 (1))沒有 IMPLICIT 類型
   make: *** [matrix1.o] Error 1

Related branches

Revision history for this message
Johan Alwall (johan-alwall) wrote :

Dear Tim,

Thanks for reporting this. It turns out that we never included the DUM0 and DUM1 variables in the grouped subprocess matrixN.f when we enabled subprocess grouping also for v4 models. These variables are needed for the 4-vector boson vertex routines in HELAS. The quick fix for this is to simply add the lines

C Needed for v4 models
    COMPLEX*16 DUM0,DUM1
    DATA DUM0, DUM1/(0d0, 0d0), (1d0, 0d0)/

at line 213 in
madgraph/iolibs/template_files/matrix_madevent_group_v4.inc

We will include this fix in the next release of MadGraph.

All the best,
Johan

Changed in madgraph5:
status: In Progress → Fix Committed
Revision history for this message
Tim Lu (timluyu) wrote : RE: [Bug 1095603] Re: Missing variable definition DUM0 in VBF for v4 models
Download full text (3.3 KiB)

Dear Dr. Johan Alwall,
Thanks a lot ! ! !
But when I add
> C   Needed for v4 models
>     COMPLEX*16 DUM0,DUM1
>     DATA DUM0, DUM1/(0d0, 0d0), (1d0, 0d0)/

> at line 213 in
> madgraph/iolibs/template_files/matrix_madevent_group_v4.inc

It could be ran, but the cross section will be very large for all usrmod model !
Could you please check again ?
Thanks again !

Best,
Tim

--- 13/1/3 (四),Johan Alwall <email address hidden> 寫道:

> 寄件者: Johan Alwall <email address hidden>
> 主旨: [Bug 1095603] Re: Missing variable definition DUM0 in VBF for v4 models
> 收件者: <email address hidden>
> 日期: 2013年1月3日,四,下午7:36
> Dear Tim,
>
> Thanks for reporting this. It turns out that we never
> included the DUM0
> and DUM1 variables in the grouped subprocess matrixN.f when
> we enabled
> subprocess grouping also for v4 models. These variables are
> needed for
> the 4-vector boson vertex routines in HELAS. The quick fix
> for this is
> to simply add the lines
>
> C   Needed for v4 models
>     COMPLEX*16 DUM0,DUM1
>     DATA DUM0, DUM1/(0d0, 0d0), (1d0, 0d0)/
>
> at line 213 in
> madgraph/iolibs/template_files/matrix_madevent_group_v4.inc
>
> We will include this fix in the next release of MadGraph.
>
> All the best,
> Johan
>
> --
> You received this bug notification because you are
> subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1095603
>
> Title:
>   Missing variable definition DUM0 in VBF for v4
> models
>
> Status in The MadGraph Matrix Element Generator version 5:
>   In Progress
>
> Bug description:
>   Timlu wrote:
>
>   When I ran the process like u d > d u w+ w- $ w+
> w- z
>   It would also induce the error :
>
>   Error detected in "generate_events run_01"
>   write debug file
> /Users/timlu/Desktop/MadGraph5/2HDM-101/run_01_tag_1_debug.log
>
>   If you need help with this issue please contact us on
> https://answers.launchpad.net/madgraph5
>   MadGraph5Error : A compilation Error occurs when
> trying to compile
> /Users/timlu/Desktop/MadGraph5/2HDM-101/SubProcesses/P0_qq_qqwpwm.
>   The compilation fails with the following output
> message:
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o symmetry.o
> symmetry.f
>      touch qmass.inc
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o setcuts.o setcuts.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o cuts.o cuts.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o cluster.o cluster.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o myamp.o myamp.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o genps.o genps.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o initcluster.o
> initcluster.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o setscales.o
> setscales.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o reweight.o
> reweight.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o get_color.o
> get_color.f
>      gfortran -O -w
> -ffixed-line-length-132 -w  -c -o matrix1.o matrix1.f
>      matrix1.f:393.15:
>
>           $ *2),DUM0,AMP(1))
>
>
>
>
>
>     1
>      錯誤: 符號「dum0」(位於
> (1))沒有 IMPLICIT 類型
>      make:...

Read more...

Revision history for this message
Johan Alwall (johan-alwall) wrote :

Dear Tim,

When I do
cd models
cp -r usrmod_v4 test_v4
cd test_v4;./ConversionScript.pl;cd ../..
bin/mg5
import model_v4 test
generate u d > w+ w- u d $ w+ w- z
output
launch

I get the normal cross section of 0.3722, same as for the sm and sm_v4 models. So I would guess the problem is in your user model implementation. Might I recommend to do the implementation in FeynRules, starting from the FR SM implementation? That is usually easier than using a v4 model.

All the best,
Johan

Revision history for this message
Tim Lu (timluyu) wrote : Re: [Bug 1095603] Re: Missing variable definition DUM0 in VBF for v4 models

Dear Dr. Johan,
Thanks for your help !
Sorry, the process I ran is
u d > w+ w- u d $ w+ w- z QCD=0 QED=4
not u d > w+ w- u d $ w+ w- z .
I try the process
u d > w+ w- u d $ w+ w- z
in my usrmod model, it would get almost the same cross section as you.
But if I try
u d > w+ w- u d $ w+ w- z QCD=0 QED=4
in my usrmod model, its cross section would be very large O(1000) pb.
I still think it is very strange, could you please check it again ?
I am learning how to use FeynRules now, I will try to build models by using FeynRules.
Thank you very much ! ! !

Best,
Tim

Johan Alwall 於 2013/1/5 下午8:26 寫道:

> Dear Tim,
>
> When I do
> cd models
> cp -r usrmod_v4 test_v4
> cd test_v4;./ConversionScript.pl;cd ../..
> bin/mg5
> import model_v4 test
> generate u d > w+ w- u d $ w+ w- z
> output
> launch
>
> I get the normal cross section of 0.3722, same as for the sm and sm_v4
> models. So I would guess the problem is in your user model
> implementation. Might I recommend to do the implementation in FeynRules,
> starting from the FR SM implementation? That is usually easier than
> using a v4 model.
>
> All the best,
> Johan
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1095603
>
> Title:
> Missing variable definition DUM0 in VBF for v4 models
>
> Status in The MadGraph Matrix Element Generator version 5:
> Fix Committed
>
> Bug description:
> Timlu wrote:
>
> When I ran the process like u d > d u w+ w- $ w+ w- z
> It would also induce the error :
>
> Error detected in "generate_events run_01"
> write debug file /Users/timlu/Desktop/MadGraph5/2HDM-101/run_01_tag_1_debug.log
> If you need help with this issue please contact us on https://answers.launchpad.net/madgraph5
> MadGraph5Error : A compilation Error occurs when trying to compile /Users/timlu/Desktop/MadGraph5/2HDM-101/SubProcesses/P0_qq_qqwpwm.
> The compilation fails with the following output message:
> gfortran -O -w -ffixed-line-length-132 -w -c -o symmetry.o symmetry.f
> touch qmass.inc
> gfortran -O -w -ffixed-line-length-132 -w -c -o setcuts.o setcuts.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o cuts.o cuts.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o cluster.o cluster.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o myamp.o myamp.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o genps.o genps.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o initcluster.o initcluster.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o setscales.o setscales.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o reweight.o reweight.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o get_color.o get_color.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o matrix1.o matrix1.f
> matrix1.f:393.15:
>
> $ *2),DUM0,AMP(1))
> 1
> 錯誤: 符號「dum0」(位於 (1))沒有 IMPLICIT 類型
> make: *** [matrix1.o] Error 1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/madgraph5/+bug/1095603/+subscriptions

Revision history for this message
Johan Alwall (johan-alwall) wrote :

Dear Tim,

Indeed, I can confirm your problem - the result for

import model_v4 sm
generate u d > d u w+ w- $ w+ w- z QCD=0
output
launch

does not seem correct (1005 pb instead of 0.11 pb). We will look into this and get back to you. Thanks so much for reporting!

Johan

Changed in madgraph5:
assignee: Johan Alwall (johan-alwall) → Olivier Mattelaer (olivier-mattelaer)
status: Fix Committed → Triaged
importance: Undecided → High
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Hi Tim, Johan,

I'm back from holiday, so I'm going to investigate this (today or tommorow).

Cheers,

Olivier

Changed in madgraph5:
status: Triaged → In Progress
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Hi Tim, Johan,

I found the problem:
The Helas call for the ZZWW interaction was not correctly written in the matrix.f

In order to have the correct call you need to do the following fix:
in file madgraph/iolibs/helas_call_writer.py

1)around line 606:
you should have
if argument.get('lorentz') == 'WWVV':
and you should replace it by
if argument.get('lorentz') == ['WWVV']:

2) You should perform the same change around line 625

3) around line 609
you should have
if argument.get('lorentz') == 'WWWW':
and you should replace it by
if argument.get('lorentz') == ['WWWW']:

4) You should perform the same change around line 628

Both fixed (the one explained by Johan and this one) will be included in version 1.5.7
Thanks so much for reporting this,

Cheers,

Olivier

Changed in madgraph5:
status: In Progress → Fix Committed
Revision history for this message
Tim Lu (timluyu) wrote : Re: [Bug 1095603] Missing variable definition DUM0 in VBF for v4 models

Dear Dr. Olivier and Dr. Johan,
Thanks a lot !
Because I am running a big process now, if it is finished, I will try to fix the helas_call_writer.py and to see it can work or not ?
Thanks again !

Best,
Tim

Olivier Mattelaer 於 2013/1/9 上午4:25 寫道:

> Hi Tim, Johan,
>
> I found the problem:
> The Helas call for the ZZWW interaction was not correctly written in the matrix.f
>
> In order to have the correct call you need to do the following fix:
> in file madgraph/iolibs/helas_call_writer.py
>
> 1)around line 606:
> you should have
> if argument.get('lorentz') == 'WWVV':
> and you should replace it by
> if argument.get('lorentz') == ['WWVV']:
>
> 2) You should perform the same change around line 625
>
> 3) around line 609
> you should have
> if argument.get('lorentz') == 'WWWW':
> and you should replace it by
> if argument.get('lorentz') == ['WWWW']:
>
> 4) You should perform the same change around line 628
>
> Both fixed (the one explained by Johan and this one) will be included in version 1.5.7
> Thanks so much for reporting this,
>
> Cheers,
>
> Olivier
>
>
> ** Changed in: madgraph5
> Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1095603
>
> Title:
> Missing variable definition DUM0 in VBF for v4 models
>
> Status in The MadGraph Matrix Element Generator version 5:
> Fix Committed
>
> Bug description:
> Timlu wrote:
>
> When I ran the process like u d > d u w+ w- $ w+ w- z
> It would also induce the error :
>
> Error detected in "generate_events run_01"
> write debug file /Users/timlu/Desktop/MadGraph5/2HDM-101/run_01_tag_1_debug.log
> If you need help with this issue please contact us on https://answers.launchpad.net/madgraph5
> MadGraph5Error : A compilation Error occurs when trying to compile /Users/timlu/Desktop/MadGraph5/2HDM-101/SubProcesses/P0_qq_qqwpwm.
> The compilation fails with the following output message:
> gfortran -O -w -ffixed-line-length-132 -w -c -o symmetry.o symmetry.f
> touch qmass.inc
> gfortran -O -w -ffixed-line-length-132 -w -c -o setcuts.o setcuts.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o cuts.o cuts.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o cluster.o cluster.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o myamp.o myamp.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o genps.o genps.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o initcluster.o initcluster.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o setscales.o setscales.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o reweight.o reweight.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o get_color.o get_color.f
> gfortran -O -w -ffixed-line-length-132 -w -c -o matrix1.o matrix1.f
> matrix1.f:393.15:
>
> $ *2),DUM0,AMP(1))
> 1
> 錯誤: 符號「dum0」(位於 (1))沒有 IMPLICIT 類型
> make: *** [matrix1.o] Error 1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/madgraph5/+bug/1095603/+subscriptions

Changed in madgraph5:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.