Loading doc/src/Errors_messages.txt +0 −62 Original line number Diff line number Diff line Loading @@ -1092,11 +1092,6 @@ correct. :dd The specified file cannot be opened. Check that the path and name are correct. :dd {Cannot open fix ave/spatial file %s} :dt The specified file cannot be opened. Check that the path and name are correct. :dd {Cannot open fix ave/time file %s} :dt The specified file cannot be opened. Check that the path and name are Loading Loading @@ -1677,10 +1672,6 @@ provided by an atom map. An atom map does not exist (by default) for non-molecular problems. Using the atom_modify map command will force an atom map to be created. :dd {Cannot use fix ave/spatial z for 2 dimensional model} :dt Self-explanatory. :dd {Cannot use fix bond/break with non-molecular systems} :dt Only systems with bonds that can be changed can be used. Atom_style Loading Loading @@ -2425,10 +2416,6 @@ Self-explanatory. :dd Self-explanatory. :dd {Compute ID for fix ave/spatial does not exist} :dt Self-explanatory. :dd {Compute ID for fix ave/time does not exist} :dt Self-explanatory. :dd Loading Loading @@ -4074,10 +4061,6 @@ Self-explanatory. :dd Self-explanatory. :dd {Fix ID for fix ave/spatial does not exist} :dt Self-explanatory. :dd {Fix ID for fix ave/time does not exist} :dt Self-explanatory. :dd Loading Loading @@ -4379,51 +4362,6 @@ same style. :dd Self-explanatory. :dd {Fix ave/spatial compute does not calculate a per-atom array} :dt Self-explanatory. :dd {Fix ave/spatial compute does not calculate a per-atom vector} :dt A compute used by fix ave/spatial must generate per-atom values. :dd {Fix ave/spatial compute does not calculate per-atom values} :dt A compute used by fix ave/spatial must generate per-atom values. :dd {Fix ave/spatial compute vector is accessed out-of-range} :dt The index for the vector is out of bounds. :dd {Fix ave/spatial fix does not calculate a per-atom array} :dt Self-explanatory. :dd {Fix ave/spatial fix does not calculate a per-atom vector} :dt A fix used by fix ave/spatial must generate per-atom values. :dd {Fix ave/spatial fix does not calculate per-atom values} :dt A fix used by fix ave/spatial must generate per-atom values. :dd {Fix ave/spatial fix vector is accessed out-of-range} :dt The index for the vector is out of bounds. :dd {Fix ave/spatial for triclinic boxes requires units reduced} :dt Self-explanatory. :dd {Fix ave/spatial settings invalid with changing box size} :dt If the box size changes, only the units reduced option can be used. :dd {Fix ave/spatial variable is not atom-style variable} :dt A variable used by fix ave/spatial must generate per-atom values. :dd {Fix ave/time cannot set output array intensive/extensive from these inputs} :dt One of more of the vector inputs has individual elements which are Loading doc/src/Errors_warnings.txt +0 −18 Original line number Diff line number Diff line Loading @@ -291,24 +291,6 @@ This may cause accuracy problems. :dd This may cause accuracy problems. :dd {Fix thermal/conductivity comes before fix ave/spatial} :dt The order of these 2 fixes in your input script is such that fix thermal/conductivity comes first. If you are using fix ave/spatial to measure the temperature profile induced by fix viscosity, then this may cause a glitch in the profile since you are averaging immediately after swaps have occurred. Flipping the order of the 2 fixes typically helps. :dd {Fix viscosity comes before fix ave/spatial} :dt The order of these 2 fixes in your input script is such that fix viscosity comes first. If you are using fix ave/spatial to measure the velocity profile induced by fix viscosity, then this may cause a glitch in the profile since you are averaging immediately after swaps have occurred. Flipping the order of the 2 fixes typically helps. :dd {Fixes cannot send data in Kokkos communication, switching to classic communication} :dt This is current restriction with Kokkos. :dd Loading Loading
doc/src/Errors_messages.txt +0 −62 Original line number Diff line number Diff line Loading @@ -1092,11 +1092,6 @@ correct. :dd The specified file cannot be opened. Check that the path and name are correct. :dd {Cannot open fix ave/spatial file %s} :dt The specified file cannot be opened. Check that the path and name are correct. :dd {Cannot open fix ave/time file %s} :dt The specified file cannot be opened. Check that the path and name are Loading Loading @@ -1677,10 +1672,6 @@ provided by an atom map. An atom map does not exist (by default) for non-molecular problems. Using the atom_modify map command will force an atom map to be created. :dd {Cannot use fix ave/spatial z for 2 dimensional model} :dt Self-explanatory. :dd {Cannot use fix bond/break with non-molecular systems} :dt Only systems with bonds that can be changed can be used. Atom_style Loading Loading @@ -2425,10 +2416,6 @@ Self-explanatory. :dd Self-explanatory. :dd {Compute ID for fix ave/spatial does not exist} :dt Self-explanatory. :dd {Compute ID for fix ave/time does not exist} :dt Self-explanatory. :dd Loading Loading @@ -4074,10 +4061,6 @@ Self-explanatory. :dd Self-explanatory. :dd {Fix ID for fix ave/spatial does not exist} :dt Self-explanatory. :dd {Fix ID for fix ave/time does not exist} :dt Self-explanatory. :dd Loading Loading @@ -4379,51 +4362,6 @@ same style. :dd Self-explanatory. :dd {Fix ave/spatial compute does not calculate a per-atom array} :dt Self-explanatory. :dd {Fix ave/spatial compute does not calculate a per-atom vector} :dt A compute used by fix ave/spatial must generate per-atom values. :dd {Fix ave/spatial compute does not calculate per-atom values} :dt A compute used by fix ave/spatial must generate per-atom values. :dd {Fix ave/spatial compute vector is accessed out-of-range} :dt The index for the vector is out of bounds. :dd {Fix ave/spatial fix does not calculate a per-atom array} :dt Self-explanatory. :dd {Fix ave/spatial fix does not calculate a per-atom vector} :dt A fix used by fix ave/spatial must generate per-atom values. :dd {Fix ave/spatial fix does not calculate per-atom values} :dt A fix used by fix ave/spatial must generate per-atom values. :dd {Fix ave/spatial fix vector is accessed out-of-range} :dt The index for the vector is out of bounds. :dd {Fix ave/spatial for triclinic boxes requires units reduced} :dt Self-explanatory. :dd {Fix ave/spatial settings invalid with changing box size} :dt If the box size changes, only the units reduced option can be used. :dd {Fix ave/spatial variable is not atom-style variable} :dt A variable used by fix ave/spatial must generate per-atom values. :dd {Fix ave/time cannot set output array intensive/extensive from these inputs} :dt One of more of the vector inputs has individual elements which are Loading
doc/src/Errors_warnings.txt +0 −18 Original line number Diff line number Diff line Loading @@ -291,24 +291,6 @@ This may cause accuracy problems. :dd This may cause accuracy problems. :dd {Fix thermal/conductivity comes before fix ave/spatial} :dt The order of these 2 fixes in your input script is such that fix thermal/conductivity comes first. If you are using fix ave/spatial to measure the temperature profile induced by fix viscosity, then this may cause a glitch in the profile since you are averaging immediately after swaps have occurred. Flipping the order of the 2 fixes typically helps. :dd {Fix viscosity comes before fix ave/spatial} :dt The order of these 2 fixes in your input script is such that fix viscosity comes first. If you are using fix ave/spatial to measure the velocity profile induced by fix viscosity, then this may cause a glitch in the profile since you are averaging immediately after swaps have occurred. Flipping the order of the 2 fixes typically helps. :dd {Fixes cannot send data in Kokkos communication, switching to classic communication} :dt This is current restriction with Kokkos. :dd Loading
