-
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
Do you have the plan to add the pileup functions? #51
Comments
The There is a plan to make this easier to query intersection and overlaps with GenomicFeatures v3, which will use the |
However, the |
Oh, I assume you are referring to the Pileup format. Would you provide some references to the functionality/features you are requesting, and we'll see if adding them to this package makes sense? |
A good example is python class |
I agree this would be extremely useful. I don't think we would need to support the pileup format, per se, but provide a pileup iterator. Basically, a pileup iterator on a @kwdef struct Pileup
chr
pos
ref = 'N'
count = 0
reads::Vector = []
mapquals::Vector = []
basequals::Vector = []
end #struct So iterating through a sorted BAM should return a set like [
Pileup("chr1", 1),
Pileup("chr1", 2),
Pileup("chr1", 3),
Pileup("chr2", 1),
Pileup("chr2", 2),
] |
I think part of the ideal solution is to further develop |
I think it would be good to have something like this but it would be even better if it could be made generic enough to accodate things like grouping reads pairs into fragments, e.g if you have to overlapping reads :
A read-wise pileup at position 5 would return [C = 1 , T = 1] while a fragment-wise at position 4 would return [G = 1] while at position 5 [N=1] or [C = 1 if quality of R1 > quality of R2]. Same things for groups of PCR duplicates, possibly using UMIs. For this I think you need 1) a (possibly) user-defined grouping criteria ("take R1 and R2 together"), and 2) a (possibly) user-defined reducing/consensus method to compute the pileup number for the grouped reads. Then the interface would like something like this :
That said it might be difficult to make it generic and efficient. |
That would be a great addition. Here's how I count reference and alternate allele it at the moment (there may be better ways, i'm a beginner in Julia):
Usage:
|
Sometimes,We want to iter bam according to the position not record. So do you have the plan to add the function.
The text was updated successfully, but these errors were encountered: