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

Integrating dMaSIF #1

Closed
linminhtoo opened this issue Apr 21, 2022 · 2 comments
Closed

Integrating dMaSIF #1

linminhtoo opened this issue Apr 21, 2022 · 2 comments

Comments

@linminhtoo
Copy link

Hello authors,

First off, really well written paper & great code base. Enjoyed reading it and managed to understand the key concepts on just the first pass.

As you have rightly pointed out in your paper, dMaSIF is a concurrent work that greatly optimises MaSIF, especially by removing the need for pre-computed features, which is not trivial to set up + slows down inference.

Would you happen to have any intention to integrate dMaSIF into your work?

Or phrased another way, what are the steps needed to accomplish it? I am willing to contribute.

Keep up the great research! (I also really enjoyed GraphRetro, having worked under Connor myself!)

Best,
Min Htoo

@vsomnath
Copy link
Owner

Hi Min Htoo,

Thank you for your kind words, and sorry for the delayed response!

Right now, there are no immediate plans as to integrate dMaSIF into this work.

In my opinion, the following steps are needed to accomplish this integration:

  1. 3D surface generation - dMaSIF uses atomic point clouds as inputs to generate surfaces (their SDF function uses atomic radii), but HoloProt directly uses the C_alpha coordinates in the 3D structure, so the generation would have to account for this fact, by modifying the attributes and coordinates stored in the backbone object.

  2. Mapping between surface and structure nodes - When using MSMS, one of the returned outputs is the residue each surface node is connected to. To integrate into dMaSIF, one would require an additional tensor that tracks the membership between each atom in the protein and corresponding residue, and uses this to assign the corresponding mapping between surface and structure.

  3. dMaSIF convolutions - Right now, the APIs for surface and structure MPNs are consistent and so are the attribute tensors (like x, edge_index, edge_attr etc). This would change a bit with using dMaSIF convolutions, and one would have to account for it. It should also be feasible to create a more hacky solution, but I am usually not in favor of it.

I'll populate my thoughts here if I realize some other issues or considerations with the integration.

Best,
Vignesh

@vsomnath
Copy link
Owner

Closing this for now, feel free to reopen if necessary!

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