Data of post-processing

One presents the example of data for honeycomb calculation. Also examples of data for dynamic post-processing with “PostExtract” class are presented.

X.F.5.2.1 Static post-processing

The first operation consists in creating an instance object of class "PostCauchy":

require "post_Cauchy"
post_honeycomb=PostCauchy.new

Then, three instance methods are created. For example, the "calcAll" method definition looks as follows:

def post_honeycomb.calcAll(db,lcName,scName)
list = ["pan_MX_Honey_50", "pan_MY_Honey_50", ...
end

One sees that the method is attached to the instance object created earlier, and not to its class.

The object also defines a "postCalc" method that defines several data and performs a call to writeGmshMinMosResults method:

def post_honeycomb.postCalc(db)
    skeleton=Group.new
    skeleton.setEntitiesByType("Element","Element 1:100000")
    skeleton.matchWithDbEntities(db)
    writeGmshMinMosResults(db,"OUT_STATICS/postSandwichHoney.gmsh",skeleton)
end

Note that object "post_skins" does not define the method "postCalc" and produces no Gmsh file.

In file “DATA/data_Post_TsaiHill.rb”, one defines the corresponding data for the calculation of Tsai-Hill criterion in panel -Z. Before doing a loop on the different load cases, one initializes the “@compDb” member data as follows:

def post_TsaiHill.preCalc(db)
@compDb=db.getClaDb
end

At the end of the calculations, the envelopes of Results and the mesh are printed:

def post_TsaiHill.postCalc(db)
    skeleton=db.getGroupAllFEM()
    writeGmshMinMosResults(db,"OUT_STATIC/postTsaiHill.gmsh",skeleton)

    db.writeGmshMesh("OUT_STATIC/postTsaiHill.msh",0,skeleton)
end

X.F.5.2.2 Dynamic post-processing

A first instance of the “PostExtract” class is created. This instance is devoted to the printing of several nodal accelerations in Z direction. Basically, the method contains several calls to “calcOneGroup” method with the appropriate arguments that define the data:

def post_accel.calcAll(db,lcName,scName)
    resName="Accelerations (RI), translational"
    method="Nodes"
    csId=0
    component="Z"

    calcOneGroup(db,lcName,scName,"Accel_Node_500001", "Node 500001",
                     resName, method, csId, component)
    calcOneGroup(db,lcName,scName,"Accel_Node_20919", "Node 20919",
                     resName, method, csId, component)
    calcOneGroup(db,lcName,scName,"Accel_Node_20920", "Node 20920",
                     resName, method, csId, component)
    calcOneGroup(db,lcName,scName,"Accel_Node_40913", "Node 40913",
                     resName, method, csId, component)
    ...

A second instance of the method is used to output the launcher interface force recovered from the corresponding CBUSH element=

def post_cbush.calcAll(db,lcName,scName)
    resName="Beam Forces (RI)"
    method="Elements"
    csId=0
    component="XZ"

    calcOneGroup(db,lcName,scName,"Force_launcher", "Element 500003",
                     resName, method, csId, component)
end

Remember that the “calcAll” method is called for each load case or sub-case.

The final printing of values in “OUT_DYNAM” directory is called from “postCalc” method:

def post_accel.postCalc(db)
gnuplot("post_accel.dat")
end

When the post-processing is finished, and if you have gnuplot on your computer, you can visualize the values by entering the “OUT_DYNAM” directory and typing:

gnuplot < post_accel.dat
gnuplot < post_cbush.dat

For example, the results obtained for the post-processing of CBUSH element forces are represented in Figure X.F.1 and X.F.2.

The data for the composite dynamic post-processing are defined in file
“DATA/data_Post_TsaiHillDynam.rb”. This file is very similar to the corresponding file for static post-processing. Only one selects 12 sub-divisions for the rotation angles.

X.F.5.2 Data of post-processing

X.F.5.2.1 Static post-processing

X.F.5.2.2 Dynamic post-processing