# Clipping by scalar incorrect for super-build

**URL:** https://discourse.paraview.org/t/clipping-by-scalar-incorrect-for-super-build/13196
**Category:** ParaView Support
**Created:** [November 6, 2023, 12:06pm UTC](https://discourse.paraview.org/t/clipping-by-scalar-incorrect-for-super-build/13196 "2023-11-06T12:06:53Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Thomas](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://discourse.paraview.org/u/Thomas)
#### Post date: [November 6, 2023, 12:06pm UTC](https://discourse.paraview.org/t/clipping-by-scalar-incorrect-for-super-build/13196/1 "2023-11-06T12:06:53Z")

</div>

Hi,

I have compiled paraview superbuild 5.10 and 5.11 (5.12 failed on download - separate problem) but when reading OpenFoam VTK files and clipping the data by the U\_Z velocity, I get the following image:

 ![Screenshot from 2023-11-06 13-54-59](https://discourse.paraview.org/uploads/default/original/2X/0/0ba5532679a4c259d3937f532a1b89ee8468d906.jpeg)

If I clip the same data with the system paraview (5.10), I get the following correct result:

 ![Screenshot from 2023-11-06 13-56-42](https://discourse.paraview.org/uploads/default/original/2X/8/884e64726f9f30763260b2d58564d1a0dfe4e44a.jpeg)

This suggests there is something wrong with how I have compiled paraview. The reason for compiling paraview is to have some additional python modules as well as rendering. I followed the instructions as per [here](https://gitlab.kitware.com/paraview/paraview-superbuild). The cmake command I am using is as follows:

```auto
cmake -DPARAVIEW_BUILD_EDITION=CANONICAL -DPARAVIEW_USE_PYTHON:BOOL=ON -DENABLE_python3=ON -DPython3_EXECUTABLE:FILEPATH=path/to/env/bin/python3.10 -DENABLE_qt5=ON -DENABLE_ospray=ON -DENABLE_boost=ON -DENABLE_cxx11=ON -DENABLE_eigen=ON -DENABLE_ffmpeg=ON -DENABLE_fortran=ON -DENABLE_lapack=ON -DENABLE_las=ON -DENABLE_libxml2=ON -DENABLE_nlohmannjson=ON -DENABLE_paraview=ON -DENABLE_tiff=ON -DPARAVIEW_USE_PYTHON=ON -DPython3_EXECUTABLE=ON -DUSE_SYSTEM_png=ON -DUSE_SYSTEM_python3=ON -DUSE_SYSTEM_qt5=ON /path/to/paraview/superbuild/folder/paraview-superbuild/

```

I am compiling on Ubuntu 22.04.

I do have the python modules that I required, rendering is available and paraview and pvpython run, but they produce the unexpected results as shown in the images.

Does anyone know what I have done wrong or any suggestions as to how to troubleshoot this further.

Thanks,  
Thomas

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 6, 2023, 12:29pm UTC](https://discourse.paraview.org/t/clipping-by-scalar-incorrect-for-super-build/13196/2 "2023-11-06T12:29:30Z")

</div>

Can you test the binary release as well ?

Please share your data.

---

<div class="post-metadata">

### Author: ![Thomas](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://discourse.paraview.org/u/Thomas)
#### Post date: [November 6, 2023, 8:14pm UTC](https://discourse.paraview.org/t/clipping-by-scalar-incorrect-for-super-build/13196/3 "2023-11-06T20:14:03Z")

</div>

Hi Mathieu,

Thank you for getting back to me so fast.

I have tested the binary release from [here](https://www.paraview.org/download/). I have tested with both 5.10 and 5.11. The 5.10 binary produced the smooth clip and the 5.11 produced the jagged clip as before.

To reproduce what I observe: added a clip to the data → clipped by scalar Uz (value = 0.2, click invert) → apply.

I have uploaded the data [here](https://drive.google.com/drive/folders/1LeGFZnJUTzW4CfOzlh1lBlGeg-lUIaMX?usp=sharing). There are two files:  
internal.tar.gz is the original file I was using.  
I also extracted the Uz scalar and saved the data from within ParaView to “extractedData.vtm” which created the \*.vtm files and the folders with the same name. This was just to try make your life easier by not having to download the whole data set.

Thank you again for your help  
Thomas

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [November 7, 2023, 9:48am UTC](https://discourse.paraview.org/t/clipping-by-scalar-incorrect-for-super-build/13196/4 "2023-11-07T09:48:28Z")

</div>

I reproduce with 5.11.1 but it seems to have been fixed in the meantime, you can test the nightly here: [https://www.paraview.org/download/](https://www.paraview.org/download/)

If you want to build it yourself, set this cmake option in the superbuild:

`-Dparaview_SOURCE_SELECTION=git`

Best,

---

<div class="post-metadata">

### Author: ![Thomas](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://discourse.paraview.org/u/Thomas)
#### Post date: [November 7, 2023, 6:12pm UTC](https://discourse.paraview.org/t/clipping-by-scalar-incorrect-for-super-build/13196/5 "2023-11-07T18:12:07Z")

</div>

Thank you Mathieu.

I will stick to 5.10 for now and wait for a super-build with the newer version.

Since the bug seems to have been resolved already I consider this issue resolved.

Your help has been greatly appreciated.

Regards,  
Thomas

---

<div class="post-metadata">

### Author: ![Thomas](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/t/e36b37/32.png) [@Thomas](https://discourse.paraview.org/u/Thomas)
#### Post date: [November 8, 2023, 4:51am UTC](https://discourse.paraview.org/t/clipping-by-scalar-incorrect-for-super-build/13196/6 "2023-11-08T04:51:15Z")

</div>

Hi,

Just to confirm, I tried the nightly build (5.11.1) using the

```auto
-Dparaview_SOURCE_SELECTION=git

```

flag and it showed that the clipping issue had been resolved.

Regards,  
Thomas