Difference between revisions of "DeleteLimit Command"
Jump to navigation
Jump to search
(→Notes) |
|||
| Line 19: | Line 19: | ||
<ol> | <ol> | ||
<li>Particles that are deleted are moved | <li>Particles that are deleted are moved into the [[Material Point Reservoir]].</li> | ||
<li>If <code>(maxNum)</code> is greater than 1 and the analysis eventually finishes, the output file will include a warning when the first particle gets a nan value and will count of the number of steps that had at least one new particle with a nan value.</li> | <li>If <code>(maxNum)</code> is greater than 1 and the analysis eventually finishes, the output file will include a warning when the first particle gets a nan value and will count of the number of steps that had at least one new particle with a nan value.</li> | ||
</ol> | </ol> | ||
Revision as of 11:42, 22 July 2021
The DeleteLimit command determines how an MPM analysis responds when a particle gets a nan value:
Use DeleteLimit
In scripted files, the command is
DeleteLimit (maxNum)
In XML input files, the command, which must be within the <MPMHeader> element, is
<DeleteLimit>(maxNum)</LeaveLimit>
where (maxNum) is the number of particles with nan values that are tolerated before an analysis is stopped. Particles that get a nan value are deleted from the simulation and the simulation will continue. If (maxNum) particles get nan values, the simulation will stop.
If this command is omitted, the default is zero or the simulation will stop if any partitle gets a nan value.
Notes
- Particles that are deleted are moved into the Material Point Reservoir.
- If
(maxNum)is greater than 1 and the analysis eventually finishes, the output file will include a warning when the first particle gets a nan value and will count of the number of steps that had at least one new particle with a nan value.