Possible solution
One possible idea would be to enable to provide iVar with some kind of "dummy primerfile" or an empty one or smth and the ivar process should have no effect at all on the data then. However, we tried this at some point already and it always lead to ivar trimming either all the reads or in a very weird way. But it's likely that this behaviour can be changed by using different options in ivar.
Another idea would be to implement some snakemake magic, so that in the absence of a provided primer-file all but the ivar rule is executed.
Relevant codeThis branch already carries a no-ivar version but only trough removing it which only was supposed to be a temporary hackt tough.
Fix is merged now. Although I just noticed the RUN_IVAR_PRIMER_TRIMING var is spelled wrong, and it would have been nicer if that commit was more atomic...
Problem
Sometimes data needs so primer trimming and/or is better of without it. In this case it should be able to skip/bypass the primertrimming step, currently performed by iVar.
Possible solution One possible idea would be to enable to provide iVar with some kind of "dummy primerfile" or an empty one or smth and the ivar process should have no effect at all on the data then. However, we tried this at some point already and it always lead to ivar trimming either all the reads or in a very weird way. But it's likely that this behaviour can be changed by using different options in ivar.
Another idea would be to implement some snakemake magic, so that in the absence of a provided primer-file all but the ivar rule is executed.
Relevant code This branch already carries a no-ivar version but only trough removing it which only was supposed to be a temporary hackt tough.