- Feb 10, 2017
- Feb 08, 2017
-
-
Axel Kohlmeyer authored
(cherry picked from commit 6410797697ddffbd5b47f526dcabd74f67ff6108)
-
Axel Kohlmeyer authored
-
- Feb 04, 2017
-
-
Agilio Padua authored
-
- Feb 03, 2017
- Feb 02, 2017
-
-
Stan Moore authored
-
Stan Moore authored
-
Stan Moore authored
-
Stan Moore authored
-
Stan Moore authored
-
Stan Moore authored
-
Stan Moore authored
-
Axel Kohlmeyer authored
-
Richard Berger authored
Fixing tagint and imageint issues in Kokkos package
-
Stefan Paquay authored
-
- Feb 01, 2017
-
-
Stan Moore authored
-
Stefan Paquay authored
-
Stefan Paquay authored
-
Stefan Paquay authored
-
- Jan 31, 2017
-
-
Richard Berger authored
Fix additional tagint issue in fix qeq/reax/kk
-
Axel Kohlmeyer authored
-
Axel Kohlmeyer authored
-
-
- Jan 30, 2017
- Jan 28, 2017
-
-
Richard Berger authored
This showed up when trying to compile with -DLAMMPS_BIGBIG. Fixes issue #365
-
- Jan 27, 2017
-
-
Stan Moore authored
-
Stan Moore authored
-
Stan Moore authored
-
Dan Ibanez authored
see commit 09fc8b0b for details on why
-
Dan Ibanez authored
because the verlet_kokkos system has a "clever" optimization which will alter the datamasks before calling sync/modify, so the datamask framework must be strictly obeyed for GPU correctness. (the optimization is to concurrently compute forces on the host and GPU, and add them up at the end of an iteration. calling your own sync will overwrite the partial GPU forces with the partial host forces).
-
Dan Ibanez authored
-
Dan Ibanez authored
-
Dan Ibanez authored
-
Dan Ibanez authored
this variable is only used when FFTW3 is enabled, so its declaration and initialization should be protected under the same conditions to avoid compiler warnings
-
Dan Ibanez authored
the variable (offset) is only used in a subset of numerous scenarios with #ifdef, it seems better just to have each loop declare it as needed. (avoids compiler warnings)
-