Hi Amber Developers,
We have a user running into the above error while using Amber16. I understand it could be due to a problem with the simulation/calculation itself and we're working with them to debug the problem. However, I think several other Amber users on the mailing list have previously come across this thread [1] in the developer mailing list archive. Any chance you can make the mentioned 'workaround' available publicly? The bugzilla link appears to be private. It'd be helpful to know if this workaround might be applicable to our user's situation.
Thanks,
Marty
[1]
http://dev-archive.ambermd.org/201612/0002.html
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Tue Jul 10 2018 - 17:00:03 PDT
