Area Command - Revision history

Nairnj: /* Scripted Area Block */

2016-12-06T06:29:34Z

Scripted Area Block

← Older revision		Revision as of 06:29, 6 December 2016
Line 40:		Line 40:
	Each path can be explicitly defined (<i>e.g.</i>, the paths with subordinate [[Keypoint Command\|Keypoint commands]]) or can refer to a previously defined path (<i>e.g.</i>, the [[Path Command\|Paths]] commands with one or more path names). See the [[Path Command\|Path]] and [[Keypoint Command\|Keypoint]] commands for details on defining paths and keypoints.		Each path can be explicitly defined (<i>e.g.</i>, the paths with subordinate [[Keypoint Command\|Keypoint commands]]) or can refer to a previously defined path (<i>e.g.</i>, the [[Path Command\|Paths]] commands with one or more path names). See the [[Path Command\|Path]] and [[Keypoint Command\|Keypoint]] commands for details on defining paths and keypoints.

	The [[~~FEA Elements~~\|element type]] to use when meshing the area is determined by the [[FEA Elements#Scripted Input Files\|Element and FlipTriangles commands]].		The [[Element Types\|element type]] to use when meshing the area is determined by the [[FEA Elements#Scripted Input Files\|Element and FlipTriangles commands]].

	See more [[#Area Details\|details below]].		See more [[#Area Details\|details below]].

Nairnj: /* XML Area Block */

2015-06-02T21:03:14Z

XML Area Block

← Older revision		Revision as of 21:03, 2 June 2015
Line 62:		Line 62:
	* <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]]. It can be entered as a number or as a [[User Defined Functions\|function]]. A function is evaluated at the midpoint of an element. Triangular elements are created in pairs and the function is evaluated at the midpoint of each pair.		*<tt>angle</tt>: Optional material angle relevant to [[FEA Material Models\|anisotropic materials]]. It can be entered as a number or as a [[User Defined Functions\|function]]. A function is evaluated at the midpoint of an element. Triangular elements are created in pairs and the function is evaluated at the midpoint of each pair.
	* <tt>thick</tt>: Thickness in mm (for plane stress or plane strain 2D calculations); not needed for axisymmetric analysis.		* <tt>thick</tt>: Thickness in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] (for plane stress or plane strain 2D calculations); not needed for axisymmetric analysis.
	* <tt>type</tt>: The type of [[FEA Elements\|element to create]] in the meshed area.		* <tt>type</tt>: The type of [[FEA Elements\|element to create]] in the meshed area.
	* <tt>flip</tt>: For triangular elements, the initially created quadrilaterials are split into two elements by drawing a diagonal across the quadrilaterial. The <tt>flip</tt> option can change which diagonal is used. It should be 0 or 1. Once it is set, it will apply to that area and all subsequent areas until it is changed.		* <tt>flip</tt>: For triangular elements, the initially created quadrilaterials are split into two elements by drawing a diagonal across the quadrilaterial. The <tt>flip</tt> option can change which diagonal is used. It should be 0 or 1. Once it is set, it will apply to that area and all subsequent areas until it is changed.

Nairnj: /* Scripted Area Block */

2015-06-02T21:02:35Z

Scripted Area Block

← Older revision		Revision as of 21:02, 2 June 2015
Line 32:		Line 32:
	<li><tt>(id)</tt> is the material ID for a previously defined [[FEA Material Models\|material]]. All elements in the area will be set to this material. When the mesh will be defined using [[Create a Mesh with Images and Shapes\|images and shapes]], set the material ID for any region that will use the images and shapes to be <tt>_NONE_</tt>; the images and shapes will fill in the materials later.</li>		<li><tt>(id)</tt> is the material ID for a previously defined [[FEA Material Models\|material]]. All elements in the area will be set to this material. When the mesh will be defined using [[Create a Mesh with Images and Shapes\|images and shapes]], set the material ID for any region that will use the images and shapes to be <tt>_NONE_</tt>; the images and shapes will fill in the materials later.</li>

	<li><tt>(thick)</tt> is the thickness of all the elements in mm for 2D plane stress or plain strain analyses. It is ignored for axisymmetric analyses, but is still required.</li>		<li><tt>(thick)</tt> is the thickness of all the elements in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]] for 2D plane stress or plain strain analyses. It is ignored for axisymmetric analyses, but is still required.</li>

	<li>The optional <tt>(angle)</tt> is a material angle for all the elements. It may be needed for certain [[FEA Material Models\|anisotropic materials]]. It can be entered as a number or as a [[User Defined Functions\|user-defined function]]. A function is evaluated at the midpoint of an element. Triangular elements are created in pairs and the function is evaluated at the midpoint of each pair.</li>		<li>The optional <tt>(angle)</tt> is a material angle for all the elements. It may be needed for certain [[FEA Material Models\|anisotropic materials]]. It can be entered as a number or as a [[User Defined Functions\|user-defined function]]. A function is evaluated at the midpoint of an element. Triangular elements are created in pairs and the function is evaluated at the midpoint of each pair.</li>

Nairnj at 17:14, 20 January 2014

2014-01-20T17:14:59Z

← Older revision		Revision as of 17:14, 20 January 2014
Line 3:		Line 3:
	== Area Command Blocks ==		== Area Command Blocks ==

	== Scripted Area Block ==		=== Scripted Area Block ===

	In scripted files, the <tt>Area</tt> command is a block that begins with an <tt>Area</tt> command and ends with an <tt>EndArea</tt> command.		In scripted files, the <tt>Area</tt> command is a block that begins with an <tt>Area</tt> command and ends with an <tt>EndArea</tt> command.

Nairnj at 17:14, 20 January 2014

2014-01-20T17:14:44Z

← Older revision		Revision as of 17:14, 20 January 2014
Line 1:		Line 1:
	The <tt>Area</tt> command defines a 2D area or a 1D interface which will automatically be divided into elements to [[FEA Mesh Generation Commands\|generate]] all or part of an FEA mesh.		The <tt>Area</tt> command defines a 2D area or a 1D interface which will automatically be divided into elements to [[FEA Mesh Generation Commands\|generate]] all or part of an FEA mesh.
	__TOC__		__TOC__
	== Area Command Blocks		== Area Command Blocks ==

	== Scripted Area Block ==		== Scripted Area Block ==

Nairnj: /* Area Details */

2014-01-20T17:14:02Z

Area Details

← Older revision		Revision as of 17:14, 20 January 2014
Line 74:		Line 74:

	<math>n_1+n_2 = n_3+n_4 \qquad{\rm or}\qquad n_1+n_4 = n_2+n_3</math>		<math>n_1+n_2 = n_3+n_4 \qquad{\rm or}\qquad n_1+n_4 = n_2+n_3</math>


	For interface meshing, the two paths must be different, but indentical paths. More more details see help on [[Imperfect Interfaces#Imperfect Interfaces in FEA\|imperfect interfaces in FEA]].		For interface meshing, the two paths must be different, but indentical paths. More more details see help on [[Imperfect Interfaces#Imperfect Interfaces in FEA\|imperfect interfaces in FEA]].

Nairnj: /* Area Details */

2014-01-20T17:13:53Z

Area Details

← Older revision		Revision as of 17:13, 20 January 2014
Line 70:		Line 70:
	Quadrilateral areas must use [[Element Types\|solid elements]] and interface areas must use [[Element Types\|interface elements]].		Quadrilateral areas must use [[Element Types\|solid elements]] and interface areas must use [[Element Types\|interface elements]].

	For quadrilateral areas, the end of the fourth path must connect to the start of the first path. The direction of each path does not matter as they will be rearranged if needed to define the area; but the paths must circumnavigate the area in the counter-clockwise direction. Furthermore, if n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub>, and n<sub>4</sub> are the number of intervals along the four paths, they must satisfy ~~either n~~<~~sub>1</sub~~>+~~n<sub>2</sub>~~=~~n<sub>3</sub>~~+~~n<sub>4</sub>~~ or ~~n<sub>1</sub>~~+~~n<sub>4</sub>~~=~~n<sub>2</sub>~~+~~n<sub>3~~</~~sub~~>.		For quadrilateral areas, the end of the fourth path must connect to the start of the first path. The direction of each path does not matter as they will be rearranged if needed to define the area; but the paths must circumnavigate the area in the counter-clockwise direction. Furthermore, if n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub>, and n<sub>4</sub> are the number of intervals along the four paths, they must satisfy


			<math>n_1+n_2 = n_3+n_4 \qquad{\rm or}\qquad n_1+n_4 = n_2+n_3</math>


	For interface meshing, the two paths must be different, but indentical paths. More more details see help on [[Imperfect Interfaces#Imperfect Interfaces in FEA\|imperfect interfaces in FEA]].		For interface meshing, the two paths must be different, but indentical paths. More more details see help on [[Imperfect Interfaces#Imperfect Interfaces in FEA\|imperfect interfaces in FEA]].

Nairnj: /* Area Details */

2014-01-20T17:11:41Z

Area Details

← Older revision		Revision as of 17:11, 20 January 2014
Line 68:		Line 68:
	== Area Details ==		== Area Details ==

	Quadrilateral areas must use [[Element Types}solid elements]] and interface areas must use [[Element Types\|interface elements]].		Quadrilateral areas must use [[Element Types\|solid elements]] and interface areas must use [[Element Types\|interface elements]].

	For quadrilateral areas, the end of the fourth path must connect to the start of the first path. The direction of each path does not matter as they will be rearranged if needed to define the area; but the paths must circumnavigate the area in the counter-clockwise direction. Furthermore, if n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub>, and n<sub>4</sub> are the number of intervals along the four paths, they must satisfy either n<sub>1</sub>+n<sub>2</sub>=n<sub>3</sub>+n<sub>4</sub> or n<sub>1</sub>+n<sub>4</sub>=n<sub>2</sub>+n<sub>3</sub>.		For quadrilateral areas, the end of the fourth path must connect to the start of the first path. The direction of each path does not matter as they will be rearranged if needed to define the area; but the paths must circumnavigate the area in the counter-clockwise direction. Furthermore, if n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub>, and n<sub>4</sub> are the number of intervals along the four paths, they must satisfy either n<sub>1</sub>+n<sub>2</sub>=n<sub>3</sub>+n<sub>4</sub> or n<sub>1</sub>+n<sub>4</sub>=n<sub>2</sub>+n<sub>3</sub>.

Nairnj: /* Area Details */

2014-01-20T17:11:30Z

Area Details

← Older revision		Revision as of 17:11, 20 January 2014
Line 68:		Line 68:
	== Area Details ==		== Area Details ==

	Quadrilateral areas must use solid elements and interface areas must use interface elements.		Quadrilateral areas must use [[Element Types}solid elements]] and interface areas must use [[Element Types\|interface elements]].

	For quadrilateral areas, the end of the fourth path must connect to the start of the first path. The direction of each path does not matter as they will be rearranged if needed to define the area; but the paths must circumnavigate the area in the counter-clockwise direction. Furthermore, if n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub>, and n<sub>4</sub> are the number of intervals along the four paths, they must satisfy either n<sub>1</sub>+n<sub>2</sub>=n<sub>3</sub>+n<sub>4</sub> or n<sub>1</sub>+n<sub>4</sub>=n<sub>2</sub>+n<sub>3</sub>.		For quadrilateral areas, the end of the fourth path must connect to the start of the first path. The direction of each path does not matter as they will be rearranged if needed to define the area; but the paths must circumnavigate the area in the counter-clockwise direction. Furthermore, if n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub>, and n<sub>4</sub> are the number of intervals along the four paths, they must satisfy either n<sub>1</sub>+n<sub>2</sub>=n<sub>3</sub>+n<sub>4</sub> or n<sub>1</sub>+n<sub>4</sub>=n<sub>2</sub>+n<sub>3</sub>.

Nairnj: /* Area Details */

2014-01-20T17:10:56Z

Area Details

← Older revision		Revision as of 17:10, 20 January 2014
Line 67:		Line 67:

	== Area Details ==		== Area Details ==

			Quadrilateral areas must use solid elements and interface areas must use interface elements.

	For quadrilateral areas, the end of the fourth path must connect to the start of the first path. The direction of each path does not matter as they will be rearranged if needed to define the area; but the paths must circumnavigate the area in the counter-clockwise direction. Furthermore, if n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub>, and n<sub>4</sub> are the number of intervals along the four paths, they must satisfy either n<sub>1</sub>+n<sub>2</sub>=n<sub>3</sub>+n<sub>4</sub> or n<sub>1</sub>+n<sub>4</sub>=n<sub>2</sub>+n<sub>3</sub>.		For quadrilateral areas, the end of the fourth path must connect to the start of the first path. The direction of each path does not matter as they will be rearranged if needed to define the area; but the paths must circumnavigate the area in the counter-clockwise direction. Furthermore, if n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub>, and n<sub>4</sub> are the number of intervals along the four paths, they must satisfy either n<sub>1</sub>+n<sub>2</sub>=n<sub>3</sub>+n<sub>4</sub> or n<sub>1</sub>+n<sub>4</sub>=n<sub>2</sub>+n<sub>3</sub>.

	For interface meshing, the two paths must be different, but indentical paths. More more details see help on [[Imperfect Interfaces#Imperfect Interfaces in FEA\|imperfect interfaces in FEA]]~~. To insure this connection, the paths for an interface must have each been previously used in exactly one quadrilateral area~~.		For interface meshing, the two paths must be different, but indentical paths. More more details see help on [[Imperfect Interfaces#Imperfect Interfaces in FEA\|imperfect interfaces in FEA]].

	== Notes ==		== Notes ==

← Older revision		Revision as of 06:29, 6 December 2016
Line 40:		Line 40:
	Each path can be explicitly defined (<i>e.g.</i>, the paths with subordinate [[Keypoint Command\|Keypoint commands]]) or can refer to a previously defined path (<i>e.g.</i>, the [[Path Command\|Paths]] commands with one or more path names). See the [[Path Command\|Path]] and [[Keypoint Command\|Keypoint]] commands for details on defining paths and keypoints.		Each path can be explicitly defined (<i>e.g.</i>, the paths with subordinate [[Keypoint Command\|Keypoint commands]]) or can refer to a previously defined path (<i>e.g.</i>, the [[Path Command\|Paths]] commands with one or more path names). See the [[Path Command\|Path]] and [[Keypoint Command\|Keypoint]] commands for details on defining paths and keypoints.

	The [[~~FEA Elements~~\|element type]] to use when meshing the area is determined by the [[FEA Elements#Scripted Input Files\|Element and FlipTriangles commands]].		The [[Element Types\|element type]] to use when meshing the area is determined by the [[FEA Elements#Scripted Input Files\|Element and FlipTriangles commands]].

	See more [[#Area Details\|details below]].		See more [[#Area Details\|details below]].