You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the same/related issue I've previously asked in the prankweb page however I thought it was useful to ask here as well. cusbg/prankweb#142 (comment)
I am trying to use p2rank to predict pockets for a bunch of proteins but I noticed there are different results compared to the web server. I.e. if I go to the web server and use the "predicted structure" and input a uniprot ID, it seemingly gives different results compared to if I download the AF model from uniprot, and then run that on p2rank.
Similarly if I download the AF model and submit as custom structure to the web server, it gives same result as the standalone p2rank.
Is the web server over/underestimating pocket probabilities? Please see below for an example using A0A644EZV9
Using "predicted structure" on prankweb
Using "custom structure" on prankweb, same results as running standalone p2rank
The text was updated successfully, but these errors were encountered:
This is the same/related issue I've previously asked in the prankweb page however I thought it was useful to ask here as well.
cusbg/prankweb#142 (comment)
I am trying to use p2rank to predict pockets for a bunch of proteins but I noticed there are different results compared to the web server. I.e. if I go to the web server and use the "predicted structure" and input a uniprot ID, it seemingly gives different results compared to if I download the AF model from uniprot, and then run that on p2rank.
Similarly if I download the AF model and submit as custom structure to the web server, it gives same result as the standalone p2rank.
Is the web server over/underestimating pocket probabilities? Please see below for an example using A0A644EZV9
Using "predicted structure" on prankweb
Using "custom structure" on prankweb, same results as running standalone p2rank
The text was updated successfully, but these errors were encountered: