Closed kool7d closed 1 year ago
So, this was an interesting one. I actually found 2 problems:
So, the first one was actually on the recovery from previous steps. The copy
function was being used instead of ProtoSyn.recoverfrom!
(which makes sure the pose graph and state ids remain connected). I'm not sure but I think somehow this is what was causing the GB problem.
The second one was a wrong negative sign when calculating forces in the distance-based flat-bottom potential restraint employed in the "all-atom clash restraint" component. Atoms were actually being pushed together instead of further apart.
All-in-all, the two fixes I've added should solve this issue. I've also went ahead and refurbished example 4. Take a look at commit 985e0986b80ea40556637df7533d3426449cf7ec, and give me some feedback.
Seems like this issue has been resolved. Closing.
I am getting an error at the example 6 (steepest descent) step:
It gives me what looks like one round.
energy_function(pose)
gives me a value, then I runsteepest_descent(pose)
and it shows an updated number.0 1134.041
is what the output looks like before it errors. I checkenergy_function(pose)
again and it is 1134.041. So I think one round is happening. Also, I remove the all-atom clash with really high energy and get the same error.I am pretty sure I have the dependencies like torch and torchani installed correctly, and I get no warning about anything except SeqDes.
Anyways, the stacktrace looks like: