Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

VISUALIZATION OF RESERVE FACTORS

Hi there,

can Hyperview visualize the RF in some way?... or at least any result related to the failure criterias selected or the stress limits added to the material information?

I'm searching everywhere but I can't find an answer. I'll appreciate your help.

Thanks in advance!

Find more posts tagged with

English

HyperView

Accepted answers

All comments

Altair Forum User

Well, I answer myself again: the .xdb files from Nastran has NO FAILURE INDEXES, so, there is no values to create a MoS or a RF...

These values can only be found in the .op2 files. That's why I wasn't able to get the results in HV.

With the .op2 file you get the Failure Indexes, and then with a transformation you can get the RF, and after this, present them in HV...

Hope this help to somebody else...

Altair Forum User

sometime, hv lost some information, or it just can not show out all the information.

many of the tables can not bee seen in HV.

If you just want to see the stress limit information, add the information by xml file.

select 'advance' when apply Model and Result files. in derived result, click 'add resource'.

write a xml file containing a table with an array, of which the index is material id, the value is the stress limit.(the format can be found in help)

then select 'model', use 'BCMatToElem( )' insert the table you add.

the limit will be able to contour plot .

If funtion BCMatToElem( the table you add )/(insert the stress table you evaluate) used, you get saftey factor plotable.

Altair Forum User

Thanks for the answer Spucke, but I can confirm that the information needed (Failure Indexes as basis to generate RF or MoS) is in OP2 files but not in XDB files.

I'm missing also some information from the Patran Laminate Modeler... several RF are calculated using the Laminate Modeler and this is a very big problem, because they remain attached to the .db file (as Result Cases), instead of being in the results file (op2 or xdb), or even to have the input in the nastran input file (.dat or .bdf)...

People is working too much on .db files, and this is a problem if you want to use a different software... Of course, sometimes there is no other possibility than working on the .db