You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thank you for producing and supporting this tool, it is most excellent!
I have been struggling with a problem that seems to crop up for a small proportion of all the samples I attempting to process, namely the samblaster error below
samblaster: Can't find first and/or second of pair in sam block of length 2 for id: A00351:169:HLCY7DSXX:3:1220:15591:9862
I am running lumpyexpress as
lumpyexpress -B sample.bam -o sample.lumpy.vcf
The analysis-ready, coordinate-sorted sample.bam was generated following GATK's best practices from 16 paired FASTQs. When I look at the region where the error occurred I think I understand what it is complaining about but am not entirely sure
I was hoping to avoid pulling the split and discordant reads prior to input lumpy as I've already processed a couple hundred samples without issue. Is there some other filtering I should apply to sample.bam or should I rethink/reprocess everything to be consistent?
Thanks again,
Jonah.
The text was updated successfully, but these errors were encountered:
Hello, thank you for producing and supporting this tool, it is most excellent!
I have been struggling with a problem that seems to crop up for a small proportion of all the samples I attempting to process, namely the
samblaster
error belowI am running
lumpyexpress
asThe analysis-ready, coordinate-sorted
sample.bam
was generated following GATK's best practices from 16 paired FASTQs. When I look at the region where the error occurred I think I understand what it is complaining about but am not entirely sureI was hoping to avoid pulling the split and discordant reads prior to input
lumpy
as I've already processed a couple hundred samples without issue. Is there some other filtering I should apply tosample.bam
or should I rethink/reprocess everything to be consistent?Thanks again,
Jonah.
The text was updated successfully, but these errors were encountered: