-
Notifications
You must be signed in to change notification settings - Fork 50
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
Bond constraints #50
Comments
This is the problem that @jchodera is observing with the lack of bond. Parmed does not perceive constraints, and so there is just no bond. I'm going to add the constraint stuff in the next PR. |
Discussed in here. |
Constraint tolerance is a context parameter in OpenMM, no? Is there a good way to deal with this in |
Constraint tolerance is an integrator parameter! |
Oops. Thanks! Still not accessible to |
Are we talking about constraint tolerance or what kind of bond constraints to use? We definitely want to specify what kind of bond constraints to use, but that is permitted already. See this example. Note that these are all changed to |
Constraint tolerance. if np.abs(bond_length-constraint)<constraint_tolerance:
logp_bond = 0.0
else:
logp_bond = -np.inf |
I'm confused. Doesn't for index in range(system.getNumConstraints()):
[atom1, atom2, r] = system.getConstraint(index) |
Yes, I know that. I can tell which bonds are constrained. The problem is comparing the constraint to the actual bond length, and determining whether that difference is within the tolerance. |
if we did something like if np.abs(bond_length-constraint)==0.0:
logp_bond = 0.0
else:
logp_bond = -np.inf it would probably fail every time. |
Concluded that we will assume constraints are iterated to convergence, so if there is a bond constraint, we will use a logp of 0.0. Resolved in #113 |
What are we doing about constrained bonds at the moment?
We obviously have to make sure not to try to convert constrained bonds to unconstrained bonds.
If we only deal with hydrogen constraints, does our current MCSS atom matching algorithm ensure we will never map a bond that changes constraint status in old/new topologies as atoms that should be retained?
Also, we will screw up if we draw a bond length from a harmonic X-H bond length distribution and then apply constraints that change the bond length. We need to make sure to fix those bond lengths to the constrained bond length in the geometry engine.
The text was updated successfully, but these errors were encountered: