- 23 Jun, 2015 4 commits
-
-
Jason Swails authored
-
Jason Swails authored
to precision)
-
Jason Swails authored
-
Jason Swails authored
-
- 19 Jun, 2015 5 commits
-
-
Jason Swails authored
numpy.
-
Jason Swails authored
-
Jason Swails authored
This should be *lower* than that of Unit (and ScaledUnit/BaseUnit), since we still want Units to take priority over Quantities (but Quantity to take precedence over regular ndarrays) for reasons like this: >>> a = np.array([1]) * u.angstroms >>> b = a * u.angstroms # should be np.array([1])*u.angstroms**2 >>> np.arange(10) * a # utilize broadcasting [1 2 3 4 5 6 7 8 9 10] A**2
-
Jason Swails authored
-
Jason Swails authored
The main thing that's done here is that numpy arrays can be given units via the * operator, rather than relying on the Quantity constructor e.g., >>> import numpy as np >>> np.zeros(10) * u.angstroms Quantity(value=array([ 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.]), unit=angstrom) yay!
-
- 12 Jun, 2015 1 commit
-
-
Peter Eastman authored
-
- 05 Jun, 2015 1 commit
-
-
Jason Swails authored
-
- 04 Jun, 2015 2 commits
-
-
Jason Swails authored
-
Jason Swails authored
- Add an informative __repr__ to Topology - Add __len__ to Chain and Residue to quickly tell how many residues or atoms are in them, respectively
-
- 03 Jun, 2015 1 commit
-
-
Jason Swails authored
-
- 30 May, 2015 1 commit
-
-
Kyle Beauchamp authored
-
- 27 May, 2015 3 commits
-
-
peastman authored
-
Jason Swails authored
This was actually fully supported already, since it parsed pairtypes and assigned the exception parameters correctly from there. All this does is throw an exception when pair parameters are not defined and gen-pairs=no.
-
Jason Swails authored
Due to a bug that was uncovered in mdtraj with scipy's NetCDF implementation regarding mmapping, scipy started issuing the following warning if any NetCDF variable objects had references remaining after closing the file: /.../lib/python2.7/site-packages/scipy/io/netcdf.py:287: RuntimeWarning: Cannot close a netcdf_file opened with mmap=True, when netcdf_variables or arrays referring to its data still exist. All data arrays obtained from such files refer directly to data on disk, and must be copied before the file can be cleanly closed. (See netcdf_file docstring for more information on mmap.) We were already copying data to avoid segfaults on some scipy versions, but there were still references to variables that went out of scope shortly after the NetCDF file was closed. Simply deleting these references gets rid of the warning.
-
- 26 May, 2015 3 commits
-
-
Jason Swails authored
Virtual sites are never created by the OpenMM system, and their information is not parsed from the Gromacs topology file. For now just throw an exception rather than let them run, since TIP4Pew behaves *very* strangely...
-
peastman authored
-
peastman authored
-
- 19 May, 2015 1 commit
-
-
peastman authored
-
- 18 May, 2015 2 commits
-
-
Jason Swails authored
-
Jason Swails authored
Gromacs uses the preprocessor to replace previously #define'd tokens in strings. This is used, for instance, to override certain parameters without having to introduce new file types. This is how Gromacs implemented ff99SB-ILDN (i.e., by simply replacing the chi torsion for isoleucine, leucine, aspartate, and asparagine with a define token). So OpenMM *was* missing some in-line parameters that were defined. The immediate consequence I see is that whenever someone tried to run ff99SB-ILDN with OpenMM, what they were *really* getting was ff99SB. Not sure where else, if anywhere, this kind of thing was happening.
-
- 14 May, 2015 1 commit
-
-
peastman authored
-
- 13 May, 2015 1 commit
-
-
peastman authored
-
- 12 May, 2015 1 commit
-
-
Robert T. McGibbon authored
-
- 06 May, 2015 1 commit
-
-
Peter Eastman authored
-
- 05 May, 2015 1 commit
-
-
peastman authored
-
- 04 May, 2015 3 commits
- 02 May, 2015 2 commits
-
-
Jason Swails authored
-
Jason Swails authored
Prints out a more helpful error message than a weird regex-based missing "groups" attribute on NoneType.
-
- 22 Apr, 2015 6 commits
-
-
Jason Swails authored
This also removes assert statements, since those can't be relied upon to *not* be optimized away -- they should never be used to check user input sanity.
-
Jason Swails authored
Masses do not increase monotonically with atomic number
-
Jason Swails authored
Also fixes the test case. Everything should pass now.
-
Jason Swails authored
Reduces time taken from 15.7 seconds (last commit) to 2.2 seconds by avoiding Quantity comparisons altogether.
-
Jason Swails authored
The old approach iterated through the entire periodic table by atomic number and subtracted the provided mass by the element's mass and kept track of the smallest difference. The new approach steps through the elements in order of atomic number and bails once it hits an element with a higher mass than the target mass (assuming masses are monotonically increasing). On my desktop, processing 4TVP-dmj_wat-ion.psf dropped from 297 s to 15.4 s. But 15.4 s is still a bit too long...
-
Jason Swails authored
See swig/swig#387 for a discussion. It would actually be nice to *not* set the "compactdefaultargs" feature globally, since that would allow us to actually see the real API at the Python level the same as you would see by looking at the C++ header files. But this is the only way to support both SWIG 2 and SWIG 3 easily and avoid a lot of retooling for the SWIG input code generator.
-