[evaliu246]

Is there a way to export data for all the nodes for all timesteps in a transient simulation? I'm looking to either export velocity.lamda2, or the vortex core region for all the timesteps of my run.

I can do it for one timestep pretty easily, but don't want to have to do it manually for all my timesteps

[ghorrocks]

There are three main ways to do it:

* You can automate CFD-Post using a session file. Record a session file of exporting one time step, and then edit the session file with a text editor to export all the other time steps.

* You can export files with output settings in CFX-Pre.

* You can convert transient results files into several format using the Solver Manager, in the tools\export menu item.

[evaliu246]

Which of these options can give me the data in a .csv or excel file?

[ghorrocks]

The first one can give you a CSV file. None of them can give you an excel file.

[evaliu246]

I've recorded a session file, could you give more detail on how to edit it? I wasn't able to find a tutorial online

[ghorrocks]

The format of the session file is pretty obvious. Grab the bit which loads the time step and exports it and copy/paste it a few times, and update the time step number and file name each time.

I usually write a python program to generate these scripts because then you can get it to repeat thousands of times (if you have that many steps).

[evaliu246]

There isn't a play option under the Session tab for CFD-Post, and when I open up a new CFD-Post not from my work bench that has the play option I can't open the file because the variables and location don't exist. What should I be doing differently?

[ghorrocks]

Yes, you are going to have to run CFD-Post outside of workbench. What do you mean "the variables and location do not exist"? You are going to have to extract the CFX data out of the workbench data structure. Look in the directory structure workbench has created to find it.

[evaliu246]

I'm able to edit the session file to include looping through the different timesteps, but I'm struggling with how to save each timestep data file as a separate document, or have all the timestep data in one giant csv file. Currently the csv exported file just rewrites with each timestep

[ghorrocks]

In the session file you need to set it to save to a new file name each time step. You already have it loading up a different time step each loop, you need to edit the export line to use a new file name each loop as well.