Open laughedelic opened 8 years ago
Fine for me about doing in the same task: merge, count, assign
Same reasons to merge flash and split step. But this requires having split as a separate step for pipelines that don't need paired-end reads merging.
and this I would also prefer to have it in independent steps so we can work with single reads/scaffolds...
and this I would also prefer to have it in independent steps so we can work with single reads/scaffolds...
what I mean is having different pipelines for these cases:
For paired-end reads:
And for non paired-end reads/scaffolds:
(the difference is only in the first loquat/step).
@marina-manrique @eparejatobes I'd like to get feedback from you, because if you support this suggestion, I want to include it in the next release:
Perfect for me
OK, :+1:
Everybody knows that launching loquats is not so fast and managing the pipeline manually is not convenient at all. So I suggest some simplification to the pipeline.
So I suggest to merge these three steps in one loquat:
Again, this works as task per sample.
Same reasons to merge flash and split step. But this requires having split as a separate step for pipelines that don't need paired-end reads merging.