-
Notifications
You must be signed in to change notification settings - Fork 16
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
weird encoding for reference name #66
Comments
Hi! could you share the bamfile / part of the bamfile that leads to this? Or paste in the bam header output from samtools when used on that bamfile as well. |
I'm experiencing the same issue with a few different references I'm trying to get perbase to work with:
Here is my bam file header:
I've also noticed that if I supply the reference fasta file in my
As far as I can tell, there is nothing wrong with either my reference fasta file or the input bam file. Other programs (samtools, bwa, bbmap, etc.) don't report any issues with them. Any idea what the problem could be? I'm happy to share the full fasta and/or bam files if it would be useful. Best, |
If you had a minimal example with a bamfile and reference that would be awesome! I'm really not sure what the issue is. This function is what would generate the ref_seq name, which in these outputs looks very mangled (breadcrumb for myself looking at this again later) |
Sure thing. The reference is very small (~10 Kb) and I've extracted a subset of 10k BAM entries that produce the weird results. Thanks for taking a look! Best, |
Quick update - I reinstalled the latest version of perbase, and I'm no longer seeing the same errors on the exact same reference fastas and bam files. I don't know what caused the issue in the first place, but it's working now, so I'm happy! :) Thanks! |
@sstadick Sorry for the delay here! @davidecarlson thanks for chiming in as well. I installed |
@davidecarlson I'm glad that worked! |
I am having a similar issue with the latest version (0.10.0). The REF encoding is weird... It is as expected at first, then it suddenly changes, then it flips back to normal. It does so a few times on my bam. The bam file appears to be ok.
This is a section of the output file showing the sudden change in the REF column:
If I run
with the RUST_BACKTRACE set to 1 I get:
and with the full backtrace:
|
I'm trying to run
perbase depth-only in.bam
and I am getting the following output:The bam file isn't corrupt (according to
samtools
) and works with other parts of my pipeline.This reproduced when running
base-depth
as well, and replicated by other users.Running
perbase v0.8.5
Please let me know if I can provide any more information!
The text was updated successfully, but these errors were encountered: