-
Notifications
You must be signed in to change notification settings - Fork 77
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
Unaccepted characters after Rfam-database-check #116
Comments
First of all, thank you for your commits in the forked repo, they were quite helpful at least to get rid of the bad characters. I was wondering if there is any way to resolve the Meanwhile, by any chance, have you encountered problems with downloading |
Sadly, I don't know. I'm not familiar with this kind of issue, however it might simply be due to the fasta-files? If the error is in the origin, then I assume it's fine for running the program - however, I finally don't know. I remember this message - if not wrongly remembered - and I think I simply ignored it. However, regarding the second question: I think sadly the best is to have fast internet. In example, with poor internet git clone can be a horror. In case there are disconnections from NCBI-side maybe wait some days or a week. However, in the end a stable and fast connection is required. I downloaded it a my university on a server over days using screen, which allowed me to let the command run and detach my terminal to allow shutdown of my local PC. |
Actually, you are right. As long as the bad characters are gone, it shouldn't be a big deal to have those FASTA invalid warnings. About the second point, in fact, I also run the tmux session as running nohup on the background didn't help initially:
It is so strange that even with timeout of 1 hour, running the attached session disconnects after 1-2 hours. The output keeps telling that
Did you have any specific installations by any chance or running this perl script after maybe downloading MoreUtils or other library was sufficient? |
Also, on top of the installations part, did you have any issues with downloading all the necessary packages for running RF2NA? Maybe any specific blast versions were necessary or any other specificity |
I encountered the error "assert (np.all(msa<=31))" when running the program sometimes. It seems that after checking the Rfam-database some annotations contain like an R, which is unknown within the RoseTTAFold2NA-RNAalphabet. I circumvent this problem by writing characters to an N. The code is in my forked repository in case someone encounters the same problem.
Thanks for the model!
The text was updated successfully, but these errors were encountered: