Updated workplan (May 2023) towards a first alpha release

[valassi]

This is an updated workplan (as of May 2023) towards a first alpha release. It follows up on and replaces the previous workplan from December 2022 in #576, where several issues have been fixed, but some are still open, and in addition many new ones have appeared.

The plan is essentially that I presented at the dev meeting last Monday in https://indico.cern.ch/event/1288364/

Trying to put things in order (but I also indicate the numbers of #576)

Licensing etc (non technical blocker) - new with respect to #576

• done for cudacpp (Andrea): MR #643

General resync of madgraph4gpu to upstream mg5amcnlo (blocker) - this was in point 2 in #576

• done (Andrea, Olivier): MR #654 fixing "launch" in #629 and cleaning up vector.inc

Relocatable builds - this was part of point 3 in #576, even if not explicitly mentioned there

• todo #613 generated code must build/run outside madgraph4gpu, including:
  • done: random numbers (Zenny, Andrea) in MRs #657, #662, #663, #665
  • todo: google tests, wip (Andrea) in MR #666

Handling of multiple P1/P2/... subprocesses (blocker for this common use case) - part of point 6 in #576

• done (Andrea) MR #560 fixing #644 different nwf values in different P1 directories
• wip (Andrea) MR #668 fixing #667 different npar values in P1 and P2 directories [the patch also introduced and later fixed performance regression #669, register pressure from int vs size_t]

Madevent application cleanup (blocker) - this was in point 3 of #576

• todo #658 fix parameter input, decide on executable names, decide on vector builds (Stefan's WIP in MR #620)

Cleanup of other build issues (~blocker for c++-only builds?) - new added June 4

• wip #679 remove C++ build dependencies on CUDA headers, except where needed

Port post-generation patches upstream (blocker) - this was part of 2 in #576

• todo #656: remove patchMad.sh, patch.P1, patch.common (includes proper generation of coloramps.h)

Test the launch functionality (blocker) - this was point 5 in #576

• todo: performance tests checking gridpack parameters (possible also with gridpacks, eg Stefan's MR #620)
• todo #659 test the fully integrated launch, rather than from gridpacks

Cross check handling of parameters (blocker) - this was point 4 in #576

• todo #660 ensure correct handling of parameters after full "launch" integration

Copy plugins to mg5amcnlo (~blocker: the final blocker step?) - new with respect to #576

• todo #661 create new repos, copy cudacpp and sycl plugins, integrate changes in mg5amcnlo upstream
• todo (Olivier) #867 clean up the gpucpp branch (from mg5amcnlo) to have this plugin integrable mainstream

Cleanup of color (high priority for physics results, but not a technical blocker) - this was point 1 in #576

• todo (Olivier) #655: check 'select_color'
• todo (Olivier): confirm that coloramps.inc is correct (and possibly understand why coloramps.h gives different values in codegen)

Experiment integration (our final goal - to be tested both before and after the release) - ~part of point 6 in #576

• wip (Stefan) #673 test integration in ATLAS gridpack production
• todo #672 test integration in CMS gridpack production

Other physics validation issues (high priority for the experiments, not strictly technical blockers) - ~part of point 6 in #576

• todo #630 cross section mismatch in Fortran and cudacpp for gq_ttq
• todo #678 check that Fortran cross sections and LHE files are the same with and without vector interfaces

SM process-specific issues (high priority for the experiments, not strictly technical blockers) - ~part of point 6 in #576

• done (Olivier) #645 CMS Drell-Yan CKKW
• todo wip (Andrea, Olivier) #628 unary minus on pointers -COUP in FFV calls

BSM process-specific issues (varying, lower priorities) - ~part of point 6 in #576

• todo #616 SMEFT HRDCOD=0 builds fail (BSM only supports HRDCOD=1 currently), high priority for Zenny/Robert
• todo #614 SMEFT HRDCOD=1 builds fail, lower priority but easier to fix than the one above
• todo #627 SUSY HRDCOD=1 builds fail because sin/cos/atan are not constexpr, low priority
• todo #615 exostic SMEFT codegen fails, low priority

[nscottnichols]

@valassi I saw your comment here when I was syncing the sycl branch with the latest cudacpp changes. I am getting the correct value for nwf (at least for gg_tt) using self.matrix_elements[0].get_number_of_wavefunctions() in model_handeling.py. It could be because I added code in generate_process_files() to write CPPProcess.cc before CPPProcess.h.

[valassi]

@valassi I saw your comment here when I was syncing the sycl branch with the latest cudacpp changes. I am getting the correct value for nwf (at least for gg_tt) using self.matrix_elements[0].get_number_of_wavefunctions() in model_handeling.py. It could be because I added code in generate_process_files() to write CPPProcess.cc before CPPProcess.h.

Thanks @nscottnichols ! I opened #677 as a reminder that I could also try to move nwf from CPPProcess.cc to CPPProcess.h. This is low priority anyway - so no longer a blocker for the alpha release - because the main issue was moving nwf from src to P1, and this is done. It would be a nice future cleanup/improvement however.

[oliviermattelaer]

I need also to focus on https://github.com/madgraph5/madgraph4gpu/issues/867 to allow the integration of gpucpp within the 3.6.0 branch of MG5aMC