-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZipperBams failed. Error: processed all unmapped reads but there are mapped reads remaining to be read. #978
Comments
Somehow the |
I used STAR to map the uBAM, so the code looks weird, 2)then I extract fastq from uBAM, mapped them using STAR, forgive me that I didn't find ways to mapping one fastq file using STAR.
All commands above runs fine, but After I GroupReadsByUmi, CallMolecularConsensusReads, FilterConsensusReads, and mapping them sencond time, ZipperBams have problem;
STAR alignment code is like it above, and then picard sorted; Tips: using picard sortBam is because I used to use picard mergeBam to merge unmapped and mapped reads; I know the sort_order need to be the same when using picard mergeBam; (why I didnt use samtools sort is that some BAM files didnt support samtools's sort somehow.) |
Did you mean that '/A' is necessary for ZipperBams? And that should be retain whatever I run command on it? |
hello! I'm doing with sequencing data with UMI, I followed #fgbio-best-practise-fastq---consensus-pipeline
When I run fgbio ZipperBams to merge my consensus.ubam and consensus.mapped.bam, there is an exception:
Exception in thread "main" java.lang.IllegalStateException: Error: processed all unmapped reads but there are mapped reads remaining to be read.
and I check my two bam files; they all are queryname sorted, have same number of reads, the difference between them is all of queryname of ubam have suffix "/A". like this:
I found it is caused by fgbio CallConsensusReads...
I wanna know whether this is the problem caused ZipperBams failed, or how to deal with this problem(ZipperBams)?
#my fgbio version is 2.2.2-3a74fd2-SNAPSHOT
The text was updated successfully, but these errors were encountered: