paper comments that should become code changes

[mhance]

See some comments especially from Zach: scipp-atlas/mapyde-paper#11. Some of these motivate some code changes, especially the ones near the end starting at Line 413:

• L413: Can they define multiple scripts? How? Or do they need to do this by hand (e.g. tying all their own scripts together with a top-level bash script)?

• L420+: “This is particularly…” — can we set blocks that run both on the Pythia output and on the Delphes output in a single run?

• L432: “The options entry…” — in the other steps where there’s a script (e.g. B.9), can I just provide options in the “script” string? Or do I have to have a separate entry, or even only use the defaults?

• L438: You might specify that muscan.py is a script from pyhf (the pyhf script muscan.py), rather than a script that the user should write (because its name doesn’t appear in the [pyhf] block, I assume this is hard-coded?). If it’s not, then you might be clear about where this is coming from (maybe also up on L90?).

[kratsg]

L438: You might specify that muscan.py is a script from pyhf (the pyhf script muscan.py), rather than a script that the user should write (because its name doesn’t appear in the [pyhf] block, I assume this is hard-coded?). If it’s not, then you might be clear about where this is coming from (maybe also up on L90?).

This is #86.