Unexpected end of data file

Dear Lammps Users,

i am doing simulations of cnt-dna system.i first prepared input files and data files in lammps for both system. they worked .and then i combined the data files and wrote an input script for this mixed system.but when i run it i got an error says “unexpected end of data file”.i used airebo potential for cnt and charmm27 for ADE.data file types were complitely different of course.since one is atomic and the other one was in full style.what i have done is: i basicly added the atoms of cnt to atom list of ADE nin data file.i changed the informations a little bit, like number of atoms, and atom types.and in input scrip i used hybride atom type command for atomic and full.but it seems like it is not working.can anyone help with that?

Thanks

Aysun

Dear Lammps Users,

i am doing simulations of cnt-dna system.i first prepared input files and
data files in lammps for both system. they worked .and then i combined the
data files and wrote an input script for this mixed system.but when i run it
i got an error says "unexpected end of data file".i used airebo potential
for cnt and charmm27 for ADE.data file types were complitely different of
course.since one is atomic and the other one was in full style.what i have
done is: i basicly added the atoms of cnt to atom list of ADE nin data
file.i changed the informations a little bit, like number of atoms, and atom
types.and in input scrip i used hybride atom type command for atomic and
full.but it seems like it is not working.can anyone help with that?

please read the documentation about hybrid atom types carefully!
they change the format. hybrid atom types are meant to store
additional information to *all* atoms.

in general *all* atoms in the Atoms section of a data file have to
follow the same format. so the easiest way to get this done, would
be to convert the data file for atomic atom style into a data file
for full and *then* merge the two.

the error message about a premature end of file, is very likely
due to the missing entries for the part you created with atomic.
that will also lead to all information being corrupted.

axel.

You should not use atom_style hybrid to model atomic + full.
Just make it atom_style full. Full is a superset of atomic.

Steve

Hi,
I made the changes you suggested me.I converted my CNT PDB file into full style Lammps data file then i added the atoms of nanotube to ADE base atoms in data section.but this time i got an error like this:

LAMMPS (25 Sep 2011)
Lattice spacing in x,y,z = 2.5 2.5 2.5
Scanning data file …
3 = max bonds/atom
6 = max angles/atom
13 = max dihedrals/atom
1 = max impropers/atom
Reading data file …
orthogonal box = (-2.18391 -2.26112 -2.88621) to (7.66891 12.5181 2.04021)
1 by 1 by 1 processor grid
437 atoms
43 bonds
64 angles
91 dihedrals
2 impropers
Finding 1-2 1-3 1-4 neighbors …
4 = max # of 1-2 neighbors
7 = max # of 1-3 neighbors
17 = max # of 1-4 neighbors
19 = max # of special neighbors
ERROR: Incorrect args for pair coefficients (pair_airebo.cpp:155)
I know this is a very common mistake which is discussed before too many times in lammps mails.i read lots of mail but i can not make it.something is missing from my attention.please take a look to my data file and inputscript file which is attached.
Sincerely
Aysun Itai

cntw-ade.data (57 KB)

cntv-ade.in (1.03 KB)

Hi,
I made the changes you suggested me.I converted my CNT PDB file into full
style Lammps data file then i added the atoms of nanotube to ADE base atoms
in data section.but this time i got an error like this:
LAMMPS (25 Sep 2011)
Lattice spacing in x,y,z = 2.5 2.5 2.5
Scanning data file ...
3 = max bonds/atom
6 = max angles/atom
13 = max dihedrals/atom
1 = max impropers/atom
Reading data file ...
orthogonal box = (-2.18391 -2.26112 -2.88621) to (7.66891 12.5181 2.04021)
1 by 1 by 1 processor grid
437 atoms
43 bonds
64 angles
91 dihedrals
2 impropers
Finding 1-2 1-3 1-4 neighbors ...
4 = max # of 1-2 neighbors
7 = max # of 1-3 neighbors
17 = max # of 1-4 neighbors
19 = max # of special neighbors
ERROR: Incorrect args for pair coefficients (pair_airebo.cpp:155)
I know this is a very common mistake which is discussed before too many
times in lammps mails.i read lots of mail but i can not make it.something
is missing from my attention.please take a look to my data file and
inputscript file which is attached.

your line for the airebo parameters is broken in two
without using the continuation character '&'.

axel.

Thank you very much!

i fixed that problem in my input file.then i got another problem, this time error says:

Neighbor list overflow, boost neigh_modify one or page (neigh_full.cpp:426)

i read the manual and the mail lists, but since this is my first job with lammps may be, things did not make quite sense…how can i decide in my system what is the suitable neighbor page size or maximum number of neighbors allowed for one atom?what is the meaning of " page size must be >= 10x the one atom setting "?Could you please make those a little bit more clear?

Sincerely,

Aysun Itai

Thank you very much!

i fixed that problem in my input file.then i got another problem, this time
error says:

Neighbor list overflow, boost neigh_modify one or page (neigh_full.cpp:426)

i read the manual and the mail lists, but since this is my first job with
lammps may be, things did not make quite sense...how can i decide in my

if this is your first calculation with lammps, i strongly suggest that
you start by setting up a simple system from scratch and play with
the examples. trying to make a complicated system work as the
first lammps job is self-inflicted torture. it is much better to learn
the basic do's and don'ts with a system that you know about rather
than being constantly in the dark about whether something makes
sense or not. please keep in mind, that a successfully run trajectory
in classical MD is not necessarily a meaningful one. there are
a bit of skill and practical experience needed to choose parameters
wisely and to get to know how a specific MD code works.

you are currently making your life miserable without need.

system what is the suitable neighbor page size or maximum number of
neighbors allowed for one atom?what is the meaning of " page size must be >=
10x the one atom setting "?Could you please make those a little bit more
clear?

this is a very technical issue and you are most welcome to submit
a better wording for the explanation, after you have worked out what
went wrong. i personally find the text in the neigh_modify documentation
very to the point and helpful.

"The page and one options affect how memory is allocated for the
neighbor lists. For most simulations the default settings for these
options are fine, but if a very large problem is being run or a very
long cutoff is being used, these parameters can be tuned. The indices
of neighboring atoms are stored in "pages", which are allocated one
after another as they fill up. The size of each page is set by the
page value. A new page is allocated when the next atom's neighbors
could potentially overflow the list. This threshold is set by the one
value which tells LAMMPS the maximum number of neighbor's one atom can
have."

the translation is: that "one" is the estimate for the largest amount of
storage a single atom may need for its neighbor list. if an atom has
more neighbors, it may silently corrupt the neighbor lists. and "page"
is a measure for the size of a single block of memory (or page or tile)
that is allocated in one step for storing neighbors. the larger page is
relative to one, the more efficiently the neighbor lists can be packed
together, but if page is too large, memory will be wasted, too.

so neighborlist overflow happens, when you have too many neighbors
for a single atom. LAMMPS uses a per-job fixed limit for this, in
order to be more efficient. rather than simply silencing the error,
you should wonder, whether there is a good reason to have so many
neighbors. the default settings are well suited for all, but a select
few calculations with very small particles relative to their cutoff
radius, or simulations at high pressure.

you should first check your input and see, if the choices for
cutoffs are reasonable and that the distances between atoms
make sense, too. if they are off, then increasing the neighbor
list storage will only postpone the inevitable crash due to bad
dynamics of your system later.

that being said, if this large number of neighbors is indeed expected,
you can change the value of "one" to something larger and then
change the value for "page" accordingly.

cheers,
   axel.