-
Notifications
You must be signed in to change notification settings - Fork 2
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
About rmats_long.py #26
Comments
Ideally the espresso run would include all of your samples and the It's not easy to merge the results from multiple espresso runs since the novel isoforms detected would have different IDs ( |
Sorry,,,, I have an additional question. We would appreciate your advice.
|
It looks like the main error was:
I was able to run FindAltTSEvents.py for those two transcripts based on the gencode v46 gtf and got this output:
I don't know why that command would get a SIGKILL. It may have been due to something else happening on your system. If you run rmats_long.py again do you get the same error for the same two transcript IDs? |
If you run rmats_long.py again do you get the same error for the same two transcript IDs? Yes, Can I remove it? transcript1 transcript2 event coordinates When this ID is reached, the system suddenly stops. |
If you replace Then if you run the |
Hello,
I've completed the analysis with ESPRESSO and am now planning to proceed with rMATS-long analysis. However, I generated the .esp and updated.gtf files individually for each sample, so I’m unable to perform a multi-sample analysis. Is it acceptable to merge these files, or should I start the analysis from scratch?
For exmple
How can I output [gs689_1 gs689_2 gs689_3 pc3e_1 pc3e_2 pc3e_3] in espresso like this?
Or should I merge the results output one sample at a time?
The text was updated successfully, but these errors were encountered: