GitLab

Fixed a compiler warning

Fixed a compilation error on some compilers

Update packaging devtools scripts for CUDA 7.0 on linux

Make sure RBTorsion parameters are returned with the correct units.

Minor enhancements to Topology

- Add an informative __repr__ to Topology
- Add __len__ to Chain and Residue to quickly tell how many residues or atoms
  are in them, respectively

Look in cuda dir for opencl headers

Useful when cuda is not installed in the default location.

Fixed race condition doing PME in a separate stream

GBn now uses Discrete2DFunctions

Move to using a continuous 2D function.

Ported OpenCL FFT to CUDA

Add elapsed time column in statedatareporter

Disabled PME stream on CUDA 7

Eliminate scipy RuntimeWarning when reading NetCDF restart files

support gen-pairs=no in Gromacs

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.

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.

Improved accuracy of energy computation

Raise exception when processing Gromacs molecule with virtual sites

Moved the MTS and aMD integrators into the main repository

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...