Lamps Errors

Dear Sirs,

I would like to post the following:

Please can you kindly help me with the following: when running lammps, I get an error - Created orthogonal box = (-0.03 -4.5 -2.7) to (27 4.5 4.8)
1 by 1 by 1 MPI processor grid

ERROR: Numeric index is out of bounds (…/force.cpp:783)

The following is the first half of my inout script.
#Preliminaries
units cgs
atom_style sphere
atom_modify map array
boundary f f f
newton off

communicate single vel yes

#Atom definition: Declare domain
region reg block -0.03 27.0 -4.5 4.5 -2.7 4.8 units box
#bounding box

#Material Types: 1-Lactose 200M; 2-Magnesium Stearate; 3-Steel
create_box 3 reg

#Neighbor listing
neighbor 0.001 bin
neigh_modify delay 0

Thanks in advance for your help

Queen

Where are the types being defined ?

Arun

Dear Sirs,

I would like to post the following:

before sending any more e-mails, i recommend, you spend some time
reading this essay: http://www.catb.org/esr/faqs/smart-questions.html
it provides important advice on how to get the best help for your
questions on open source software without wasting your and other
people's time and energy.

please note that you have already made three (3!) mistakes that are
considered serious blunders in that document:

- you have made unsolicited contact to developers off-list on a rather
trivial issue (something that is often considered equivalent to
unsolicited commercial e-mails aka spam).

- you have chosen the wrong forum (LIGGGHTS has its own user support
infractruture and forums)

- you have withheld crucial information, e.g. the exact version of the
software you are using, the platform that you are running on, and fact
that you are using LIGGGHTS and not LAMMPS as well as the parts of
your input that are really causing the error. the part you quoted is
error free but also indicative of using LIGGGHTS over LAMMPS, as
LAMMPS doesn't provide the communicate command for quite some time
anymore.

so please think about this for a bit, do the necessary research (e.g.
using a web search engine) to determine already posted solutions to
addressing the (quite common) error message you have encountered and
in the future make a better effort when posting inquiries.

thanks for your understanding,
     axel.