Difference between revisions of "Main Page"

From OSUPDOCS
Jump to navigation Jump to search
Line 11: Line 11:
== Visualization ==
== Visualization ==


The various code engines do the calculations. Visualization of results is usually using either [[NairnFEAMPM]] (preferred, but Mac only) or [[NairnFEAMPMViz]] (Java program for Windows or Linux). For 3D analysis, some things can be visualized in [[NairnFEAMPM]]. Alternatively, calculation results can be archived as <tt>vtk</tt> files and then visualized in [[ParaView]] or an other software that can read standard <tt>vtk</tt> files. Finally, for custom visualization options, you can use the [[ExtractMPM]] tool to extract selected data in various formats and input that data and to any visualization tool of your choice.
The various code engines do the calculations. Visualization of results is usually using either [[NairnFEAMPM]] (preferred, but Mac only) or [[NairnFEAMPMViz]] (Java program for Windows or Linux). For 3D analysis, some things can be visualized in [[NairnFEAMPM]]. Alternatively, calculation results can be archived as <tt>vtk</tt> files and then visualized in [[ParaView]] or an other software that can read standard <tt>vtk</tt> files. For custom visualization options, you can use the [[ExtractMPM]] tool to extract selected data in various formats and input that data and to any visualization tool of your choice. If you need even more customization, you can write you own software to read output files; to make that task possible you can see help on [[Archive File Formats|format of the archive files]].


== Configuring Input Commands Files ==
== Configuring Input Commands Files ==

Revision as of 17:22, 9 September 2013

This documentation wiki is for the computational mechanics software from Oregon State University in the research group of John A. Nairn. This software package focuses on material point method (MPM) calculations, but also includes basic finite element analysis (FEA) calculations. The various software components in this project are listed in the navigation bar.

Getting Starting

The calculation engines for material point method (MPM) simulations are called OSParticulas and NairnMPM. The calculation engine for finite element analysis (FEA) is called NairnFEA. These are all object-oriented, C++, platform-independent code engines. The first steps to using these tools are

Visualization

The various code engines do the calculations. Visualization of results is usually using either NairnFEAMPM (preferred, but Mac only) or NairnFEAMPMViz (Java program for Windows or Linux). For 3D analysis, some things can be visualized in NairnFEAMPM. Alternatively, calculation results can be archived as vtk files and then visualized in ParaView or an other software that can read standard vtk files. For custom visualization options, you can use the ExtractMPM tool to extract selected data in various formats and input that data and to any visualization tool of your choice. If you need even more customization, you can write you own software to read output files; to make that task possible you can see help on format of the archive files.

Configuring Input Commands Files

MPM simulations using OSParticulas or NairnMPM or FEA calculations using NairnFEA are controlled by input from an XML input file. This input file can be created manually by using any text or XML editing software. It is usually preferred, however, to use a higher-level scripting language to set up the calculations and then have an interpreter format those commands into the XML files needed by the code engines. This scripting method can be done by using either the NairnFEAMPM application (Mac only) or the NairnFEAMPMViz (Java tool) application. The scripting languages in these two applications are almost identical.

The bulk of the documentation in this wiki is involved with describing the features of the software and explaining the input commands needed to use those features. The features and input commands documentation for MPM or FEA calculations are in the following sections:

Format of Output Files

The various visualization tools automatically read output files created by these code engines. If needed, the format of those files are documented here.