-
Notifications
You must be signed in to change notification settings - Fork 5
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
An error (related to rule concat_deepSea) when running https://deeprvat.readthedocs.io/en/latest/annotations.html#running-the-pipeline #117
Comments
hi @pichuan, it looks like your |
Hi @Marcel-Mueck , (1) I'm still running through the example input data. At this point, I've finished running https://deeprvat.readthedocs.io/en/latest/preprocessing.html. And according to the documentation there, I believe these were the output from the preprocessing pipeline:
(2) Here is what's in my deeprvat_annotation_config.yaml:
Actually, at this point, I haven't modified deeprvat_annotation_config.yaml, so it's exactly the same as the original version. I know I'll need to comment out lines like spliceAI and primateAI etc because I won't be using them. I'll do that soon! (3) I don't know exactly what the
Looking a bit closely, I wonder if this line in the deeprvat_annotation_config.yaml file doesn't match the file structure above?
Did I do something wrong in my steps, or is this something that you should update in the example documentation as well? Thanks! |
linking #118 |
Hello @pichuan, the PR #118 is merged now. I corrected some path of the annotation config file: I also updated the docs, so when you want to run the example data, I can recommand checking this part: |
Thank you! On the same machine, I get the latest version of the code. I reran the preprocessing step first, and then: I have this at the end of my yaml file:
Then I ran this command, and got this error:
Which seems to say that my I did a search in my directory, and didn't find a filename like that:
I can try to get a new machine and completely from scratch. Do you think that would solve the problem? Thanks! |
Hi @pichuan, looks like the |
Thanks @Marcel-Mueck ! I downloaded that in the preprocess step, but didn't quite realize it wasn't pointing to the same one. Thanks for pointing that out. I found it here:
It seems like I already have the GTF file:
For convenience, I just did:
Then I ran this again:
This time it made a bit more progress. This one failed:
From the command above, I wonder if it requires
This time it failed with:
Then I tried to directly run that command:
But it told me: I'm pretty sure previously I installed that on this machine. I'll go back and check. I'll let you know how it goes. But if it's clear what I'm missing here, please let me know. |
I went back and checked:
Here is the full log from my attempt in step 3:
Any advice for me to run that step correctly? Thank you! |
Looks like it could have something to do with this pytorch bug. Could you run |
Here is what I have:
Any suggestions on how I change the mld version in that environment? I searched for the files under the directory, but it seems like it was not explicitly set in any config files there:
|
I tried this manually:
which now seems to work:
I'll keep going from here. It'll be nice to figure out how to have this fix in a config file, or as a step that I write into a script. I guess - worst case I could just write down what I did in a script. (For context: My hope here is that I can write all the steps in a script, so that eventually I can use this to automatically set up a machine, and eventually so that I can scale this to run on more files automatically (bring up instances, point to an input, set up the environment, etc all through just one script)) |
Worklog:OK, now I'm got around the pytorch error, I ran this command again:
Here is a next blocker:
When I ran that command directly, I got this error:
I searched for it:
Not exactly sure why, but the path is different. So I did:
and try this again:
Still seems to have a few errors:
I ran this directly, and got a few more messages that's useful to follow up on :
It seems like I don't have
Try again:
So, I think next I'll need to install AlphaMissense. I'll try that and see if I can proceed. |
Worklog : install AlphaMissenseI went back and did this:
I went through the steps, and made sure to install this Plugins this time:
Log:
Trying again:
This is when I realize the problem is where the Plugins is located. Instead of
while doing that, I think this path also looks wrong:
So I changed that too:
Try the
Hmm, when I install AlphaMissense earlier, it did say that so I did:
OK, now I tried again:
Still having some error at the
Here is the error:
@Marcel-Mueck : question for you: Is it clear to you what this latest error indicates that I'm missing?
Thank you! One follow up on this: After reading Ensembl/ensembl-vep#1716 , I tried adding @Marcel-Mueck : I'd love to know your thoughts on whether using |
Dear @pichuan regarding the alpha missense plugin data, the link you got the data from looks correct, it looks like the same link as in the annotation docs: https://deeprvat.readthedocs.io/en/latest/annotations.html#requirements (under AlphaMissense). |
Thanks. In my case, somehow my cache directory is repo_dir/ensembl-vep/t/testdata/cache, so I did:
Now I have:
After that, I was able to run the following command without
Thanks. Now I'm having a different errors in the |
Hi,
When I'm running this step in https://deeprvat.readthedocs.io/en/latest/annotations.html#running-the-pipeline:
I got this error:
It seems like the usage here is missing one flag. Specifically, when I ran that command, I got:
I searched a bit, and found that in the
../../pipelines/annotations/deepSEA.snakefile
file, there is this rule:For whatever reason, it doesn't seem like I have the
deepSEAscoreFiles
, which I assume should be generated by a previous step(?).So far I'm still only running through the documentation steps, so I'm not using my own VCF input files yet. (And I did already go through the preprocessing pipeline.)
If you know what I might be missing here, please let me know. Thank you!
The text was updated successfully, but these errors were encountered: