krikr808/MD — comment on commit 69c739bbf96b00db31ba572f2ee4422b2808a98c
File:  line 0
By krikr808:

Ah, I knew the property measures could become a bit messy, especially since not everything is measured at the same place. I tried to solve the problem with having the velocity half a time step behind when measuring the properties, and that is solved now, but maybe it caused some other problems when I was moving around with the code.

I'm also thinking if it is best to let the velocity be half a time step behind or let the position be half a time step behind – now I changed so that the position is half a time step behind instead of the velocity. I don't know why I changed that, maybe it is better if it is the other way around because then we can separate leapfrog and force_calculation again (right now force_calculation has to be included in leapfrog). I will look into it a bit more.