[kornickel]

Hello everyone,

I am struggling with Paraview at the moment. I have a turbomachinery case with two cyclic patches. Now I am trying to add stream traces to my geometry but everytime they hit the cyclic wall they just stop (as Paraview usually does, I know, that's not a bug). Is there any way to tell Paraview to continue the streamlines on the neighbour-patch?


Kind regards,

Frank Ubber


edit: I've just seen there's a special section for Paraview in the Post-Processing section, can anybody move this thread, please (or tell me how to move it on my own )

[Ruli]

Hi kornickel,

I would like to know about streamlines and cyclic patches as well.

Does anybody have a clue?

Best regards
Julian

[wyldckat]

Greetings to all!

Well, a few quick tests of my own on the tutorial case "DNS/dnsFoam/boxTurb16", which has got 6 patches in a cube which are all cyclic in pairs, I can come up with the following possible solutions:

1. The lazy way - use the filter "Stream Tracer With Custom Source":
   1. Open the file ".OpenFOAM" a second time on the same ParaView, but on this second one choose to only load all of the patches that have the cyclic characteristics you want.
   2. Select the first file and apply the filter "Stream Tracer With Custom Source" to it. It will ask to choose an "Input" and a "Source". The input is the first file and the source is the second file.
   3. And that's it! It will use the vertexes of the faces on the patches as sources for the streamlines.
2. The very hard and annoying way - still use the filter "Stream Tracer With Custom Source", but use a point replicating strategy:
   1. Apply the standard Streamlines filter near the first patch, if you want greater control on the number of points. Or use "Stream Tracer With Custom Source" using a single patch as source, not all.
   2. Then apply the filter "Slice" to the result of the streamline. The slice place should be as close as possible to the other patch, so that you catch the points very near to the patch surface.
   3. Then apply the "Transform" filter to the slice and specify iit to translate the points on the slice to be X metres to the left or right, depending on where the corresponding patch on the other end is.
   4. Then choose the initial file entry on the "Pipeline Browser" an apply the filter "Stream Tracer With Custom Source". The input is the first file and the source is the transformation entry.
   5. Repeat the process as many times as you deem necessary.
3. The "clone-a-lot" strategy - shown in attachment:
   1. Apply the "Transform" filter to the original file entry and configure it to be X metres to the side of the cyclic patch.
   2. Repeat as many times as you want to see the evolution of the streamline. In the attached case, I only used once.
   3. Select all transformation entries and the first entry and apply the filter "Group Datasets".
   4. You can now use the resulting entry as the input for your streamlines.
   Note: Since you can group datasets, you can exponentially increase the number of clones, since you can apply the "Transform" filter to each group as well!
4. Mix the grouping strategy from #3 with the strategy on #2, i.e., group the slices into a single group that is transformed to the left or right... er, be careful to not try and create a recursive loop, because it will crash ParaView

Best regards,
Bruno

[yhy20081016]

Originally Posted by wyldckat

Greetings to all!

Well, a few quick tests of my own on the tutorial case "DNS/dnsFoam/boxTurb16", which has got 6 patches in a cube which are all cyclic in pairs, I can come up with the following possible solutions:

1. The lazy way - use the filter "Stream Tracer With Custom Source":
   1. Open the file ".OpenFOAM" a second time on the same ParaView, but on this second one choose to only load all of the patches that have the cyclic characteristics you want.
   2. Select the first file and apply the filter "Stream Tracer With Custom Source" to it. It will ask to choose an "Input" and a "Source". The input is the first file and the source is the second file.
   3. And that's it! It will use the vertexes of the faces on the patches as sources for the streamlines.
2. The very hard and annoying way - still use the filter "Stream Tracer With Custom Source", but use a point replicating strategy:
   1. Apply the standard Streamlines filter near the first patch, if you want greater control on the number of points. Or use "Stream Tracer With Custom Source" using a single patch as source, not all.
   2. Then apply the filter "Slice" to the result of the streamline. The slice place should be as close as possible to the other patch, so that you catch the points very near to the patch surface.
   3. Then apply the "Transform" filter to the slice and specify iit to translate the points on the slice to be X metres to the left or right, depending on where the corresponding patch on the other end is.
   4. Then choose the initial file entry on the "Pipeline Browser" an apply the filter "Stream Tracer With Custom Source". The input is the first file and the source is the transformation entry.
   5. Repeat the process as many times as you deem necessary.
3. The "clone-a-lot" strategy - shown in attachment:
   1. Apply the "Transform" filter to the original file entry and configure it to be X metres to the side of the cyclic patch.
   2. Repeat as many times as you want to see the evolution of the streamline. In the attached case, I only used once.
   3. Select all transformation entries and the first entry and apply the filter "Group Datasets".
   4. You can now use the resulting entry as the input for your streamlines.
   Note: Since you can group datasets, you can exponentially increase the number of clones, since you can apply the "Transform" filter to each group as well!
4. Mix the grouping strategy from #3 with the strategy on #2, i.e., group the slices into a single group that is transformed to the left or right... er, be careful to not try and create a recursive loop, because it will crash ParaView

Best regards,
Bruno

The "Transform" filter does work for translational-periodic cases, but it does not work for rotational-periodic cases. For rotational-periodic cases, after the "Transform" filter is applied, although the geometry rotates, the velocity vectors don't rotate.