-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update imports for python 3 compatibility #3
Conversation
…rmal ints by swig
Wow, that was a lot more work than I bargained for. I fixed a large number of relative imports for things that had been rearranged, and the remaining errors suggest there is still code that isn't working yet:
I'm going to stop here and hand this back to @maxentile to carry forward, since it looks like I've fixed enough to look into the original |
…byte reading/writing
…ng shadow work to avoid initial energy loss for some integrators.
…and velocities at the beginning of each integrator step.
The last two commits fix the problem noted in #12 where it looked like energy was leaking out of integrator splittings that begin with I went a bit overboard and constrained positions and velocities at the beginning of each integrator step just for safety, but this may be unnecessary if we simply ensure to apply position and velocity constraints at the beginning of integration (step = 0). Note that I think we'll need to fix this in the I've also temporarily disabled the solvated alanine dipeptide and modified the parameters for the vacuum alanine dipeptide data collection to ensure the samples were less correlated. This should be ready to merge after #4 is merged, and then we should get the |
Ahh, sorry about this! Thank you for all of these fixes and improvements.
Thanks! Just reviewed all changes,
Sorry about this -- I believe I removed this file in the
Ahh, that would do it! Thanks for tracking down this error. I thought I had checked at the beginning of the study that
Thanks! Will think about how to address this efficiently. If this is only an issue on the very first step, then the most direct thing might be to patch the
Thanks!
Will do |
I've updated enough imports to get
baoab_vs_vvvr.py
to run!Fixes #2