Trajectory problem with Paraview

[chesswright]

I am running cases with air flow and water particles going past a 2D airfoil with 1 cell in the 3rd dimension. The case did not give any errors but when I try to open Trajectory.CASe in paraview I get this error:

vtkEnSightReader.cxx, line 307
vtkEnSightGoldReader (0x20f9cc0): error reading geometry file

ERROR: In
(path)/VTK/Filtering/vtkExecutive.cxx, line 756
vtkCompositeDataPipeline (0x54cc260): Algorithm vtkEnsightGoldReader(0x54cd7b0) returned failure for request: vtkInformation (0x28d26e0)
Debug:off
Modified Time: 148481
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1
FROM_OUTPUT_PORT: 0

Any ideas on what the problem is would be most helpful. Thanks.

[Yvan Fournier]

Hello,

Which versions of Code_Saturne and ParaView ?

Disclaimer: I rewrote the Lagrangian postprocessing output for version 3.1, so I can help you with that, but I won't be of much help for this specific aspect with previous versions of Code_Saturne.

Regards,

Yvan

[chesswright]

Paraview 3.12.0 and Code_Satune 3.0.1. I've been thinking about downloading 3.1 though just to see if it helps

[Yvan Fournier]

Hello,

ParaView 3.12 is pretty old. That does not mean newer versions have less bugs (they may have different bugs), but 4.0.1 is quite a bit nicer than 3.12, so you may at least download the binary from their site and check that.

In any case, moving to 3.1 may be a good idea for users of the Lagrangian module (even thought it is not an officially validated version like 3.0.1, there are not many changes in physical modeling, so the risk of new bugs is low, and the Lagrangian posprocessing is one of the few major improvements we added between March and May of this year).

Regards,

Yvan

[chesswright]

I installed code-Saturne 3.1 and Paraview4 and reran my trajectory case. Could someone give me a quick tutorial on how to view results? I don't see anything when I load the PARTICLES.case file

[Yvan Fournier]

Hello,

To avoid unwanted / excess output of trajectories, a "particles" type mesh must be associated with a "transient connectivity" type writer (particles move, some enter, others exit), while a "trajectories" type mesh must be associated "fixed mesh" writer (new segments, or mesh blocks, are added at each output, not changing the output already done). Other combinations are silently ignored.

So you probably need to add a new particles mesh and set its type to "trajectories", then associate it to the "trajectories" writer.

Regards,

Yvan

[chesswright]

I created a particles mesh and set its type to "trajectories" and then associated it to the "trajectories" writer. I got a file TRAJECTORIES.case when I ran the case, but I still don't see any output in Paraview. I've attached the case1.xml and the listing file. I'd really like to know if I have set up wrong or if I am just not lloking at the results correctly in Paraview

[Yohann Eude]

Hello,

If you want to follow the displacement of the particles in paraview, you need to open Displacement.CASE, for the statistic open Result.case.
There will be a tutorial about Lagragian simulations on the website soon.

Yohann

[chesswright]

I don't have a file DISPLACEMENT.case. I have RESULTS.case, PARTICLES.CASE and TRAJECTORIES.case

[Yohann Eude]

In the ‘Particles and droplets tracking’ folder that appears in the GUI tree menu, click on the sub-folder ‘Output’ sub-folder and ensure that the ‘Output listing at each time step’ is set to 1. This will output particle information at every time step. Next, tick the boxes for ‘Trajectory mode’ and ‘Displacement Mode’ and set the ‘Output frequency’ to 1. You can set any number of particles for post-processing.

With the Displacement Mode activated you will have the file Displacement.case.

Yohann