Difference between revisions of "MPM Input Files"

From OSUPDOCS
Jump to navigation Jump to search
(Created page with "The following are all the possible sections for input XML files for running NairnMPM. When input files are validated using the DTD file (as recommended), the sections must app...")
 
Line 1: Line 1:
The following are all the possible sections for input XML files for running NairnMPM. When input files are validated using the DTD file (as recommended), the sections must appear in the specified order. Optional sections that are not needed may be omitted. A sample NairnMPM input file shows a sample calculation of two colliding disks.
The following are all the possible sections for input XML files for running NairnMPM. When input files are validated using the DTD file (as recommended), the sections must appear in the specified order. Optional sections that are not needed may be omitted. A sample NairnMPM input file shows a sample calculation of two colliding disks.


File Start Header MPM Header Defining the MPM Background Grid Generated MPM Grid Explicit Mesh Definition Defining the Material Points Defining Cracks (optional) Defining Materials Grid Boundary Conditions (optional) Generated Grid Boundary Conditions Generated Velocity Conditions Generated Temperature Conditions Generated Concentration Conditions Explicit Velocity Conditions Particle Boundary Conditions (optional) Generated Particle Boundary Conditions Generated Particle Load Conditions Generated Concentration Flux Conditions Explicit Particle Loading Thermal Conduction and Loading (optional) Adding Gravity Field (optional) Custom Tasks (optional) End the File
== XML File Overview ==
 
All input files for MPM calculations are <tt>XML</tt> files. When using [[NairnFEAMPM]] or [[NairnFEAMPMViz]] to set up calculations using a scripting language, the XML file is created for you by interpreting the scripting commands (and you can skip this section). If you are manually writing <tt>XML</tt> files, however, it must follow the structure defined in this section.
 
All <tt>XML</tt> command files for MPM 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 MPM calculations, the global file structure is:
 
<pre>
&lt;?xml version='1.0'?&gt;
&lt;!DOCTYPE JANFEAInput SYSTEM &quot;NairnMPM.dtd&quot;
[
  &lt;!ENTITY maxtime &quot;1e-03&quot;&gt;
  &lt;!ENTITY width &quot;100&quot;&gt; 
]&gt;
&lt;JANFEAInput version='3'&gt;
  ...
  (XML Command to define the calculation)
  ...
&lt;/JANFEAInput&gt;
</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. The 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>&amp;maxtime;</tt> and it will be replaced with the text <code>1e-03</code>. 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. 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 table of contents on this page. Elements that are not used can be omitted, but all needed elements must be in that specific order.
 
== Main Header ==
== MPM Header ==
== Creating the MPM Background Grid ==
=== Generated MPM Grid ===
=== Explicit Mesh Definition ===
== Creating the Material Point ==
== Using Explicit Cracks ==
== Defining Material Models ==
== Grid-Based Boundary Conditions ==
=== Velocity Conditions ===
=== Temperature Conditions ===
=== Concentration Conditions ===
=== Explicit Grid-Based Boundary Conditions ===
== Particle-Based Boundary Conditions ==
=== Load and Traction Conditions ===
=== Concentration Flux Conditions ===
=== Explicit Particle-Based Boundary Conditions ===
== Thermal Calculations ==
=== Conduction ===
=== Thermal Ramp ===
== Gravitation Field ==
== Custom Tasks ==

Revision as of 09:31, 22 March 2013

The following are all the possible sections for input XML files for running NairnMPM. When input files are validated using the DTD file (as recommended), the sections must appear in the specified order. Optional sections that are not needed may be omitted. A sample NairnMPM input file shows a sample calculation of two colliding disks.

XML File Overview

All input files for MPM calculations are XML files. When using NairnFEAMPM or NairnFEAMPMViz to set up calculations using a scripting language, the XML file is created for you by interpreting the scripting commands (and you can skip this section). If you are manually writing XML files, however, it must follow the structure defined in this section.

All XML command files for MPM calculations must begin with an XML 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:

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

The !DOCTYPE element defines the file type and has the SYSTEM option to provide a path to a Document Type Definition (or DTD) file. The path is needed when you run the code with the validation option (-v), which is highly recommended. The required DTD file for MPM calculations is provided in the /input folder of the source code files.

The !DOCTYPE element can define any number of entities. These entities can be used elsewhere in the text of the XML file and they will be replaced by the text in the entity definition. For example, the above MPM file can use the entity &maxtime; and it will be replaced with the text 1e-03. Entities can define values that make it easier to read input XML files and easier to modify them for new calculations.

The remainder of the file is included withing a JANFEAInput block. The version attribute is currently not needed, but may be important in the future. To be consistent with the document definition in the DTD file, all elements with the JANFEAInput block must be entered in the ordered defined in the table of contents on this page. Elements that are not used can be omitted, but all needed elements must be in that specific order.

Main Header

MPM Header

Creating the MPM Background Grid

Generated MPM Grid

Explicit Mesh Definition

Creating the Material Point

Using Explicit Cracks

Defining Material Models

Grid-Based Boundary Conditions

Velocity Conditions

Temperature Conditions

Concentration Conditions

Explicit Grid-Based Boundary Conditions

Particle-Based Boundary Conditions

Load and Traction Conditions

Concentration Flux Conditions

Explicit Particle-Based Boundary Conditions

Thermal Calculations

Conduction

Thermal Ramp

Gravitation Field

Custom Tasks