1. Introduction

Sierra/SolidMechanics (Sierra/SM) is a three-dimensional solid mechanics code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. It is built on the SIERRA Framework [[1], [2], [3], [4]]. SIERRA provides a data management framework in a parallel computing environment that allows the addition of capabilities in a modular fashion. Contact capabilities are parallel and scalable.

This document provides information about the functionality in Sierra/SM and the command structure required to access this functionality in a user input file. This document is divided into chapters based primarily on functionality. For example, the command structure related to the use of various element types is grouped in one chapter; descriptions of material models are grouped in another chapter.

Sierra/SM provides both explicit transient dynamics and implicit quasistatics and dynamics capabilities. Both the explicit and implicit modules are highly scalable in a parallel computing environment. In the past, the explicit and implicit capabilities were provided by two separate codes, known as Presto and Adagio, respectively. These capabilities have been consolidated into a single code. The executable is named Adagio, but it provides the full suite of solid mechanics capabilities, for both implicit and explicit. The Presto executable has been disabled as a consequence of this consolidation.

Important references for both the implicit and explicit capabilities are given in the references section at the end of this chapter. Adagio was preceded by the codes JAC and JAS3D; JAC is described in [[5]]; JAS3D is described in [[6]]. Presto was preceded by the code Pronto3D. Pronto3D is described in [[7]] and [[8]]. Some of the fundamental nonlinear technologies used by Sierra/SM are described in [[9], [10], [11]]. Sierra/SM uses the Exodus II database. (Other options may be added in the future.) The Exodus II database format is described in [[12]].

One of the key concepts for the command structure in the input file is a concept called scope. A detailed explanation of scope is provided in Section 1.3. Most of the command lines in Section 2 are related to a cerain scope rather than to some particular functionality.