Increasing atom-ID when implementing "fix gcmc"

LAMMPS LAMMPS Mailing List Mirror
1

Hi LAMMPS mailing lists,

I used “fix gcmc” to control the density of system and used “compute cluster/atoms” & “dump” to output the cluster-ID of each atom. However, I encountered a problem: the cluster-ID and atom-ID keep increasing when implementing “fix gcmc”, therefore, the cluster-ID was too big to be displayed completely (like 1.09374e+006 rather than 1093742 ) after about 5 000 000 steps.

I suppose the reason is the atom-ID arranged to a new atom inserted by “fix gcmc” is always bigger than the biggest atom-ID of existing atoms. Is there any way to avoid the increase of atom-ID when implementing “fix gcmc”?

The software I used is “LAMMPS 64-bit 20160629”.

Thanks,
Dingbin Huang

Shanghai Jiao Tong University

2

Hi LAMMPS mailing lists,

I used "fix gcmc" to control the density of system and used "compute
cluster/atoms" & "dump" to output the cluster-ID of each atom. However, I
encountered a problem: the cluster-ID and atom-ID keep increasing when
implementing "fix gcmc", therefore, the cluster-ID was too big to be
displayed completely (like 1.09374e+006 rather than 1093742 ) after about 5
000 000 steps.

I suppose the reason is the atom-ID arranged to a new atom inserted by
"fix gcmc" is always bigger than the biggest atom-ID of existing atoms. Is
there any way to avoid the increase of atom-ID when implementing "fix
gcmc"?

​no, but there are ways to change the formatting of output to write out
more than 6 digits.

axel.​