-
Notifications
You must be signed in to change notification settings - Fork 44
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
Missed call - not clear why #491
Comments
Hi,
Also, from the one junction that you provided the results, it's hard for us to understand what might be happening. Can you provide the output of the |
Sorry, none of these work. I'm getting these errors:
|
Hi @gevro, do you have any updates on this issue? You could maybe try again with DROP 1.4.0. I suspect this would fix the issue with |
We reran with 1.4.0 and we will check to see if it is now detected. |
We checked and this splice event is still missed in drop 1.4.0. |
Then let's try to redo the results section and see what's going on. First, read in the fds object:
And check the metrics for the junctions that are missed. This time probably it will run through since you updated DROP as opposed to the previous try one year ago. Let us how how the results looks like! |
What R libraries do I need to load to run this? |
only FRASER |
Which RDS object? ./processed_results/aberrant_splicing/datasets/savedObjects/GTEX100--v32/fds-object.RDS |
Getting errors
|
Ok, figured out how to pull out the data. Here is the data for that junction. Why wasn't this detected? It is very obvious in the raw reads. Note, I redacted the location of the splice junction and sampleID and hgncSymbol. I can e-mail separately if helpful.
|
Hi,
We did RNA-seq on a sample on which we know there is a very clear and strong splicing defect, as a positive control for the DROP pipeline.
The exon skipping is very obvious:
However, DROP did not detect it.
Here are our config parameters:
Here is the call in results_gene_all.tsv, but it was not in the final FRASER output:
Can you help us understand why this did not get into the final call set and how we can fix this?
Also would appreciate to know if there is a fix, how we can do that without rerunning the whole pipeline, which takes a long time.
Thanks
The text was updated successfully, but these errors were encountered: