Rob
Ansys Employee
On each DPM update Fluent re-calculates the particle trajectory and hence source terms (how much the particle alters the flow). If the update is very frequent the solution may never converge, and may use a lot of cpu resource, on the other hand the solver is using the correct DPM data. If the interval is very long, you'll see spikes, use less cpu but risk using less up to date data. Both high and low intervals are valid depending on how much of a change you see in the particle tracks and how much cpu you have. Default is 10, and 10-50 is a common range, I often use the default. n