Explicit FEA Mesh Generation - Revision history

Nairnj at 21:18, 2 June 2015

2015-06-02T21:18:39Z

← Older revision		Revision as of 21:18, 2 June 2015
Line 28:		Line 28:

	The <tt><NodeList></tt> block must have one <tt><pt></tt> tag for each nodal point.		The <tt><NodeList></tt> block must have one <tt><pt></tt> tag for each nodal point.
	The <tt>x</tt> and <tt>y</tt> attributes give the coordinates of each point in mm. The optional <tt>temp</tt> can be used to set the temperature of the node as the temperature difference relative to the stress free temperature.		The <tt>x</tt> and <tt>y</tt> attributes give the coordinates of each point in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]. The optional <tt>temp</tt> can be used to set the temperature of the node as the temperature difference relative to the stress free temperature.

	==== <ElementList> Block ====		==== <ElementList> Block ====
Line 39:		Line 39:
	* <tt>matname</tt>: Alternatively, materials can be specified [[Material Command Block#Referencing Materials in XML Files\|"By Name"]].		* <tt>matname</tt>: Alternatively, materials can be specified [[Material Command Block#Referencing Materials in XML Files\|"By Name"]].
	*<tt>angle</tt>: Optional material angle relevant to [[FEA Material Models\|anisotropic materials]].		*<tt>angle</tt>: Optional material angle relevant to [[FEA Material Models\|anisotropic materials]].
	*<tt>thick</tt>: Thickness in mm (for plane stress or plane strain 2D calculations)		*<tt>thick</tt>: Thickness in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] (for plane stress or plane strain 2D calculations)

	The value of the <tt><elem></tt> tags are the node numbers listed in the counter-clockwise direction. For elements with mid-side nodes, the corner nodes are first followed by the mid-side nodes. The numbers correspond to the above nodal list with the first node being numbered 1. The node numbers can be delimited by any white space, commas, colons, semicolons, or any combination of those delimiters.		The value of the <tt><elem></tt> tags are the node numbers listed in the counter-clockwise direction. For elements with mid-side nodes, the corner nodes are first followed by the mid-side nodes. The numbers correspond to the above nodal list with the first node being numbered 1. The node numbers can be delimited by any white space, commas, colons, semicolons, or any combination of those delimiters.

Nairnj: /* Explicit MPM Grid */

2013-11-19T17:31:37Z

Explicit MPM Grid

← Older revision		Revision as of 17:31, 19 November 2013
Line 52:		Line 52:

	# You should not use a <tt>temp</tt> attribute to set temperature of a node.		# You should not use a <tt>temp</tt> attribute to set temperature of a node.
	# The only attribute allowed for the <tt>Element</tt> tag is the <tt>type</tt> attribute. It must be 2 for 2D calculations and 7 for 3D calculations (to give [[Element Types#MPM ~~Elements~~\|four-node quadrilateral or eight-node brick elements]])		# The only attribute allowed for the <tt>Element</tt> tag is the <tt>type</tt> attribute. It must be 2 for 2D calculations and 7 for 3D calculations (to give [[Element Types#MPM Element Types\|four-node quadrilateral or eight-node brick elements]])

	Because many MPM features assume, and are only efficient in, a regular grid, you probably would never want to explicity define the MPM grid. Instead, you should always create the MPM grid using commands that [[MPM Grid Generation\|generate the grid]].		Because many MPM features assume, and are only efficient in, a regular grid, you probably would never want to explicity define the MPM grid. Instead, you should always create the MPM grid using commands that [[MPM Grid Generation\|generate the grid]].

Nairnj: /* Explicit MPM Grid */

2013-11-19T17:27:21Z

Explicit MPM Grid

← Older revision		Revision as of 17:27, 19 November 2013
Line 54:		Line 54:
	# The only attribute allowed for the <tt>Element</tt> tag is the <tt>type</tt> attribute. It must be 2 for 2D calculations and 7 for 3D calculations (to give [[Element Types#MPM Elements\|four-node quadrilateral or eight-node brick elements]])		# The only attribute allowed for the <tt>Element</tt> tag is the <tt>type</tt> attribute. It must be 2 for 2D calculations and 7 for 3D calculations (to give [[Element Types#MPM Elements\|four-node quadrilateral or eight-node brick elements]])

	Because many MPM features assume, and are only efficient in, a regular grid, you probably would never want to explicity define the MPM grid. Instead, you should ~~use~~ create the MPM grid using commands that [[MPM Grid Generation\|generate the grid]].		Because many MPM features assume, and are only efficient in, a regular grid, you probably would never want to explicity define the MPM grid. Instead, you should always create the MPM grid using commands that [[MPM Grid Generation\|generate the grid]].

Nairnj: /* Explicit MPM Grid */

2013-11-15T18:31:12Z

Explicit MPM Grid

← Older revision		Revision as of 18:31, 15 November 2013
Line 52:		Line 52:

	# You should not use a <tt>temp</tt> attribute to set temperature of a node.		# You should not use a <tt>temp</tt> attribute to set temperature of a node.
	# The only attribute allowed for the <tt>Element</tt> tag is the <tt>type</tt> attribute. It must be 2 for 2D calculations and 7 for 3D calculations (to give four-node quadrilateral or eight-node ~~block~~ elements)		# The only attribute allowed for the <tt>Element</tt> tag is the <tt>type</tt> attribute. It must be 2 for 2D calculations and 7 for 3D calculations (to give [[Element Types#MPM Elements\|four-node quadrilateral or eight-node brick elements]])

	Because many MPM features assume, and are only efficient in, a regular grid, you probably would never want to explicity define the MPM grid. Instead, you should use create the MPM grid using commands that [[MPM Grid Generation\|generate the grid]].		Because many MPM features assume, and are only efficient in, a regular grid, you probably would never want to explicity define the MPM grid. Instead, you should use create the MPM grid using commands that [[MPM Grid Generation\|generate the grid]].

Nairnj: /* Explicit MPM Grid */

2013-11-15T18:04:36Z

Explicit MPM Grid

← Older revision		Revision as of 18:04, 15 November 2013
Line 52:		Line 52:

	# You should not use a <tt>temp</tt> attribute to set temperature of a node.		# You should not use a <tt>temp</tt> attribute to set temperature of a node.
	# ~~Elements should~~ only ~~specify a~~ <tt>type</tt> attribute ~~and it~~ must be 2 for 2D calculations and 7 for 3D calculations.		# The only attribute allowed for the <tt>Element</tt> tag is the <tt>type</tt> attribute. It must be 2 for 2D calculations and 7 for 3D calculations (to give four-node quadrilateral or eight-node block elements)

	Because many MPM features assume, and are only efficient in, a regular grid, you ~~should~~ never ~~explicitly~~ define the MPM grid. Instead, you should use ~~command to~~ [[MPM Grid Generation\|generate the grid]].		Because many MPM features assume, and are only efficient in, a regular grid, you probably would never want to explicity define the MPM grid. Instead, you should use create the MPM grid using commands that [[MPM Grid Generation\|generate the grid]].

Nairnj: /* Explicit MPM Grid */

2013-11-15T18:02:39Z

Explicit MPM Grid

← Older revision		Revision as of 18:02, 15 November 2013
Line 49:		Line 49:
	== Explicit MPM Grid ==		== Explicit MPM Grid ==

	The above procedure can be used to explicitly define a background MPM ~~grid as well with the following~~ exceptions:		The above procedure for an explicit finite element mesh can also be used to explicitly define a background MPM. There are two exceptions:

	# You should not use a <tt>temp</tt> attribute to set temperature of a node.		# You should not use a <tt>temp</tt> attribute to set temperature of a node.

Nairnj: /* Explicit MPM Grid */

2013-09-27T20:03:11Z

Explicit MPM Grid

← Older revision		Revision as of 20:03, 27 September 2013
Line 49:		Line 49:
	== Explicit MPM Grid ==		== Explicit MPM Grid ==

	The above procedure can be used to ~~explicit~~ define a background MPM grid with the following exceptions:		The above procedure can be used to explicitly define a background MPM grid as well with the following exceptions:

	# You should not use a <tt>temp</tt> attribute to set temperature of a node.		# You should not use a <tt>temp</tt> attribute to set temperature of a node.
	# Elements should only specify a <tt>type</tt> attribute and it must be 2 for 2D calculations and 7 for 3D calculations		# Elements should only specify a <tt>type</tt> attribute and it must be 2 for 2D calculations and 7 for 3D calculations.

	Because many MPM features assume, and are only efficient in, a regular grid, you should never ~~explicit~~ define the MPM grid. Instead, you should use command to generate the grid.		Because many MPM features assume, and are only efficient in, a regular grid, you should never explicitly define the MPM grid. Instead, you should use command to [[MPM Grid Generation\|generate the grid]].

Nairnj at 20:00, 27 September 2013

2013-09-27T20:00:57Z

← Older revision		Revision as of 20:00, 27 September 2013
Line 46:		Line 46:

	If some elements in the explicitly defined mesh are set to <tt>mat=0</tt>, you can follow the <tt><Mesh></tt> block with [[Create a Mesh with Images and Shapes\|image and shape commands]] to fill in material types, angles, and define the final mesh geometry. This option is described [[Create a Mesh with Images and Shapes\|here]].		If some elements in the explicitly defined mesh are set to <tt>mat=0</tt>, you can follow the <tt><Mesh></tt> block with [[Create a Mesh with Images and Shapes\|image and shape commands]] to fill in material types, angles, and define the final mesh geometry. This option is described [[Create a Mesh with Images and Shapes\|here]].

			== Explicit MPM Grid ==

			The above procedure can be used to explicit define a background MPM grid with the following exceptions:

			# You should not use a <tt>temp</tt> attribute to set temperature of a node.
			# Elements should only specify a <tt>type</tt> attribute and it must be 2 for 2D calculations and 7 for 3D calculations

			Because many MPM features assume, and are only efficient in, a regular grid, you should never explicit define the MPM grid. Instead, you should use command to generate the grid.

Nairnj: /* Using Images and Shapes */

2013-09-11T03:47:58Z

Using Images and Shapes

← Older revision		Revision as of 03:47, 11 September 2013
Line 45:		Line 45:
	== Using Images and Shapes ==		== Using Images and Shapes ==

	If some elements in the explicitly defined mesh are set to <tt>mat=0</tt>, you can follow the <tt><Mesh></tt> block with [[Create a Mesh with Images and Shapes\|image and shape commands]] to fill in material types, angles, and define the final mesh geometry. This option is described [[Create a Mesh with Images and Shapes\|~~elsewhere~~]]		If some elements in the explicitly defined mesh are set to <tt>mat=0</tt>, you can follow the <tt><Mesh></tt> block with [[Create a Mesh with Images and Shapes\|image and shape commands]] to fill in material types, angles, and define the final mesh geometry. This option is described [[Create a Mesh with Images and Shapes\|here]].

Nairnj: /* Block */

2013-09-11T03:47:00Z

Block

← Older revision		Revision as of 03:47, 11 September 2013
Line 36:		Line 36:

	* <tt>type</tt>: The type of [[FEA Elements\|element by number]].		* <tt>type</tt>: The type of [[FEA Elements\|element by number]].
	* <tt>mat</tt> (or <tt>matl</tt> for backward compatibility): Material number in the list of [[Material Command Block#XML Input Commands\|defined materials]] when referring to a material [[Material Command Block#Referencing Materials in XML Files\|"By Number"]]. If you are using [[Create a Mesh with Images and Shapes\|images and ~~shapes~~ commands]] to set element properties, the <tt>mat</tt> should be 0 for elements that will be set later by other commands.		* <tt>mat</tt> (or <tt>matl</tt> for backward compatibility): Material number in the list of [[Material Command Block#XML Input Commands\|defined materials]] when referring to a material [[Material Command Block#Referencing Materials in XML Files\|"By Number"]]. If you are using [[Create a Mesh with Images and Shapes\|images and shape commands]] to set element properties, the <tt>mat</tt> should be 0 for elements that will be set later by other commands.
	* <tt>matname</tt>: Alternatively, materials can be specified [[Material Command Block#Referencing Materials in XML Files\|"By Name"]].		* <tt>matname</tt>: Alternatively, materials can be specified [[Material Command Block#Referencing Materials in XML Files\|"By Name"]].
	*<tt>angle</tt>: Optional material angle relevant to [[FEA Material Models\|anisotropic materials]].		*<tt>angle</tt>: Optional material angle relevant to [[FEA Material Models\|anisotropic materials]].

← Older revision		Revision as of 03:47, 11 September 2013
Line 36:		Line 36:

	* <tt>type</tt>: The type of [[FEA Elements\|element by number]].		* <tt>type</tt>: The type of [[FEA Elements\|element by number]].
	* <tt>mat</tt> (or <tt>matl</tt> for backward compatibility): Material number in the list of [[Material Command Block#XML Input Commands\|defined materials]] when referring to a material [[Material Command Block#Referencing Materials in XML Files\|"By Number"]]. If you are using [[Create a Mesh with Images and Shapes\|images and ~~shapes~~ commands]] to set element properties, the <tt>mat</tt> should be 0 for elements that will be set later by other commands.		* <tt>mat</tt> (or <tt>matl</tt> for backward compatibility): Material number in the list of [[Material Command Block#XML Input Commands\|defined materials]] when referring to a material [[Material Command Block#Referencing Materials in XML Files\|"By Number"]]. If you are using [[Create a Mesh with Images and Shapes\|images and shape commands]] to set element properties, the <tt>mat</tt> should be 0 for elements that will be set later by other commands.
	* <tt>matname</tt>: Alternatively, materials can be specified [[Material Command Block#Referencing Materials in XML Files\|"By Name"]].		* <tt>matname</tt>: Alternatively, materials can be specified [[Material Command Block#Referencing Materials in XML Files\|"By Name"]].
	*<tt>angle</tt>: Optional material angle relevant to [[FEA Material Models\|anisotropic materials]].		*<tt>angle</tt>: Optional material angle relevant to [[FEA Material Models\|anisotropic materials]].