<@U039DEJ1RJS> do you mind checking it out?
# sarek_dev
m
@Matthias De Smet do you mind checking it out?
m
🤔 Does this really warrant a subworkflow?
is just mosdepth and samtools stats
stats
is already included in a million other subworkflows for QC, and that just leaves mosdepth then 🤷🏻
I could agree to some sort of coverage focused QC subworkflow, but this seems too random and doesn’t solve any specific usecase
for example, we could do
BAM_QC_COVERAGE
that includes • mosdepth • samtools coverage • picard/riker (preferably riker, or both, but with an on/off switch) • ....
m
yeah, I was thinking along this way, we noticed we also have a similar subworkflow that is running this one and ngscheckmate
I do think all tools should be with a
.filter { 'mytools' in tools }
on the input data
similarly to how we're doing in #C06PHJM0Y3D /#C01NHS4CC91 / #C05GH685FKJ...
m
would be nice if we could combine all the approaches and then reuse across pipelines
m
That's my plan
Shall we talk about this during the maintainers meeting?
m
Be my guest, but I can’t join 😞
m
ok, no worries
m
School’s out at 1500h and it’s the last friday before the summer holidays
✅ 1