Problem compiling code after issuing "launch" and question for single VLQ T' production

Looks like you are using a LO run_card for your NLO computation.
In 3.5.0, we will (if my latest merge request is included in that branch) have a much more clear error when this occurs.

Cheers,

Olivier

> On 8 Jan 2023, at 17:00, Alexis Kalogeropoulos <email address hidden> wrote:
>
> Question #704329 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/704329
>
> Description changed to:
> Hello
>
> After successfully using the following syntax for a VLQ process @ NLO
> v3.2
>
> import model VLQ_v4_4FNS_UFO-3rdL_noCKM
> define tt = t t~
> define bb = b b~
> define ww = w+ w-
> define tpp = tp tp~
> define bpp = bp bp~
> define xx = x x~
> define yy = y y~
>
> generate p p > tpp bb j / bpp xx yy [QCD] aEW=1 aS=1 VLQ=1
>
> So, my first question is if the syntax above is the correct one, or
> maybe ommiting VLQ term and have QCD=>2
>
> generate p p > tpp bb j / bpp xx yy [QCD] aEW=1 aS<=2
>
> should be used instead... Could you please advise? We want to get a
> single VLQ T' in NWA but we are not certain of which one is better.
>
> Anyway, moving forward, while issuing launch to generate events I do
> get the following compilation error:
>
> ```INFO: Using LHAPDF v6.4.0 interface for PDFs
> INFO: Compiling source...
> Command "launch" interrupted with error:
> MadGraph5Error : A compilation Error occurs when trying to compile /afs/cern.ch/work/a/alkaloge/Gridpacks/VLQ/genproductions/bin/MadGraph5_aMCatNLO/TestGrid/MG5_aMC_v3_2_0/bW_t_NLOv322_VLQ/Source.
> The compilation fails with the following output message:
> gfortran -O -fno-automatic -ffixed-line-length-132 -c -o setrun.o setrun.f
> run_card.inc:155.14:
> Included at setrun.f:42:
>
> GRIDPACK = ' .false. '
> 1
> Error: Symbol 'gridpack' at (1) has no IMPLICIT type
> run_card.inc:153.11:
> Included at setrun.f:42:
>
> IAPPL = ' 0 '
> 1
> Error: Symbol 'iappl' at (1) has no IMPLICIT type
> make: *** [setrun.o] Error 1
>
> Please try to fix this compilations issue and retry.
>
>
> I am having gcc version 4.8.5 - any ideas?
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

(edited)

Thanks, I fixed/removed the gridpack line but it now fails to a different point

```
Command "launch" interrupted with error:
MadGraph5Error : A compilation Error occurs when trying to compile /afs/cern.ch/work/a/alkaloge/Gridpacks/VLQ/genproductions/bin/MadGraph5_aMCatNLO/TestGrid/MG5_aMC_v3_2_0/bW_t_NLOv322_VLQ/Source.
 The compilation fails with the following output message:
     rm -f ../lib/libdhelas.a
     cd DHELAS; make
     make[1]: Entering directory `/afs/cern.ch/work/a/alkaloge/Gridpacks/VLQ/genproductions/bin/MadGraph5_aMCatNLO/TestGrid/MG5_aMC_v3_2_0/bW_t_NLOv322_VLQ/Source/DHELAS'
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o aloha_functions.o aloha_functions.f
     aloha_functions.f:483.25:

                 ip = nhel * -1 * ((1-nh)/2)
                              1
     Warning: Extension: Unary operator following arithmetic operator (use parentheses) at (1)
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o FFV2L2_1.o FFV2L2_1.f
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o MP_FFV2L2_1.o MP_FFV2L2_1.f
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o FFV1_8L2_1.o FFV1_8L2_1.f
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o MP_FFV1_8L2_1.o MP_FFV1_8L2_1.f
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o FFV1_2.o FFV1_2.f
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o MP_FFV1_2.o MP_FFV1_2.f
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o FFV2_0.o FFV2_0.f
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o MP_FFV2_0.o MP_FFV2_0.f
     gfortran -O -fno-automatic -ffixed-line-length-132 -c -o FFV1L2P0_3.o FFV1L2P0_3.f
     FFV1L2P0_3.f:20.26:

           COEFF(1,0,1)= COUP*-CI * F1(7)
....

```

any ideas?

ok, more updates - switching to a different machine, looks like that the above problem disappears... I am closing the issue now, because I am getting a different error, related to collinear test etc reported failures - I will open a new ticket for this.