-
Notifications
You must be signed in to change notification settings - Fork 34
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
Distance prediction treshold #4
Comments
Hi, Answering to your question: since we were training in frames of 200x200, I couldn't find a better way for the model to "ignore" the padding than converting it into a classification problem and giving that cclass a very little value. |
To add my opinion to the mix. When you predict a distance you need a degree of uncertainty associated with the prediction to use it effectively as a constraint. Predicting distances in bins is a useful way to do this. It is unclear how you would train a system that predicted distance and an uncertainty value together. Also, distance predictions above a certain threshold (perhaps 20 Angstrom) are not accurate when using covariation data, as they just tell you the residues are not close in the protein. You wouldn't want a strong constraint on that. Predicting into distance bins lets you have a catch-all last bin that takes account of this. |
Ok Thank you ! Now it make sense for me. |
The threshold values are an arbitrary decision (although some constraints may apply), so they could be replaced with some other ones. |
How do you choose the value of the weighted_categorical_crossentropy for the loss function used in the distance prediction model? |
Trial and error with different valules. You're encouraged to share your weights if you find a combination which produces better results! |
Hello,
Nice work !
In the notebook predicting_distances,
Why did you want to predict classes of distances, instead of distances values directly ?
The text was updated successfully, but these errors were encountered: