No errors reports and the code stops after dem setting

I was simulating a rotator in a column.
The rotator works well in the rectangular domain but fails when transported to column geomerty.

The attachment is the files.
rotator.zip (3.9 MB)

Hi Yuanhe. I got a segmentation fault running your case. In the current version of MFiX, solver crashes like these do not generate error popups but there should be a stack trace in the console window - printed in red. In the next version of MFiX this will be a popup to make it easier to find.

I’m seeing this error:

#0  0x00007fe431165df4 in usr0 () at /tmp/ROTATOR/usr0.f:49
#1  0x00007fe431160d07 in main::initialize (mfix_dat=..., _mfix_dat=_mfix_dat@entry=20347) at /tmp/ROTATOR/build/pymfix/main.f90:438
#2  0x00007fe43130a85f in run_mfix (mfix_dat_filename=..., mfix_dat_size=20347, _mfix_dat_filename=_mfix_dat_filename@entry=1000)
    at /home/cgw/Work/NETL/mfix/model/mfix.f:132
#3  0x00007fe431161013 in main::run_mfix0 (mfix_dat_filename=..., cmdline_loglevel=<optimized out>, _mfix_dat_filename=<optimized out>)
    at /tmp/ROTATOR/build/pymfix/main.f90:82

(gdb) list


44	! Particles below y=0.1 represent the screw.
45	! They are flagged with a value of DES_USR_VAR = 1.0
46	! Regular particles are set a value of DES_USR_VAR = 0.0
47	! The screw particles will be assign a velocity in cfnewvalues.f
48	
49	      DES_USR_VAR(1,:) = 0.0D0
50	      WHERE(DES_POS_NEW(:,2)<0.03D0) DES_USR_VAR(1,:) = 1.0D0
51	
52	      RETURN
53	      END SUBROUTINE USR0

I believe the problem is that you are assigning 0 to DES_USR_VAR but the array is not allocated. DES_USR_VAR is allocated to DES_USR_VAR_SIZE and you do not have this set. It’s in the GUI under Enable User Scalar Tracking

After setting this to 1 your simulation runs but complains about particle_input.dat being too short.

– Charles

2 Likes