🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

[SOLVED] ParaView Post Processing

User: "Junta_20361"
New Altair Community Member
Updated by Junta_20361

hi all,
I'm using Paraview for post-processing AcuSolve result.
The process i used is:

1. use AcuOut to convert AcuSolve result into Ensight format.

2. input Ensight format file into Paraview.

 

Basically, i can see the result in Paraview for both steady state and transient analysis.
However, for simulations which contains mesh movement, i cannot see the moving mesh in paraview. Everytime when i move to the next frame, the mesh disappear.
Does anyone have the solution for my case?

This is the settings in AcuOut i used:

<?xml version="1.0" encoding="UTF-8"?>image.thumb.png.e61fe00d4856c3ac9c04a11cae78a3b3.png

Result loaded in ParaView:
<?xml version="1.0" encoding="UTF-8"?>image.thumb.png.528748de1fff1b6ab1995de110fe2818.png

Mesh dissappread when i move to the next time steps:

<?xml version="1.0" encoding="UTF-8"?>image.thumb.png.c42164cfbdff014ea025fc0ed26a4320.png

 

Thanks in advance!

Find more posts tagged with

Sort by:
1 - 2 of 21
    User: "cfdguru"
    New Altair Community Member
    Updated by cfdguru

    This is actually a ParaView bug.  The Ensight reader doesn't properly handle the displace coordinates option.  There are a couple work arounds available.  The easiest is to write the data out using CGNS format instead of Ensight.  The other option would be to continue using Ensight format, but deactivate the 'Mesh Motion' option in AcuOut (alternatively, you can just comment out the corresponding line in the .case file and not re-run the conversion).  Then, you'll be able to displace the coordinates in ParaView manually by adding the mesh_displacement vector to the coordinates vector at each time step.  This can be done using the Calculator filter by enabling the 'Coordinate Results' option. 

    User: "Junta_20361"
    New Altair Community Member
    OP
    Updated by Junta_20361

    This is actually a ParaView bug.  The Ensight reader doesn't properly handle the displace coordinates option.  There are a couple work arounds available.  The easiest is to write the data out using CGNS format instead of Ensight.  The other option would be to continue using Ensight format, but deactivate the 'Mesh Motion' option in AcuOut (alternatively, you can just comment out the corresponding line in the .case file and not re-run the conversion).  Then, you'll be able to displace the coordinates in ParaView manually by adding the mesh_displacement vector to the coordinates vector at each time step.  This can be done using the Calculator filter by enabling the 'Coordinate Results' option. 

    hi cfdguru,
    your solution worked. i used CGNS format instead of Ensight.

    Thank you very much! :D