Potential support for CRAM input

[HudoGriz]

Hello ClinSV team!

Great software, we include it regular in our new workflows!
We would like to re-analyse old data, but the alignments are compressed in CRAM files. We are sure that there are more labs which keep the data as CRAM (less space than BAM), so we suggest including CRAM files as optional input files.

Keep up the great work!

Blaž Vrhovšek

[melnel000]

Thanks ClinSV for sharing this pipeline. I am about to try it out but I also need to uncompress my CRAM files to BAM so CRAM support would be a great feature.

[drmjc]

Hi, thanks for the great feedback.
Adding seamless support for different ref genomes is at the top of the list, but I agree this will be a useful feature to add

[HudoGriz]

@melnel000 out of curiosity, did you manage to run the analysis on converted files?
For me CNVnator fails on converted BAM files. The conversion was done using Samtools: samtools view -b -T <refgenome.fa> -o <file.bam> <file.cram>.

[melnel000]

@HudoGriz yes, I could run on the bam files without issues and some of these were converted using samtools.

[cluhaowie]

Hi, all I just have the same suggestion with the cram file and see people have already posted it earlier. Wonder if it's any update?

[drmjc]

Hi, thanks for the feature request. It's a very sensible one. We've just switched to cram too so this has got a chance of getting done, but we'll need to assess how much work it'll take to implement this, so I don't have a timeline for you. Cheers

…

On Fri, 13 Jan 2023, 3:15 am HDu, ***@***.***> wrote: Hi, all I just have the same suggestion with the cram file and see people have already posted it earlier. Wonder if it's any update? — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEQQM3SU456ZJ74KF7J66DWSAUY5ANCNFSM5T334TLQ> . You are receiving this because you commented.Message ID: ***@***.***>