ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-07-09T07:59:23-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18505AutoConvert properties selecting an converted array has no effet2021-07-09T07:59:23-04:00Mathieu Westphal (Kitware)AutoConvert properties selecting an converted array has no effetWhen selecting a converted array and no non converted array is available in the domain, this has no effect.
How to reproduce :
* Open ParaView
* Create a Wavelet
* Add a calc, RTData/2, Apply
* Add a PointDataToCellData, Apply
* Co...When selecting a converted array and no non converted array is available in the domain, this has no effect.
How to reproduce :
* Open ParaView
* Create a Wavelet
* Add a calc, RTData/2, Apply
* Add a PointDataToCellData, Apply
* Contour, Apply
* Select RTData instead of Result in the contour
* No changes and the filter is not reexecuted.
Due to a check in pqFieldSelectionAdaptor
May be related to #18504 #18506https://gitlab.kitware.com/paraview/paraview/-/issues/18504AutoConvert Properties cannot select converted array2021-07-09T08:01:41-04:00Mathieu Westphal (Kitware)AutoConvert Properties cannot select converted arrayThey are multiple bugs with the AutoConvert Properties Setting :
1. Point and cell arrays with the same name do not allow selection in a combo box if there is more than on point data array.
How to reproduce :
* Open ParaView
* Creat...They are multiple bugs with the AutoConvert Properties Setting :
1. Point and cell arrays with the same name do not allow selection in a combo box if there is more than on point data array.
How to reproduce :
* Open ParaView
* Create a Wavelet, Apply
* Create a Calc, "RTData", Apply
* Use PointDataToCellData, pass PointArray to ON, Apply
* Edit->Settings->AutoConvert Properties to on
* Create a Contour
* Try to select the Cell Array RTData or Result, not possible
This may be related to #18505 and #18506.https://gitlab.kitware.com/paraview/paraview/-/issues/18497Image Gradient filter loses origin and spacing information2021-03-23T18:54:42-04:00Kenneth MorelandImage Gradient filter loses origin and spacing informationWhen you apply the `Gradient` filter (`vtkImageGradient` under the covers), the resulting image data set does not have its origin and spacing properly set. Instead, they are set to their defaults, which causes the result to potentially b...When you apply the `Gradient` filter (`vtkImageGradient` under the covers), the resulting image data set does not have its origin and spacing properly set. Instead, they are set to their defaults, which causes the result to potentially be translated and scaled.
To replicate, do the following.
1. Open `disk_out_ref.ex2`. Load all variables. Apply.
2. Add `Resample To Image` filter. Apply.
3. Add the `Gradient` filter. Apply.
4. Turn the visibility of the `Resample To Image`filter back on.
You will see that the outline of the `Gradient` filter does not match its input. It is much larger, square, and off center. If you look in the information tab, you will see that, unlike its input, its bounds match its extents because the origin and spacing were not set correctly.
This problem was [reported on discourse](https://discourse.paraview.org/t/numerics-of-gradient-of-unstructured-dataset-filter/638/9).https://gitlab.kitware.com/paraview/paraview/-/issues/18496Image Gradient filter giving warnings when no active scalars2021-03-23T18:54:53-04:00Kenneth MorelandImage Gradient filter giving warnings when no active scalarsWhen you apply the `Gradient` filter (`vtkImageGradient` under the covers), you get _thousands_ of the following warning if your data does not have an active scalar field (and instead selected from a list).
```
ERROR: In C:\bbd\2d618e80...When you apply the `Gradient` filter (`vtkImageGradient` under the covers), you get _thousands_ of the following warning if your data does not have an active scalar field (and instead selected from a list).
```
ERROR: In C:\bbd\2d618e80\build\superbuild\paraview\src\VTK\Common\DataModel\vtkImageData.cxx, line 1324
vtkImageData (000002942B446150): No Scalar Field has been specified - assuming 1 component!
```
To replicate, do the following.
1. Open `disk_out_ref.ex2`. Load all variables. Apply.
2. Add `Resample To Image` filter. Apply.
3. Add the `Gradient` filter. Apply.
The output messages window will pop up with lots and lots of the aforementioned warning.
This problem was [reported on discourse](https://discourse.paraview.org/t/numerics-of-gradient-of-unstructured-dataset-filter/638/9)https://gitlab.kitware.com/paraview/paraview/-/issues/18495Crash with Contingency Statistics filter2020-05-05T01:10:10-04:00Joachim PouderouxCrash with Contingency Statistics filterContingency Statistics filter requires pairs of attributes. But if input has a single attributes, it just crashes instead of printing an error.
How to reproduce:
- Create a Wavelet
- Apply the Contingency Statistics filter (default se...Contingency Statistics filter requires pairs of attributes. But if input has a single attributes, it just crashes instead of printing an error.
How to reproduce:
- Create a Wavelet
- Apply the Contingency Statistics filter (default settings) => * crash *https://gitlab.kitware.com/paraview/paraview/-/issues/18494`help(Sphere)` doesn't have useful information2021-03-23T18:55:08-04:00Utkarsh Ayachit`help(Sphere)` doesn't have useful informationIn Python shell or pvpython, do the following
```python
>>> from paraview.simple import *
>>> help(Sphere)
```
You'll see something like this:
![image](/uploads/f0b6033380ae29081b2e386629fe6359/image.png)
Now try the following:
```pyth...In Python shell or pvpython, do the following
```python
>>> from paraview.simple import *
>>> help(Sphere)
```
You'll see something like this:
![image](/uploads/f0b6033380ae29081b2e386629fe6359/image.png)
Now try the following:
```python
>>> from paraview.simple import *
>>> s = Sphere()
>>> help(s)
```
You'll see this:
![image](/uploads/61ee1ade1d140440f077f4dc42e5ea55/image.png)
It would be good to not require user to instantiate the filter/source to lookup its help.https://gitlab.kitware.com/paraview/paraview/-/issues/18475ParaView 5.6.0-RC1 OSX Favorites and Recent sections of file dialog don't res...2021-03-23T18:55:27-04:00Robert MaynardParaView 5.6.0-RC1 OSX Favorites and Recent sections of file dialog don't respond to mouse clicksWhen using the file browser the left hand side Favorites and Recent directory sections don't respond to mouse clicks.
ParaView was installed through the DragNDrop package to /Applications.
OS: OSX High Sierra ( 10.13.6 ).When using the file browser the left hand side Favorites and Recent directory sections don't respond to mouse clicks.
ParaView was installed through the DragNDrop package to /Applications.
OS: OSX High Sierra ( 10.13.6 ).https://gitlab.kitware.com/paraview/paraview/-/issues/18461Isosurfaces widget doesn't respect real number precision and notation2020-05-05T01:13:59-04:00Utkarsh AyachitIsosurfaces widget doesn't respect real number precision and notationThe follow widget needs to be updated to respect real number precision and notation
![image](/uploads/2258ce2f173f064c16bb856f747f6546/image.png)
relates to paraview/paraview#17966The follow widget needs to be updated to respect real number precision and notation
![image](/uploads/2258ce2f173f064c16bb856f747f6546/image.png)
relates to paraview/paraview#17966https://gitlab.kitware.com/paraview/paraview/-/issues/18451Full support of Nvidia Material Definition Language (.MDL) and Appearance eXc...2018-09-13T16:03:07-04:00Jonathan BorduasFull support of Nvidia Material Definition Language (.MDL) and Appearance eXchange Format (.AXF)Please support Nvidia MDL for all rendering material definitions : https://www.nvidia.com/en-us/design-visualization/technologies/material-definition-language/
Also the AXF format would be useful: https://www.xrite.com/axf
Ideally, it ...Please support Nvidia MDL for all rendering material definitions : https://www.nvidia.com/en-us/design-visualization/technologies/material-definition-language/
Also the AXF format would be useful: https://www.xrite.com/axf
Ideally, it would be compatible with both OptiX and OSPRay.https://gitlab.kitware.com/paraview/paraview/-/issues/18449GUI for OSPRay material edit / create material from template.2018-09-13T16:03:44-04:00Jonathan BorduasGUI for OSPRay material edit / create material from template.In term of user experience, it would be helpful to be able to create new materials from a set of existing materials and edit the different allowed properties within the ParaView GUI. This would enable people to refine their ray-tracing v...In term of user experience, it would be helpful to be able to create new materials from a set of existing materials and edit the different allowed properties within the ParaView GUI. This would enable people to refine their ray-tracing visualization without editing a JSON file. The modification would be applied in real-time.https://gitlab.kitware.com/paraview/paraview/-/issues/18448Examples of rendering scene (statefile) using OSPRay2018-09-13T16:04:08-04:00Jonathan BorduasExamples of rendering scene (statefile) using OSPRayIt would be of great help to have the different statefile to recreate the examples presented here: https://www.ospray.org/documentation.html#materials.
Such examples would guide a user on how to create a beautiful rendering.It would be of great help to have the different statefile to recreate the examples presented here: https://www.ospray.org/documentation.html#materials.
Such examples would guide a user on how to create a beautiful rendering.https://gitlab.kitware.com/paraview/paraview/-/issues/18429Near clipping plane error2021-03-23T18:55:49-04:00Golyakov AlexsandrNear clipping plane errorHi,
I am using ParaView 5.5.2 to visualize a volume.
In parallel projection when the near plane is very close to zero, the accuracy of the overall Z depth starts to fall apart and object is clipped.
Аnyone can help me, please.
![err...Hi,
I am using ParaView 5.5.2 to visualize a volume.
In parallel projection when the near plane is very close to zero, the accuracy of the overall Z depth starts to fall apart and object is clipped.
Аnyone can help me, please.
![error2](/uploads/1108068d0e249015226debe9501ccaf9/error2.mp4)![NearPlaneError](/uploads/e657f7ff1759900a13b5313751e7fe62/NearPlaneError.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18420AutoMPI not working with OpenMPI2021-09-30T11:01:19-04:00Mathieu Westphal (Kitware)AutoMPI not working with OpenMPIOn ArchLinux and Ubuntu 20.04, when building and using ParaView with AutoMPI and OpenMPI is not working and displays the following output :
```
[glow@snowman ~/work/paraview/paraviewThird/paraview_build]$ ./bin/paraview
AutoMPI: SUCCESS...On ArchLinux and Ubuntu 20.04, when building and using ParaView with AutoMPI and OpenMPI is not working and displays the following output :
```
[glow@snowman ~/work/paraview/paraviewThird/paraview_build]$ ./bin/paraview
AutoMPI: SUCCESS: command is:
"/usr/bin/mpiexec" "-np" "2" "/home/glow/work/paraview/paraviewThird/paraview_build/bin/pvserver" "--server-port=38647"
AutoMPI: starting process server
AutoMPI: server never started.
vtkProcessModuleAutoMPIInternals: Server never started.
Generic Warning: In /home/glow/work/paraview/paraviewThird/paraview/ParaViewCore/ServerManager/Core/vtkSMSession.cxx, line 307
Failed to automatically launch 'pvserver' for multi-core support. Defaulting to local session.
```
kwSys seems fails to run the command for some reason.https://gitlab.kitware.com/paraview/paraview/-/issues/18409VTKPythonAlgorithm writers cannot use same extension as any other ParaView wr...2021-03-23T19:06:43-04:00Bane SullivanVTKPythonAlgorithm writers cannot use same extension as any other ParaView writersWhen creating a `VTKPythonAlgorithmBase` subclass writer algorithm, you cannot use an extension that a ParaView (or another `VTKPythonAlgorithmBase`) writer already uses. For example, I cannot use the `txt` extension because the `DataSet...When creating a `VTKPythonAlgorithmBase` subclass writer algorithm, you cannot use an extension that a ParaView (or another `VTKPythonAlgorithmBase`) writer already uses. For example, I cannot use the `txt` extension because the `DataSetCSVWriter` already has that extension.
```python
@smproxy.writer(extensions="txt", file_description="Some custom writer", support_reload=False)
@smproperty.input(name="Input", port_index=0)
@smdomain.datatype(dataTypes=["vtkDataSet"], composite_data_supported=True)
class PVWriterPlugin(VTKPythonAlgorithmBase):
...
```
If I try to use a writer with that extension it defaults to the `DataSetCSVWriter`:
I choose my custom writer plugin via the pop-up dialog after File->Save Data...:
![Screen_Shot_2018-09-03_at_7.15.12_PM](/uploads/46d0ff73f7d7666c00e0c57892ad7edc/Screen_Shot_2018-09-03_at_7.15.12_PM.png)
After clicking Okay, I am prompted with the configuration options for the `DataSetCSVWriter`:
![Screen_Shot_2018-09-03_at_7.15.26_PM](/uploads/3d9e557237ffeb979fe85bc41d303824/Screen_Shot_2018-09-03_at_7.15.26_PM.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18408Automatic Loading of Python plugins in PV_PLUGIN_PATH fails2021-03-23T18:50:15-04:00Bane SullivanAutomatic Loading of Python plugins in PV_PLUGIN_PATH failsWith XML and other plugins, we can automatically load all plugins in a given `PV_PLUGIN_PATH` directory; this fails for the new Python plugins (`.py` files).
Also, after loading several Python plugins through the Plugin Manager manuall...With XML and other plugins, we can automatically load all plugins in a given `PV_PLUGIN_PATH` directory; this fails for the new Python plugins (`.py` files).
Also, after loading several Python plugins through the Plugin Manager manually, the `Auto Load` flag appears to only be saved for the last loaded plugin and thus PV forgets to load plugins on the next launch.https://gitlab.kitware.com/paraview/paraview/-/issues/18405Image test passes for major difference in test and baseline images2022-11-23T11:10:37-05:00Cory Quammencory.quammen@kitware.comImage test passes for major difference in test and baseline imagesWhile investigating some test failures in `pv.TraceExportAndSaveData` caused by some changes I was making, I found that the test image generated from ParaView master has large differences with the baseline image.
Test image:
![image](/...While investigating some test failures in `pv.TraceExportAndSaveData` caused by some changes I was making, I found that the test image generated from ParaView master has large differences with the baseline image.
Test image:
![image](/uploads/4f87095fa64e30c54427dfd0fe9fbea2/image.png)
Baseline image:
![image](/uploads/8b4b9752a5a1f57d1eba06dd242ed761/image.png)
This should result in a test failure, yet the test passes!https://gitlab.kitware.com/paraview/paraview/-/issues/18403Exodus data not read correctly?2021-03-29T08:09:37-04:00Nico SchlömerExodus data not read correctly?Here's a funny issue with an Exodus file ([test.e](/uploads/60f24f326cd43b5bae94f44a41d2f61e/test.e)). It contains two triangles, four nodes, and on the four nodes two data points `a` and `b`. The data can be read with, e.g.,
```python
...Here's a funny issue with an Exodus file ([test.e](/uploads/60f24f326cd43b5bae94f44a41d2f61e/test.e)). It contains two triangles, four nodes, and on the four nodes two data points `a` and `b`. The data can be read with, e.g.,
```python
import netCDF4
nc = netCDF4.Dataset("test.e")
names = nc.variables["name_nod_var"]
names.set_auto_mask(False)
point_data_names = [b"".join(c).decode("UTF-8") for c in names[:]]
print(point_data_names)
value1 = nc.variables["vals_nod_var1"]
value1.set_auto_mask(False)
print(value1[:])
value2 = nc.variables["vals_nod_var2"]
value2.set_auto_mask(False)
print(value2[:])
```
Output:
```
['a', 'b']
[[0.5488135 0.71518937 0.60276338 0.54488318]]
[[0.4236548 0.64589411 0.43758721 0.891773 ]]
```
Looks good. Now, when opening the file with ParaView, the node coordinates and the connectivity are read alright, but the data is off:
![off](/uploads/a551246cdbc02a33aa6e10ad21c0e666/off.png)
Is this a ParaView bug?https://gitlab.kitware.com/paraview/paraview/-/issues/18399Filtering and toggling header check state should only affect the filtered items2018-08-29T19:16:48-04:00Utkarsh AyachitFiltering and toggling header check state should only affect the filtered itemsThis issue is a todo item from paraview/paraview!2700. When a tree widget is filtered to only show a subset, toggling checkstate using the header should only affect the subset visible not all items.
Currently, a work around is to highli...This issue is a todo item from paraview/paraview!2700. When a tree widget is filtered to only show a subset, toggling checkstate using the header should only affect the subset visible not all items.
Currently, a work around is to highlight all items in the view and then toggle their checkstate rather than using the header.https://gitlab.kitware.com/paraview/paraview/-/issues/18381Plot over line, custom range, min can be larger than max2020-05-05T01:26:31-04:00W. Alan ScottPlot over line, custom range, min can be larger than maxPlease check to see if users are doing dump stuff in a plot over line, Axis use custom range. Please check that the minimum is less than (or equal?) to the maximum.Please check to see if users are doing dump stuff in a plot over line, Axis use custom range. Please check that the minimum is less than (or equal?) to the maximum.https://gitlab.kitware.com/paraview/paraview/-/issues/18376Rescale and disable automatic rescaling doesn't work with Rescale to Custom D...2018-08-21T17:42:50-04:00Andrew BauerRescale and disable automatic rescaling doesn't work with Rescale to Custom Data RangeSteps to reproduce:
1. Create a Wavelet
2 Create a Slice with a Z Normal (unclick Show Plane)
3. Hide Wavelet
4. Click on `Rescale to Custom Data Range` and set values to 100 and 200 and then click `Rescale and disable automatic resc...Steps to reproduce:
1. Create a Wavelet
2 Create a Slice with a Z Normal (unclick Show Plane)
3. Hide Wavelet
4. Click on `Rescale to Custom Data Range` and set values to 100 and 200 and then click `Rescale and disable automatic rescaling`
5. Create a Calculator filter and check `Coordinate Results` and put in `coords+20*iHat`
The scalar range is now changed back to 77 to 280.
This may be a similar fix as in https://gitlab.kitware.com/paraview/paraview/merge_requests/2663.