Closed schwancr closed 10 years ago
Aren't we about to remove this code anyways?
Yea, I'll use this PR to use the new wrapper when it's done
On Wed, Feb 12, 2014 at 12:35 PM, Robert McGibbon notifications@github.comwrote:
Aren't we about to remove this code anyways?
Reply to this email directly or view it on GitHubhttps://github.com/SimTk/msmbuilder/pull/352#issuecomment-34914306 .
Yes I suppose there could be value in fixing bugs first to have a reference. On Feb 12, 2014 3:35 PM, "Robert McGibbon" notifications@github.com wrote:
Aren't we about to remove this code anyways?
Reply to this email directly or view it on GitHubhttps://github.com/SimTk/msmbuilder/pull/352#issuecomment-34914306 .
The -1's were actually buggy. The indices that mdtraj used are already 0-indexed.
Yeah that sounds right, it seemed to double-subtract them.
Now that rmcgibbo/mdtraj#304 is pulled in, we can use that code
Yeah. As I mentioned at https://github.com/rmcgibbo/mdtraj/issues/312, we should do an mdtraj release first. Then we can put in an install_requires
flag during msmbuilder setup.py to ensure the proper version.
Okay. I've made the mdtraj-0.7.0 release on pypi/github/binstar.
I'm closing this. I've fixed this in master now.
Or atleast in #375
I fixed this bug for the closest-heavy/closest scheme, but it was also present in the calpha scheme and I didn't realize.