How much source code to keep?
Current gridpacks have a clean script that allows to remove the various source code.
Maybe have 2 modes:
- normal one
- autoclean one: automatic cleaning of not-needed source code
What about a gridpack mode on the same level of output/launch?
Something like output gridpack where it will just go directly to launch.
Or maybe launch --gridpack where it will immediately deactivate stuff like MadSpin or reweight which would not be included in the gridpack anyway.
Experiments
Target the smallest possible size: only to ship it to a cluster, generate events and that's it.
We don't need to provide ways of recompiling the code.
What about MadSpace?
3 modes:
- system-wide
- copy the already compiled MadSpace from the local process folder
- include the entire source code inside the gridpack for maximum portability
In general, if MadSpace will be installed within the tools that experiments are using, then it will be very easy to link it to the gridpack.
How much source code to keep?
Current gridpacks have a clean script that allows to remove the various source code.
Maybe have 2 modes:
What about a
gridpackmode on the same level ofoutput/launch?Something like
output gridpackwhere it will just go directly tolaunch.Or maybe
launch --gridpackwhere it will immediately deactivate stuff like MadSpin or reweight which would not be included in the gridpack anyway.Experiments
Target the smallest possible size: only to ship it to a cluster, generate events and that's it.
We don't need to provide ways of recompiling the code.
What about MadSpace?
3 modes:
In general, if MadSpace will be installed within the tools that experiments are using, then it will be very easy to link it to the gridpack.