"Error: failed to reduce to color indices" in gg to ttg (only for event generation, not for cross sections) #14

valassi · 2022-05-17T10:00:47Z

Hi Olivier, I am having some failures in my tests for gg to tt plus at least one gluon for instance ggttg (instead ggtt is ok).

NB I am getting this also with standard madevent in fortran...

From this repo 311 branch I produce a normal madevent run

generate g g > t t~ g
output pippo --vector_size=32
launch pippo

This works fine.

However then I go to the P1 directory and use the typical (no multichannel) input that I use for my tests

64 1 1 ! Number of events and max and min iterations
0.000001 ! Accuracy (ignored because max iterations = min iterations)
0 ! Grid Adjustment 0=none, 2=adjust (NB if = 0, ftn26 will still be used if present)
0 ! Suppress Amplitude 1=yes (i.e. use MadEvent single-diagram enhancement)
0 ! Helicity Sum/event 0=exact
1 ! Channel number for single-diagram enhancement multi-channel (IGNORED as suppress amplitude is 0?)

Using that as input file in tmp, I do

cd pippo/SubProcesses/P1_gg_ttxg
 \rm results.dat 
 ./madevent < /tmp/avalassi/tmp.2BuWFo5V3p
 ./madevent < /tmp/avalassi/tmp.2BuWFo5V3p

The first madevent execution, which only prints out a xsec and writes out results.dat with the grid, is ok.

The second madevent execution fails with this as last line:

 Error: failed to reduce to color indices:

(By the way, it returns 0 as status code, it should return non 0 if it fails).

Any suggestion?
Thanks!
Andrea

The text was updated successfully, but these errors were encountered:

…oliviermattelaer/mg5amc_test#14

valassi · 2022-05-20T06:18:48Z

(Just trying to do a checkpoint whether this is still needed. I do not see this issue in my tests now, but I think that it is because I am bypassing it, not because it is solved. I am only running the first part of the tests: I always delete results.dat before running my tests, an dthen things are ok for ggttgg. If I wanted to do not only cross section calculations but also event generation, then I would need to keep the existing results.dat, and then I think that this error would show up. So I guess this needs to be fixed eventually).

…ermattelaer/mg5amc_test#14 is fixed Check however that the issue still holds in rev 1009 *** EXECUTE MADEVENT (create results.dat) *** [XSECTION] Cross section = 651.1 [COUNTERS] PROGRAM TOTAL : 1.0732s [COUNTERS] Fortran Overhead ( 0 ) : 0.1695s [COUNTERS] Fortran MEs ( 1 ) : 0.9037s for 544 events => throughput is 6.02E+02 events/s *** EXECUTE MADEVENT (create events.lhe) *** [XSECTION] ERROR! No cross section in log file: /tmp/avalassi/tmp.Ojo8zIuE3W ... Added good helicity 57 1.5850518443661059 in event 1 local: 1 Added good helicity 58 3.5778776023609069 in event 1 local: 1 Added good helicity 59 4.8713456144336122 in event 1 local: 1 Added good helicity 60 9.5428346755235207 in event 1 local: 1 Added good helicity 61 2.8833062592214464E-003 in event 1 local: 1 Added good helicity 62 1.5987514411446659E-002 in event 1 local: 1 Added good helicity 63 0.25383891647259821 in event 1 local: 1 Added good helicity 64 0.48584814560916501 in event 1 local: 1 RESET CUMULATIVE VARIABLE Error: failed to reduce to color indices: 1 1

oliviermattelaer · 2022-06-03T11:05:01Z

I guess that setting multi-channel to False is pushing too much on the phase-space integrator and that it leads to some issue on some part of the phase-space. I do not face that issue with the normal run of the code.
(or that some meta-data are not pass correctly in that case)

I can reproduce that behavior with the official version of the code, so I do not think that this is actually critical.
Is that a blocker for you?

…sh : actually it works! In other words, issue oliviermattelaer/mg5amc_test#14 no longer appears As mentioned by Olivier, the issue probably only appeared with "Suppress Amplitude = no" This is not the case here, as in the scripts I am now only using "Suppress Amplitude = yes"

…test#14 is irrelevant with suppress=1)

valassi · 2022-06-03T14:17:44Z

Hi Olivier, thanks a lot!

I confirm that this no longer appears if I use by default "suppress amplitude = 1". I guess I was using it equal to 0 to debug other issues, but now I can use 1 always. In any case I have the other option of using channel=0 to disable the enhancement factor.

This can be closed. I am now routinely doing both:

remove results.dat and compute cross section
then in a second step keep results.dat and generate unweighted events

…r from fortran (and some processes crash...) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/ee_mumu.mad/SubProcesses/P1_ll_ll Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/ee_mumu.mad/SubProcesses/P1_ll_ll [XSECTION] Cross section = 0.09017 [XSECTION] Cross section = 0.09017 [UNWEIGHT] Wrote 1009 events (found 1010 events) [XSECTION] Cross section = 0.09066 [UNWEIGHT] Wrote 998 events (found 999 events) [XSECTION] Cross section = 0.09066 [UNWEIGHT] Wrote 998 events (found 999 events) [XSECTION] Cross section = 0.08975 [UNWEIGHT] Wrote 966 events (found 967 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttggg.mad/SubProcesses/P1_gg_ttxggg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttggg.mad/SubProcesses/P1_gg_ttxggg [XSECTION] Cross section = 3.447e-07 [XSECTION] Cross section = 3.447e-07 [UNWEIGHT] Wrote 4 events (found 15 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttgg.mad/SubProcesses/P1_gg_ttxgg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttgg.mad/SubProcesses/P1_gg_ttxgg [XSECTION] Cross section = 0.0001289 [XSECTION] Cross section = 0.0001289 [UNWEIGHT] Wrote 4 events (found 74 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttg.mad/SubProcesses/P1_gg_ttxg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttg.mad/SubProcesses/P1_gg_ttxg [XSECTION] Cross section = 0.08045 [XSECTION] Cross section = 0.08045 [UNWEIGHT] Wrote 56 events (found 449 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_tt.mad/SubProcesses/P1_gg_ttx Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_tt.mad/SubProcesses/P1_gg_ttx [XSECTION] Cross section = 45.91 [XSECTION] Cross section = 45.91 [UNWEIGHT] Wrote 788 events (found 2238 events) [XSECTION] Cross section = 45.84 [UNWEIGHT] Wrote 798 events (found 2234 events) [XSECTION] Cross section = 45.84 [UNWEIGHT] Wrote 798 events (found 2234 events) [XSECTION] Cross section = 47.62 [UNWEIGHT] Wrote 804 events (found 2280 events) The crash is again the 'Error: failed to reduce to color indices' of oliviermattelaer/mg5amc_test#14

valassi · 2022-06-14T14:01:34Z

Sorry @oliviermattelaer I must reopen this. The details about how to reproduce this are a bit complex, see madgraph5/madgraph4gpu#486. Essentially, even in "suppress amplitude = 1", I get this error in ggttgg and ggttggg when I only compare the cudacpp ME and I skip the SMATRIX1 computation of the Fortran ME. I suspect that there might be some info filled in through common blocks somewhere? I am having a look...

valassi · 2022-06-14T14:03:04Z

See logs in madgraph5/madgraph4gpu@d5a7a60#diff-ed50f3ccef2c94de76c78d7daba1e807078073b09d01087d517c5996910df0b7

oliviermattelaer · 2022-06-15T07:23:01Z

Hi, I guess it makes sense since the JAMP2 are then not populated. Did you include my sketch of program to select the color inside the cudacpp part? Then one need to adapt the fortran part (which is doing that selection for the moment) to just pick the choice from cudacpp.

valassi · 2022-06-15T09:26:24Z

Hi Olivier, thanks.

Hi, I guess it makes sense since the JAMP2 are then not populated. Did you include my sketch of program to select the color inside the cudacpp part? Then one need to adapt the fortran part (which is doing that selection for the moment) to just pick the choice from cudacpp.

Is it this one you refer to? mg5amcnlo/mg5amcnlo@a809e27

No I have not yet included that.

oliviermattelaer · 2022-06-15T09:30:17Z

Is it this one you refer to? mg5amcnlo/mg5amcnlo@a809e27

No I have not yet included that.

Yes exactly

valassi · 2022-06-15T09:42:31Z

Thanks but I am confused, I tried to generate my '--madgpu' option (ie madevent + your standalone_gpu as 2nd exporter, NOT madevent + my cudacpp as 2nd exporter) for ggtt and I seem to get no difference in generated code. Is this normal? I mean, is this a change in python code that will ease my life in code generation only, or are you generating some code differently?

oliviermattelaer · 2022-06-15T09:46:16Z

I'm moviing forward on a new handling of the color part (starting with #19) but yes indeed this is not yet ready.

valassi · 2022-06-15T09:49:04Z

Ok no problem! Thanks I will keep this in mind then (and will move to that new github commit anyway).

(NB: need 9 characters here as this is the output of git log --oneline) This may help fixing 'failed to reduce to color indices'? oliviermattelaer/mg5amc_test#14

valassi · 2022-06-15T10:17:16Z

Hi, I guess it makes sense since the JAMP2 are then not populated.

Very good now I see what you mean. I was getting confused but it totally makes sense. This is completely related to the random choice of color madgraph5/madgraph4gpu#402.

Until/unless we implement that in cudacpp and in the bridge, I want to at least have a way out so that we still write events.lhe files, for instance where the 'randomly chosen color' is always 1.

I now see that all of the complex algorithmic of this is in addmothers.f. I will try to cook up a fake JAMP2 that I can pass to addmothers so that the algorithm proceeds and always chooses 1. I guess I just need to send an array where the first element is 1, and all other elements are 0...

… is not called (dummy random choice of color madgraph5#402) This is a WORKAROUND for "Error: failed to reduce to color indices" oliviermattelaer/mg5amc_test#14 Note: in this patch I only set JAMP2(0), while all other JAMP2(1:NCOLOR) are zero. It seems that addmothers.f already has a workaround to cover this case.

…iermattelaer/mg5amc_test#14 (En passant: ggttg addmothers is regenerated without debug printouts)

…ements Indeed now NCOLOR no longer builds... ccache /cvmfs/sft.cern.ch/lcg/releases/gcc/10.2.0-c44b3/x86_64-centos7/bin/gfortran -w -fPIC -ffixed-line-length-132 -w -cpp -c -DMG5AMC_MEEXPORTER_CUDACPP auto_dsig1.f -I../../Source/ -fopenmp -o auto_dsig1_cudacpp.o auto_dsig1.f:584:38: 584 | JAMP2_MULTI(0,IVEC) = NCOLOR ! workaround for oliviermattelaer/mg5amc_test#14 | 1 Error: Symbol ‘ncolor’ at (1) has no IMPLICIT type

…sue is fixed for gggttg* generation This shows that the workaround is ok for oliviermattelaer/mg5amc_test#14 cat tmad/logs_*/* | egrep '(Cross|Working|Wrote|Error|ERROR)' Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/ee_mumu.mad/SubProcesses/P1_ll_ll Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/ee_mumu.mad/SubProcesses/P1_ll_ll [XSECTION] Cross section = 0.09017 [XSECTION] Cross section = 0.09017 [9.0170633677521428E-002] [UNWEIGHT] Wrote 1009 events (found 1010 events) [XSECTION] Cross section = 0.09017 [9.0170633677521442E-002] [UNWEIGHT] Wrote 1009 events (found 1010 events) [XSECTION] Cross section = 0.09017 [9.0170633677521442E-002] [UNWEIGHT] Wrote 1009 events (found 1010 events) [XSECTION] Cross section = 0.2175 [0.21754196695805308] [UNWEIGHT] Wrote 966 events (found 967 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttggg.mad/SubProcesses/P1_gg_ttxggg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttggg.mad/SubProcesses/P1_gg_ttxggg [XSECTION] Cross section = 3.447e-07 [XSECTION] Cross section = 3.447e-07 [3.4471868628442136E-007] [UNWEIGHT] Wrote 4 events (found 15 events) [XSECTION] Cross section = 3.447e-07 [3.4471908676045729E-007] [UNWEIGHT] Wrote 4 events (found 15 events) [XSECTION] Cross section = 3.447e-07 [3.4471908676045713E-007] [UNWEIGHT] Wrote 4 events (found 15 events) [XSECTION] Cross section = 2.008e-06 [2.0075279247605889E-006] [UNWEIGHT] Wrote 2 events (found 11 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttgg.mad/SubProcesses/P1_gg_ttxgg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttgg.mad/SubProcesses/P1_gg_ttxgg [XSECTION] Cross section = 0.0001289 [XSECTION] Cross section = 0.0001289 [1.2885825323149218E-004] [UNWEIGHT] Wrote 4 events (found 74 events) [XSECTION] Cross section = 0.0001289 [1.2885954287258873E-004] [UNWEIGHT] Wrote 4 events (found 74 events) [XSECTION] Cross section = 0.0001289 [1.2885954287258873E-004] [UNWEIGHT] Wrote 4 events (found 74 events) [XSECTION] Cross section = 0.0002221 [2.2210365310367753E-004] [UNWEIGHT] Wrote 7 events (found 79 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttg.mad/SubProcesses/P1_gg_ttxg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttg.mad/SubProcesses/P1_gg_ttxg [XSECTION] Cross section = 0.08045 [XSECTION] Cross section = 0.08045 [8.0445416635721884E-002] [UNWEIGHT] Wrote 56 events (found 449 events) [XSECTION] Cross section = 0.08045 [8.0446406133394599E-002] [UNWEIGHT] Wrote 56 events (found 449 events) [XSECTION] Cross section = 0.08045 [8.0446406133394599E-002] [UNWEIGHT] Wrote 56 events (found 449 events) [XSECTION] Cross section = 0.08402 [8.4018030529591323E-002] [UNWEIGHT] Wrote 16 events (found 397 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_tt.mad/SubProcesses/P1_gg_ttx Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_tt.mad/SubProcesses/P1_gg_ttx [XSECTION] Cross section = 45.91 [XSECTION] Cross section = 45.91 [45.914216281363188] [UNWEIGHT] Wrote 788 events (found 2238 events) [XSECTION] Cross section = 45.91 [45.914455838006880] [UNWEIGHT] Wrote 788 events (found 2238 events) [XSECTION] Cross section = 45.91 [45.914455838006880] [UNWEIGHT] Wrote 788 events (found 2238 events) [XSECTION] Cross section = 47.67 [47.668452211994605] [UNWEIGHT] Wrote 804 events (found 2280 events)

… is not called (dummy random choice of color madgraph5#402) This is a WORKAROUND for "Error: failed to reduce to color indices" oliviermattelaer/mg5amc_test#14 Note: in this patch I only set JAMP2(0), while all other JAMP2(1:NCOLOR) are zero. It seems that addmothers.f already has a workaround to cover this case.

…iermattelaer/mg5amc_test#14 (En passant: ggttg addmothers is regenerated without debug printouts)

…ements Indeed now NCOLOR no longer builds... ccache /cvmfs/sft.cern.ch/lcg/releases/gcc/10.2.0-c44b3/x86_64-centos7/bin/gfortran -w -fPIC -ffixed-line-length-132 -w -cpp -c -DMG5AMC_MEEXPORTER_CUDACPP auto_dsig1.f -I../../Source/ -fopenmp -o auto_dsig1_cudacpp.o auto_dsig1.f:584:38: 584 | JAMP2_MULTI(0,IVEC) = NCOLOR ! workaround for oliviermattelaer/mg5amc_test#14 | 1 Error: Symbol ‘ncolor’ at (1) has no IMPLICIT type

…sue is fixed for gggttg* generation This shows that the workaround is ok for oliviermattelaer/mg5amc_test#14 cat tmad/logs_*/* | egrep '(Cross|Working|Wrote|Error|ERROR)' Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/ee_mumu.mad/SubProcesses/P1_ll_ll Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/ee_mumu.mad/SubProcesses/P1_ll_ll [XSECTION] Cross section = 0.09017 [XSECTION] Cross section = 0.09017 [9.0170633677521428E-002] [UNWEIGHT] Wrote 1009 events (found 1010 events) [XSECTION] Cross section = 0.09017 [9.0170633677521442E-002] [UNWEIGHT] Wrote 1009 events (found 1010 events) [XSECTION] Cross section = 0.09017 [9.0170633677521442E-002] [UNWEIGHT] Wrote 1009 events (found 1010 events) [XSECTION] Cross section = 0.2175 [0.21754196695805308] [UNWEIGHT] Wrote 966 events (found 967 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttggg.mad/SubProcesses/P1_gg_ttxggg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttggg.mad/SubProcesses/P1_gg_ttxggg [XSECTION] Cross section = 3.447e-07 [XSECTION] Cross section = 3.447e-07 [3.4471868628442136E-007] [UNWEIGHT] Wrote 4 events (found 15 events) [XSECTION] Cross section = 3.447e-07 [3.4471908676045729E-007] [UNWEIGHT] Wrote 4 events (found 15 events) [XSECTION] Cross section = 3.447e-07 [3.4471908676045713E-007] [UNWEIGHT] Wrote 4 events (found 15 events) [XSECTION] Cross section = 2.008e-06 [2.0075279247605889E-006] [UNWEIGHT] Wrote 2 events (found 11 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttgg.mad/SubProcesses/P1_gg_ttxgg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttgg.mad/SubProcesses/P1_gg_ttxgg [XSECTION] Cross section = 0.0001289 [XSECTION] Cross section = 0.0001289 [1.2885825323149218E-004] [UNWEIGHT] Wrote 4 events (found 74 events) [XSECTION] Cross section = 0.0001289 [1.2885954287258873E-004] [UNWEIGHT] Wrote 4 events (found 74 events) [XSECTION] Cross section = 0.0001289 [1.2885954287258873E-004] [UNWEIGHT] Wrote 4 events (found 74 events) [XSECTION] Cross section = 0.0002221 [2.2210365310367753E-004] [UNWEIGHT] Wrote 7 events (found 79 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttg.mad/SubProcesses/P1_gg_ttxg Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_ttg.mad/SubProcesses/P1_gg_ttxg [XSECTION] Cross section = 0.08045 [XSECTION] Cross section = 0.08045 [8.0445416635721884E-002] [UNWEIGHT] Wrote 56 events (found 449 events) [XSECTION] Cross section = 0.08045 [8.0446406133394599E-002] [UNWEIGHT] Wrote 56 events (found 449 events) [XSECTION] Cross section = 0.08045 [8.0446406133394599E-002] [UNWEIGHT] Wrote 56 events (found 449 events) [XSECTION] Cross section = 0.08402 [8.4018030529591323E-002] [UNWEIGHT] Wrote 16 events (found 397 events) Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_tt.mad/SubProcesses/P1_gg_ttx Working directory: /data/avalassi/GPU2020/madgraph4gpuX/epochX/cudacpp/gg_tt.mad/SubProcesses/P1_gg_ttx [XSECTION] Cross section = 45.91 [XSECTION] Cross section = 45.91 [45.914216281363188] [UNWEIGHT] Wrote 788 events (found 2238 events) [XSECTION] Cross section = 45.91 [45.914455838006880] [UNWEIGHT] Wrote 788 events (found 2238 events) [XSECTION] Cross section = 45.91 [45.914455838006880] [UNWEIGHT] Wrote 788 events (found 2238 events) [XSECTION] Cross section = 47.67 [47.668452211994605] [UNWEIGHT] Wrote 804 events (found 2280 events)

valassi · 2022-06-15T16:20:30Z

Hi @oliviermattelaer finally I added a basic workaround in madgraph5/madgraph4gpu#489

Essentially I implemented a 'dummy' color choice (all events have the same color). By setting JAMP2_MULTI(0,IVEC) to NCOLOR, this is enough for addmothers.f to avoid the crash and select a dummy color (I guess the first one available).

I am closing this.

valassi · 2022-12-06T17:55:14Z

For the record, I am working on the random choice of color and helicity
madgraph5/madgraph4gpu#402
madgraph5/madgraph4gpu#403
The jamp2 will disappear from the bridge, so this issue #14 and my workaround will also normally disappear?

PS No I tried to simply remove the code where I was implementing the workaround for this #14 (otherwise my code was not building as JAMP2 is not defined in IMPLICIT NONE), but like this it segfaults in addmothers.f. This means that I must add a different workaround somewhere...

…s not build yet! ccache /cvmfs/sft.cern.ch/lcg/releases/gcc/11.2.0-ad950/x86_64-centos7/bin/gfortran -w -fPIC -O3 -ffast-math -fbounds-check -ffixed-line-length-132 -w -cpp -c -DMG5AMC_MEEXPORTER_CUDACPP auto_dsig1.f -I../../Source/ -fopenmp -o auto_dsig1_cudacpp.o auto_dsig1.f:518:62: 518 | CALL FBRIDGESEQUENCE(FBRIDGE_PBRIDGE, P_MULTI, ALL_G, OUT2, 0) ! 0: multi channel disabled for helicity filtering | 1 Error: Symbol ‘all_g’ at (1) has no IMPLICIT type auto_dsig1.f:569:10: 569 | JAMP2_MULTI(0,IVEC) = 2 ! workaround for oliviermattelaer/mg5amc_test#14 | 1 Error: Function ‘jamp2_multi’ at (1) has no IMPLICIT type

Revert "[lhe] fix the second build error in gg_tt.mad, which now compiles... I have not tries to run it though" This reverts commit fa2c4c73160c5ccd8920685dfc243fa384eb7023. ./tmad/teeMadX.sh -ggtt ... Executing ' ./build.none_d_inl0_hrd0/cmadevent_cudacpp < /tmp/avalassi/input_ggtt_x1_cudacpp > /tmp/avalassi/output_ggtt_x1_cudacpp' At line 124 of file addmothers.f Fortran runtime error: Index '0' of dimension 2 of array 'jamp2' below lower bound of 1 Error termination. Backtrace: I think that this is clearly related to oliviermattelaer/mg5amc_test#14

…h now compiles... I have not tried to run it though Essentialy, add another workaround for oliviermattelaer/mg5amc_test#14

…dmothers.f Will then regenerate - this is a third attempt to fix the second build error in addmothers.f This is related to oliviermattelaer/mg5amc_test#14 NB eventually I must severaly clean up the codegen patches and minimise them...

valassi added a commit to valassi/madgraph4gpu that referenced this issue May 17, 2022

[fvsc] in madX.sh compute xsec only (no event generation), work around …

4e37dbc

…oliviermattelaer/mg5amc_test#14

valassi changed the title ~~"Error: failed to reduce to color indices" in gg to ttg~~ "Error: failed to reduce to color indices" in gg to ttg (only for event generation, not for cross sections) May 20, 2022

valassi mentioned this issue May 20, 2022

First patch for automatic Fortran vs cuda/cpp comparisons madgraph5/madgraph4gpu#454

Merged

valassi added a commit to valassi/madgraph4gpu that referenced this issue Jun 3, 2022

[mch] cleanup, remove genevt=0 option (issue oliviermattelaer/mg5amc_…

c3908de

…test#14 is irrelevant with suppress=1)

valassi closed this as completed Jun 3, 2022

valassi mentioned this issue Jun 14, 2022

First attempt to produce cross sections and events using cudacpp MEs (debug common blocks behind SMATRIX1: add RESET_CUMULATIVE_VARIABLE call) madgraph5/madgraph4gpu#486

Merged

valassi reopened this Jun 14, 2022

valassi mentioned this issue Jun 15, 2022

Upgrade upstream mg5amc to github commit a809e2705 madgraph5/madgraph4gpu#488

Merged

valassi mentioned this issue Jun 15, 2022

Randomly pick one color for each event written to file (jamp2 handling) madgraph5/madgraph4gpu#402

Closed

valassi added a commit to valassi/madgraph4gpu that referenced this issue Jun 15, 2022

[fvsc] regenerate all five processes mad with the workaround for oliv…

7784c4d

…iermattelaer/mg5amc_test#14 (En passant: ggttg addmothers is regenerated without debug printouts)

valassi added a commit to valassi/madgraph4gpu that referenced this issue Jun 15, 2022

[fvsc] regenerate all five processes mad with the workaround for oliv…

d7115ac

…iermattelaer/mg5amc_test#14 (En passant: ggttg addmothers is regenerated without debug printouts)

valassi mentioned this issue Jun 15, 2022

Next patch for cudacpp-only MEs: add dummy color choice to fix 'failed to reduce to color index' madgraph5/madgraph4gpu#489

Merged

valassi closed this as completed Jun 15, 2022

valassi added a commit to valassi/madgraph4gpu that referenced this issue Dec 7, 2022

[lhe] second attempt to fix the second build error in gg_tt.mad, whic…

0d860d4

…h now compiles... I have not tried to run it though Essentialy, add another workaround for oliviermattelaer/mg5amc_test#14

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

"Error: failed to reduce to color indices" in gg to ttg (only for event generation, not for cross sections) #14

"Error: failed to reduce to color indices" in gg to ttg (only for event generation, not for cross sections) #14

valassi commented May 17, 2022

valassi commented May 20, 2022

oliviermattelaer commented Jun 3, 2022

valassi commented Jun 3, 2022

valassi commented Jun 14, 2022

valassi commented Jun 14, 2022

oliviermattelaer commented Jun 15, 2022

valassi commented Jun 15, 2022

oliviermattelaer commented Jun 15, 2022

valassi commented Jun 15, 2022

oliviermattelaer commented Jun 15, 2022

valassi commented Jun 15, 2022

valassi commented Jun 15, 2022

valassi commented Jun 15, 2022

valassi commented Dec 6, 2022 •

edited

Loading

"Error: failed to reduce to color indices" in gg to ttg (only for event generation, not for cross sections) #14

"Error: failed to reduce to color indices" in gg to ttg (only for event generation, not for cross sections) #14

Comments

valassi commented May 17, 2022

valassi commented May 20, 2022

oliviermattelaer commented Jun 3, 2022

valassi commented Jun 3, 2022

valassi commented Jun 14, 2022

valassi commented Jun 14, 2022

oliviermattelaer commented Jun 15, 2022

valassi commented Jun 15, 2022

oliviermattelaer commented Jun 15, 2022

valassi commented Jun 15, 2022

oliviermattelaer commented Jun 15, 2022

valassi commented Jun 15, 2022

valassi commented Jun 15, 2022

valassi commented Jun 15, 2022

valassi commented Dec 6, 2022 • edited Loading

valassi commented Dec 6, 2022 •

edited

Loading