Difference between revisions of "Finite Element Analysis"

Revision as of 18:59, 26 March 2010

Finite Element Analysis is a very computational intensive technique for solving a wide range of problems. This page will give you some suggestions for improving FEM performance of ISV codes such as Abaqus, ANSYS, and Nastran, as well as open-source codes such as OpenSees, Tahoe, OOFEM, Calculix, Impact, Elmer, Warp3D, MechSysNG, Kratos, PDD, Adventure, deal.ii GeoFEM, ParaFEM that are focused on solving solid mechanics problems with FEA techniques.

Popular Open Source Packages

• Elmer is an open source multiphysical simulation software developed by CSC. Elmer development was started 1995 in collaboration with Finnish Universities, research institutes and industry. Elmer includes physical models of fluid dynamics, structural mechanics, electromagnetics, heat transfer and acoustics, for example. These are described by partial differential equations which Elmer solves by the Finite Element Method (FEM).
• Impact is an open source finite element program suite which can be used to predict most dynamic events such as car crashes or metal sheet punch operations. They usually involve large deformations and high velocities. Simulations are made on a virtual three dimensional model which can be created with a pre-processor or with the built-in Fembic language. Results are viewed in a post-processor.
• WARP3D is under continuing development as a research code for the solution of very large-scale, 3-D solid models subjected to static and dynamic loads. Specific features in the code oriented toward the investigation of fracture in metals include a robust finite strain formulation, a general J-integral computation facility (with inertia, thermal, face loading), interaction integrals for computation of linear-elastic fracture parameters, very general element extinction and node release facilities to model crack growth, nonlinear material models including viscoplastic and cyclic, cohesive elements and cohesive constitutive models, and the Gurson-Tvergaard dilatant plasticity model for void growth.

Non-FEM Solver tips

The following list of items are not related to the actual FEM solver itself. But since solvers range so widely, these tips are somewhat generic and may or may not help your specific applicaiton.

IO

FEM codes, for the most part, do a great deal of local IO. This is a result of several possibilities including the solver itself (an out-of-core solver) or retaining intermediate results to make post-processing, including stress recovery, much faster.

Based on some testing of commercial FEM codes, here are some tips for improving performance.

• Use RAID-0 for the local scratch space.
• If possible use EXT2 or XFS for the local IO