- 05 Jan, 2015 1 commit
-
-
Jason Swails authored
Context into the platform rather than hacked into getRandomNumberSeed... Someone please check this.
-
- 03 Jan, 2015 6 commits
-
-
Jason Swails authored
rather than some pre-set seed generated at construction time. Any call to "setRandomNumberSeed" prevents this behavior (unless the generator is seeded with 0).
-
peastman authored
Add a check and raise an exception if someone tries to use a CHAMBER-style prmtop
-
peastman authored
Implements `usesPeriodicBoundaryConditions` on `Force`s and `System`
-
Jason Swails authored
topology file with the Amber file parsers. These do *not* currently work for creating a system.
-
Jason Swails authored
} else { --> } else { However, these were not my additions originally, but rather part of the Amoeba test cases that have been around for awhile. I figured while I was at it, I might as well update these styles as well. -
Jason Swails authored
-
- 30 Dec, 2014 11 commits
-
-
Jason Swails authored
-
Jason Swails authored
-
Jason Swails authored
the barostats and andersen thermostat.
-
Jason Swails authored
-
Jason Swails authored
-
Jason Swails authored
-
Jason Swails authored
function call.
-
Jason Swails authored
Reference platform.
-
Jason Swails authored
-
Jason Swails authored
-
Jason Swails authored
the System. The System inspects all of its forces and calls usePeriodicBoundaryConditions -- it reports 'true' if at least one of its Forces returns 'true' for usesPeriodicBoundaryConditions. The default Force implementation is to raise an exception (NotImplementedError). The System implementation will return true if at least one of its Forces returns 'true' for usesPeriodicBoundaryConditions, _regardless_ of whether or not one or more of the forces does not implement the method. If at least one of the forces does not implement usesPeriodicBoundaryConditions and all forces return false, an OpenMMException is thrown.
-
- 28 Dec, 2014 1 commit
-
-
peastman authored
Squash the following warning:
-
- 26 Dec, 2014 3 commits
-
-
Jason Swails authored
/usr/local/openmm/include/openmm/CustomHbondForce.h:477:25: warning: field 'p3' will be initialized after field 'parameters' [-Wreorder] p1(p1), p2(p2), p3(p3), parameters(parameters) { ^ I believe that the initializer is supposed to assign variables in the same order they're declared in the class definition (not the same order they're defined in the constructor argument list. -
peastman authored
Fix typo.
-
Jason Swails authored
-
- 25 Dec, 2014 1 commit
-
-
peastman authored
Fix small bug in `simtk.unit` related to mutable sequences.
-
- 18 Dec, 2014 3 commits
- 08 Dec, 2014 3 commits
-
-
Jason Swails authored
-
Jason Swails authored
found in doctests.py (and quite a bit more, too)
-
Jason Swails authored
are NOT numpy arrays.
-
- 06 Dec, 2014 1 commit
-
-
Jason Swails authored
-
- 04 Dec, 2014 2 commits
- 03 Dec, 2014 6 commits
-
-
peastman authored
-
peastman authored
Modified packaging scripts so that we no longer install Python into lib
-
John Chodera (MSKCC) authored
-
John Chodera (MSKCC) authored
-
John Chodera (MSKCC) authored
-
John Chodera (MSKCC) authored
-
- 02 Dec, 2014 1 commit
-
-
John Chodera (MSKCC) authored
-
- 26 Nov, 2014 1 commit
-
-
peastman authored
Workaround for compiler bug in Visual Studio
-