-
Notifications
You must be signed in to change notification settings - Fork 71
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
Error when running gridss #82
Comments
The BAM file format requires read names to be less than 254 characters (lowest 8 bytes of the bit-packed bin_mq_nl field). When identifying split reads from soft clipped alignments, GRIDSS appends unique alignment identifier containing the segment index, reference contig name, read start position, orientation (+ or -), CIGAR, and offset of this alignment with respect to the read template. Appending this information to your read name appears to have exceeded this read name limit. A short-term fix is the generate your varsim reads with shorter names, I'll work on update to GRIDSS that hashes this information so the read length is bounded regardless of the input data. |
…not exceed the 254 character BAM limit Hashing of split read realignment fastq read names is always done Hashing of evidenceIDs is controlled by the hashEvidenceID configuration option. Default of true reduces file sizes (especially important for long reads as the unhashed value includes the full CIGAR), at the cost of losing human readability of which reads contributed to which assembly.
https://github.com/PapenfussLab/gridss/releases/tag/v1.4.1 should have your issue fixed. |
Thank you for fixing! I just sucessfully re-ran gridss. |
I'm attempting to run gridss on a simulated bam file generated by varsim so that I can assess gridss precision/sensitivity. I'm using the example script gridss.sh (modified with my input bam and reference genome). The same bam file runs fine with other SV software. I am getting an error when gridss runs CallVariants.
The error is below:
The text was updated successfully, but these errors were encountered: