-
Notifications
You must be signed in to change notification settings - Fork 63
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
Splicing doesn't appear to be handled correctly? #534
Comments
Thanks for finding this @choosehappy! What is the expected output you intend to see in the popup? I believe the code you are looking for can be found in the getOpInfo function, which parses the cigar string. Is this what you are looking for? We would love any contributions! The best way to get started would be to make a unit test in pileup utils , simulate a Alignment with a similar CigarString, and then test the modified getOpInfo function. |
this is an example of one of the reads:
The main point is to look at the cigar string: 115M8933N5M1S It looks like the "8933N" is counted as a coverage, when in fact it should not be I can verify this by looking at the pile up:
looking at that particular location shown above:
this is what the bases look like:
which coincides with these counts:
so, i would expect the pileup.js pop up to say: 909 A While in fact all of the ">" are being bundled into the "A" Do you see what i'm saying? |
By the way, this is the entire pileup line for that point:
so pileup.js is reporting the coverage is "5173 " when really it should be 910, with 909 being "A" and "1" being G |
I have a BAM file which looks like this in IGV:
Note the splicing
plotting the same with pileup.js looks like this:
What is interesting is if i click on a location, this is the readout:
Which means i suspect that when pileup.js encounters an "N" in the cigar string, it simply adds a count to the last item in the bin.
I can't readily see where to correct that, but ifyou could point me in the right direction, i'd be happy to take a stab at correcting
thoughts?
The text was updated successfully, but these errors were encountered: