From d66323cfcc6d6a439c7f237d2738fc1792ce1f2f Mon Sep 17 00:00:00 2001
From: sjplimp
If you get an error message about an invalid command in your input script, you can determine what command is causing the problem by @@ -91,8 +92,8 @@ buffering or boost the sizes of messages that can be buffered.
If you are confident that you have found a bug in LAMMPS, we'd like to -know about it via email. +
If you are confident that you have found a bug in LAMMPS, please send +an email to the developers.
First, check the "New features and bug fixes" section of the LAMMPS WWW site to see if the bug has already been reported or fixed. @@ -101,8 +102,8 @@ WWW site to see if the bug has already been reported or fixed. problem. Run it on the smallest number of atoms and fewest number of processors and with the simplest input script that reproduces the bug.
-Send an email that describes the problem and any ideas you have as to -what is causing it or where in the code the problem might be. We'll +
In your email, describe the problem and any ideas you have as to what +is causing it or where in the code the problem might be. We'll request your input script and data files if necessary.
In the spirit of an open-source code, these are various ways you can contribute to making LAMMPS better. You can send email to the -developers on any of these items. +developers on any of these +items.
If you add something you think is truly useful and doesn't impact LAMMPS performance when it isn't used, send an email to the -developers. We might be interested in adding it to the LAMMPS -distribution. +developers. We might be +interested in adding it to the LAMMPS distribution.
If you have a build problem that you are convinced is a LAMMPS issue (e.g. the compiler complains about a line of LAMMPS source code), then -please send an email to the developers. Note that doesn't include -linking problems - that's a question for a local expert! +please send an email to the +developers. Note that doesn't +include linking problems - that's a question for a local expert!
Also, if you succeed in building LAMMPS on a new kind of machine (which there isn't a similar Makefile for in the distribution), send @@ -176,7 +177,8 @@ you'll need to set the appropriate -I and -L switches in Makefile.foo.
If you examine fft3d.c and fft3d.h you'll see it's possible to add other vendor FFT libraries via #ifdef statements in the appropriate places. If you successfully add a new FFT option, like -DFFT_IBM, -please send the developers an email; we'd like to add it to LAMMPS. +please send the developers an email; we'd +like to add it to LAMMPS.
(6) If you don't plan to use PPPM, you don't need an FFT library. Use a -DFFT_NONE switch in the CCFLAGS setting of Makefile.foo, or exclude