Propagation of generator names from jO to skeleton and to log.generate
There was some confusion about how generator names are propagated from the jO file to log.generate
and what logParser
uses in the end.
looking at log.generate from a MG sample:
11:32:32 MetaData: generatorName = MadGraph(v.2.6.5)+Pythia8(v.240)+EvtGen(v.1.6.0)
so I think it’s the non abbreviated names there, because I think we get these directly from the interfaces, e.g. for P8 I think we get it from here: https://gitlab.cern.ch/atlas/athena/blob/21.6/Generators/Pythia8_i/share/common/Pythia8_Base_Fragment.py#L4
BTW I am thinking now: what if someone puts
evgenConfig.generators = [“Unknown”]
I just did that and logParser
doesn’t complain at all.
So I also need to understand whether my assumption is correct that there is actually no control over what goes into
MetaData: generatorName
and we completley rely on what the user puts in evgenConfig.generators, which might be nonsense.
If that’s correct then we have to devise a test to catch things which are not allowed or enforce it in the skeleton?
-
try to run one of the jO but giving an invalid name => does the transform complain? If yes then nothing more to do? -
if the transform doesn't complain we should make it so that it complains -
why is MetaData: generatorName
not the abbreviated form?