we now have the basic assembly under CI (yay!), up through annotation. but I'm wary of adding too many more execution tests on Travis, because they take real time and memory and disk space.
eelpond is all about getting parameters from config file(s) to downstream programs.
so, what about inspecting the command line that is output by snakemake -n as a way to determine if configuration parameters are making it "out" to downstream programs"
we now have the basic assembly under CI (yay!), up through annotation. but I'm wary of adding too many more execution tests on Travis, because they take real time and memory and disk space.
eelpond is all about getting parameters from config file(s) to downstream programs.
so, what about inspecting the command line that is output by
snakemake -n
as a way to determine if configuration parameters are making it "out" to downstream programs"