request a XDB or OP2 result file for post processing

request a XDB or OP2 result file for post processing

fabian.scholz
Contributor Contributor
14,075 Views
5 Replies
Message 1 of 6

request a XDB or OP2 result file for post processing

fabian.scholz
Contributor
Contributor

It is not possible to import the  standard *.out files from Nastran into Hyperview for post processing.

 

So I want to write a OP2, or XDB file via an entry in the bulk section

 

I have tried both

 

PARAM,POST,0  $$    for XDB

or

PARAM,POST,-1  $$    for OP2

 

It leads always to the same files in the calculation folder:

 

*.FNO

*.LOG

*.OUT

*.RSF

*.INI

 

Why doesn't nastran write a *.xdp or a *.op2? Is there something missing in the bulk section?

 

Thank you a lot for your help

0 Likes
Accepted solutions (3)
14,076 Views
5 Replies
Replies (5)
Message 2 of 6

nicklaus.trebilcock
Autodesk
Autodesk
Accepted solution

Hello Fabian,

 

The Output Control Directive you are looking for is -- RSLTFILETYPE

 

For .op2 output you would need to set this to:

RSLTFILETYPE = NASTRANBINARY

 

Note that the .xdb format is not supported in Autodesk Nastran.  Additionally, depending on the post processing software you are targeting, the PARAM, POST option should be set accordingly.

 

-Nick

0 Likes
Message 3 of 6

fabian.scholz
Contributor
Contributor

thank you!

 

But there is one Problem with that.

When import this input deck into the Nastran editor, the editor always keeps its default settings and overwrites my script. Is there a setting or something I can do that this connection between editor and deck is bidirectional? Or some option that the editor doesn’t overwrite my inputdeck before the solution?

 

0 Likes
Message 4 of 6

nicklaus.trebilcock
Autodesk
Autodesk
Accepted solution

You have a couple of options, depending on how you want this setting to persist.

 

1) Set RSLTFILETYPE = NASTRANBINARY nastran.ini file and this will become the default for all models - even in the Editor.

        - Note: The Editor will create a local {modelname}.ini file with the original setting when you run it the first time on a model.  So if you have ran with the old setting for RSLTFILETYPE you may have to delete this {modelname}.ini.  By {modelname} this is the name of your .nas file.  So, if you have a file tank.nas, the Editor will create a tank.ini.  In that case you would delete the original tank.ini with the old RSLTFILETYE setting.

 

2) Depending on how you run the solution you can add this directive to your script (?) or on the command line. 

        - Example call to use Nastran --> Nastran.exe Nastran.ini RSLTFILETYPE = NASTRANBINARY tank.nas

 

3) Final option if this is file specific is to add this line into your nastran file:
SOL STATIC
TITLE = INSTALLATION TEST CASE
SUBTITLE = 2-D CANTILEVER BEAM -QUADR ELEMENTS -2X5 MESH
RSLTFILETYPE = NASTRANBINARY

$
$ OUTPUT CONTROL.
$
DISPLACEMENT = ALL
..........

..........

 

There is more detail on how this is handled here - https://knowledge.autodesk.com/support/nastran/troubleshooting/caas/CloudHelp/cloudhelp/2017/ENU/NST...

 

0 Likes
Message 5 of 6

Andrew.Sartorelli
Alumni
Alumni
Hallo Fabian,

It looks like you indicated you didn't receive an answer to your question. Is there anything further on this topic that you needed assistance with beyond what Nick has already provided?

Regards,
Andrew


Andrew Sartorelli - Autodesk GmbH
0 Likes
Message 6 of 6

Andrew.Sartorelli
Alumni
Alumni
Accepted solution
Hallo Fabian,

I just wanted to follow up again and see if there was anything further on this topic that you required assistance with.

Regards,
Andrew


Andrew Sartorelli - Autodesk GmbH
0 Likes