jianmu
/
lammps
forked from lijiext/lammps
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

git-svn-id: svn://svn.icms.temple.edu/lammps-ro/trunk@2038 f3b2605a-c512-4ea7-a41b-209d697bcdaa

This commit is contained in:
sjplimp 2008-08-06 14:10:28 +00:00
parent d034ff7606
commit f8d8c7d280
2 changed files with 44 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
doc/Section_errors.html
View File

@ -94,19 +94,31 @@ buffering or boost the sizes of messages that can be buffered.
<A NAME = "9_2"></A><H4>9.2 Reporting bugs
</H4>
<P>If you are confident that you have found a bug in LAMMPS, please send
an email to the <A HREF = "http://lammps.sandia.gov/authors.html">developers</A>.
<P>If you are confident that you have found a bug in LAMMPS, follow these
steps.
</P>
<P>First, check the "New features and bug fixes" section of the <A HREF = "http://lammps.sandia.gov">LAMMPS
WWW site</A> to see if the bug has already been reported or fixed.
<P>Check the <A HREF = "http://lammps.sandia.gov/bug.html">New features and bug
fixes</A> section of the <A HREF = "http://lammps.sandia.gov">LAMMPS WWW
site</A> to see if the bug has already been reported or fixed or the
<A HREF = "http://lammps.sandia.gov/unbug.html">Unfixed bug</A> to see if a fix is
pending.
</P>
<P>If not, the most useful thing you can do for us is to isolate the
problem. Run it on the smallest number of atoms and fewest number of
processors and with the simplest input script that reproduces the bug.
<P>Check the <A HREF = "http://lammps.sandia.gov/mail.html">mailing list</A>
to see if it has been discussed before.
</P>
<P>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.
<P>If not, send an email to the mailing list describing the problem any
ideas you have as to what is causing it or where in the code the
problem might be. The developers will ask for more info if needed,
such as an input script or data files.
</P>
<P>The most useful thing you can do to help us fix the bug is to isolate
the problem. Run it on the smallest number of atoms and fewest number
of processors and with the simplest input script that reproduces the
bug so that it is clear what command or combination of commands is
causing the problem.
</P>
<P>As a last resort, you can send an email directly to the
<A HREF = "http://lammps.sandia.gov/authors.html">developers</A>.
</P>
<HR>

32
doc/Section_errors.txt
View File

@ -91,19 +91,31 @@ buffering or boost the sizes of messages that can be buffered.
9.2 Reporting bugs :link(9_2),h4
If you are confident that you have found a bug in LAMMPS, please send
an email to the "developers"_http://lammps.sandia.gov/authors.html.
If you are confident that you have found a bug in LAMMPS, follow these
steps.
First, check the "New features and bug fixes" section of the "LAMMPS
WWW site"_lws to see if the bug has already been reported or fixed.
Check the "New features and bug
fixes"_http://lammps.sandia.gov/bug.html section of the "LAMMPS WWW
site"_lws to see if the bug has already been reported or fixed or the
"Unfixed bug"_http://lammps.sandia.gov/unbug.html to see if a fix is
pending.
If not, the most useful thing you can do for us is to isolate the
problem. Run it on the smallest number of atoms and fewest number of
processors and with the simplest input script that reproduces the bug.
Check the "mailing list"_http://lammps.sandia.gov/mail.html
to see if it has been discussed before.
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.
If not, send an email to the mailing list describing the problem any
ideas you have as to what is causing it or where in the code the
problem might be. The developers will ask for more info if needed,
such as an input script or data files.
The most useful thing you can do to help us fix the bug is to isolate
the problem. Run it on the smallest number of atoms and fewest number
of processors and with the simplest input script that reproduces the
bug so that it is clear what command or combination of commands is
causing the problem.
As a last resort, you can send an email directly to the
"developers"_http://lammps.sandia.gov/authors.html.
:line