next up previous contents index
Next: VII. FeResPost as .NET Up: VI. FeResPost Examples with Previous: VI.3 Extraction and manipulation   Contents   Index

Subsections


VI.4 An Excel workbook devoted to post-processing

In directory ``COMEX/EX10'', one gives an excel workbook ``PostProject.xls'' devoted to the automation of stressing of the satellite.

This example shows how FeResPost COM component can be used to build an excel project defining post-processing methods and data. More precisely, the purpose of this example is to define with excel a post-processing similar to the example of Chapter IV.4 FeResPost ruby extension.

The advantage of using Excel and COM component, is that it is now possible to use Excel to define the different data of the detailed calculation, and several formatting functions. Actually the definition of data is no longer dispersed in the ruby programming code. At the same time, The use of functions in excel allows to define many things as the sequencing of calculations, the formatting of results, the calculation and archive of results for load cases or not...

Here again, the example is defined in a workbook that contains both worksheets (section VI.4.2) and VBA modules (section VI.4.3).


VI.4.1 Preparing the application

VI.4.1.1 ``Optimizing'' excel

FeResPost is not programmed as a multi-threaded library, but some versions of excel are (2007 and later versions). Therefore, the multi-threaded calculation should be disabled in excel when FeResPost is used. (See the ``advanced options'' in excel.)

The use of FeResPost with excel ``multi-threaded'' option enabled may result in a multiplication of elapsed computing time by a factor 2 approximately.

VI.4.1.2 Referencing FeResPost in VBA

Before using the excel workbook, the FeResPost COM component must be referenced. This is done as follows:

Once this has been done, you may save the excel workbook so that the references to FeResPost library shall be ``remembered'' the next time you open the workbook.

If a FeResPost COM server is already referenced in the workbook when you open it the first time. (As it probably will be the case with the workbook you download from FeResPost web site.) You must first un-select the old reference to FeResPost server, before selecting the new one. You will have to perform this operation each time you install a new version of FeResPost COM server on your computer.

When you change the version of FeResPost, you will also have to modify the variable ``appName'' in ``DbAndLoadCases'' VBA module of the workbook.

VI.4.1.3 Installing ``SQLite for Excel''

The application outputs an SQLite database that stores Results for different loadcases. (See ``ResultsGMSH'' module in section VI.4.3.5.) This means that the corresponding libraries must be installed on your computer. Note that these libraries are provided with the ``TESTSAT/COMEX/EX11'' example.

The variable ``sqliteLibDirName'' contains the path to the directory containing the ``SQLite3'' shared libraries. This variable must be adapted to match your installation.


VI.4.2 Worksheets

Several types of worksheets are defined in the workbook:


VI.4.2.1 ``LcSelector'' worksheet

This worksheet is used to select the definition of databases and load cases, and to select a sub-set of load cases that shall be post-processed. Two data must be entered ``manually'' (they appear in blue in the worksheet):

The worksheet also defines several automation buttons: More information on the archiving of Results and the creation of GMSH files is provided in the sections devoted to the corresponding VBA modules.


VI.4.2.2 Worksheet for Definition of databases and load cases

One or several worksheets defining databases and load cases can be defined in the workbook. However, only one such worksheet can be selected in ``LcSelector'' worksheet. The content of the worksheet must comply with certain conventions:


VI.4.2.3 Worksheet for Selection of load cases and associated parameters

One or several worksheets define selections of load cases and associated parameters. The first line is a title line. It also defines the names of parameters that are defined for each selected load case. The following lines define the load cases and parameters:

One notes that one load case can be defined in different ``selection'' worksheets with identical or different parameter values. The ``TempLoad'' parameter is used here to associate a load case name to an integer ID corresponding to the name of the temperature field used by Nastran to load the structure. This value is used by some post-processing functions to retrieve the temperature fields stored in an SQLite database. (See the ``recoverTemp.rb'' example in section IV.2.8.5.)

The ``FEMDB'' parameter name is a reserved one. It allows to force the association of one or several load cases to a particular finite element database. This can be handy when one tries to avoid the definition of too many different databases. The associated value is a String corresponding to the identifier attributed to the database in the databases and load cases definition worksheet.


VI.4.2.4 Post-processing worksheets

Those are the worksheets in which the detailed data of post-processing are defined. Four such worksheets are defined so far: ``post_connect'' is devoted to the post-processing of connection loads, ``post_sandwich'' is devoted to the post-processing of stresses in sandwich panels, and ``post_composite'' uses the function ``getCompositeRf'' that calculates reserve factors using the classical laminate analysis. Worksheet ``post_extract'' has been added to illustrate the extraction of Results on lists of elements and/or nodes defined explicitly in ranges of cells.

These worksheets mainly use the functions defined in ``ExtractionCriteria'', "ResultsExtraction", and ``ResultsArchiver'' modules. Basically, they define the data, and perform the call to functions of these modules. One makes several remarks about the use of these worksheets:


VI.4.2.5 ``envelopeGMSH'' worksheet

This worksheet is used to generate ``manually'' the GMSH files containing the envelopes of Results. More precisely, a selection of load cases is read, and the corresponding Results retrieved from ``'' SQLITE database are retrieved and used to generate envelopes of Results that shall be saved in GMSH files.

This is done by clicking the ``Save GMSH envelope'' button. The arguments of the corresponding subroutine are stored in two cells:


VI.4.3 VBA modules

One presents below the different modules that have been defined in the project.


VI.4.3.1 ``DbAndLoadCases'' VBA module

This module is closely related to the definition of databases and load cases. It manages the recovery of information needed to create the databases, and to generate and read the Results corresponding to the different load cases. Several variables corresponding to the lists of databases, elementary and combined load cases are defined in the module. For example:

Also this module provides functions that allow to retrieve Results or load case information. Several such functions deserve more explanation: These methods are mentioned here because they are used in ``ExtractCriteria'' module to program post-processing operations. The user that wishes to modify the post-processing criteria will use these functions.


VI.4.3.2 ``ExtractionCriteria'' VBA module

Among other things, one defines in that module the different functions called in post-processing worksheets to perform specific post-processing operations. As this module defines many functions that can be called from post-processing worksheets, a separate section is specifically devoted to this module. (See section VI.4.4.)


VI.4.3.3 ``ResultsExtraction'' VBA module

The module defines the ``extract'' function that is used to extract values on selections of elements and nodes explicitly defined in the post-processing worksheet. This function is matricial as the different functions defined in ``ExtractionCriteria'' VBA module. The arguments of this function are:

  1. A String corresponding to the type of entities on which the values are extracted. Possible values are ``E'' for elements, ``N'' for nodes or ``EN'' for pairs of elements and nodes.
  2. A selection defining the list of entities on which the values are extracted. The values in the selection must be of integer type. The selection must have two columns if the first parameter is ``EN'', one column otherwise.

    The number of lines or the matrix returned by the function matches the number of lines of this selection.

  3. A String corresponding to the name of the current load case.
  4. A String corresponding to the type of Result that is requested.
  5. A String or Integer corresponding to the layer on which values are extracted.
  6. A String or Integer corresponding to the coordinate system in which the components are given.
  7. A String corresponding to the name of the component that is requested. If this argument is ``NONE'', all the components are returned.
The use of this function is illustrated in ``post_extract'' worksheet. So far the example worksheet only performs extraction operations without using the extracted values in post-processing.

The actual exploitation of extracted Results could be done directly by calculations in the excel worksheet. `ResultsExtraction'' VBA module corresponds to a type of operation that is very often done in aeronautics. For example, when wings or fuselages are stressed, one often works with finite element models characterized by a structured numbering of elements and nodes that allow to easily extract shell forces or stresses for panels, beam forces for elements representing stringers or frames... This allows to estimate loads on rows of connections, assess the risk for a panel to buckle...


VI.4.3.4 ``ResultsArchiver'' VBA module

This module and the associated variables manage the archiving of Results. One of the module variables is a collection of arrays called ``archiveList''. Each element in the collection contains the information necessary to archive one Result for later re-use:

The elements of each array correspond actually to the arguments of function ``saveToArchive'' used in post-processing worksheets. `saveToArchive'' function returns a string that allows a check of the validity of arguments. It is the calculation of these functions that fills the ``archiveList'' collection in the module. This means that a recalculation of the worksheets must be performed before the archiving of Results. (By pressing ``ArchiveResults'' button in ``LcSelector'' worksheet for example). Also, the calculation of worksheets must be redone after pushing ``ReinitArchiveResults'' button in ``LcSelector'' worksheet. Indeed, the ``ReinitArchiveResults'' button clears the ``archiveList'' collection. This ``clearing'' operation may be useful to re-create the ``archiveList'' collection after a modification of the post-processing worksheets.


VI.4.3.5 ``ResultsGmsh'' VBA module

This module is used in the management of Results to be saved in GMSH files. To some extent, this module is similar to ``ResultsArchiver'' VBA module: it manages a outputsList module collection that contains the characteristics of Results to be saved, and the Results themselves.

One difference with ``ResultsArchiver'' VBA module is that the methods of ``ResultsGmsh'' are never called directly from the post-processing worksheets. Instead, methods from other VBA modules in the project call the methods of ``ResultsGmsh''. For example, nearly all the methods of ``ExtractionCriteria'' module use ``ResultsGmsh'' to save envelope of Results in GMSH files. Indirectly, the user defines associated parameters in optional arguments of the post-processing functions defined in ``ExtractionCriteria'' module. (See section VI.4.4.)

The module defines several global variables:


VI.4.3.6 ``Sqlite3'' VBA module

Sqlite3 VBA module contains the VBA code devoted to the management of SQLite databases in Excel. This module is exactly the same as the one used in Small COM example 11. The reader is referred to section VI.1.8 for more information.

In this workbook, ``Sqlite3'' VBA module is used to generate a database containing for each load case the maximum stress or ``failure indices''. These can be read a posteriori to save envelopes generated ``manually'' in GMSH files.

Note that the SQLite3 module is used by ``ResultsGmsh'' VBA module. This module generates all the SQLite3 operations, from the generation to the exploitation.


VI.4.3.7 ``UTIL'' VBA module

This module defines subroutines and functions that can be used from several different locations in the VBA project. For example:

These methods are called from several locations in the VBA module, but should never be used directly from an excel spreadsheet of the project.


VI.4.4 ``ExtractionCriteria'' VBA module

The module defines several functions for extracting and manipulating Results. For example, the extraction of maximum Von Mises stress on a Group of elements, the calculation of honeycomb worst element and associated reserve factor, or the calculation of reserve factors for different connection criteria. One notes that:

The module is the one that the user is most likely to modify to define new post-processing criteria. However, one advises those who wish to create their own criteria to define a new module called for example ``UserCriteria'' to develop their own functions.


VI.4.4.1 Post-processing of stress Results

VI.4.4.1.1 ``getVonMisesMax'' function

Function ``getVonMisesMax'' in ``ExtractionCriteria'' VBA module extracts the maximum Von Mises equivalent stress on a Group of elements and on a selection of layers. The arguments of the function are:

  1. A String corresponding to the name of the load case for which stresses are extracted.
  2. A String corresponding to the location of extraction points on the elements. (For example: ``Elements'', ``ElemCenters'' or ``ElemCorners''.)
  3. A selection of layers. This is a range of cells containing Integer or String values that are converted to a list of layers by ``layersFromRange'' method of ``UTIL'' VBA module.
  4. A String corresponding to the Group of elements on which stresses are extracted.
  5. Two optional String arguments corresponding to the name of the GMSH file in which the envelope of maximum equivalent stress shall be saved, and the name of the Result by which the Result is referred to in GMSH.
The function returns an Array of one line and six columns:
  1. The element ID for maximum equivalent stress,
  2. The node ID for maximum equivalent stress,
  3. The layer ID for maximum equivalent stress,
  4. The sub-layer ID for maximum equivalent stress,
  5. The coordinate system ID which is always ``NONE'',
  6. The maximum Von Mises equivalent stress.
The use of ``getVonMisesMax'' is illustrated in ``post_sandwich'' spreadsheet.

VI.4.4.1.2 ``getShellVonMisesMax'' function

Function ``getShellVonMisesMax'' in ``ExtractionCriteria'' VBA module extracts the maximum Shell Von Mises equivalent stress on a Group of elements and on a selection of layers. The arguments of the function are:

  1. A String corresponding to the name of the load case for which stresses are extracted.
  2. A String corresponding to the location of extraction points on the elements. (For example: ``Elements'', ``ElemCenters'' or ``ElemCorners''.)
  3. A String corresponding to the Group of elements on which stresses are extracted.
  4. Two optional String arguments corresponding to the name of the GMSH file in which the envelope of maximum equivalent stress shall be saved, and the name of the Result by which the Result is referred to in GMSH.
The function returns an Array of one line and six columns:
  1. The element ID for maximum equivalent stress,
  2. The node ID for maximum equivalent stress,
  3. The layer ID for maximum equivalent stress,
  4. The sub-layer ID for maximum equivalent stress,
  5. The coordinate system ID which is always ``NONE'',
  6. The maximum Von Mises equivalent stress.
The difference between ``getShellVonMisesMax'' and ``getVonMisesMax'' is that one does not need to provide a selection of layers argument: the extraction is automatically done on layers ``Z1'' and ``Z2''. The function returns a single value: the maximum Von Mises equivalent stress. The use of ``getShellVonMisesMax'' is illustrated in ``post_sandwich'' spreadsheet.

VI.4.4.1.3 ``getHoneycombCoreAirbusRF'' function

Function ``getHoneycombCoreAirbusRF'' in ``ExtractionCriteria'' VBA module calculates the minimum honeycomb reserve factor on a Group of elements using the so-called ``Airbus'' criterion:

$\displaystyle {\text{RF}}=
\cfrac{1}{{\text{FoS}}\sqrt{\left(\cfrac{\tau_L}{\sigma_L}\right)^2
+\left(\cfrac{\tau_W}{\sigma_W}\right)^2}}\ ,
$

in which $ \tau_L$ and $ \tau_L$ are the honeycomb longitudinal and transverse shear components of Cauchy stress tensor and $ \sigma_L$ and $ \sigma_W$ the corresponding allowables.

The arguments of the function are:

  1. A String corresponding to the name of the load case for which Cauchy stress tensor is extracted.
  2. A String corresponding to the location of extraction points on the elements. (For example: ``Elements'', ``ElemCenters'' or ``ElemCorners''.)
  3. A String corresponding to the Group of elements on which stresses are extracted.
  4. A String corresponding to the layer on which stresses are extracted.
  5. A Real safety factor.
  6. A Real value corresponding to the honeycomb longitudinal shear stress allowable $ \sigma_L$ .
  7. A Real value corresponding to the honeycomb transverse shear stress allowable $ \sigma_W$ .
  8. Two optional String arguments corresponding to the name of the GMSH file in which the envelope of maximum equivalent stress shall be saved, and the name of the Result by which the Result is referred to in GMSH.
The function returns an Array of one line and eight columns:
  1. The element ID for minimum reserve factor,
  2. The node ID for minimum reserve factor,
  3. The layer ID for minimum reserve factor,
  4. The sub-layer ID for minimum reserve factor,
  5. The coordinate system ID for minimum reserve factor,
  6. The value of longitudinal shear stress $ \tau_L$ for minimum reserve factor,
  7. The value of transverse shear stress $ \tau_W$ for minimum reserve factor,
  8. The minimum reserve factor.
The use of ``getHoneycombCoreAirbusRF'' is illustrated in ``post_sandwich'' spreadsheet.

VI.4.4.1.4 ``getHoneycombCoreMaxShearRF'' function

Function ``getHoneycombCoreMaxShearRF'' in ``ExtractionCriteria'' VBA module calculates the minimum honeycomb reserve factor on a Group of elements using a maximum shear criterion:

$\displaystyle {\text{MoS}}=\cfrac{\sigma_W}{{\text{FoS}}*\tau}-1\ ,
$

in which $ \tau$ is the maximum shear stress and $ \sigma_W$ the transverse shear allowable.

The arguments of the function are:

  1. A String corresponding to the name of the load case for which Cauchy stress tensor is extracted.
  2. A String corresponding to the location of extraction points on the elements. (For example: ``Elements'', ``ElemCenters'' or ``ElemCorners''.)
  3. A String corresponding to the Group of elements on which stresses are extracted.
  4. A String corresponding to the layer on which stresses are extracted.
  5. A Real safety factor.
  6. A Real value corresponding to the honeycomb longitudinal shear stress allowable $ \sigma_L$ . (This allowable is not used in the calculation.)
  7. A Real value corresponding to the honeycomb transverse shear stress allowable $ \sigma_W$ . (Only this allowable is used in the calculation.)
  8. Two optional String arguments corresponding to the name of the GMSH file in which the envelope of maximum equivalent stress shall be saved, and the name of the Result by which the Result is referred to in GMSH.
The function returns an Array of one line and eight columns:
  1. The element ID for minimum reserve factor,
  2. The node ID for minimum reserve factor,
  3. The layer ID for minimum reserve factor,
  4. The sub-layer ID for minimum reserve factor,
  5. The coordinate system ID for minimum reserve factor,
  6. The value of longitudinal shear stress $ \tau_L$ for minimum reserve factor,
  7. The value of transverse shear stress $ \tau_W$ for minimum reserve factor,
  8. The minimum reserve factor.
The use of ``getHoneycombCoreMaxShearRF'' is illustrated in ``post_sandwich'' spreadsheet.


VI.4.4.2 Post-processing of connection loads

For the post-processing of connection loads, the first step of the calculations is always to estimate for each connection the axial force, the shear force, the torsional moment and the bending moment. Afterwards the criterion for the connection is calculated (sliding, gapping, insert, rivet...). More precisely, one calculates the critical connection (node or element) and the associated reserve factor.

VI.4.4.2.1 Calculation of the different components of connection loads

One explains here how the components of loading (axial and shear forces, torsional and bending moments) are first calculated for the different connections before the calculation of reserve factors for a selected criterion.

The parameters used for the calculation of these connection load components are always the first 6 parameters of the connection criterion function:

  1. The name of the load case for which the calculation is done.
  2. The name of a first Group (group1) corresponding generally to a part of the structure to which the connections are connected (sandwich panel, shell, metallic fitting...).
  3. The name of second Group (group2) of finite element entities corresponding generally to the modeling of the connections (For example RBE2 elements, CBAR or CBUSH elements...).
  4. A String corresponding to the type of operations done to build the different components of connection loads. This String determines which Results are first read from Result files, and how they are manipulated afterwards. More information about this parameter is given below.
  5. An integer or String value corresponding to the coordinate system in which the force and moment vectors are to be expressed before extracting the different force and moment components.
  6. A vector of three real values corresponding to the axis of the connection in the coordinate system given by the previous argument. The direction of this vector must be defined in such a way that a positive axial force corresponds to a tension in connection. For example, when internal forces are extracted from Grid Point Forces results, this is achieved by defining the vector pointing from grp2 to grp1 (to the direction of the group containing the elements from which Grid Point Forces are extracted.)
Presently, the available extraction methods for the load components, given by the fourth argument above are the following: When the option ``BMFRC'' is adopted, the loads are extracted on the ``beam-type'' elements modeling the connections (CBUSH elements for example). This means that the only the second Group argument (third argument of the function) matters. The first Group argument is not considered. In all other cases, Group operations are done to obtain a list of nodes which is the intersection of the two Group arguments provided. More precisely, the Group ``targetGrp'' is build as follows:
    If extractionMethod = "BMFRC" Then
        Set targetGrp = grp2
    Else
        Set nodeGrp1 = db.getNodesAssociatedToRbes(grp1)
        Set tmpGrp1 = db.getNodesAssociatedToElements(grp1)
        nodeGrp1.importEntitiesByType "Node", tmpGrp1
        
        Set nodeGrp2 = db.getNodesAssociatedToRbes(grp2)
        Set tmpGrp2 = db.getNodesAssociatedToElements(grp2)
        nodeGrp2.importEntitiesByType "Node", tmpGrp2
        
        Set tmpGrp3 = nodeGrp1.opMul(nodeGrp2)
        Set tmpGrp2 = db.getElementsAssociatedToNodes(tmpGrp3)
        Set tmpGrp1 = grp1.opMul(tmpGrp2)
        Set targetGrp = tmpGrp1.opAdd(tmpGrp3)
    End If
Depending on the type of extraction, and on specific aspects of the problem, the correspondence between grp1 and grp2 on one side and the connections or assembled part may differ. For example:

Figure VI.4.1: Example of assembly of different layers with a single connection.
\begin{figure}
\centerline{%
\input{COM_examples/EX_ExcelPost/xfig/assy.pstex_t}}
\end{figure}

All the operations are managed by subroutine ``getConnectionLoads'' of ``ExtractionCriteria'' VBA module. This subroutine is called by each of the connection post-processing function. This is why the six parameters (eight values) of these connection post-processing functions are always the same.

VI.4.4.2.2 ``getSlidingRF'' function

This function calculates reserve factors for the sliding criterion with the following expression:

$\displaystyle {\text{RF}}=\cfrac{C_f*P_{\text{min}}}
{{\text{FoS}}*\left(C_f*\max(F_{\text{axial}},0)+F_{\text{shear}}\right)}\ ,
$

in which $ C_f$ is the friction coefficient between assembled elements and $ P_{\text{min}}$ is an estimate of the minimum possible pretension of the bolt. Parameters specific to this function are: The function returns an Array of one line and four columns containing:

VI.4.4.2.3 ``getGappingRF'' function

This function calculates reserve factors for the gapping criterion with the following expression:

$\displaystyle {\text{RF}}=\cfrac{P_{\text{min}}}
{{\text{FoS}}*\left(\max(F_{\text{axial}},0)
+M_{\text{bending}}/R\right)}\ ,
$

in which $ R$ is a parameter that allows to take into account the prying effect related to the bending moment in the connection and $ P_{\text{min}}$ is an estimate of the minimum possible pretension of the bolt. Parameters specific to this function are: The function returns an Array of one line and four columns containing:

VI.4.4.2.4 ``getInsertRF'' function

This function calculates reserve factors for the insert criterion with the following expression:

$\displaystyle {\text{RF}}=
\cfrac{1}{{\text{FoS}}\sqrt{\left(\cfrac{F_{\text{...
...t{PSS}}\right)^2
+\left(\cfrac{F_{\text{shear}}}{\text{QSS}}\right)^2}}\ ,
$

In which ``PSS'' is the axial allowable of the insert and ``QSS'' is its shear allowable. Parameters specific to this function are: The function returns an Array of one line and four columns containing:

VI.4.4.2.5 ``getShearBearingRF'' function

This function calculates reserve factors for the shear-bearing failure mode with the following expression:

$\displaystyle {\text{RF}}=\cfrac{\text{ShrAll}}{{\text{FoS}}*F_{\text{shear}}}\ ,
$

in which ShrAll is the shear bearing allowable. Parameters specific to this function are: The function returns an Array of one line and three columns containing:

VI.4.4.2.6 ``getPullThroughRF'' function

This function calculates reserve factors for the pull-through failure mode with the following expression:

$\displaystyle {\text{RF}}=\cfrac{\text{PullAll}}{{\text{FoS}}*
{\text{max}}\left(F_{\text{axial}},{\text{PullAll}}*10^{-9}\right)}\ ,
$

in which PullAll is the pull-through tensile allowable. Parameters specific to this function are: The function returns an Array of one line and three columns containing:


VI.4.4.3 composite post-processing

Function ``getCompositeRF'' of ``ExtractionCriteria'' VBA module calculates reserve factors using the classical laminate analysis. More precisely, the Shell Forces and Moments are recovered on shell elements with laminated properties (PCOMP or PCOMPG properties), and the layered reserve factors are calculated using ``calcFiniteElementResponse'' method of the generic Database class. Note however that one limitation of this post-processing function is that no thermo-elastic or hygro-elastic contribution is taken into account in the post-processing. Reserve factors are generally calculated at mid thickness of each layer. One exception is the inter-laminar shear stress reserve factor which is calculated at bottom sub-layer of the selected plies.

Function ``getCompositeRF'' has the following arguments:

  1. The name of the load case for which the calculation is done.
  2. The location(s) in elements of the points at which reserve factors will be calculated. (For example ``ElemCenters'' or ``ElemCorners''.)
  3. The name of a Group on which the reserve factors are calculated.
  4. The name of the failure criterion for which reserve factors are calculated. (The list of available criteria is summarized in Table II.1.2.)
  5. A selection of cells containing the list of layers on which the composite criterion is to be estimated.
  6. The factor of safety.
  7. Two optional String arguments corresponding to the name of the GMSH file in which the envelope of inverse reserve factors shall be saved, and the name of the Result by which the Result is referred to in GMSH.
The function returns an Array of one line and five columns containing:
  1. The element ID for minimum reserve factor.
  2. The node ID for minimum reserve factor.
  3. The layer ID for minimum reserve factor.
  4. The sub-layer ID for minimum reserve factor.
  5. The minimum reserve factor.
The use of ``getCompositeRF'' function is illustrated in ``post_composite'' worksheet.

``getCompositeRF2'' function defined in ``UserCriteria'' Module is a variant of ``getCompositeRF'' with two additional arguments:

Note that one explains in section IV.2.8.5 how the SQLite database containing the temperature Results can be produced.

``getCompositeRF3'' function defined in ``UserCriteria'' Module is a variant of ``getCompositeRF'' that calculates laminate failure criteria directly from the stresses extracted from finite element model results. This function has been used to test the different variants of the functions calculating laminate criteria. The arguments of this function are the same as those of ``getCompositeRF'' function.


next up previous contents index
Next: VII. FeResPost as .NET Up: VI. FeResPost Examples with Previous: VI.3 Extraction and manipulation   Contents   Index
FeResPost 2017-05-28