Any can help me with this: ''ERROR on proc 0: assertion failed''
_____________________________________________________________________________________________________________________
boundary m m m
units si
region domain block -3.7 2.6 -4.2 3.9 -4.5 1.95 units box
create_box 3 domain
neighbor 0.003 bin
neigh_modify delay 0 check no
fix pts1 all particletemplate/sphere 15485863 atom_type 1 density constant 2500 radius constant 0.17
fix pts2 all particletemplate/sphere 15485867 atom_type 1 density constant 2500 radius constant 0.0545
fix pts3 all particletemplate/sphere 32452843 atom_type 1 density constant 2500 radius constant 0.02
_____________________________________________________________________________________________________________________
How I can solv this?
All my attempts are in parallel: mpirun -np 6 liggghts -in in.conveyor > log.conveyor
Thanks.
marcelo | Mon, 07/03/2017 - 01:12
..... continuing on the case.
I posted the above error and continued to search for related errors. I saw that everyone is related to my neighbor. I would really like to know what parameters I should take into account before assigning values to my bin size; Is there a mathematical formula?
The properties of my particle are above, they have not changed. The changes I made in order to try to run my case were assigning arbitrary values to my neighbor (exactly the blind ones, because I did not find anything related). Some errors were appearing as: '' ERROR on proc 0: Too many neighbor bins '', '' ERROR on proc 0: Failed to allocate 7435103268 bytes for array neighlist: stencil '' and the one described above.
I'm trying to simulate a conveyor belt whose domain (it's described above in meters). I tried to toggle between 'boundary m m' and 'f f f', but to no avail.
Another detail that I need help, is to predict the timing of my simulation ... I did not find content on timestep (I also sighted values according to the Liggghts tutorials - the blind)
Please, I would love to learn to relate these values to timestep, boundary and most importantly, set which my ideal neighbor (bin size).
My last unsuccessful attempt:
boundary f f f
communicate single vel yes
units si
neighbor 3.0 bin
neigh_modify delay 0 every 1 check yes binsize 0.001