In order to increase readability of code, we should remove arguments/options that are set to the tools' default settings (and can't be changed by the user) from the shell calls within rules.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
Since we have a reasonable integration test, I think that's a great idea. If, however, we didn't have good tests, it would mean that bumping a tool's version (e.g., because of some bug/security issue) might have obscure side effects, because default values may change. Probably not a bad idea to set up another integration test with real data that we should manually run whenever we bump the version, just to make sure all of our tools still give expected results.
I have removed all default arguments for now, however, we should probably discuss more about how we make our choices of fixed arguments visible to the user. E.g. would it be better to retrieve ALL parameters from the config, for example by having a config template that already contains our fixed parameters. Experienced users could then change those parameters without having to change the Snakefile. Moreover, we could provide kind of a blank parameter for each tool in the config, where experienced users could specify additional parameters that we are not using by default as a string. This bears some dangers though in terms of conflicting parameters that wouldn't be checked.