Difference between revisions of "LeaveLimit Command"

From OSUPDOCS
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 11: Line 11:
  <LeaveLimit>(maxNum)</LeaveLimit>
  <LeaveLimit>(maxNum)</LeaveLimit>
where <tt>(maxNum)</tt> is the number of steps with one or more unique particles leaving the grid that are tolerated before an analysis is stopped. If this command is omitted, the default is 1% of the particles. If a particle leaves the grid prior to reaching this limit, the particle will be moved back into the grid and the analysis will continue. Set it to 1 to have simulations stop if any particle leaves the grid.
where <tt>|(maxNum)|</tt> is the number of particles leaving the grid that are tolerated before an analysis is stopped. If <tt>(maxNum)</tt> is positive, a particle that leaves the grid will be moved back into the grid. If <tt>(maxNum)</tt> is negative, particles that leave the grid will be deleted from the simulation. If <tt>|(maxNum)|</tt> particles leave the grid, the simulation will stop.
 
If this command is omitted, the default is positive and set to 1% of the particles. Setting <tt>(maxNum)</tt> to 1 will cause a simulation to stop if any particle leaves the grid.


== Notes ==
== Notes ==
Line 18: Line 20:


<li>Particles that are forced back into the grid might lead to nonphysical or erroneous results. Analyses that have many particles leaving the grid should be highly suspect.
<li>Particles that are forced back into the grid might lead to nonphysical or erroneous results. Analyses that have many particles leaving the grid should be highly suspect.
<li>Particles that are deleted are moved into the [[Material Point Reservoir]].


<li>This command is must useful when the particle leaving the grid itself is already a numerical artifact and therefore forcing it back in may not be making things any worse. A common numerical artifact is an isolated particle that picks up a nonphysical acceleration propelling it off the grid. This command can trap those problem particles and keep the analysis running for the bulk of the remaining particles.
<li>This command is must useful when the particle leaving the grid itself is already a numerical artifact and therefore forcing it back in may not be making things any worse. A common numerical artifact is an isolated particle that picks up a nonphysical acceleration propelling it off the grid. This command can trap those problem particles and keep the analysis running for the bulk of the remaining particles.


<li>If the <tt>LeaveLimit</tt> is greater than 1 and the analysis eventually finishes, the output file will include a warning when the first particle left left the grid and a count of the number of steps that had at least one new particle leaving the grid.
<li>If the <tt>LeaveLimit</tt> is greater than 1 and the analysis eventually finishes, the output file will include a warning when the first particle left left the grid and a count of the number of steps that had at least one new particle leaving the grid.
</ol>

Latest revision as of 12:41, 22 July 2021

The LeaveLimit command determines how an MPM analysis responds when a particle leaves the grid:

Use LeaveLimit

In scripted files, the command is

LeaveLimit (maxNum)

In XML input files, the command, which must be within the <MPMHeader> element, is

<LeaveLimit>(maxNum)</LeaveLimit>

where |(maxNum)| is the number of particles leaving the grid that are tolerated before an analysis is stopped. If (maxNum) is positive, a particle that leaves the grid will be moved back into the grid. If (maxNum) is negative, particles that leave the grid will be deleted from the simulation. If |(maxNum)| particles leave the grid, the simulation will stop.

If this command is omitted, the default is positive and set to 1% of the particles. Setting (maxNum) to 1 will cause a simulation to stop if any particle leaves the grid.

Notes

  1. Particles that are forced back into the grid might lead to nonphysical or erroneous results. Analyses that have many particles leaving the grid should be highly suspect.
  2. Particles that are deleted are moved into the Material Point Reservoir.
  3. This command is must useful when the particle leaving the grid itself is already a numerical artifact and therefore forcing it back in may not be making things any worse. A common numerical artifact is an isolated particle that picks up a nonphysical acceleration propelling it off the grid. This command can trap those problem particles and keep the analysis running for the bulk of the remaining particles.
  4. If the LeaveLimit is greater than 1 and the analysis eventually finishes, the output file will include a warning when the first particle left left the grid and a count of the number of steps that had at least one new particle leaving the grid.