Slice and clip filter

Hello,

I am trying to extract a surface region in my computational domain.
I use the slice filter together with the clip filter to do this.
However I have recently noticed this:

  • When i use the clip filter directly on my .case file with the data, there are no points within that region.

  • However when i used the slice filter - and then the clip filter there are point within the region.
    What is the reason for this?

I wonder why this happens.
Could someone help me with this.

Please share your dataset

Hi,
The results are written in EnSight6 binary format.
The result files are case files.
I am not quite sure how i can share the dataset. There are a lot of files each timestep.

Save a single timestep as a .vtu file and share it here.

Hello,

I’ve saved the data for a single timestep and attached the .vtu file.
Please have a look and let me know.

Paraview_1_0.vtu (6.7 KB)

Your dataset is really flat. Is that really how your model.case looks like ?

In any case, I was able to use slice and clip on your dataset without any issues.

Hi, I think there was a problem while saving the data.
I am not able to upload the dataset here because the file size is too big.
I have uploaded it to the drive, and I have sent a link to you.

Please check your inbox.

I am able to use Clip on both dataset you sent me.

Please provide precise steps to reproduce your issue.

Hello,

These are the following steps:
Approach 1

  1. Slice filter on the model.case file
    Type: Plane
    Origin: 1.168, 0.02196, 0.4578
    Normal: 0.202789776, 0.81456055, 0.54347716
  2. Clip filter on the above slice filter:
    Type: Sphere
    Origin: 1.168, 0.02196, 0.4578
    Radius: 0.0017

Approach 2
3. Clip filter directly on the model.case file
Origin: 1.168, 0.02196, 0.4578
Radius: 0.0017

The resulting number of points selected in Approach 1, is different from Approach 2.#
I hope this helps.

Approach 1 would give you a 2D dataset
Approach 2 would give you a 3D dataset

Why do you expect to have the same result here ?

Yeah i understand that, but won’t the 2D dataset be a subset of the 3D dataset?

Yes, the 2D dataset is that surface of the 3D dataset. But they do not have the same number of points.

Yes. So shouldn’t the 3D dataset have the points contained in the 2D dataset as well ?considering the coordinates of the origin and type of filters I have used, shouldn’t approach 2 have the same or more number of points than approach 1?

shouldn’t the 3D dataset have the points contained in the 2D dataset as well

No, because clip and slice are not the same operation

shouldn’t approach 2 have the same or more number of points than approach 1

Not at all. their exterior surface is the same, but the 3D dataset has points inside, the 2D dataset do not.

Yes that’s my understanding of it as well.

But please look at the pictures I have posted above. Image one is Approach 2, and image 2 is approach one ( sorry they aren’t in order ).
Image one is a 3D dataset ( has no points ).
Image two is a 2D dataset ( has points )

You clip with sphere is failing because your cells in your dataset are completely mixed up and overlapping.

Why does that happen? And how can I fix it?
Is there any other operation (filter) that works the same as image 2?
I need to extract a part of a certain surface.

Because you are creating an incorrect mesh. How did you create it ?

how can I fix it?

By creating a corrected mesh

Just take a look at your dataset with the surface with edges representation, you will see that your cells are all mixed up.

Since the solver is based on the point cloud approach, I don’t create the mesh. The solver fills the points in the computational domain. The surfaces are just for representation.

Is there a workaround for this? Something I can maybe do on Paraview?

Your point cloud is fine, it is your mesh that is incorrect. If the cells are just for representation, then you can’t expect the cells based filter like clip to perform correctly.

How are the cells created ?