-
Notifications
You must be signed in to change notification settings - Fork 18
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
Local Foldseek searches are no longer working #91
Comments
Which commit is this? I did a lot of refactoring today and might have broken something. However, this does looks more like a foldseek issue and not server issue. What are you searching? |
I think I currently have commit 00f89de checked out?
I'm searching one of my structures (a small protein ~ 50 AA) against the PDB structure database as a test that my setup is functional. I've run this search many times with previous commits without any issues but I saw new updates on the foldseek server so re-cloned the repo to implement them locally |
I tested the same sequence on the public server and this ran without error. Is the public server using your latest commits or a previous commit that I could roll back to? |
Did you rebuilt the docker containers or are you using the containers downloaded from GHCR? Can you try to do a (This is the exact setup that the server is using). |
Apologies, I now think that this is relating to my setup. I'm running this inside a Multipass VM (Ubuntu 22.04) and observing the |
I have no idea about multipass, but I've seen issues with SIMD support and VMs before. Make sure you are using whatever "host" cpu mode multipass might offer. It's likely that the VM claims to support AVX2 in the /proc/cpuinfo, however then doesn't correctly expose the instructions. |
Recently cloned the repo again and re-built the PDB database, setting up for foldseek local server.
On docker compose up the server seems functional, however after submitting any job mmseqs-web-worker-1 errors out with the following:
Any clues on what changes could have caused this?
Thanks!
The text was updated successfully, but these errors were encountered: