LIGGGHTS® - User Forum

LIGGGHTS® related topics can be discussed here: discussion about models, installation, feature requests and general discussion

ERROR: Fix property/global (id m3): per-atom type property matrix must be symmetric

Submitted by laudari on Mon, 12/06/2021 - 10:56

Hello,

I am trying to do simulation with two different particles at once.
So my first simulation will include particles differe in their cofficient of restitution,

This is my script
```
#Simple chute wear test

MPI communication error with fix multisphere/break

Submitted by Xinyi Qian on Sat, 12/04/2021 - 16:35

I used the 'fix multisphere/break' feature for a simple direct shear simulation on clusters. After breakage occurs, I would soon receive error message telling me that there is problem with MPI all_reduce. The simulation went well when I used 'fix multisphere' instead. I don't have any idea what went wrong with it.

Atom fixed but finding its velocity update

Submitted by mofazli on Thu, 12/02/2021 - 09:08

Hi everyone,
I hope you are all well.
I have a question about Liggghts ability to fix the particles in their position but update their velocities. We know liggghts has the following command:
fix 3 wall nve/noforce
which does the opposite thing I need, changing particles position but fixing their velocity. I need to keep the particles in their initial position, but update their velocities based on forces. Now I am using the following command:
fix integr all nve/sphere

move/mesh time high - use Vektor/Region as mesh/surface?

Submitted by Phil93 on Thu, 11/25/2021 - 18:30

Hello,

briefly about my problem, i have a cylinder where i fill particles and move this cylinder to mix the particles. I quickly notice that even with small numbers of particles (about 10,000) it takes a long time to simulate. To better see where the most time is spent I ran the script with modify_timing verbose.

About scaling particles postion from 10 to 1, 100 to 1, or 1000 to 1 in liggghts files or in dump liggghts files

Submitted by Dinesh Dhameliya on Sun, 11/21/2021 - 13:17

Hi everyone I am new to LIGGGHTS and I am getting for scale factor 10 particle position x,y,z 10 times bigger and for scale factor 100 position 100 times bigger compared to Scale factor 1. It is obvious. But I want dump files again to scale factor 1 from 10 or 100. I think that dump_modify is not suitable for dump custom command. I am also uploading pictures of dump files for factor 1, factor 10, and factor 100. If anyone has an Idea about that it is very useful for me and I will be very thankful if you can share it with me. Thanks in advance.

Error with compute group/group command ... "pair style does not support compute group/group"

Submitted by berlinphoenix on Sat, 11/20/2021 - 16:40

Dear all,

i want to evaluate the number of contacts of a group of particles with themselves. Basically i want to know if a group of particles stays "intact" all the time or gets "fractured" over time. For this i found the interesting compute "group/group" command. Unfortunatly when i use the command i get the error message:

"Pair style does not support compute group/group"

In the documentation it says there are no restrictions to this compute, so i'm curious what the reason can be. I'm using the pair_style gran model hertz ...

DEM only simulation - Add dragforce - Recirculation

Submitted by sohaibmalik on Wed, 11/17/2021 - 22:40

Hi Everyone,
I am a newbie using LIGGGHTS. My problem would be similar to a steady state flow of spherical particles through a hopper domain with conical bottom, so I took it as a start. I have been able to run a simulation where I inserted the particles, and let them fall under gravity (picture attached)
However, I have not been able to run it in a "Recirculation" mode where the particles leaving the domain would be reinserted from the top. Can any body help me out with a means to do that.

gravity vs addforce vs setforce

Submitted by Kashminder on Tue, 11/16/2021 - 22:45

My issue is that I have ran three different codes keeping everything same but only these 3 commands different in each code

fix gravi all gravity 9.81 vector 0. 0.0 -1.0.
fix p all addforce 0 0 -9.81
fix p all setforce 0 0 -9.81

So, the code with gravity force command acts like the particle comes down very slowly but in their 2 commands i.e. (add-force and setforce) the particles leaves the box quiet early, My question is that in all three cases the particles should act similarly as the force is same in three cases? Is the issue seems to be in fix?

Pages

Subscribe to RSS - LIGGGHTS® - User Forum