LeaveLimit Command - Revision history

Nairnj: /* Notes */

2021-07-22T19:41:29Z

Notes

← Older revision		Revision as of 19:41, 22 July 2021
Line 21:		Line 21:
	<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 to the ~~lower-left corner of the grid. That corner element needs to be empty and away from other particles~~.		<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.

Nairnj: /* Notes */

2021-01-01T07:55:23Z

Notes

← Older revision		Revision as of 07:55, 1 January 2021
Line 26:		Line 26:

	<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>

Nairnj: /* Notes */

2021-01-01T07:50:26Z

Notes

← Older revision		Revision as of 07:50, 1 January 2021
Line 21:		Line 21:
	<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 ~~move~~ to the lower-left corner of the grid. That corner element needs to be empty and away from other particles.		<li>Particles that are deleted are moved to the lower-left corner of the grid. That corner element needs to be empty and away from other 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>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.

Nairnj: /* Use LeaveLimit */

2021-01-01T07:29:10Z

Use LeaveLimit

← Older revision		Revision as of 07:29, 1 January 2021
Line 13:		Line 13:
	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.		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 ~~simulations~~ stop if any particle leaves the grid.		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 ==

Nairnj: /* Use LeaveLimit */

2021-01-01T07:28:30Z

Use LeaveLimit

← Older revision		Revision as of 07:28, 1 January 2021
Line 13:		Line 13:
	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.		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 simulations stop if any particle leaves the grid.		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 simulations stop if any particle leaves the grid.

	== Notes ==		== Notes ==

Nairnj at 07:27, 1 January 2021

2021-01-01T07:27:42Z

← Older revision		Revision as of 07:27, 1 January 2021
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 simulations 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 move to the lower-left corner of the grid. That corner element needs to be empty and away from other 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>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.

Nairnj: /* Use LeaveLimit */

2013-11-19T17:26:08Z

Use LeaveLimit

← Older revision		Revision as of 17:26, 19 November 2013
Line 7:		Line 7:
	LeaveLimit (maxNum)		LeaveLimit (maxNum)

	In XML input files, the command, which must be within the [[MPM Input Files#~~MPMHeader~~\|<tt><MPMHeader></tt> element]], is		In XML input files, the command, which must be within the [[MPM Input Files#MPM Header\|<tt><MPMHeader></tt> element]], is

	<LeaveLimit>(maxNum)</LeaveLimit>		<LeaveLimit>(maxNum)</LeaveLimit>

Nairnj: /* Use LeaveLimit */

2013-11-19T17:21:15Z

Use LeaveLimit

← Older revision		Revision as of 17:21, 19 November 2013
Line 7:		Line 7:
	LeaveLimit (maxNum)		LeaveLimit (maxNum)

	In XML input files, the command, which must be within the [[MPM Input Files#MPMHeader\|<tt><MPMHeader> ~~element~~</tt>]], is		In XML input files, the command, which must be within the [[MPM Input Files#MPMHeader\|<tt><MPMHeader></tt> element]], is

	<LeaveLimit>(maxNum)</LeaveLimit>		<LeaveLimit>(maxNum)</LeaveLimit>

Nairnj: /* Use LeaveLimit */

2013-11-19T17:20:52Z

Use LeaveLimit

← Older revision		Revision as of 17:20, 19 November 2013
Line 7:		Line 7:
	LeaveLimit (maxNum)		LeaveLimit (maxNum)

	In XML input files, the command, which must be within the <MPMHeader> ~~block~~, is		In XML input files, the command, which must be within the [[MPM Input Files#MPMHeader\|<tt><MPMHeader> element</tt>]], is

	<LeaveLimit>(maxNum)</LeaveLimit>		<LeaveLimit>(maxNum)</LeaveLimit>

Nairnj at 17:19, 19 November 2013

2013-11-19T17:19:22Z

← Older revision		Revision as of 17:19, 19 November 2013
Line 3:		Line 3:
	== Use LeaveLimit ==		== Use LeaveLimit ==

	In ~~script~~ files, the command is		In scripted files, the command is

	LeaveLimit (maxNum)		LeaveLimit (maxNum)