simple and transparent scheme to define required input files and outputs from a simulation
Ideally required files are not derived from tag names but from the HAWC2 input file (using an HAWC2 wrapper/reader). Could be related to issue #37 where special tag names might be defined for input and output files.