break particle

Hi Tarun
Any luck with the above-stated problem
Are you able to break the multi sphere particle assemblies
Plz, share your experience in that case.

the following should work.
fix breakHeight all multisphere/break allow_group_and_set yes trigger_threshold ${heightThreshold} trigger_timeStep 0 trigger_name v_myAtomHeightVariable
where
variable myAtomHeightVariable atom z
if z is the correct axis...

Hi mschramm

I tried the command which you suggested
but as soon as I activate the command for multisphere/break, I am getting following error

Memory usage per processor = 12.2488 Mbytes
Step Atoms KinEng 1 Volume ts[1] ts[2]
5000001 1540 8072.2278 0 58500000 0 0
[pawar:14776] *** Process received signal ***
[pawar:14776] Signal: Segmentation fault (11)
[pawar:14776] Signal code: Address not mapped (1)
[pawar:14776] Failing at address: 0xfffffffe0312ed98
[pawar:14776] [ 0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f4e210db390]
[pawar:14776] [ 1] lmp_auto[0xa0f8a2]
[pawar:14776] [ 2] lmp_auto[0x6e05b1]
[pawar:14776] [ 3] lmp_auto[0xa08066]
[pawar:14776] [ 4] lmp_auto[0xa92b09]
[pawar:14776] [ 5] lmp_auto[0x69feef]
[pawar:14776] [ 6] lmp_auto[0x4edf42]
[pawar:14776] [ 7] lmp_auto[0x4eb843]
[pawar:14776] [ 8] lmp_auto[0x4ec2b7]
[pawar:14776] [ 9] lmp_auto[0x416e0b]
[pawar:14776] [10] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f4e20d20830]
[pawar:14776] [11] lmp_auto[0x418f99]
[pawar:14776] *** End of error message ***
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 14776 on node pawar exited on signal 11 (Segmentation fault).

Plz, share your experience in that case.

Thank You

Hello,
I was able to recreate this error in a stock version of liggghts and I am looking into over the weekend.

Hello,
I believe there is a bug in the fix_multisphere_break.cpp file.
https://github.com/CFDEMproject/LIGGGHTS-PUBLIC/blob/master/src/fix_mult...

This line assumes that a fix was used for the trigger. Thus when using a variable trigger you get undefined behavior of the form k % 0 giving the division by zero error.
To fix this, I propose first checking that the trigger is of fix style and then checking the rest of the line:
if (triggerType_ == FIX)
if (triggerName_ && update->ntimestep % (modify->fix[triggerIdx_]->peratom_freq))
error->all(FLERR,"Fix used in fix multisphere/break not computed at compatible time");
I will make a bug report and give an input file.