Last week, a <new version of samtools> dropped. Ho...
# team-maintainers
m
Last week, a new version of samtools dropped. However, this release changes the default cram version to v3.1, which is currently incompatible with a lot of downstream tools (GATK/Picard for example). We can proceed in two ways now: • hold off updating the samtools modules and samtools/htslib dependent modules until there’s more widespread adoption of cram 3.1 • update everything and place the burden of fixing the samtools args on the pipeline devs (e.g. just add
--output-format cram,version=3.0
) Opinions?
shakefist 2
meow tableflip 3
f
Maybe we can update and open issues / PRs on the nf-core pipelines?
party this 1
m
I like Famke's idea
Maybe a blog post even?
m
I don’t know all the intricacies of every pipelines that use
samtools
in any shape or form, so that might be a very difficult task
party this 1
The blog post might be good idea though. Document the changes needed and just open issues with a warning
👍🏻 1
m
it should be "simple" enough to check, but yeah a blogpost would be easier I guess
r
also need to spread the word for anyone that is using samtools modules externally
party this 2
it has finally come to bite me and I had forgotten about this one.
m
FWIW, the latest HTSjdk supports cram 3.1 (including much faster read/write) and is available in the latest Picard release. GATK still lagging behind though.
m
Half a good news
m
FYI, I’m preparing a bulk version bump for the GATK modules, so the whole cram 3.1 issue should be fixed by updating the modules
🎉 1
A second PR should benchmark the new cram encoding/decoding performance to see if we could drop
samtools
from the
markduplicates
module to streamline the containers
👍 3