- 10 Sep, 2015 1 commit
-
-
peastman authored
-
- 03 Sep, 2015 1 commit
-
-
peastman authored
-
- 02 Sep, 2015 1 commit
-
-
peastman authored
-
- 01 Sep, 2015 1 commit
-
-
peastman authored
-
- 31 Aug, 2015 1 commit
-
-
peastman authored
-
- 29 Jul, 2015 1 commit
-
-
peastman authored
-
- 16 Jul, 2015 1 commit
-
-
peastman authored
-
- 13 Jul, 2015 1 commit
-
-
peastman authored
-
- 10 Jul, 2015 1 commit
-
-
peastman authored
-
- 09 Jul, 2015 1 commit
-
-
peastman authored
-
- 07 Jul, 2015 1 commit
-
-
Robert McGibbon authored
-
- 10 Jun, 2015 2 commits
-
-
Kyle Beauchamp authored
-
Kyle Beauchamp authored
-
- 06 May, 2015 2 commits
-
-
Peter Eastman authored
-
peastman authored
-
- 10 Apr, 2015 1 commit
-
-
peastman authored
-
- 19 Mar, 2015 1 commit
-
-
peastman authored
-
- 16 Mar, 2015 1 commit
-
-
peastman authored
-
- 06 Mar, 2015 1 commit
-
-
peastman authored
-
- 25 Feb, 2015 2 commits
- 24 Feb, 2015 2 commits
- 21 Feb, 2015 1 commit
-
-
peastman authored
-
- 20 Feb, 2015 1 commit
-
-
peastman authored
-
- 13 Feb, 2015 1 commit
-
-
peastman authored
-
- 17 Jan, 2015 1 commit
-
-
Jason Swails authored
-
- 10 Jan, 2015 1 commit
-
-
Jason Swails authored
-
- 09 Jan, 2015 2 commits
-
-
Jason Swails authored
-
Jason Swails authored
"truly" random seed being generated from the wall clock upon Context creation.
-
- 08 Jan, 2015 1 commit
-
-
Peter Eastman authored
-
- 05 Jan, 2015 3 commits
-
-
Jason Swails authored
-
Jason Swails authored
-
Jason Swails authored
Context into the platform rather than hacked into getRandomNumberSeed... Someone please check this.
-
- 03 Jan, 2015 2 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).
-
Jason Swails authored
-
- 30 Dec, 2014 4 commits
-
-
Jason Swails authored
the barostats and andersen thermostat.
-
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.
-