Difference between revisions of "MPM Input Files"

From OSUPDOCS
Jump to navigation Jump to search
Line 3: Line 3:
== Input Command File Overview ==
== Input Command File Overview ==


When using [[NairnFEAMPM]] or [[NairnFEAMPMViz]] to set up calculations, the input command files are script files. When you interpret these scripts, the applications will create an <tt>XML</tt> input command file that is needed to drive the code engines. Because the scripting language handles all the <tt>XML</tt> formatting, you can skip this section. See the help documentation in [[NairnFEAMPM]] or [[NairnFEAMPMViz]] for syntax and features of the scripting languages. Click this link to see a [[Sample MPM Input Command FIle|sample scripted MPM input command file]] for simulation of two colliding disks.
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 MPM Input Command FIle|sample scripted MPM input command file]] for simulation of two colliding disks.


Alternatively, you can directly create <tt>XML</tt> input command files (although usually much less powerful then learning the scripting methods). If you use the manual methods, the files must conform to the structure defined in this section. 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:
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 NairnMPM|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.


<pre>
When using [[NairnFEAMPM]] or [[NairnFEAMPMViz]] to set up calculations, the input command files are script files. When you interpret these scripts, the applications will create an <tt>XML</tt> input command file that is needed to drive the code engines. Because the scripting language handles all the <tt>XML</tt> formatting, you can skip this section. See the help documentation in [[NairnFEAMPM]] or [[NairnFEAMPMViz]] for syntax and features of the scripting languages. Click this link to see a [[Sample MPM Input Command FIle|sample scripted MPM input command file]] for simulation of two colliding disks.
&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. 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>&amp;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.
Alternatively, you can directly create <tt>XML</tt> input command files (although usually much less powerful then learning the scripting methods). If you use the manual methods, the files must conform to the structure defined in this section.


== Main Header ==
== Main Header ==

Revision as of 11:53, 11 September 2013

MPM simulations are run using OSParticulas and NairnMPM. Some of the key features of these code engines (with links) are listed here. The documentation on this page explains how to run MPM calculations by described all the sections of input command files.

Input Command File Overview

When using NairnFEAMPM or NairnFEAMPMViz to set up calculations, the input command files are usually script files written using the custom scripting language. When you interpret these scripts, the applications will create an XML input command file that is needed to drive the code engines. Click this link to see a sample scripted MPM input command file for simulation of two colliding disks.

Alternatively, you can directly create XML input command files. Because this approach cannot use the language control options of a 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 XML method, the files must conform to the structure defined here. Click this link to see a sample XML 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 script files. When you interpret these scripts, the applications will create an XML input command file that is needed to drive the code engines. Because the scripting language handles all the XML formatting, you can skip this section. See the help documentation in NairnFEAMPM or NairnFEAMPMViz for syntax and features of the scripting languages. Click this link to see a sample scripted MPM input command file for simulation of two colliding disks.

Alternatively, you can directly create XML input command files (although usually much less powerful then learning the scripting methods). If you use the manual methods, the files must conform to the structure defined in this section.

Main Header

This section defines the type of analysis to run and provides an optional description of the calculations. When using a scripting language, the header is created automatically and its content is controlled by commands defined below. When manually writing XML files, the header, which is required, is defined in a single header block:

<Header>
  (commands)
</Header>

The possible header commands are

MPM Header

This section defines many settings and features for the MPM calculations. When using a scripting language, the MPM header is created automatically by various commands defined in this section. When writing XML input files, all these commands must be within a single MPM header block:

<MPMHeader>
  (commands)
</MPMHeader>

The possible MPM header commands are given below by categories.

Creating the MPM Background Grid

Generated MPM Grid

Explicit Mesh Definition

Creating the Material Point

Using Explicit Cracks

Defining Material Models

Each material point is assigned a material type. NairnMPM and OSParticulas support numerous material models. For plasticity materials, each material type can choose from among a set of hardening laws. Finally, when using explicit cracks, the material points along the cracks can be assigned to various traction laws. The information on these options are in the following sections:

  • Material Models - all material models available for MPM simulations
  • Hardening Laws - all hardening laws available for plasticity materials
  • Traction Laws - all traction laws available for modeling cohesive zones on cracks

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

MPM simulations can do thermal calculations that account for thermal strains in the stress analysis and can model thermal conduction. The commands in this section activate thermal calculations.

Gravitation Field

Custom Tasks