Too many atom sorting bins

Submitted by NSalloum on Tue, 11/06/2018 - 09:17

hello,

I am trying to perform a simple flow simulation, but it is not being run because of the following error:

ERROR on proc 0: Too many atom sorting bins (../atom.cpp:1506)

So what are the parameter/s that I should modify to overcome this error, knowing that the time-step is less than 20% of the rayleigh time.
Would it be that I am using a very fine mesh in which the particles are in contact with many mesh elements at each time step?

I hope any may please help me in solving the issue.

best wishes,

paul | Tue, 11/06/2018 - 12:35

use a coarser mesh - this could be the culprit indeed, or give your full input script to let us look at what might've gone wrong.

NSalloum | Wed, 11/07/2018 - 10:47

thanks Paul for your concern, but how would I know what it is the minimum/maximum mesh size for my simulation to be run efficiently?
please find the input script :

#coarse graining application

coarsegraining 3.0 model_check warn
modify_timing verbose
### Initialization

# Preliminaries
########## Standard block #############
atom_style sphere
atom_modify map array
boundary m m m
newton off
communicate single vel yes
units si

######################################

# Simulation Domain
region domain block -0.05213 0.05213 -0.08175 0.08175 -0.031 0.09 units box
create_box 2 domain

# Neighbor listing
neighbor 0.000062 bin #0.25xradius_max #particle diameter
neigh_modify delay 0

# Define Material propertiesf
fix m1 all property/global youngsModulus peratomtype 1.0e7 1.0e7
fix m2 all property/global poissonsRatio peratomtype 0.3 0.3
fix m3 all property/global coefficientRestitution peratomtypepair 2 0.3 0.1 0.1 0.1
fix m4 all property/global coefficientFriction peratomtypepair 2 0.61 0.115 0.115 0.1

# Define contact model
pair_style gran model hertz tangential history
pair_coeff * *

# Time step
timestep 0.0000023 #2.3e-6

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

# Import mesh from cad
fix cad1 all mesh/surface file meshes/Simplified_Model_Walzen_001_stirrer.stl type 2 &
rotate axis 1 0 0 angle 90 scale 0.001
fix cad2 all mesh/surface file meshes/Simplified_Model_Walzen_Dosierwalze.stl type 2 rotate axis 1 0 0 angle 90 &
scale 0.001
fix cad3 all mesh/surface file meshes/Simplified_Model_fuer_D_60_1.stl type 2 &
rotate axis 1 0 0 angle 90 scale 0.001

# Use the imported meshes as granular walls
fix geometry1 all wall/gran model hertz tangential history mesh n_meshes 3 meshes cad1 cad2 cad3

#region of insertion
region factory block -0.018 0.018 -0.058 0.058 0.080 0.085 units box

# Integrator
fix integrate all nve/sphere

# Create stopper for machine
fix stopper all wall/gran model hertz tangential history primitive type 2 ycylinder 0.0305 0 0

# Particle insertion
fix pts1 all particletemplate/sphere 15485863 atom_type 1 density constant 1536.1 &
radius constant 0.000062 volume_limit 1e-22

fix pdd all particledistribution/discrete 15485867 1 pts1 1.0

fix ins all insert/rate/region seed 32452843 distributiontemplate pdd &
mass 0.05 massrate 0.05 insert_every 1000 &
overlapcheck yes vel constant 0.0 0.0 -1.0 region factory ntry_mc 10000
#5g

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

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

# Create imaging information #make a dump of particles and the stl file
dump dmp all custom 43482 post/movingMesh_*.liggghts id type type mass x y z ix iy iz vx vy vz fx fy fz omegax omegay omegaz radius diameter
dump dumpstl all mesh/stl 43482 post/dump*.stl

### Execution and further settings

# Fill the hopper
run 869566 upto

# Pull the stopper
unfix stopper

run 1739131

#Simulation is Done
print "The Simulation is now Ready"

paul | Thu, 11/08/2018 - 12:38

> boundary m m m
I'd suggest using a fixed boundary size using f f f. m m m means that the domain grows to accommodate the particles - which can be the cause of your problem if particle are ejected due to too high a timestep or other reasons.

NSalloum | Fri, 11/09/2018 - 07:47

hello Paul,

thanks a lot, I tried this, and I am not getting the previous error any more, but I am facing another one which is as follows:

ERROR: Mesh error - root causes: (a) mesh empty or (b) dimensions too small - use different unit system ( ../multi_node_mesh_parallel_I.h:384)

Knowing that I made sure that my stl files are in Ascii format and not binary ones.

So what do you suggest in this regards?

best wishes,
Nizar