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
Allow input of already p-shifted reads (bigwig) #102
Comments
Thanks for the suggestions. While I do not have immediate plans to support this functionality, a PR is always welcome. |
I have already forked the repo, I think I see how it can be done. Your final processing before ORF prediction is this:
I see the dict is structured like this:
So if I understand correctly, I would need to convert the bigwig (which is split on strand) I then could call the main detection function: export_orf_coverages() I think it sounds good, what do you think? Would you be interested to put it as a separate function in the cli if I make a PR, Would make your already quite fast tool, finish in no time. |
Your understanding is correct. I will just elaborate it below.
In principle, all that needs to be modified is a helper function that enables bigwig -> |
Is your feature request related to a problem? Please describe.
This tool can not input already shifted data, makes it less useful for the community,
since sometimes large bigwig files can be used, which are not possible to fit in a bam file.
Describe the solution you'd like
optional input for bigwig (ORFquant supports this with very little tinkering already)
Describe alternatives you've considered
One alternative is either to use another tool,
or I can also just hack a solution by creating a fork that skips to the step
where you have the alignments as p sites
Additional context
For very large Ribo-seq files (What would have been a > 1 TB bam file etc)
With bigwig, it can be loaded basically instantly.
The text was updated successfully, but these errors were encountered: