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
I was thinking we could set the distance-based building to be even more flexible, and I see some use cases where the current code won't perform correctly. I think we should also allow the user to define a set of atoms (or a single atom) as the center of the sphere.
this would allow a user to define a specific seed atom as the geometric center. In the case of phosphoryl transfer reactions, we might want to define the center as just the phosphorous atom of the substrate, rather than the center of mass or Cartesian mean of the entire seed.
The user could define the geometric center as being a point between two residues. For example in TJ's hydrogenase case, we might want to define the center as being the average Cartesian coordinates of the S and N atoms that are undergoing the proton transfer, rather than the giant seed we defined in that project.
This is the kind of thing we can discuss in the software paper, without having to run any new QM-cluster model calculations. We could look at model composition of all the different permutations of distance-building options and see if anything actually changes. This is a hypothesis that has never been analyzed or tested in the community.
The text was updated successfully, but these errors were encountered:
I was thinking we could set the distance-based building to be even more flexible, and I see some use cases where the current code won't perform correctly. I think we should also allow the user to define a set of atoms (or a single atom) as the center of the sphere.
This is the kind of thing we can discuss in the software paper, without having to run any new QM-cluster model calculations. We could look at model composition of all the different permutations of distance-building options and see if anything actually changes. This is a hypothesis that has never been analyzed or tested in the community.
The text was updated successfully, but these errors were encountered: