Why is my .disp file empty?

Sebastian_981
Sebastian_981 Altair Community Member
edited March 5 in Community Q&A

Hello everyone,

I'm running a model which includes a frequency response load step. In this load step I've set an output request for accelaration in format "Opti", which should output the accelarations in a .disp file. When running the analysis though the .disp file is empty.

I've tried the same with a demo beam model containing a Frequency and Random Response load step which I got from a colleague.

When running the analysis of the beam model on my colleagues machine the .disp file gets filled with the requested output, when running the exact same file on my machine the .disp file stays empty only containing the following:

OPTISTRUCT RESULT 2025

$ITERATION 0

The output request in the demo file looks like this:

It is setup the same in the actual model I want to run minus the "PUNCH" and "H3D" requests.

My colleague uses HyperMesh and OptiStruct Version 2022 while I use 2025. We've tried running a solver deck generated on my machine with Hm 2025 which produces an empty .disp on my machine on the machine of my colleague. There the .disp file gets filled correctly.

This narrows down the error to my OptiStruct 2025 installation.

Can anylone help? I've attached the Demo Beam Model, the generated solver deck and the analysis outputs to this post.

Best,

Sebastian

Best Answer

  • solon
    solon
    Altair Employee
    Answer ✓

    Hello,

    Thank you for pointing this issue out, it will be fixed in the upcoming release.

    For now you can do two things:

    1)Request ACCELERATION(OPTI) in conjunction with DISPLACEMENT(OPTI)

    2)Or request ACCELERATION(OPTI) in the old format, by adding PARAM,OPTI,OLD in the Bulk data

Answers

  • Adriano_Koga
    Adriano_Koga
    Altair Employee

    i had the same empty file here, using 22.3, 24.1 and 25.0.

    i couldn1t find yet the cause for not writting the .disp correctly.

  • solon
    solon
    Altair Employee
    Answer ✓

    Hello,

    Thank you for pointing this issue out, it will be fixed in the upcoming release.

    For now you can do two things:

    1)Request ACCELERATION(OPTI) in conjunction with DISPLACEMENT(OPTI)

    2)Or request ACCELERATION(OPTI) in the old format, by adding PARAM,OPTI,OLD in the Bulk data

Welcome!

It looks like you're new here. Sign in or register to get started.

Welcome!

It looks like you're new here. Sign in or register to get started.