Transform Command - Revision history

Nairnj: /* Comments on Transform Command */

2021-08-03T22:58:14Z

Comments on Transform Command

← Older revision		Revision as of 22:58, 3 August 2021
Line 34:		Line 34:
	=== Comments on Transform Command ===		=== Comments on Transform Command ===

	# When not transforming particles, [[MPM Region and Hole Commands\|Region commands]] keep track of which locations in each cell are occupied by a material point. If two [[MPM Region and Hole Commands\|Region commands]] try to create particles at the same location, the first will create a particle and the second will do nothing. This feature lets you overlay regions without causing particle interferences. When particles are transformed, however, the particle locations of free from the grid and therefore particle locations are no longer tracked. In other words, whenever transforming particles, your input file in responsible for insuring that material points are not created in the same location. Similarly, transformed particle will be created in their new locations without regard to whether or that the location has been marked using a [[MPM Region and Hole Commands\|Region or Hole command]].		# When not transforming particles, [[MPM Region and Hole Commands\|Region commands]] keep track of which locations in each cell are occupied by a material point. If two [[MPM Region and Hole Commands\|Region commands]] try to create particles at the same location, the first will create a particle and the second will do nothing. This feature lets you overlay regions without causing particle interferences. When particles are transformed, however, the particle locations of free from the grid and therefore particle locations are no longer tracked. In other words, whenever transforming particles, your input file in responsible for insuring that material points are not created in the same location. Similarly, transformed particle will be created in their new locations without regard to whether or not that the location has been marked using a [[MPM Region and Hole Commands\|Region or Hole command]].
	# Only one transformation is allowed in each [[MPM Region and Hole Commands\|Region command]] and the transformation applies to all particles created by that command.		# Only one transformation is allowed in each [[MPM Region and Hole Commands\|Region command]] and the transformation applies to all particles created by that command.
	# When transforming rigid particles, the effect of rotations will not affect the simulation results unless shape functions account for particle deformation (''e.g.'', by using [[MPM Methods and Simulation Timing\|CPDI shape functions]]).		# When transforming rigid particles, the effect of rotations will not affect the simulation results unless shape functions account for particle deformation (''e.g.'', by using [[MPM Methods and Simulation Timing\|CPDI shape functions]]).

Nairnj: /* Transforming Created Particles in XML Files */

2019-08-19T17:46:31Z

Transforming Created Particles in XML Files

← Older revision		Revision as of 17:46, 19 August 2019
Line 46:		Line 46:
	where		where

	* <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> define elements of the <math>\vec T</math> translation vector (in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]). These values can be [[User Defined Functions\|user-~~define~~ functions]].		* <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> define elements of the <math>\vec T</math> translation vector (in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]). These values can be [[User Defined Functions\|user-defined functions]].

	* <tt>F11</tt>, <tt>F12</tt>, <tt>F13</tt>, ... <tt>F33</tt> can specify up to nine elements of the initial particle deformation gradient (dimensionless).		* <tt>F11</tt>, <tt>F12</tt>, <tt>F13</tt>, ... <tt>F33</tt> can specify up to nine elements of the initial particle deformation gradient (dimensionless).
Line 54:		Line 54:
	# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.		# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.
	# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should not deform particles this way because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.		# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should not deform particles this way because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.
	# <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> can be [[User Defined Functions\|user-~~define~~ functions]] while the [[#Transforming Created Particles in Script Files\|Transform scripting command]] only numerical values (and applications convert those numerical values for rotation angle, origin, and translation into [[User Defined Functions\|user-~~define~~ functions]] for <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt>.		# <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> can be [[User Defined Functions\|user-defined functions]] while the [[#Transforming Created Particles in Script Files\|Transform scripting command]] only numerical values (and applications convert those numerical values for rotation angle, origin, and translation into [[User Defined Functions\|user-defined functions]] for <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt>.

	=== Comments on Deform Command ===		=== Comments on Deform Command ===

Nairnj: /* Transforming Created Particles in XML Files */

2019-08-19T17:45:58Z

Transforming Created Particles in XML Files

← Older revision		Revision as of 17:45, 19 August 2019
Line 54:		Line 54:
	# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.		# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.
	# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should not deform particles this way because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.		# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should not deform particles this way because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.
	# <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> can be [[User Defined Functions\|user-define functions]] while the scripting command ~~allows~~ only numerical values (and applications convert those numerical values for rotation angle, origin, and translation into [[User Defined Functions\|user-define functions]] for <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt>.		# <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> can be [[User Defined Functions\|user-define functions]] while the [[#Transforming Created Particles in Script Files\|Transform scripting command]] only numerical values (and applications convert those numerical values for rotation angle, origin, and translation into [[User Defined Functions\|user-define functions]] for <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt>.

	=== Comments on Deform Command ===		=== Comments on Deform Command ===

Nairnj: /* Transforming Created Particles in XML Files */

2019-08-19T17:45:21Z

Transforming Created Particles in XML Files

← Older revision		Revision as of 17:45, 19 August 2019
Line 46:		Line 46:
	where		where

	* <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> define elements of the <math>\vec T</math> translation vector (in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]). These values can be a [[User Defined ~~Function~~]].		* <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> define elements of the <math>\vec T</math> translation vector (in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]). These values can be [[User Defined Functions\|user-define functions]].

	* <tt>F11</tt>, <tt>F12</tt>, <tt>F13</tt>, ... <tt>F33</tt> can specify up to nine elements of the initial particle deformation gradient (dimensionless).		* <tt>F11</tt>, <tt>F12</tt>, <tt>F13</tt>, ... <tt>F33</tt> can specify up to nine elements of the initial particle deformation gradient (dimensionless).

	If the provided deformation gradient corresponds to rigid rotation, this transformation will be identical to a corresponding [[#Transforming Created Particles in Script Files\|Transform command]] in a script file. The <tt>XML</tt> command, however, provides ~~two~~ additional options:		If the provided deformation gradient corresponds to rigid rotation, this transformation will be identical to a corresponding [[#Transforming Created Particles in Script Files\|Transform command]] in a script file. The <tt>XML</tt> command, however, provides three additional options:

	# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.		# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.
	# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should not deform particles this way because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.		# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should not deform particles this way because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.
			# <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> can be [[User Defined Functions\|user-define functions]] while the scripting command allows only numerical values (and applications convert those numerical values for rotation angle, origin, and translation into [[User Defined Functions\|user-define functions]] for <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt>.

	=== Comments on Deform Command ===		=== Comments on Deform Command ===

Nairnj: /* Transforming Created Particles in XML Files */

2019-08-19T17:41:23Z

Transforming Created Particles in XML Files

← Older revision		Revision as of 17:41, 19 August 2019
Line 46:		Line 46:
	where		where

	* <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> define elements of the <math>\vec T</math> translation vector (in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]).		* <tt>dX</tt>, <tt>dY</tt>, and <tt>dZ</tt> define elements of the <math>\vec T</math> translation vector (in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]). These values can be a [[User Defined Function]].

	* <tt>F11</tt>, <tt>F12</tt>, <tt>F13</tt>, ... <tt>F33</tt> can specify up to nine elements of the initial particle deformation gradient (dimensionless).		* <tt>F11</tt>, <tt>F12</tt>, <tt>F13</tt>, ... <tt>F33</tt> can specify up to nine elements of the initial particle deformation gradient (dimensionless).

Nairnj: /* Comments on Transform Command */

2018-10-10T22:42:16Z

Comments on Transform Command

← Older revision		Revision as of 22:42, 10 October 2018
Line 34:		Line 34:
	=== Comments on Transform Command ===		=== Comments on Transform Command ===

	# When not transforming particles, [[MPM Region and Hole Commands\|Region commands]] keep track of which locations in each cell are occupied by a material point. If two [[MPM Region and Hole Commands\|Region commands]] try to create particles at the same location, the first will create a particle and the second will do nothing. This feature lets you overlay regions without causing particle interferences. When particles are transformed, however, the particle locations of free from the grid and therefore particle locations are no longer tracked. In other words, whenever transforming particles, your input file in responsible for insuring that material points are not created in the same location. Similarly, transformed particle will be created in their new locations without regard to whether or that the location has be marked using a [[MPM Region and Hole Commands\|Hole command]].		# When not transforming particles, [[MPM Region and Hole Commands\|Region commands]] keep track of which locations in each cell are occupied by a material point. If two [[MPM Region and Hole Commands\|Region commands]] try to create particles at the same location, the first will create a particle and the second will do nothing. This feature lets you overlay regions without causing particle interferences. When particles are transformed, however, the particle locations of free from the grid and therefore particle locations are no longer tracked. In other words, whenever transforming particles, your input file in responsible for insuring that material points are not created in the same location. Similarly, transformed particle will be created in their new locations without regard to whether or that the location has been marked using a [[MPM Region and Hole Commands\|Region or Hole command]].
	# Only one transformation is allowed in each [[MPM Region and Hole Commands\|Region command]] and the transformation applies to all particles created by that command.		# Only one transformation is allowed in each [[MPM Region and Hole Commands\|Region command]] and the transformation applies to all particles created by that command.
	# When transforming rigid particles, the effect of rotations will not affect the simulation results unless shape functions account for particle deformation (''e.g.'', by using [[MPM Methods and Simulation Timing\|CPDI shape functions]]).		# When transforming rigid particles, the effect of rotations will not affect the simulation results unless shape functions account for particle deformation (''e.g.'', by using [[MPM Methods and Simulation Timing\|CPDI shape functions]]).

Nairnj: /* Comments on Transform Command */

2018-10-10T22:41:23Z

Comments on Transform Command

← Older revision		Revision as of 22:41, 10 October 2018
Line 34:		Line 34:
	=== Comments on Transform Command ===		=== Comments on Transform Command ===

	# When not transforming particles, ~~the~~ [[MPM Region and Hole Commands\|Region commands]] keep track of which locations in each cell are occupied by a material point. If two [[MPM Region and Hole Commands\|Region commands]] try to create particles at the same location, the first will create a particle and the second will do nothing. This feature lets you overlay regions without causing particle interferences. When particles are transformed, however, the particle locations of free from the grid and therefore particle locations are no longer tracked. In other words, whenever transforming particles, your input file in responsible for insuring that material points are not created in the same location. Similarly, transformed particle will be created in their new locations without regard to whether or that the location has be marked using a [[MPM Region and Hole Commands\|Hole command]].		# When not transforming particles, [[MPM Region and Hole Commands\|Region commands]] keep track of which locations in each cell are occupied by a material point. If two [[MPM Region and Hole Commands\|Region commands]] try to create particles at the same location, the first will create a particle and the second will do nothing. This feature lets you overlay regions without causing particle interferences. When particles are transformed, however, the particle locations of free from the grid and therefore particle locations are no longer tracked. In other words, whenever transforming particles, your input file in responsible for insuring that material points are not created in the same location. Similarly, transformed particle will be created in their new locations without regard to whether or that the location has be marked using a [[MPM Region and Hole Commands\|Hole command]].
	# Only one transformation is allowed in each [[MPM Region and Hole Commands\|Region command]] and the transformation applies to all particles created by that command.		# Only one transformation is allowed in each [[MPM Region and Hole Commands\|Region command]] and the transformation applies to all particles created by that command.
	# When transforming rigid particles, the effect of rotations will not affect the simulation results unless shape functions account for particle deformation (''e.g.'', by using [[MPM Methods and Simulation Timing\|CPDI shape functions]]).		# When transforming rigid particles, the effect of rotations will not affect the simulation results unless shape functions account for particle deformation (''e.g.'', by using [[MPM Methods and Simulation Timing\|CPDI shape functions]]).

Nairnj: /* Transforming Created Particles in Script Files */

2018-10-10T22:41:09Z

Transforming Created Particles in Script Files

← Older revision		Revision as of 22:41, 10 October 2018
Line 30:		Line 30:
	Transform (angle),(Tx),(Ty),(Ox),(Oy),(angle2),(angle3),(Tz),(Oz)		Transform (angle),(Tx),(Ty),(Ox),(Oy),(angle2),(angle3),(Tz),(Oz)

	The transformation equation is the same as defined above in 2D, but now the rotation matrix, <math>\mathbf{R}</math> is for rotation using 3D Euler angles corresponding to rotation about z axis by <tt>(angle)</tt>, rotation about y axis by <tt>(angle2)</tt>, and last rotation about z axis by <tt>(angle3)</tt> (all in degrees). The <tt>(Tz)</tt> and <tt>Oz</tt> add z components to the translation and rotation origin vectors.		The transformation equation is the same as defined above in 2D, but now the rotation matrix, <math>\mathbf{R}</math> is for rotation using 3D Euler angles corresponding to rotation about z axis by <tt>(angle)</tt>, rotation about y axis by <tt>(angle2)</tt>, and last rotation about z axis by <tt>(angle3)</tt> (all in degrees). The <tt>(Tz)</tt> and <tt>(Oz)</tt> add z components to the translation and rotation origin vectors.

	=== Comments on Transform Command ===		=== Comments on Transform Command ===

Nairnj: /* Transforming Created Particles in XML Files */

2018-10-04T23:09:07Z

Transforming Created Particles in XML Files

← Older revision		Revision as of 23:09, 4 October 2018
Line 53:		Line 53:

	# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.		# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.
	# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should be deform particles because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.		# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should not deform particles this way because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.

	=== Comments on Deform Command ===		=== Comments on Deform Command ===

Nairnj: /* Transforming Created Particles in XML Files */

2018-10-04T23:08:09Z

Transforming Created Particles in XML Files

← Older revision		Revision as of 23:08, 4 October 2018
Line 52:		Line 52:
	If the provided deformation gradient corresponds to rigid rotation, this transformation will be identical to a corresponding [[#Transforming Created Particles in Script Files\|Transform command]] in a script file. The <tt>XML</tt> command, however, provides two additional options:		If the provided deformation gradient corresponds to rigid rotation, this transformation will be identical to a corresponding [[#Transforming Created Particles in Script Files\|Transform command]] in a script file. The <tt>XML</tt> command, however, provides two additional options:

	# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent ~~setting~~. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.		# In <tt>XML</tt> files, you can have more than one <tt>Deform</tt> command in a single <tt><Body></tt> element interspersed between shape commands used to create materials points. Each new <tt><Deform></tt> element will replace the transformation settings of the previous element. Each shape command within the <tt><Body></tt> will use the most recent transformation. To revert to creating particles with no transformations, you can insert an <tt><Undeform/></tt> element to remove previous settings and create subsequent particle by standard methods.
	# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should be deform particles because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.		# In <tt>XML</tt> files, you can deform particles using general deformation gradient that need not correspond to a rigid rotation materials. Normally you should be deform particles because the initial state would not have the correct initial stress state. An important except is when using rigid particles. A non-rotation deformation matrix can be used to deform rigid particle shapes to better conformed to a rigid surface. One example is to shear particles to create an angled surface.