Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update the mg5amcnlo submodule to the latest commit in branch gpucpp #811

Merged
merged 15 commits into from
Feb 2, 2024

Conversation

valassi
Copy link
Member

@valassi valassi commented Jan 31, 2024

Hi @oliviermattelaer as discussed in PR #801.

This WIP PR updates the mg5amcnlo submodule to the latest commit in branch gpucpp.

Note: code generation now fails (well it is actually treatcards in my case) because reset_simd in banner.py throws an exception. It would be enough to change that exception to a warning for the time being, an dthings would be better.

Or otherwise we can take the time to understand better what goes on.

…428e38c6 in branch gpucpp

(NB: code generation now succeds...? I thought it failed because reset_simd in banner.py throws an exception, but this is only in jt774?)
@oliviermattelaer
Copy link
Member

oliviermattelaer commented Jan 31, 2024

Is your issue is this?

Command "generate_events run_01" interrupted with error:
InvalidCardEdition : value 'fortran' for entry 'cudacpp_backend' is not valid.  Preserving previous value: 'CPP'.
	allowed values are Fortan, CPP, CUDA

Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in 'ME5_debug'.
Please attach this file to your report.

I'm looking about that issue (not sure if this is mg5 or the plugin), I can not do any run as long as this is not solved (and therefore can not run on #801), so I'm investigating it for the moment

UPDATE: that one was easy to fix (it is obvious but my brain hide to issue for me for so so long ....)

@valassi
Copy link
Member Author

valassi commented Jan 31, 2024

Hi Olivier, sorry NO! I was wrong.

Code generation succeeds if I update mg5amcnlo to gpucpp on top of the master of madgraph4gpu. I will test this here.

Instead I have the impression that code generation fails if I update mg5amcnlo to gpucpp on top of the jt774 branch (PR #801) of madgraph4gpu. So it seems that there is an interplay of my/Jorgen's changes for HIP and your changes for mg5amcnlo? I need to check better, sorry.

If the above is confirmed, I suggest:

Sounds ok? But let me check before I say stupid things. It will take me time to run all tests however, will merge this tomorrow at the earliest

@valassi
Copy link
Member Author

valassi commented Jan 31, 2024

Is your issue is this?

Command "generate_events run_01" interrupted with error:
InvalidCardEdition : value 'fortran' for entry 'cudacpp_backend' is not valid.  Preserving previous value: 'CPP'.
	allowed values are Fortan, CPP, CUDA

Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in 'ME5_debug'.
Please attach this file to your report.

I'm looking about that issue (not sure if this is mg5 or the plugin), I can not do any run as long as this is not solved (and therefore can not run on #801), so I'm investigating it for the moment

UPDATE: that one was easy to fix (it is obvious but my brain hide to issue for me for so so long ....)

No my issue was different... but again, I think only in jt774 ie PR 801

…ng major difference in generated c++/fortran code, just version number, setcuts, and a few things around setgrid in myamp.f (many things change in python instead)
@oliviermattelaer
Copy link
Member

Ok, I have pushed the fix for the mistake that I face directly in jt774.
For the update of the current submodule, I do not use it personally, so this is not urgent for me.

…ll rerun all tests now (after reverting this commit)
…tests

Revert "[gpucpp] rerun one tput and one tmad test for ggtt, all seems ok - will rerun all tests now (after reverting this commit)"
This reverts commit 94fcb10.
@valassi
Copy link
Member Author

valassi commented Jan 31, 2024

Hi Olivier, thanks. Ok thanks for confirming that this PR #811 and the gpucpp update is not urgent.

I will look at the jt774 instead then, thanks for adding the fix directly there.

@valassi
Copy link
Member Author

valassi commented Jan 31, 2024

Instead I have the impression that code generation fails if I update mg5amcnlo to gpucpp on top of the jt774 branch (PR #801) of madgraph4gpu. So it seems that there is an interplay of my/Jorgen's changes for HIP and your changes for mg5amcnlo? I need to check better, sorry.

Ok not sure anymore why/where I saw an exception in reset_simd. Now code generation with this update seems ok also in jt774? But I will postpone this anyway. I will do PR #801 WITHOUT this update. And convert this to WIP (and postponed)

@valassi valassi marked this pull request as draft January 31, 2024 15:06
@valassi valassi self-assigned this Jan 31, 2024
@valassi valassi changed the title update the mg5amcnlo submodule to the latest commit in branch gpucpp WIP (postponed to after 801) update the mg5amcnlo submodule to the latest commit in branch gpucpp Jan 31, 2024
@oliviermattelaer
Copy link
Member

Looks like we hit "could not check for binary extension: HTTP 403: API rate limit exceeded for installation ID 13042647. "
which might have trigger some false alarm in the recent commit/PR... I guess we do too much work for github ;-)

…are to merg eupstream/master with HIP madgraph5#801

git checkout 0dc3d50~ $(git ls-tree --name-only HEAD */CODEGEN*txt)
…the mg5amcnlo update: no changes except in codegen logs (changes in individual processes have been merged already)
… all ok

STARTED  AT Thu Feb  1 08:47:02 AM CET 2024
./tput/teeThroughputX.sh -mix -hrd -makej -eemumu -ggtt -ggttg -ggttgg -gqttq -ggttggg -makeclean
ENDED(1) AT Thu Feb  1 09:17:59 AM CET 2024 [Status=0]
./tput/teeThroughputX.sh -flt -hrd -makej -eemumu -ggtt -ggttgg -inlonly -makeclean
ENDED(2) AT Thu Feb  1 09:29:14 AM CET 2024 [Status=0]
./tput/teeThroughputX.sh -makej -eemumu -ggtt -ggttg -gqttq -ggttgg -ggttggg -flt -bridge -makeclean
ENDED(3) AT Thu Feb  1 09:39:06 AM CET 2024 [Status=0]
./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -rmbhst
ENDED(4) AT Thu Feb  1 09:42:25 AM CET 2024 [Status=0]
./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -curhst
ENDED(5) AT Thu Feb  1 09:45:40 AM CET 2024 [Status=0]
…- almost all ok except for two issues in ggttg and gqttq tests

They seem to be both tolerance problems (difference 2.5E-14 > 2.0E-14), will increase the tolerance and rerun those two

STARTED AT Thu Feb  1 09:49:02 AM CET 2024
ENDED   AT Thu Feb  1 02:05:10 PM CET 2024

Status=0

24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_m_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_m_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_m_inl0_hrd0.txt
4 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_m_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_m_inl0_hrd0.txt
4 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_m_inl0_hrd0.txt

tail -1 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_d_inl0_hrd0.txt
ERROR! xsec from fortran (0.10112748607749111) and cpp (0.10112748607748863) differ by more than 2E-14 (2.453592884421596e-14)

tail -1 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0.txt
ERROR! xsec from fortran (0.27110539351263330) and cpp (0.27110539351262536) differ by more than 2E-14 (2.930988785010413e-14)
…sec comparisons (failed for ggttg and gqttq double in PR madgraph5#811)
…8 tmad tests are now ok on itscrd90)

./tmad/teeMadX.sh -ggttg -gqttq +10x
…ph5#806 but otherwise OK

(1) Step 1 on login nodes

./tput/allTees.sh -hip -makeonly | tee pippotput1

STARTED  AT Thu 01 Feb 2024 09:49:48 AM EET
./tput/teeThroughputX.sh -mix -hrd -makej -eemumu -ggtt -ggttg -ggttgg -gqttq -ggttggg -makeclean  -makeonly
ENDED(1) AT Thu 01 Feb 2024 10:31:35 AM EET [Status=0]
./tput/teeThroughputX.sh -flt -hrd -makej -eemumu -ggtt -ggttgg -inlonly -makeclean  -makeonly
ENDED(2) AT Thu 01 Feb 2024 10:45:14 AM EET [Status=0]
./tput/teeThroughputX.sh -makej -eemumu -ggtt -ggttg -gqttq -ggttgg -ggttggg -flt -bridge -makeclean  -makeonly
ENDED(3) AT Thu 01 Feb 2024 10:58:09 AM EET [Status=0]
./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -rmbhst  -makeonly
ENDED(4) AT Thu 01 Feb 2024 11:00:47 AM EET [Status=0]
./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -rorhst  -makeonly
ENDED(5) AT Thu 01 Feb 2024 11:03:02 AM EET [Status=0]

(2) Step 2 on worker nodes

./tput/allTees.sh |& tee pippotput; ./tmad/allTees.sh |& tee pippotmad

STARTED  AT Thu 01 Feb 2024 12:37:01 PM EET
./tput/teeThroughputX.sh -mix -hrd -makej -eemumu -ggtt -ggttg -ggttgg -gqttq -ggttggg -makeclean
ENDED(1) AT Thu 01 Feb 2024 01:29:23 PM EET [Status=2]
./tput/teeThroughputX.sh -flt -hrd -makej -eemumu -ggtt -ggttgg -inlonly -makeclean
ENDED(2) AT Thu 01 Feb 2024 01:46:27 PM EET [Status=0]
./tput/teeThroughputX.sh -makej -eemumu -ggtt -ggttg -gqttq -ggttgg -ggttggg -flt -bridge -makeclean
ENDED(3) AT Thu 01 Feb 2024 02:05:23 PM EET [Status=2]
./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -rmbhst
ENDED(4) AT Thu 01 Feb 2024 02:09:08 PM EET [Status=0]
./tput/teeThroughputX.sh -eemumu -ggtt -ggttgg -flt -curhst
ENDED(5) AT Thu 01 Feb 2024 02:11:28 PM EET [Status=0]

./tput/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0_bridge.txt:Backtrace for this error:
./tput/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0_bridge.txt:ERROR! Fortran calculation (F77/CUDA) crashed
./tput/logs_gqttq_mad/log_gqttq_mad_m_inl0_hrd1.txt:Backtrace for this error:
./tput/logs_gqttq_mad/log_gqttq_mad_m_inl0_hrd1.txt:ERROR! Fortran calculation (F77/CUDA) crashed
./tput/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd1.txt:Backtrace for this error:
./tput/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd1.txt:ERROR! Fortran calculation (F77/CUDA) crashed
./tput/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0.txt:Backtrace for this error:
./tput/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0.txt:ERROR! Fortran calculation (F77/CUDA) crashed
./tput/logs_gqttq_mad/log_gqttq_mad_m_inl0_hrd0.txt:Backtrace for this error:
./tput/logs_gqttq_mad/log_gqttq_mad_m_inl0_hrd0.txt:ERROR! Fortran calculation (F77/CUDA) crashed
./tput/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd1.txt:Backtrace for this error:
./tput/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd1.txt:ERROR! Fortran calculation (F77/CUDA) crashed
./tput/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd0.txt:Backtrace for this error:
./tput/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd0.txt:ERROR! Fortran calculation (F77/CUDA) crashed
./tput/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd0_bridge.txt:Backtrace for this error:
./tput/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd0_bridge.txt:ERROR! Fortran calculation (F77/CUDA) crashed
…ttq as on itscrd90, will rerun them after increasing the tolerance

STARTED AT Thu 01 Feb 2024 02:15:12 PM EET
ENDED   AT Thu 01 Feb 2024 05:13:34 PM EET

Status=0

16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_d_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_f_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_m_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_d_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_f_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_m_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_d_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_f_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_m_inl0_hrd0.txt
4 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_d_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_f_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_m_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_d_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_f_inl0_hrd0.txt
16 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_m_inl0_hrd0.txt
4 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0.txt
12 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd0.txt
12 /users/valassia/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_m_inl0_hrd0.txt
[valassia@uan03 bash] ~/GPU2023/madgraph4gpuX/epochX/cudacpp >
…ance, now "ok" or as good as it gets (gqttq fails with expected madgraph5#806)

 ./tmad/teeMadX.sh -ggttg -gqttq +10x
@valassi valassi changed the title WIP (postponed to after 801) update the mg5amcnlo submodule to the latest commit in branch gpucpp update the mg5amcnlo submodule to the latest commit in branch gpucpp Feb 1, 2024
@valassi valassi marked this pull request as ready for review February 1, 2024 18:20
@valassi
Copy link
Member Author

valassi commented Feb 1, 2024

Hi Olivier, in the end it was easier for me to do this one first.

I upgraded mg5amcnlo to the current (well yesterday's) gpucpp branch, have regenerated the code and run all tests.

If this is ok for you I would go ahead and merge.

Apart from generated code and test logs, there are no changes other than that in MG5aMC/mg5amcnlo.

It should be a trivial change, but still please approve it ;-)

Thanks
Andrea

Copy link
Member

@oliviermattelaer oliviermattelaer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perfect thanks

@valassi
Copy link
Member Author

valassi commented Feb 2, 2024

Thanks a lot Olivier, now merging

@valassi valassi merged commit 94df524 into madgraph5:master Feb 2, 2024
57 checks passed
valassi added a commit to valassi/madgraph4gpu that referenced this pull request Feb 2, 2024
…raph5#801 and gpucpp PR madgraph5#811) into rocrand

Fix conflicts here (plus some in gg_tt.mad fixed by checking out rocrand version)
	epochX/cudacpp/CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/madgraph/iolibs/template_files/gpu/check_sa.cc
	epochX/cudacpp/tput/allTees.sh
	epochX/cudacpp/tput/throughputX.sh
valassi added a commit that referenced this pull request Feb 2, 2024
valassi added a commit to valassi/madgraph4gpu that referenced this pull request Feb 5, 2024
valassi added a commit to valassi/madgraph4gpu that referenced this pull request Feb 5, 2024
…nd maybe more) ** rerun 18 tmad tests on itscrd90, all ok

STARTED AT Sat Feb  3 07:02:02 PM CET 2024
ENDED   AT Sat Feb  3 11:20:09 PM CET 2024

Status=0

24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_eemumu_mad/log_eemumu_mad_m_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttggg_mad/log_ggttggg_mad_m_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttgg_mad/log_ggttgg_mad_m_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggttg_mad/log_ggttg_mad_m_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_ggtt_mad/log_ggtt_mad_m_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_d_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_f_inl0_hrd0.txt
24 /data/avalassi/GPU2023/madgraph4gpuX/epochX/cudacpp/tmad/logs_gqttq_mad/log_gqttq_mad_m_inl0_hrd0.txt
valassi added a commit to valassi/madgraph4gpu that referenced this pull request Feb 5, 2024
…dgraph5#801 and gpucpp PR madgraph5#811) into makefiles

Fix conflicts in epochX/cudacpp/CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/madgraph/iolibs/template_files/gpu/cudacpp.mk
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants