[MOAB-dev] pull-request Tqdcfr.cpp

Lukasz Kaczmarczyk Lukasz.Kaczmarczyk at glasgow.ac.uk
Thu Sep 26 13:25:07 CDT 2013


Hello,

I've made pull request in bitbucket with small changes in src/io/Tqdcfr.cpp. I don;t know if someone that monitoring.

We have been working on boundary conditions form cubit, definition of almost all of them you can found in,
Line 1568
https://bitbucket.org/likask/mofem-joseph/src/cf172dd94bcfd8b972c0ab43a669b8256e9035aa/mofem_v0.0.1/common.hpp?at=master

Each meshset with cubit NodeSet, SideSet for which boundary conditions are specified (in cubit) has tag bc_data, which could be interpreted as in above file. You could consider if you like to add that to moab.  

For example, dirihlet bc in cubit is represented by structure,
struct __attribute__ ((packed)) _data_{
    char name[12]; // 12 characters for "Displacement"
    char pre1; // Always zero
    char pre2; // pre-processing flags for modification of displacement bcs. They should not affect analysis, i.e. safe to ignore; 1: smallest combine, 2: average, 3: largest combine, 4: overwrite or no combination defined (default)
    char flag1; // Flag for X-Translation (0: N/A, 1: specified)
    char flag2; // Flag for Y-Translation (0: N/A, 1: specified)
    char flag3; // Flag for Z-Translation (0: N/A, 1: specified)
    char flag4; // Flag for X-Rotation (0: N/A, 1: specified)
    char flag5; // Flag for Y-Rotation (0: N/A, 1: specified)
    char flag6; // Flag for Z-Rotation (0: N/A, 1: specified)
    double value1; // Value for X-Translation
    double value2; // Value for Y-Translation
    double value3; // Value for Z-Translation
    double value4; // Value for X-Rotation
    double value5; // Value for Y-Rotation
    double value6; // Value for Z-Rotation
    };
    

The recent changes are about BlockSet attributes, we use them for specifying material and model parameter.

All of that works quite well, we use that for mesh smoothing and solid mechanics.

Kind regards,
Lukasz


More information about the moab-dev mailing list