Home · DEM Course · Module 6
DEM (Discrete Element Method) Course with BrixDEM

Module 6 · Running and post-processing

🎬 9 lessons ⏱ 2 h course 📝 5 questions · pass with 4
🔒

This module is still locked

To unlock it, pass the Module 5 quiz with at least 70%.

Go to the quiz · Module 5
Lesson 1 of 9 · 0:13

From Run to report

Lesson transcript

This module starts when you click Run. How to monitor the simulation. How to see what happened, without fooling yourself. How to pull numbers out of the files. And how to turn all that into a report.

Quiz · Module 6

Check what you learned

5 multiple-choice questions. Get at least 4 right to complete the module. You can try as many times as you like.

✓ You have already passed this module. You may retake the quiz to review.
1.With the simulation paused, what can be changed and applied in the same run?
2.Why fix the colour scale in the particle view?
3.The mass leaving a chute starts flat and then becomes a straight line. How do you get the real flow rate?
4.The shaft power of a mixer comes out negative. What does that mean?
5.For analysis outside the interface, why prefer the CSV files?
Transcripts of every lesson in this module

1. From Run to report

This module starts when you click Run. How to monitor the simulation. How to see what happened, without fooling yourself. How to pull numbers out of the files. And how to turn all that into a report.

2. Before Run

When you click Run, BrixDEM does three things before it starts. It checks that the project is saved. If the folder already has results, it warns you and asks whether it may delete them, so the two don't get mixed. And it shows an estimate of the disk space that will be used. Everything the solver writes goes to the results folder. A file with the energy. Another with contact statistics. Another with the force and torque on each part. And the full pictures of the particles, the snapshots.

3. CPU, GPU and performance

Don't guess, measure. For small cases and calibration, the CPU usually wins. With a lot of STL geometry, too. With hundreds of thousands of particles or more, the GPU pays off. Want to run faster? Follow this order. Turn Verlet on. Lower Young's modulus, keeping an eye on the overlap. Save only the files you need. Use coarse-graining for huge cases. And only then move to the GPU, measuring the gain.

4. Monitoring and recovery

Let's run again, this time looking at how to control the simulation. I click Run. During the run, the console is your dashboard. t is the simulated time. N is the number of particles. And KE is the kinetic energy. If N stops growing, the inlet has stopped. If KE shoots up for no reason, be suspicious. Need to change something? Click Pause. The solver waits until it reaches a safe point, and the button turns into Continue. With the case paused, I go to Setup and cut the end time to one point two seconds. I click Continue. The program compares what changed, shows the list and asks whether to apply it. End time, gravity, inlet flow rate and part motion can change like this, in the same run. But material, geometry, domain, backend and CGF do not change mid-run. Those only take effect on the next Run. The same goes for the Elevator and the free body. Stop ends the run. Stopping takes a moment, because the solver finishes the current step and the last file. Do not force the program closed at that moment. And if the computer crashes? When you reopen it, the Session Recovery window lists what was interrupted, and you can continue from the last checkpoint. One detail: the checkpoint stores the particles, but not the setup. Material and geometry must stay the same. This is what a healthy case looks like. Kinetic energy rises during filling, peaks and levels off. If it only keeps growing for no reason, stop and investigate.

5. Viewing particles

In the 3D Particles tab you see every particle, and choose what the color shows. It is on this palette button. Under Variable, you pick the quantity. Velocity shows fast zones and dead regions. Force shows the impacts. Radius and material show who is who. Under Palette, prefer perceptually uniform palettes, such as Viridis, in reports. They don't invent bands that the data does not have. And this is the option most people forget: limiting the range. With a fixed range, the same color always means the same speed. Without it, each frame uses a different ruler, and the comparison misleads you. I click Apply, and the silo shows up colored by velocity. These buttons play the simulation like a movie. Each frame is a file saved during the run. You can go back to the start, play and step forward.

6. Charts and files

The charts are under Results. Everything is grouped: energy, particles and, further down, each geometry and each outlet. Let's look at the kinetic energy, the first chart I always check. It rises during filling and then should level off. If it only keeps growing, be suspicious. For particle variables, these dots choose the mean, the minimum or the maximum. Here I ask for the maximum velocity. Each chart has its own buttons. CSV exports the numbers, and PNG saves the image for your report. An example of why you look at the chart. This is the mass that left a chute. At first the curve is flat, then it becomes a straight line. The real flow rate is the slope of that line: thirty-three kilograms per second. If you averaged over the whole time, you would get seventeen, almost half. Always compute it in the steady-state window. Another example: motor power. It is the shaft torque times the angular velocity. In this mixer, the average power is around a thousand watts. The negative sign is not braking: it only indicates direction, opposite to the reference axis. To size the motor, use the magnitude. And mixing. This index goes from zero, fully segregated, to one, a perfect mix. Here it rises and levels off. Once the curve stops rising, mixing longer only wastes energy.

7. Beyond the interface

The built-in charts cover a lot, but not everything. Every result is also in a CSV file. You open it in a spreadsheet or in Python. And compute whatever you want, such as the flow rate over the steady-state window only. One warning. Always prefer the CSV. The binary particle files are versioned, and the format may change between program updates.

8. When it goes wrong

Particles flying off, energy rising non-stop? Follow this order. Halve the time step. Check whether particles are born inside the wall. Check the inlet velocity. Look at the mesh. And review Young's modulus. Some symptoms come up all the time. An inlet that does not inject? Check the normal, the times and the position. An outlet that does not remove? The normal, again. Particles disappearing? The domain may be too tight. If you need help, send our team what it takes to reproduce the problem. The project and the geometry folder. The console log: use the Save Log button. A screenshot of the symptom. And the program version.

9. From file to report

Finally, the report. Start with the question and the case. Show the calibration and the validation. Present the results in the steady-state window. And archive everything in one folder, so anyone can repeat it. Now you can go from the drawing to the answer.