-
Notifications
You must be signed in to change notification settings - Fork 13
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
Read sequences don't have overlapping with gene, but eachoverlap() reported there're. #75
Comments
Copying from Slack
|
Hi Kevin, Unfortunately, I haven't solved the issue: how to check overlapping between a feature and the sequences aligned (or check if a feature is located within gaps if there're). Why I'm interested in this, if a feature isn't really aligned by reads, these reads are not from the feature. I may have to parse CIGAR string to get the coordinates of alignment blocks. Dose XAM.jl (or other package) have a function for this? Thanks! BYW, I've asked the question on Slack. I commented here for others who will probably encounter the issue as well. |
We have some CIGAR functionality in BioAlignments.jl and some in XAM.jl. @jakobnissen recently started https://github.com/BioJulia/CIGARStrings.jl, but I think that's just a prototype |
aln = BAM.alignment(r)
BioAlignments.Alignment:
aligned range:
seq: 0-141
ref: 198265943-198266049
CIGAR string: 77M1I2M1I3M2D22M35S
julia> aln.anchors
9-element Vector{BioAlignments.AlignmentAnchor}:
AlignmentAnchor(0, 198265943, 0, '0')
AlignmentAnchor(77, 198266020, 77, 'M')
AlignmentAnchor(78, 198266020, 78, 'I')
AlignmentAnchor(80, 198266022, 80, 'M')
AlignmentAnchor(81, 198266022, 81, 'I')
AlignmentAnchor(84, 198266025, 84, 'M')
AlignmentAnchor(84, 198266027, 86, 'D')
AlignmentAnchor(106, 198266049, 108, 'M')
AlignmentAnchor(141, 198266049, 143, 'S') |
As shown, the gene "ENSMUSG00000080478.1" wasn't mapped by any read, though there're reads mapping to a nearby multi-exon gene "ENSMUSG00000041560.12". In fact, the first gene is located in one intron of the second.
Please help address the issue. Thanks!
The text was updated successfully, but these errors were encountered: