Comment 6 for bug 2001583

Hi,

I have discussed with Marco today, and he is actually using the "add_param" functionality to define such parameters to boolean.

However, to have it working you can not run the code from
./bin/mg5 or ./bin/mg5_aMC
executable
but you have to use the script from the generated directory
./bin/generate_events (or ./bin/aMCatNLO)

The MadSTR binary does prevent you to run the launch command.
But if you do "./bin/mg5_aMC launch MADSTR_DIR"
MG5aMC will think that MADSTR_DIR is a "normal" aMC@NLO directory and will not prevent you
to run it, but it will crash because of the above parsing issue.

So the plan is to add both in LTS and in 3.x version, a check within MG5aMC that separate normal aMC@NLO output from madstr output to ensure that the second type crashed nicely.