GeoFEM
Overview and Purpose
GeoFEM is a multi-purpose parallel finite element software, which can be applied to various fields in engineering and sciences.
GeoFEM is composed of analysis modules for structural / thermal fluid / wave propagation simulations and platform for parallel I/O / linear equation iterative solvers / visualization functions. System is designed to be pluggable such that each analysis module is replaceable and that communications among PEs are done implicitly in platform. Platform includes a coupler , supporting communications among analysis modules for multi-disciplinary computations. Utilities i.e. mesh partitioners, PMR ( Parallel Mesh Relocator ) and pre/post viewer are also supplied.
Autors
Research Organization for Information Sciene and Technologie, Japan
Supported Platforms at LRZ
| Platform | Version |
| SGI Altix | 6.0.1 |
How to run
Get access to the software
module load geofem
analyzer
GeoFEM command SYNOPSIS is commonly defined among analyzer, i.e., command syntax of all analyzer programs are the same as follows:
mpiexec -n nprocs -N nodes $GEOFEM_BIN/command [-in IName] [-out OName] [-cont CName]
-in IName: Indicates the "input filenames". The default IName
is"GeoFEM/in"
-out OName: Indicates the "output filenames" The default OName is
"GeoFEM/out". Currently, all the output files are generated in AVS UCD
formats.
-cont CName: Indicates the "control filename" The default CName is
"GeoFEM/control"
visualizer
Command syntax of all visualizer programs are the same as follows:
mpiexec -n nprocs -N nodes $GEOFEM_BIN/command [-in IName] [-cont CName] [-visual VName] [-out OName]
-in IName: Indicates the "input filenames".
-cont CName: Indicates the "control filename".
-visual VName: Indicates the "UCD filenames".
-out OName: Indicates the "output filename".
filenames
All the "filenames" are not ordinary UNIX filename. The filename will be expanded as the following rules.
Rule 1. One "filename" corresponds to multiple file.
For IName "in", UNIX files named in.0, in.1, in.2, ... are corresponding. Digits after '.' (.0, .1, .2) mean to the region number, i.e., PE#0 reads in.0 UNIX file and PE#1 reads in.1 UNIX file,... and so on.
In this rule, with indicating one "input filename", file SETS will be read to program. For "output filename" corresponds to multiple programs in the same manner. For "control filename", this rule is not applicable, because the "control file" is just a single file, i.e, all PEs read the same file.
Rule 2. Pathname extension is not the ordinary UNIX manner.
ALL THE PATHNAMES ARE RELATIVE TO YOUR HOME DIRECTORY. Please
pay attention that the pathnames are NOT relative to the current working
directory. Thus if you indicate "in" for the IName, the file objects
$HOME/in.0, $HOME/in.1, ... will be used. For the default name
"GeoFEM/in", $HOME/GeoFEM/in.0, $HOME/GeoFEM/in.1, ... will be used.
This file expansion manner is defined to concerning to some type of
workstation clusters, which have the file systems separately for each
processor.
Examples
see directory: $GEOFEM_EXAMPLES