upload plugins upstream to mg5amcnlo

[valassi]

upload plugins upstream to mg5amcnlo

this is around points 2 and 3 in #576... it is maybe a bit of a new idea, as discussed one month ago

we should make sure mg5amcnlo knows where to find the cudacpp and sycl plugins (probably from two repositires in mg5amcnlo)

[valassi]

Hi @oliviermattelaer (and @roiser @hageboeck @zeniheisser @Jooorgen ) this will come at some point.

Any suggestions?

• name of the repository? https://github.com/mg5amcnlo/cudacpp_plugin ? or https://github.com/mg5amcnlo/CUDACPP_PLUGIN ? or https://github.com/mg5amcnlo/CUDACPP_OUTPUT ?
• how should this look like inside the mg5amcnlo on disk? presently it is /PLUGIN/CUDACPP_SA_OUTPUT, but definitely the SA does no longer make much sense... how about PLUGIN/CUDACPP_OUTPUT? (I imagine that then I need to modify this line

  madgraph4gpu/epochX/cudacpp/CODEGEN/PLUGIN/CUDACPP_SA_OUTPUT/__init__.py

  Line 31 in f24bfbd

  import PLUGIN.CUDACPP_SA_OUTPUT.output as output

  ?)
• I guess that eventually maybe we need some hook to automatically download it? we can always tell people to do it manually to start with... but if you do think of an automated mechanism, maybe we need a naming convention? or Olivier you were just thinking of adding a database in mg5amcnlo, "if a strange plugin is required and you do not have it, look in this database if the plugin is declared to exist in a github repo...'?)

In practice, Olivier can I create the new repo?

Thanks
Andrea

[oliviermattelaer]

Hi Andrea,

So my point of view is that as long as we use PLUGIN and that we do not want to ship them with MG5aMC.
Then the solution is to use the "install XXXXX" feature of MG5aMC.

On the madgraph repo itself, the only think that we need to do is to add XXXXX to the list of supported tools.
The rest of the handling (where to get the code/...) is done inside another code/repo (HEPToolsInstaller).

I personally care more about the name that we use for XXXXX that the name of the directory that we put in the PLUGIN directory and/or the name of the repo.
My suggestion might be to use two name for the XXXXXX, one suggestion would be
LO_SIMD
LO_CUDA
Then both can install the same plugin directory which can be CUDACPP or CudaSimd

@valassi Yes you can create the repo.

Cheers,

Olivier

[valassi]

This is now almost completed.

• I have created the separate repo https://github.com/mg5amcnlo/mg5amcnlo_cudacpp which includes the plugin. (I need to add some doc and scripts here and there to say how to sync it from the plugin dir in madgraph4gpu, for th efew months we'll keep that around)
• I need to create cudacpp as a git submodule of mg5amcnlo itself

[valassi]

Note, MR #752 is related to this, as the grand plan for recursive git submodules.