XML Input Files for NairnMPM - Revision history

Nairnj: /* MPM Input XML File Definition */

2014-11-05T16:01:33Z

MPM Input XML File Definition

← Older revision		Revision as of 16:01, 5 November 2014
Line 86:		Line 86:
	<CrackList>		<CrackList>
	( pt \| Line \| Circle \| Thickness )		( pt \| Line \| Circle \| Thickness )
	</~~MaterialPoints~~ >		</CrackList >

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

Nairnj: /* FEA Input XML File Definition */

2014-01-15T07:05:14Z

FEA Input XML File Definition

← Older revision		Revision as of 07:05, 15 January 2014
Line 1:		Line 1:
	Input <tt>XML</tt> files for [[NairnMPM]] must conform to the definition on this page.		Input <tt>XML</tt> files for [[NairnMPM]] must conform to the definition on this page.
	__TOC__		__TOC__
	== ~~FEA~~ Input XML File Definition ==		== MPM Input XML File Definition ==

	All <tt>XML</tt> input command files for MPM calculations in [[NairnMPM]] 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 MPM input <tt>XMlL</tt> files is given in the <tt>DTD</tt> file provided in the source code files at <tt>NairnMPM/input/NairnMPM.dtd</tt>.		All <tt>XML</tt> input command files for MPM calculations in [[NairnMPM]] 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 MPM input <tt>XMlL</tt> files is given in the <tt>DTD</tt> file provided in the source code files at <tt>NairnMPM/input/NairnMPM.dtd</tt>.

Nairnj: /* FEA Input XML File Definition */

2014-01-15T07:04:46Z

FEA Input XML File Definition

← Older revision		Revision as of 07:04, 15 January 2014
Line 95:		Line 95:
	<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>
	<td style="padding-left:10px;">Define each material in a separate <tt>~~MaterialM~~</tt> element</td>		<td style="padding-left:10px;">Define each material in a separate <tt>Material</tt> element</td>
	</tr>		</tr>

Nairnj: /* Sample Input XML File */

2014-01-15T06:01:33Z

Sample Input XML File

← Older revision		Revision as of 06:01, 15 January 2014
Line 173:		Line 173:
	== 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 MPM Input Command File#XML MPM Input Command File\|sample XML MPM input command file]] for analysis of an end-loaded cantilever beam.

	== Notes ==		== Notes ==

Nairnj: /* FEA Input XML File Definition */

2014-01-15T05:59:57Z

FEA Input XML File Definition

← Older revision		Revision as of 05:59, 15 January 2014
Line 79:		Line 79:
	</pre></td>		</pre></td>
	<td style="padding-left:10px;">This section fills the grid with material points</td>		<td style="padding-left:10px;">This section fills the grid with material points</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;">
			<CrackList>
			( pt \| Line \| Circle \| Thickness )
			</MaterialPoints >

			</pre></td>
			<td style="padding-left:10px;">One <tt>CrackList</tt> block for each explicit crack in the simulation.</td>
	</tr>		</tr>

Line 87:		Line 98:

	</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>MaterialM</tt> element</td>
	</tr>		</tr>

Line 94:		Line 105:
	<pre style="border-style:none;margin:0px;padding:0px 10px;">		<pre style="border-style:none;margin:0px;padding:0px 10px;">
	<GridBCs>		<GridBCs>
	~~( Cracktip )~~		( DisplacementBCs \| BCLine \| LdRect
	( DisplacementBCs \| ~~LoadBCs~~ \| ~~EdgeBCs~~		\| BCArc \| BCBox )
	~~\| BCLine~~ \| ~~BCPt~~ \| ~~Periodic )~~
	~~( Resequence~~ )
	</GridBCs>		</GridBCs>

	</pre></td>		</pre></td>
	<td style="padding-left:10px;">Define all boundary conditions~~[[#Notes~~\|<~~sup~~>4</~~sup~~>]]</td>		<td style="padding-left:10px;">Define all grid-based boundary conditions</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;">
			<ParticleBCs>
			( LoadBCs \| LdRect \| BCLine
			\| BCArc \| BCBox )
			</ParticleBCs >

			</pre></td>
			<td style="padding-left:10px;">Define all particle-based boundary conditions</td>
	</tr>		</tr>

Line 108:		Line 129:
	<pre style="border-style:none;margin:0px;padding:0px 10px;">		<pre style="border-style:none;margin:0px;padding:0px 10px;">
	<Thermal>		<Thermal>
	( ~~Temperature, StressFreeTemp~~)		( Conduction \| CrackTipHeating \| EnergyCoupling
			\| NoAVHeating \| Isothermal \| CrackContactHeating
			\| ContactHeating )
	</Thermal>		</Thermal>

	</pre></td>		</pre></td>
	<td style="padding-left:10px;">Optional</td>		<td style="padding-left:10px;">Optional thermal calculations</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;">
			<Gravity>
			( BodyXForce \| BodyYForce \| BodyZForce )
			</Gravity>

			</pre></td>
			<td style="padding-left:10px;">Optional gravity section</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;">
			<CustomTasks>
			( Schedule )
			</CustomTasks>

			</pre></td>
			<td style="padding-left:10px;">Add any custom tasks to be used</td>
	</tr>		</tr>


	<tr>		<tr>

Nairnj: /* FEA Input XML File Definition */

2014-01-15T05:50:45Z

FEA Input XML File Definition

← Older revision		Revision as of 05:50, 15 January 2014
Line 73:		Line 73:
	<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 )		<MaterialPoints>
			( PointList \| Body \| Hole \| BMP )
			</MaterialPoints >

	</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;">This section fills the grid with material points</td>
	</tr>		</tr>

Nairnj: /* FEA Input XML File Definition */

2014-01-15T05:47:49Z

FEA Input XML File Definition

← Older revision		Revision as of 05:47, 15 January 2014
Line 61:		Line 61:
	<pre style="border-style:none;margin:0px;padding:0px 10px;">		<pre style="border-style:none;margin:0px;padding:0px 10px;">
	<Mesh>		<Mesh>
	( ~~Keypoints, Path, Area~~ )		( Grid )
	or		or
	( NodeList, ElementList)		( NodeList, ElementList )
	</~~Header~~>		</Mesh>

	</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 background grid is usually generated with a <tt>Grid</tt> command, but can be defined explicitly.</td>
	</tr>		</tr>

Nairnj at 05:45, 15 January 2014

2014-01-15T05:45:11Z

Show changes

Nairnj: Created page with "All `XML` input command files for MPM calculations must begin with an `XML` declaration, an optional document type declaration, and the main input file tag and e..."

2013-09-11T19:54:10Z

Created page with "All <tt>XML</tt> input command files for MPM calculations must begin with an <tt>XML</tt> declaration, an optional document type declaration, and the main input file tag and e..."

New page

All <tt>XML</tt> input command files for MPM calculations must begin with an <tt>XML</tt> declaration, an optional document type declaration, and the main input file tag and end with the corresponding closing tags. For MPM calculations, the global file structure is:

<pre>
<?xml version='1.0'?>
<!DOCTYPE JANFEAInput SYSTEM "NairnMPM.dtd"
[
<!ENTITY maxtime "1e-03">
<!ENTITY width "100">
]>
<JANFEAInput version='3'>
...
(XML Command to define the calculation)
...
</JANFEAInput>
</pre>

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. This path is needed when you [[Running_MPM_Calculations|run the code]] with the validation option (<tt>-v</tt>), which is highly recommended. The required <tt>DTD</tt> file for MPM 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. For example, the above MPM file can use the entity <tt>&maxtime;</tt> and it will be replaced with the text <tt>1e-03</tt>. Entities can define values that make it easier to read input <tt>XML</tt> files and easier to modify them for new calculations.

The remainder of the file is included withing a <tt>JANFEAInput</tt> block. The <tt>version</tt> attribute is currently not needed, but may be important in the future. When input files are validated using the DTD file (as recommended), the sections must appear in the specified order 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 MPM Input Command FIle|sample XML MPM input command file]] for simulation of two colliding disks.

XML Input Files for NairnMPM - Revision history

Nairnj: /* MPM Input XML File Definition */

Nairnj: /* FEA Input XML File Definition */

Nairnj: /* FEA Input XML File Definition */

Nairnj: /* Sample Input XML File */

Nairnj: /* FEA Input XML File Definition */

Nairnj: /* FEA Input XML File Definition */

Nairnj: /* FEA Input XML File Definition */

Nairnj at 05:45, 15 January 2014

Nairnj: Created page with "All XML input command files for MPM calculations must begin with an XML declaration, an optional document type declaration, and the main input file tag and e..."

Nairnj: Created page with "All `XML` input command files for MPM calculations must begin with an `XML` declaration, an optional document type declaration, and the main input file tag and e..."