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

Protein property prediction code #2

Open
Tian-science opened this issue Oct 7, 2024 · 4 comments
Open

Protein property prediction code #2

Tian-science opened this issue Oct 7, 2024 · 4 comments

Comments

@Tian-science
Copy link

Nice job you have done! I noticed in your article that you have done some work on protein property prediction. Could you please upload the code for this kind of task, or give me some advice on how to modify the code?

@kxz18
Copy link
Collaborator

kxz18 commented Oct 9, 2024

Hi, it should be similar to graph classifier if the property is discrete. Or affinity predictor if it is continuous. The protein property prediction problem in the paper further utilizes IEConv layers for fair comparison with the baselines, which is not the contribution in our model, therefore I chose to not include it in this repo.

@Tian-science
Copy link
Author

Thank you! Could you please give me some advice on how to pre-process the single protein data (the embedding process),
and what the parameters in config file (like the xx.json one in scripts/exps/configs/xx/), so I can do some experiments on it?

@kxz18
Copy link
Collaborator

kxz18 commented Oct 11, 2024

For the data processing, it should be similar to the processing of PDBbind, except that there is not small molecule ligand here. But you need to adjust the saved information (i.e. affinity) to the property score according to your needs. As for the config, it should be like the PPA config. Further, you need to manually specify the type of dataset (either using existing ones or defining your own class) in train.py based on the task name. However, if you are already working on some projects for protein property prediction, I would advice integrating the cleaned model into your coding framework, which might be easier to develop.

@Tian-science
Copy link
Author

Thank you!

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