next up previous contents index
Next: IV.1 A small satellite Up: IV. FeResPost Examples with Previous: IV. FeResPost Examples with   Contents   Index

Subsections

IV.0 Introduction

This Part of the document is devoted to the presentation of examples illustrating various aspects of FeResPost All the FeResPost example are done with a model and Nastran results corresponding to a very simplified and imaginary satellite represented in Figure IV.1.1. This Part is organized as follows:

All the examples are delivered in ``TESTSAT'' directory. This directory contains four subdirectories:
  1. ``MODEL'' contains the definition testSat finite element model. The splitting of this model into several files and its organization in sub-directories is described in section IV.1.6.
  2. ``RUBY'' contains the small examples described in Chapter IV.2. The sub-directories in ``RUBY'' are:
  3. Finally, a ``EXEC_OP2'' directory has been defined in ``MODEL'' directory. The main bulk data files have been copied in this directory and the calculations with Nastran must be performed in that directory.
  4. Similarly a ``EXEC_XDB'' directory has been defined in ``MODEL'' directory. There, the main bulk data files have been modified to produce ``xdb'' result outputs.
Of course, before running the examples, you must compile ruby or its shared library, and produce the Nastran finite elements results.


IV.0.1 Accessing the ruby extension

Typically, one imports the FeResPost Classes and Modules with the two following statements:

    require "FeResPost"
    include FeResPost
Note however that it works only if the different environment variables have been initialized correctly. Typically, in our Windows examples, this is done through the batch files that are used to launch the example scripts, and the following variables are generally initialized:
    set LIB=
    set INCLUDE=
    set RUBYLIB=D:/SHARED/FERESPOST/SRC/OUTPUTS/RUBY/RUBY_18
    set PATH=C:/NewProgs/MINGW/bin;C:/NewProgs/RUBY/Ruby187/bin
Note that we add the directory containing GNU compiler executables in ``PATH'' environment variable. This is necessary because some of the libraries delivered with GNU compiler are needed to run the ruby extension.

(Of course the different paths you will initialize will have to be adapted to you peculiar installation, and to the version of Ruby you are using.)


next up previous contents index
Next: IV.1 A small satellite Up: IV. FeResPost Examples with Previous: IV. FeResPost Examples with   Contents   Index
FeResPost User Manual Version 4.4.2 (2018/01/01)