Currently, users can specify an AlphaFold DB structure only by UniProt ID (for example, Q5VSL9), not by AlphaFold DB ID (for example, AF-Q5VSL9-F1-v6).
As a result, there is currently no way to run PrankWeb automatically on multimer complexes recently added to AlphaFold DB.
Example entry:
https://alphafold.ebi.ac.uk/entry/AF-0000000066503175
We should allow users to enter AF-0000000066503175 (or AF-0000000066503175-v1) and get an ad hoc or precomputed prediction for that exact entry, and possibly for that exact version.
Open questions
- Should version suffixes be accepted as part of the input and stored as part of the ID?
- What should be served if the user enters
AF-Q5VSL9-F1-v6, but the latest precomputed version is AF-Q5VSL9-F1-v4?
- If precomputed predictions are stored under AFDB IDs (with or without version), what should be served when the user enters only a UniProt ID?
Context
Currently, users can specify an AlphaFold DB structure only by UniProt ID (for example,
Q5VSL9), not by AlphaFold DB ID (for example,AF-Q5VSL9-F1-v6).As a result, there is currently no way to run PrankWeb automatically on multimer complexes recently added to AlphaFold DB.
Example entry:
https://alphafold.ebi.ac.uk/entry/AF-0000000066503175
We should allow users to enter
AF-0000000066503175(orAF-0000000066503175-v1) and get an ad hoc or precomputed prediction for that exact entry, and possibly for that exact version.Open questions
AF-Q5VSL9-F1-v6, but the latest precomputed version isAF-Q5VSL9-F1-v4?Context