Skip to content
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

DEEPScreen Supporting Data for Output/results #12

Open
prathameshvalse opened this issue Aug 3, 2021 · 1 comment
Open

DEEPScreen Supporting Data for Output/results #12

prathameshvalse opened this issue Aug 3, 2021 · 1 comment

Comments

@prathameshvalse
Copy link

DEEPScreen gives out results active or inactive.
Is there a data of binding affinity included in it. Also the accuracy of result will be lesser if 2D Image is taken rather than 3D conformation image or SMILES?
Is there a way that we run virtual docking prediction as well which gives out data of Binding Affinity Energy, Binding Site and Size of Predicted Binding Site.

@tuncadogan
Copy link
Collaborator

Thank you for your interest in DEEPScreen.

The actual binding affinity is not included in the prediction since we binarize all training data points as active and inactive before the training procedure. As a result, the model only sees labels as active/inactive and the prediction output is like that as well. In the current version of our tool, we selected binding affinities less than 10 uM as active and the ones greater than 20 uM as inactive, as a result, binarized prediction output reflects these values as well (i.e., an active prediction means that the actual binding affinity between the compound and target on interest should be less than 10 uM). It is possible to change these activity thresholds in the dataset pre-processing step if required (though it requires a bit of coding, we do not have an automated procedure for this yet).

Regarding the second question, we do not have a virtual docking tool incorporated into DEEPScreen. DEEPScreen is designed as a fast tool to scan large-scale compound sets on selected targets before using more targeted/directed methods such as docking and/or MD simulations. DEEPScreen can detect potentially active compounds from very large datasets, on which running targeted methods would be unfeasible. These targeted methods can easily be run on the compounds in a small dataset which are predicted as active by DEEPScreen. In other words, it is possible to run virtual docking on selected compound-target pairs (via a web tool or on a local server) after you get the predictions results from DEEPScreen and select the ones that seem interesting to you. This is the way we imagined DEEPScreen will be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants