Improve extraction of runArgs.inputGeneratorFile from jO

Changes introduced

• Instead of checking for the presence of runArgs.inputGeneratorFile we execute the jO to see if runArgs.inputGeneratorFile gets assigned a valid value or if it is None

Tests

jO submitted in !637 (merged)

PASSES

Using runArgs.inputGeneratorFile = "a"

ERROR

Using #runArgs.inputGeneratorFile = "a" (commented string)

PASSES

Using runArgs.inputGeneratorFile = a (where a is an undefined value in the jO)

PASSES

Using runArgs.inputGeneratorFile = a,b (where a,b are two strings previously defined in the jO)

For instance in the jO I put:

a="a"
b="b"
runArgs.inputGeneratorFile = a,b

ERROR

Issues resolved

Closes #120 (closed)

changed milestone to %S2.2020

added new feature label

added 13 commits

• d0d320cd...ded66f24 - 4 commits from branch master
• 965e3f1d - tW Diagram Subtraction (1,2) aMC@NLO+MadSpin+Pythia
• 6c3cd4e9 - removing redundant files [skip athena]
• a809bc39 - tW Diagram Subtraction (1,2) aMC@NLO+MadSpin+Pythia
• 6746687a - removing redundant files [skip athena]
• 79a405cb - =workaround to fix bug when reading lhe file [skip athena]
• 2c563d39 - =SUSY-inspired handling of tarfiles [skip athena] [skip modfiles]
• 0b974a57 - Fix runArgs check
• 9ca34fe2 - Make jo_utils more generic
• fd69fe62 - Restore changed files

Compare with previous version

approved this merge request

merged

Thanks!