@gjharsha, shall we do some (i) renaming on these classes before the code gets complicated? Naming files as scenarios would be the kind of thing Dr Sen might complain. Some names that I can think of are ScenarioInput, StochInput, ScenarioSets, ...
Also, is it possible to have these files in their own, say StochInput, folder? That way, the file reader can only focus on the subdirectories under the StochInput folder. This may come in handy, as we may need to produce multiple outputs per run, and these outputs might be placed in a solution directory, which should not be read by the Stoch reader.
@gjharsha, shall we do some (i) renaming on these classes before the code gets complicated? Naming files as scenarios would be the kind of thing Dr Sen might complain. Some names that I can think of are ScenarioInput, StochInput, ScenarioSets, ...
Also, is it possible to have these files in their own, say StochInput, folder? That way, the file reader can only focus on the subdirectories under the StochInput folder. This may come in handy, as we may need to produce multiple outputs per run, and these outputs might be placed in a solution directory, which should not be read by the Stoch reader.