Group ID error

Submitted by Pankhi Singh on Thu, 08/20/2020 - 14:51

I recently installed LIGGGHTS on Ubuntu and run the example simulation.Then i wanted to run my own simulation so i created the 3D model and wrote the script using the LIGGGHTS official Documentation but when i am running it it is giving me a error:

"ERROR:Could not find fix group ID(../modify.cpp:782)"

My script is:-

# Preliminaries
units si
atom_style sphere
atom_modify map array
boundary f f f
newton off
communicate single vel yes
#processors 2 2 3

# Declare domain
region domain block -0.138 0.138 -0.138 0.138 -0.0045 0.43 units box
create_box 2 domain

# Neighbor listing
neighbor 0.003 bin
neigh_modify every 1 check no

#setup
# Material and interaction properties required
fix m1 all property/global youngsModulus peratomtype 2.5e7 2.5e7
fix m2 all property/global poissonsRatio peratomtype 0.25 0.25
fix m3 all property/global coefficientRestitution peratomtypepair 2 0.5 0.5 0.5 0.5
fix m4 all property/global coefficientFriction peratomtypepair 2 0.2 0.175 0.175 0.5

# Particle insertion
fix pts all particletemplate/sphere 15485863 atom_type 1 density constant 1000 radius constant 0.0015
fix pdd all particledistribution/discrete 67867967 1 pts 1.0
region factory cylinder z 0 0 0.10 0.4 0.41 units box
fix ins all insert/rate/region seed 86028157 distributiontemplate pdd &
nparticles 150000 particlerate 150000 insert_every 1000 &
overlapcheck yes vel constant 0. 0. -1.0 region factory ntry_mc 10000

# Import mesh from cad:
fix cad1 all mesh/surface file Body2.stl type 2 scale 0.001
fix cad2 all mesh/surface file Body1.stl type 2 scale 0.001

# Use the imported mesh as granular wall
fix all wall/gran model hertz history rolling_friction epsd2 mesh n_meshes 2 meshes cad1 cad2

# Define the physics
pair_style gran/hertz/history
pair_coeff * *

# Integrator
fix integrate all nve/sphere

# Gravity
fix grav all gravity 9.81 vector 0.0 0.0 -1.0

#timestep
timestep 0.00001

# Thermodynamic output settings
thermo_style custom step atoms ke cpu
thermo 10000
thermo_modify norm no lost ignore

# Check time step and initialize dump file
fix ctg all check/timestep/gran 1 0.01 0.01
run 1

# Create imaging information
shell mkdir post
variable dumptime equal 0.05
variable dumpstep equal ${dumptime}/${dt}

dump dmp all custom ${dumpstep} post/Particles_*.vtk id type type x y z ix iy iz vx vy vz fx fy fz radius masss
dump dumpstress all mesh/gran/VTK 200 post/mesh_*.vtk stress wear cad

### Execution and further settings
# Fill the hopper
run 150000 upto
run 300000

AttachmentSize
Image icon This is the Screenshot of the error186.02 KB

Pankhi Singh | Thu, 08/20/2020 - 20:40

I am using LIGGGHTS-PUBLIC 3.8.0.Do i need to change my syntax.and how do i set the "dt" variable can you give an example for the same.

mschramm | Thu, 08/20/2020 - 23:31

The line
pair_style gran/hertz/history
is incorrect and should be
pair_style gran model hertz tangential history
You can see this in the chute_wear example

There is also an error with your mesh import that I just noticed looking at it again.
There are multiple errors in the following line
fix all wall/gran model hertz history rolling_friction epsd2 mesh n_meshes 2 meshes cad1 cad2
Here you forgot to give the fix a name and you are using the old syntax again to describe the contact model. This should be adjusted to
fix granWalls all wall/gran model hertz tangential history rolling_friction epsd2 mesh n_meshes 2 meshes cad1 cad2

Why are you using a rolling friction model for the wall but not the particles?

As for variables, others are defined in the input script. To assign a variable, say dt, you would do the following
variable dt equal 1.0e-10

Lastly, the attribute error is saying that one of the variables you are asking liggghts to write to file does not exist.
Looking at the line:
dump dmp all custom ${dumpstep} post/Particles_*.vtk id type type x y z ix iy iz vx vy vz fx fy fz radius masss
we can see that you asked liggghts to write the atom array "masss" which does not exist.
Removing this fixes the issue.

Pankhi Singh | Fri, 08/21/2020 - 15:10

I did the same as you mentioned but its saying "EEROR :could not find specific model type"