FEA Input Files - Revision history

Nairnj: /* Header */

2024-04-18T00:40:47Z

Header

← Older revision		Revision as of 00:40, 18 April 2024
Line 24:		Line 24:
	* [[Controlling FEA Output]]		* [[Controlling FEA Output]]
	* [[Processors Command]] - pick number of processors for parallel code.		* [[Processors Command]] - pick number of processors for parallel code.
			* [[RandSeed Command]] - to pick a seed for random number generation
	* [[Setting Developer Flags]]		* [[Setting Developer Flags]]

Nairnj: /* Input Command File Overview */

2019-04-05T17:46:52Z

Input Command File Overview

← Older revision		Revision as of 17:46, 5 April 2019
Line 6:		Line 6:

	Alternatively, you can directly create <tt>XML</tt> input command files. Because this approach cannot use the language control options of a [[Scripting Language Syntax\|scripting language]], it is much less powerful then scripting methods and much harder to customize for a range of simulations. If you do use the manual <tt>XML</tt> method, the files must conform to the structure defined [[XML Input Files for NairnFEA\|here]]. Click this link to see a [[Sample FEA Input Command File#XML FEA Input Command File\|sample XML FEA input command file]] for analysis of an end-loaded cantilever beam.		Alternatively, you can directly create <tt>XML</tt> input command files. Because this approach cannot use the language control options of a [[Scripting Language Syntax\|scripting language]], it is much less powerful then scripting methods and much harder to customize for a range of simulations. If you do use the manual <tt>XML</tt> method, the files must conform to the structure defined [[XML Input Files for NairnFEA\|here]]. Click this link to see a [[Sample FEA Input Command File#XML FEA Input Command File\|sample XML FEA input command file]] for analysis of an end-loaded cantilever beam.

			Some commands support the use of [[User Defined Functions\|user defined functions]] to increase options for setting up simulations. These functions can be used in both scripting commands in and <tt>XML</tt> commands. Scripting commands can build functions using [[Expression Syntax\|string expressions]]. In <tt>XML</tt> files, you enter the entire function.

	==Header==		==Header==

Nairnj: /* Element Types */

2016-12-06T06:28:42Z

Element Types

← Older revision		Revision as of 06:28, 6 December 2016
Line 32:		Line 32:
	=== Element Types ===		=== Element Types ===

	Calculations can use various [[~~ElementTypes~~\|types of elements]] and can mix compatible element types.		Calculations can use various [[Element Types\|types of elements]] and can mix compatible element types.

	=== Explicit Cracks ===		=== Explicit Cracks ===

Nairnj: /* Explicit Cracks */

2016-12-06T06:28:35Z

Explicit Cracks

← Older revision		Revision as of 06:28, 6 December 2016
Line 30:		Line 30:
	An advanced mesh generation option is to [[Create a Mesh with Images and Shapes\|create the mesh with image and shape commands]]. When using this procedure, you first [[FEA Mesh Generation Commands\|generate]] or [[Explicit FEA Mesh Generation\|explicitly define]] a mesh and then follow that with [[Create a Mesh with Images and Shapes\|image and shape commands]] to define material types, define material angles, and create the final mesh geometry.		An advanced mesh generation option is to [[Create a Mesh with Images and Shapes\|create the mesh with image and shape commands]]. When using this procedure, you first [[FEA Mesh Generation Commands\|generate]] or [[Explicit FEA Mesh Generation\|explicitly define]] a mesh and then follow that with [[Create a Mesh with Images and Shapes\|image and shape commands]] to define material types, define material angles, and create the final mesh geometry.

	=== ~~Explicit Cracks~~ ===		=== Element Types ===

	Calculations can use various [[ElementTypes\|types of elements]] and can mix compatible element types.		Calculations can use various [[ElementTypes\|types of elements]] and can mix compatible element types.

Nairnj: /* Explicit Cracks */

2016-12-06T06:27:52Z

Explicit Cracks

← Older revision		Revision as of 06:27, 6 December 2016
Line 29:		Line 29:

	An advanced mesh generation option is to [[Create a Mesh with Images and Shapes\|create the mesh with image and shape commands]]. When using this procedure, you first [[FEA Mesh Generation Commands\|generate]] or [[Explicit FEA Mesh Generation\|explicitly define]] a mesh and then follow that with [[Create a Mesh with Images and Shapes\|image and shape commands]] to define material types, define material angles, and create the final mesh geometry.		An advanced mesh generation option is to [[Create a Mesh with Images and Shapes\|create the mesh with image and shape commands]]. When using this procedure, you first [[FEA Mesh Generation Commands\|generate]] or [[Explicit FEA Mesh Generation\|explicitly define]] a mesh and then follow that with [[Create a Mesh with Images and Shapes\|image and shape commands]] to define material types, define material angles, and create the final mesh geometry.

			=== Explicit Cracks ===

			Calculations can use various [[ElementTypes\|types of elements]] and can mix compatible element types.

	=== Explicit Cracks ===		=== Explicit Cracks ===

Nairnj: /* Header */

2015-06-02T20:50:16Z

Header

← Older revision		Revision as of 20:50, 2 June 2015
Line 18:		Line 18:

	* [[Analysis Command]] - pick the type of FEA analysis.		* [[Analysis Command]] - pick the type of FEA analysis.
			* [[ConsistentUnits Command]] - pick input and output units for the calculations
	* [[Description Command\|Annotation Commands]] - these commands let you annotate the calculations.		* [[Description Command\|Annotation Commands]] - these commands let you annotate the calculations.
	* [[Controlling FEA Output]]		* [[Controlling FEA Output]]

Nairnj: /* Input Command File Overview */

2014-01-03T02:51:13Z

Input Command File Overview

← Older revision		Revision as of 02:51, 3 January 2014
Line 5:		Line 5:
	When using [[NairnFEAMPM]] or [[NairnFEAMPMViz]] to set up calculations, the input command files are usually script files written using the custom [[Scripting Language Syntax\|scripting language]]. When you interpret these scripts, the applications will create an <tt>XML</tt> input command file that is needed to drive the code engines. Click this link to see a [[Sample FEA Input Command File\|sample scripted FEA input command file]] for analysis of an end-loaded cantilever beam.		When using [[NairnFEAMPM]] or [[NairnFEAMPMViz]] to set up calculations, the input command files are usually script files written using the custom [[Scripting Language Syntax\|scripting language]]. When you interpret these scripts, the applications will create an <tt>XML</tt> input command file that is needed to drive the code engines. Click this link to see a [[Sample FEA Input Command File\|sample scripted FEA input command file]] for analysis of an end-loaded cantilever beam.

	Alternatively, you can directly create <tt>XML</tt> input command files. Because this approach cannot use the language control options of a [[Scripting Language Syntax\|scripting language]], it is much less powerful then scripting methods and much harder to customize for a range of simulations. If you do use the manual <tt>XML</tt> method, the files must conform to the structure defined [[XML Input Files for NairnFEA\|here]]. Click this link to see a [[Sample FEA Input Command File\|sample XML FEA input command file]] for analysis of an end-loaded cantilever beam.		Alternatively, you can directly create <tt>XML</tt> input command files. Because this approach cannot use the language control options of a [[Scripting Language Syntax\|scripting language]], it is much less powerful then scripting methods and much harder to customize for a range of simulations. If you do use the manual <tt>XML</tt> method, the files must conform to the structure defined [[XML Input Files for NairnFEA\|here]]. Click this link to see a [[Sample FEA Input Command File#XML FEA Input Command File\|sample XML FEA input command file]] for analysis of an end-loaded cantilever beam.

	==Header==		==Header==

Nairnj at 19:45, 15 September 2013

2013-09-15T19:45:08Z

← Older revision		Revision as of 19:45, 15 September 2013
Line 1:		Line 1:
	FEA simulations are run using [[NairnFEA]]. Some of the key features of this code engine (with links) are listed [[NairnFEA\|here]]. The documentation on this page explains how to run FEA calculations by ~~described~~ all the ~~sections~~ of input command files.		FEA simulations are run using [[NairnFEA]]. Some of the key features of this code engine (with links) are listed [[NairnFEA\|here]]. The documentation on this page explains how to run FEA calculations by describing all the options of input command files.

	== Input Command File Overview ==		== Input Command File Overview ==

Nairnj: /* Explicit Cracks */

2013-09-15T16:36:52Z

Explicit Cracks

← Older revision		Revision as of 16:36, 15 September 2013
Line 31:		Line 31:
	=== Explicit Cracks ===		=== Explicit Cracks ===

	[[~~Explict~~ FEA Cracks\|Defining explicit cracks]] in a finite element mesh is simply a matter of having two separate paths joined at a crack tip. When FEA calculations include cracks in the proper form, [[NairnFEAMPM]] can do crack closure calculations to find energy release once the calculation are done (crack closure calculations are not yet available in [[NairnFEAMPMViz]]).		[[Explicit FEA Cracks\|Defining explicit cracks]] in a finite element mesh is simply a matter of having two separate paths joined at a crack tip. When FEA calculations include cracks in the proper form, [[NairnFEAMPM]] can do crack closure calculations to find energy release once the calculation are done (crack closure calculations are not yet available in [[NairnFEAMPMViz]]).

	=== Imperfect Interfaces ===		=== Imperfect Interfaces ===

Nairnj: /* Defining the FEA Mesh */

2013-09-15T06:46:33Z

Defining the FEA Mesh

← Older revision		Revision as of 06:46, 15 September 2013
Line 35:		Line 35:
	=== Imperfect Interfaces ===		=== Imperfect Interfaces ===

	[[NairnFEA]] supports modeling of [[Imperfect Interfaces\|imperfect interfaces]] between phases in composite materials by including imperfect [[FEA ~~Element~~\|interface elements]] at phase boundaries.		[[NairnFEA]] supports modeling of [[Imperfect Interfaces\|imperfect interfaces]] between phases in composite materials by including imperfect [[FEA Elements\|interface elements]] at phase boundaries.

	==Defining Materials==		==Defining Materials==