Difference between revisions of "MPM Input Files"

From OSUPDOCS
Jump to navigation Jump to search
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 NairnMPM|here]]. 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. 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 MPM Input Command FIle|sample XML MPM input command file]] for simulation of two colliding disks.
=== Documentation Notes ===
Scripted input files are comprised of a series of commands an <tt>XML</tt> input files are comprised of a series of <tt>XML</tt> elements. This documentation will explain these commands and elements using the style:
  Command (arg1),(arg2),<(arg3)>,<(arg4)>
  <Command attr1='(arg1)' attr2='(arg2)'>(arg3)</Command>
where
* <tt>Command</tt> is the command name.
* <tt>(arg1),(arg2)</tt>, ''etc.'', specify arguments whose function will be explained along with the command.
* <tt><(arg3)></tt> - enclosing an argument in angle brackets indicates an optional argument. If the argument is omitted, the code will assume some default value.
* <tt>attr1</tt>, <tt>attr2</tt>, ''etc.'', are attributes to the <tt>XML</tt> element.


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

Revision as of 12:01, 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 MPM input command file for simulation of two colliding disks.

Documentation Notes

Scripted input files are comprised of a series of commands an XML input files are comprised of a series of XML elements. This documentation will explain these commands and elements using the style:

 Command (arg1),(arg2),<(arg3)>,<(arg4)>
 <Command attr1='(arg1)' attr2='(arg2)'>(arg3)</Command>

where

  • Command is the command name.
  • (arg1),(arg2), etc., specify arguments whose function will be explained along with the command.
  • <(arg3)> - enclosing an argument in angle brackets indicates an optional argument. If the argument is omitted, the code will assume some default value.
  • attr1, attr2, etc., are attributes to the XML element.

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