Closed ewels closed 9 years ago
Better still, get load_runfile_params()
to handle the entire Getopt
processing. Depending on what it returns, the module can return its requirements or execute.
Do we even need to pass @parameters
on the command line? These are written to the run file, which we're already parsing anyway. Might be good to get rid of these..
Done as part of #47 (see PR #56)
At the moment, modules receive most of the information that they need in a positional
@ARGV
array. This is a bit messy and easy to get into trouble with.It would be nicer to use
--flags
to do this instead. However, these flags really need to be processed within theHelpers.pm
functionload_runfile_params()
. Individual modules need to process some flags individually first though (--cores
and--mem
and so on).Can we partially pass the options in the module first and then do the remaining ones in the
load_runfile_params()
function? Maybe this could work?Then minimal module changes will be needed (just the extra config).
This all clears the way to make the summary modules work easier.