XML Input Files for NairnFEA - Revision history

Nairnj: /* FEA Input XML File Definition */

2014-01-15T07:06:47Z

FEA Input XML File Definition

← Older revision		Revision as of 07:06, 15 January 2014
Line 55:		Line 55:
	<td style="border-left:thin dashed blue;border-right:thin dashed blue;">		<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
	<pre style="border-style:none;margin:0px;padding:0px 10px;">		<pre style="border-style:none;margin:0px;padding:0px 10px;">
	( BMP \| Region \| Hole )		<BMP>…</BMP>
			<Region>…</Region>
			<Hole>…</Hole>

	</pre></td>		</pre></td>
	<td style="padding-left:10px;">These ~~are~~ used when [[Create a Mesh with Images and Shapes\|creating a mesh with images and shapes]]</td>		<td style="padding-left:10px;">These blocks used when [[Create a Mesh with Images and Shapes\|creating a mesh with images and shapes]]</td>
	</tr>		</tr>

Line 64:		Line 66:
	<td style="border-left:thin dashed blue;border-right:thin dashed blue;">		<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
	<pre style="border-style:none;margin:0px;padding:0px 10px;">		<pre style="border-style:none;margin:0px;padding:0px 10px;">
	( Material )		<Material>
			( property commands )
			</Material >

	</pre></td>		</pre></td>

Nairnj: /* FEA Input XML File Definition */

2014-01-15T07:03:25Z

FEA Input XML File Definition

← Older revision		Revision as of 07:03, 15 January 2014
Line 67:		Line 67:

	</pre></td>		</pre></td>
	<td style="padding-left:10px;">Define each material in a separate ~~element~~</td>		<td style="padding-left:10px;">Define each material in a separate <tt>Material</tt> block</td>
	</tr>		</tr>

Nairnj: /* Sample Input XML File */

2014-01-15T06:02:05Z

Sample Input XML File

← Older revision		Revision as of 06:02, 15 January 2014
Line 107:		Line 107:
	== Sample Input XML File ==		== Sample Input XML File ==

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

	== Notes ==		== Notes ==

Nairnj: /* FEA Input XML File Definition */

2014-01-15T05:48:49Z

FEA Input XML File Definition

← Older revision		Revision as of 05:48, 15 January 2014
Line 46:		Line 46:
	or		or
	( NodeList, ElementList)		( NodeList, ElementList)
	</~~Header~~>		</Mesh>

	</pre></td>		</pre></td>

Nairnj at 16:28, 15 September 2013

2013-09-15T16:28:09Z

← Older revision		Revision as of 16:28, 15 September 2013
Line 1:		Line 1:
	All <tt>XML</tt> input command files for FEA ~~calculations~~ must conform to the following document definition including order of all <tt>XML</tt> elements. This template lists the main element and their next-level subordinate elements. For the subordinate elements, those separated by a vertical bar (\|) mean any one of those elements in any order while those separated by commas mean in exactly that order. A more formal definition for FEA input files in given in the <tt>DTD</tt> file provided in the source files at <tt>NairnFEA/input/NairnFEA.dtd</tt>.		Input <tt>XML</tt> files for [[NairnFEA]] must conform to the definition on this page.
			__TOC__
			== FEA Input XML File Definition ==

			All <tt>XML</tt> input command files for FEA calculationsin [[NairnFEA]] must conform to the following document definition including order of all <tt>XML</tt> elements. This template lists only the top-level main element and their next-level subordinate elements. For the subordinate elements, those separated by a vertical bar (\|) mean any one of those elements in any order while those separated by commas mean in exactly that order. A more formal definition for FEA input <tt>XMlL</tt> files is given in the <tt>DTD</tt> file provided in the source code files at <tt>NairnFEA/input/NairnFEA.dtd</tt>.

	<table cellspacing="0" border="0">		<table cellspacing="0" border="0">

Line 99:		Line 104:

	</table>		</table>

			== Sample Input XML File ==

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

Nairnj at 16:24, 15 September 2013

2013-09-15T16:24:14Z

← Older revision		Revision as of 16:24, 15 September 2013
Line 26:		Line 26:
	<pre style="border-style:none;margin:0px;padding:0px 10px;">		<pre style="border-style:none;margin:0px;padding:0px 10px;">
	<Header>		<Header>
	( Analysis \| Description \| Output \| Select \| DevelFlag )		( Analysis \| Description \| Output
			\| Select \| DevelFlag )
	</Header>		</Header>

Line 43:		Line 44:

	</pre></td>		</pre></td>
	<td style="padding-left:10px;">The mesh can be generated (with keypoints, paths and areas) or explicit, but not both.</td>		<td style="padding-left:10px;">The mesh can be generated (with keypoints, paths and areas) or explicit, but not both</td>
	</tr>		</tr>

Line 49:		Line 50:
	<td style="border-left:thin dashed blue;border-right:thin dashed blue;">		<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
	<pre style="border-style:none;margin:0px;padding:0px 10px;">		<pre style="border-style:none;margin:0px;padding:0px 10px;">
	( BMP \| Region \| Hole )		( BMP \| Region \| Hole )

	</pre></td>		</pre></td>
	<td style="padding-left:10px;">These are used when .</td>		<td style="padding-left:10px;">These are used when [[Create a Mesh with Images and Shapes\|creating a mesh with images and shapes]]</td>
			</tr>

			<tr>
			<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
			( Material )

			</pre></td>
			<td style="padding-left:10px;">Define each material in a separate element</td>
			</tr>

			<tr>
			<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
			<GridBCs>
			( Cracktip )
			( DisplacementBCs \| LoadBCs \| EdgeBCs
			\| BCLine \| BCPt \| Periodic )
			( Resequence )
			</GridBCs>

			</pre></td>
			<td style="padding-left:10px;">Define all boundary conditions[[#Notes\|<sup>4</sup>]]</td>
			</tr>

			<tr>
			<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
			<Thermal>
			( Temperature, StressFreeTemp)
			</Thermal>

			</pre></td>
			<td style="padding-left:10px;">Optional</td>
	</tr>		</tr>

Line 58:		Line 93:
	<td style="border-left:thin dashed blue;border-right:thin dashed blue;border-bottom:thin dashed blue">		<td style="border-left:thin dashed blue;border-right:thin dashed blue;border-bottom:thin dashed blue">
	<pre style="border-style:none;margin:0px;padding:0px 10px;">		<pre style="border-style:none;margin:0px;padding:0px 10px;">
	</JANFEAInput>;		</JANFEAInput>
	</pre></td>		</pre></td>
	<td style="padding-left:10px;"> </td>		<td style="padding-left:10px;"> </td>
Line 72:		Line 107:
	# The <tt>!DOCTYPE</tt> element can define any number of entities. These entities can be used elsewhere in the text of the <tt>XML</tt> file and they will be replaced by the text in the entity definition. Entities can define values that make it easier to read input <tt>XML</tt> files and easier to modify them for new calculations.		# The <tt>!DOCTYPE</tt> element can define any number of entities. These entities can be used elsewhere in the text of the <tt>XML</tt> file and they will be replaced by the text in the entity definition. Entities can define values that make it easier to read input <tt>XML</tt> files and easier to modify them for new calculations.
	# All input commands are in the top-level <JANFEAInput> element. The <tt>version</tt> attribute is option, but might be used in the future.		# All input commands are in the top-level <JANFEAInput> element. The <tt>version</tt> attribute is option, but might be used in the future.
			# if the optional <tt>CrackTip</tt> and <tt>Resequence</tt> commands are used, they must be first and last, respectively, in the <tt>GridBCs</tt> element. The rest of the subordinate commands can be in any order.

Nairnj at 16:10, 15 September 2013

2013-09-15T16:10:08Z

← Older revision		Revision as of 16:10, 15 September 2013
Line 27:		Line 27:
	<Header>		<Header>
	( Analysis \| Description \| Output \| Select \| DevelFlag )		( Analysis \| Description \| Output \| Select \| DevelFlag )
	</Header></pre></td>		</Header>
	<td style="padding-left:10px;">~~The subordinate elements are in any order and one~~ <tt>Analysis</tt> is required.</td>
			</pre></td>
			<td style="padding-left:10px;">One <tt>Analysis</tt> is required.</td>
	</tr>		</tr>

Line 38:		Line 40:
	or		or
	( NodeList, ElementList)		( NodeList, ElementList)
	</Header></pre></td>		</Header>

			</pre></td>
	<td style="padding-left:10px;">The mesh can be generated (with keypoints, paths and areas) or explicit, but not both.</td>		<td style="padding-left:10px;">The mesh can be generated (with keypoints, paths and areas) or explicit, but not both.</td>
			</tr>

			<tr>
			<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
			( BMP \| Region \| Hole )

			</pre></td>
			<td style="padding-left:10px;">These are used when .</td>
	</tr>		</tr>

Nairnj at 16:06, 15 September 2013

2013-09-15T16:06:41Z

← Older revision		Revision as of 16:06, 15 September 2013
Line 1:		Line 1:
	All <tt>XML</tt> input command files for FEA calculations must ~~begin with an~~ <~~code~~>XML</~~code~~> ~~declaration, an optional document type declaration, and~~ the main ~~input file tag~~ and ~~end with~~ the ~~corresponding closing tags~~. ~~For~~ FEA ~~calculations,~~ the ~~global~~ file ~~structure is:~~		All <tt>XML</tt> input command files for FEA calculations must conform to the following document definition including order of all <tt>XML</tt> elements. This template lists the main element and their next-level subordinate elements. For the subordinate elements, those separated by a vertical bar (\|) mean any one of those elements in any order while those separated by commas mean in exactly that order. A more formal definition for FEA input files in given in the <tt>DTD</tt> file provided in the source files at <tt>NairnFEA/input/NairnFEA.dtd</tt>.
			<table cellspacing="0" border="0">
	<table cellspacing="0" ~~cellpadding~~="0">

	<tr>		<tr>
	<td><pre style="border-style:none;">		<td style="border-top:thin dashed blue;border-left:thin dashed blue;border-right:thin dashed blue;">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
	<?xml version='1.0'?>		<?xml version='1.0'?>
	<!DOCTYPE JANFEAInput SYSTEM "NairnFEA.dtd"		<!DOCTYPE JANFEAInput SYSTEM "NairnFEA.dtd"
Line 11:		Line 11:
	]>		]>
	</pre></td>		</pre></td>
	<td>XML ~~file start with optional entity~~</td>		<td style="padding-left:10px;">XML declaration[[#Notes\|<sup>1,2</sup>]]</td>
	</tr>		</tr>

	<tr>		<tr>
	<td><pre style="border-style:none;">		<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
	<JANFEAInput version='3'>		<JANFEAInput version='3'>
	</pre></td>		</pre></td>
	<td>~~This~~ element ~~encloses all input commands~~</td>		<td style="padding-left:10px;">Top level element[[#Notes\|<sup>3</sup>]]</td>
	</tr>		</tr>

	<~~/table~~>		<tr>
			<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
	<~~pre>~~
	~~<?xml version~~=~~'1.0'?&gt~~;
	~~<!DOCTYPE JANFEAInput SYSTEM "NairnFEA.dtd&quot~~;
	[
	~~&lt~~;~~!ENTITY force &quot~~;~~100&quot~~;~~>~~
	~~]>~~
	~~<JANFEAInput version='3'>~~

	<Header>		<Header>
	( Analysis \| Description \| Output \| Select \| DevelFlag )		( Analysis \| Description \| Output \| Select \| DevelFlag )
	</Header>		</Header></pre></td>
			<td style="padding-left:10px;">The subordinate elements are in any order and one <tt>Analysis</tt> is required.</td>
			</tr>

			<tr>
			<td style="border-left:thin dashed blue;border-right:thin dashed blue;">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
	<Mesh>		<Mesh>
	( Keypoints, Path+, Area+ )		( Keypoints, Path, Area )
	(~~XML Commands to define the calculation~~)		or
	~~...~~		( NodeList, ElementList)
	~~&lt~~;/~~JANFEAInput>~~		</Header></pre></td>
	</~~pre~~>		<td style="padding-left:10px;">The mesh can be generated (with keypoints, paths and areas) or explicit, but not both.</td>
			</tr>

	~~The~~ <tt>~~!DOCTYPE~~<~~/tt~~> ~~element defines the file type and has the~~ <tt>~~SYSTEM~~</~~tt> option to provide a path to a Document Type Definition (or <tt~~>~~DTD~~</tt>~~) file. The path is needed when you [[Options for Running Calculations\|run the code]] with the validation option (~~<~~tt>~~-~~v</tt>), which is highly recommended. The required <tt~~>~~DTD~~</~~tt> file for FEA calculations is provided in the <tt~~>~~/input~~</tt> ~~folder of the source code files.~~		<tr>
			<td style="border-left:thin dashed blue;border-right:thin dashed blue;border-bottom:thin dashed blue">
			<pre style="border-style:none;margin:0px;padding:0px 10px;">
			</JANFEAInput>;
			</pre></td>
			<td style="padding-left:10px;"> </td>
			</tr>

	The <tt>!DOCTYPE</tt> element can define any number of entities. These entities can be used elsewhere in the text of the <tt>XML</tt> file and they will be replaced by the text in the entity definition. Entities can define values that make it easier to read input <tt>XML</tt> ~~files and easier to modify them for new calculations.~~		</table>

	~~The remainder of the file is included within~~ a <tt>JANFEAInput</tt> block. The <tt>version</tt> attribute is currently not needed, but may be important in the future. To be consistent with the document definition in the <tt>DTD</tt> file, all elements with the <tt>JANFEAInput</tt> block must be entered in the ordered defined in the [[~~#toc~~\|~~table of contents~~]] ~~on this page. Elements that are not used can be omitted, but all needed elements must be in that specific order~~.		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.

	~~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~~.		== Notes ==

			# The <tt>!DOCTYPE</tt> element defines the file type and has the <tt>SYSTEM</tt> option to provide a path to a Document Type Definition (or <tt>DTD</tt>) file. The path is needed when you [[Options for Running Calculations\|run the code]] with the validation option (<tt>-v</tt>), which is highly recommended. The required <tt>DTD</tt> file for FEA calculations is provided in the <tt>/input</tt> folder of the source code files.
			# The <tt>!DOCTYPE</tt> element can define any number of entities. These entities can be used elsewhere in the text of the <tt>XML</tt> file and they will be replaced by the text in the entity definition. Entities can define values that make it easier to read input <tt>XML</tt> files and easier to modify them for new calculations.
			# All input commands are in the top-level <JANFEAInput> element. The <tt>version</tt> attribute is option, but might be used in the future.

Nairnj at 15:32, 15 September 2013

2013-09-15T15:32:16Z

← Older revision		Revision as of 15:32, 15 September 2013
Line 1:		Line 1:
	All <tt>XML</tt> input command files for FEA calculations must begin with an <code>XML</code> declaration, an optional document type declaration, and the main input file tag and end with the corresponding closing tags. For FEA calculations, the global file structure is:		All <tt>XML</tt> input command files for FEA calculations must begin with an <code>XML</code> declaration, an optional document type declaration, and the main input file tag and end with the corresponding closing tags. For FEA calculations, the global file structure is:

	<table ~~rowspacing~~="0">		<table cellspacing="0" cellpadding="0">

	<tr>		<tr>
Line 14:		Line 14:
	</tr>		</tr>

	<t>		<tr>
	<td><pre style="border-style:none;">		<td><pre style="border-style:none;">
	<JANFEAInput version='3'>		<JANFEAInput version='3'>
Line 22:		Line 22:

	</table>		</table>


	<pre>		<pre>

Nairnj at 15:29, 15 September 2013

2013-09-15T15:29:31Z

← Older revision		Revision as of 15:29, 15 September 2013
Line 1:		Line 1:
	All <tt>XML</tt> input command files for FEA calculations must begin with an <code>XML</code> declaration, an optional document type declaration, and the main input file tag and end with the corresponding closing tags. For FEA calculations, the global file structure is:		All <tt>XML</tt> input command files for FEA calculations must begin with an <code>XML</code> declaration, an optional document type declaration, and the main input file tag and end with the corresponding closing tags. For FEA calculations, the global file structure is:

	<table>		<table rowspacing="0">

	<tr>		<tr>
	<td>		<td><pre style="border-style:none;">
	<pre ~~textstyle~~={border-style='none'}>
	<?xml version='1.0'?>		<?xml version='1.0'?>
	<!DOCTYPE JANFEAInput SYSTEM "NairnFEA.dtd"		<!DOCTYPE JANFEAInput SYSTEM "NairnFEA.dtd"
Line 10:		Line 10:
	<!ENTITY force "100">		<!ENTITY force "100">
	]>		]>
	</pre>		</pre></td>
	<td>XML file start with optional entity</td>		<td>XML file start with optional entity</td>
	</tr>		</tr>

			<t>
			<td><pre style="border-style:none;">
			<JANFEAInput version='3'>
			</pre></td>
			<td>This element encloses all input commands</td>
			</tr>

	</table>		</table>