ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T09:10:42-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/16974Aliasing issue when using OSPRay with transparent background2023-06-15T09:10:42-04:00pggesAliasing issue when using OSPRay with transparent backgroundSaving an ospray rendered image with transparent background results in aliasing effects on edges.
This only manifests in the saved image, viewing the scene through paraview looks fine.
Changing the value of samples per pixel does not in...Saving an ospray rendered image with transparent background results in aliasing effects on edges.
This only manifests in the saved image, viewing the scene through paraview looks fine.
Changing the value of samples per pixel does not influence the edge quality in the png as expected.
I have attatched two images of the same scene. One is saved without transparency, the other is saved with transparency and then composed over a white background.
![without](/uploads/4447874516b617a7027e164ac353c52e/notranstest.png)
![with](/uploads/388bc775564a32100f02c0d39d7fa43c/transtest_flatten.png)
How to reproduce:
* Generate Plane Source
* Move viewpoint so the lines are slightly crooked and aliasing effects appear
* Switch on OSPRay, increase Samples Per Pixel to 10 and watch aliasing dissappear
* Save as png with transparent background setting enabled
* view png composed over white backgroundhttps://gitlab.kitware.com/paraview/paraview/-/issues/16966Add documentation to ParaView guide on widget control2024-03-07T20:47:42-05:00W. Alan ScottAdd documentation to ParaView guide on widget controlPlease add some verbiage to the ParaView guide on controlling widgets. Especially document the X, Y and Z functionality.Please add some verbiage to the ParaView guide on controlling widgets. Especially document the X, Y and Z functionality.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/16947Add hidden line functionality to remote server2018-02-28T17:19:35-05:00W. Alan ScottAdd hidden line functionality to remote serverAdd the ability to render wireframe, with hidden line functionality turned on, for remote server.
At that point, make Hidden Line Removal default to on.Add the ability to render wireframe, with hidden line functionality turned on, for remote server.
At that point, make Hidden Line Removal default to on.https://gitlab.kitware.com/paraview/paraview/-/issues/16937Add Annotation Toolbar2019-06-21T19:33:35-04:00Sujin PhilipAdd Annotation ToolbarThis is a new issue for the first part of #15848.
Please add a new "Annotation" toolbar. Place it to the right of the 2d data analysis toolbar. At present, give it three icons: Sources/ Text, Sources/ Annotate Time, Environment Annotat...This is a new issue for the first part of #15848.
Please add a new "Annotation" toolbar. Place it to the right of the 2d data analysis toolbar. At present, give it three icons: Sources/ Text, Sources/ Annotate Time, Environment Annotation.https://gitlab.kitware.com/paraview/paraview/-/issues/16936Range calculation includes blank points and cells2021-05-03T04:04:11-04:00Steven HahnRange calculation includes blank points and cellsParaView doesn't appear to be respecting cell/point blanking when calculating the data range. As shown below, even though the cell with the infinite value is blanked, it is still included in the range and breaks the colormap.
I tried ...ParaView doesn't appear to be respecting cell/point blanking when calculating the data range. As shown below, even though the cell with the infinite value is blanked, it is still included in the range and breaks the colormap.
I tried moidfying `vtkPVDataInformation.cxx` to use the specialized member function `vtkDataSet::GetScalarRange()`to calculate range. This however, does currently calculate the range twice and fails if there is more than one component.
https://gitlab.kitware.com/quantumsteve/paraview/commit/0afddf73e1b2a1d06503633450108bd8ba9c0cbd
![WithInfinity](/uploads/2b876fa51f04c3460ebd085d51675a57/WithInfinity.png)![WithoutInfinity](/uploads/d3052cf0a55cbe0f8a4fb8372ef9e207/WithoutInfinity.png)
input files
[WithInfinity.vts](/uploads/9ca8207731fab4b4e31022f1331f00b1/WithInfinity.vts)[WithoutInfinity.vts](/uploads/1a10a2864e5cc1aa9ddb6fe114dcecf6/WithoutInfinity.vts)
source code
[StructuredGridData.cxx](/uploads/1c5444766d2ef29a9cbca9b4e2a97008/StructuredGridData.cxx)[CMakeLists.txt](/uploads/4e0508b59139568928c43836888cef64/CMakeLists.txt)https://gitlab.kitware.com/paraview/paraview/-/issues/16934PVTU with polyhedra cells seg-faults2020-05-06T09:12:37-04:00SandeepPVTU with polyhedra cells seg-faultsI'm trying to load a mesh partitioned 4 ways using the PVTU format containing polyhedra cells. I can confirm that all 4 pieces load into Paraview individually, but it seg-faults when I incorporate them into a PVTU file. I tried simpler m...I'm trying to load a mesh partitioned 4 ways using the PVTU format containing polyhedra cells. I can confirm that all 4 pieces load into Paraview individually, but it seg-faults when I incorporate them into a PVTU file. I tried simpler meshes using purely hexahedral cells and that works, so I can conclude that it's specific to the polyhedra format.
I've attached the relevant files.
[PVTU_Poly_Bug.tgz](/uploads/ab4a83d59fe7058843f6153e08052bc3/PVTU_Poly_Bug.tgz)https://gitlab.kitware.com/paraview/paraview/-/issues/16930Wrong Trace result of camera reaction buttons in PV.2021-03-23T12:40:01-04:00Haocheng LIUWrong Trace result of camera reaction buttons in PV.Reproduce step:
1. Open PV -> Tools -> Start Trace
2. Click buttons such as `Set view direction to -X`,` -Y`, `+Z` ...
3. Tools -> Stop Trace.
4. All these actions produce the same result as`rederView1.ResetCamera()` which is not the r...Reproduce step:
1. Open PV -> Tools -> Start Trace
2. Click buttons such as `Set view direction to -X`,` -Y`, `+Z` ...
3. Tools -> Stop Trace.
4. All these actions produce the same result as`rederView1.ResetCamera()` which is not the right call.
cc @utkarsh.ayachit @shawn.waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/169255.1.2 doesn't display full dataset when rendering volume2021-03-23T12:40:36-04:00Tim5.1.2 doesn't display full dataset when rendering volumeWhen I load a raw binary file, about 400x400x2000 unsigned chars, it doesn't display when rendering volume. I try reloading the same file with less data by decreasing the data extent in the 3rd dimension. Then after that successfully ren...When I load a raw binary file, about 400x400x2000 unsigned chars, it doesn't display when rendering volume. I try reloading the same file with less data by decreasing the data extent in the 3rd dimension. Then after that successfully renders, I reload again, slowly increasing the data extent in the third dimension. But even after I'm all the way back at the full dataset, not all the data is being displayed volumetrically.Alvaro SanchezAlvaro Sanchezhttps://gitlab.kitware.com/paraview/paraview/-/issues/16917Color legend shows wrong label when running in pvbatch/pvpython2021-03-23T12:40:59-04:00Shawn WaldonColor legend shows wrong label when running in pvbatch/pvpythonHere is an image generated by the attached python script when running in pvbatch. However, this bug affects the python script no matter how it is run, pvbatch, pvpython or running it from the ParaView GUI's python shell. Why does the c...Here is an image generated by the attached python script when running in pvbatch. However, this bug affects the python script no matter how it is run, pvbatch, pvpython or running it from the ParaView GUI's python shell. Why does the color legend say 'vtkBlockColors Magnitude'? vtkBlockColors is not a vector! And when I follow the steps needed to generate the script manually the legend only says 'vtkBlockColors'.
![testimg-black](/uploads/533f68ac5ce9bf9a6540bd44029cfe2b/testimg-black.png)
Background color may vary based on your settings. Mine was transparent by default so I had to edit the image (paste it on top of a black background) to see the error.
[export-screenshot.py](/uploads/57bcf91640c8415a21a2dc05e0f31c95/export-screenshot.py)
Assumes you are in a build tree with data so that bake.e will be found in the data directory.https://gitlab.kitware.com/paraview/paraview/-/issues/16908Angular Periodic filter fails for volume rendering2024-03-07T20:47:41-05:00W. Alan ScottAngular Periodic filter fails for volume renderingYou can't volume render the output of the Angular Periodic filter. This is important functionality, and needs to be fixed.
Lets create a quarter of a cylinder that we will then rotate.
* Linux, 5.1.2, local server.
* disk_out_ref.exo....You can't volume render the output of the Angular Periodic filter. This is important functionality, and needs to be fixed.
Lets create a quarter of a cylinder that we will then rotate.
* Linux, 5.1.2, local server.
* disk_out_ref.exo. All vars on. Apply.
* Clip. Apply.
* Clip. Y Normal. Apply.
* Angular Periodic filter. 90 degrees. Z Normal. Apply.
>> Now, try to volume render by temp. This is a bug.
Hack!!
* Merge Blocks filter. Apply.
>> Now, try to volume render by temp. This works.
Since I have a workaround, scheduling for 5.3.5.13 (Summer 2024)Sujin PhilipSujin Philiphttps://gitlab.kitware.com/paraview/paraview/-/issues/16902Glyphs: Scale only the arrow length instead of the whole glyph size2021-04-22T15:04:57-04:00W. Alan ScottGlyphs: Scale only the arrow length instead of the whole glyph sizeFrom UserVoice.
The glyph filter has the nice property which allows to scale the glyph. However, for all arrow glyphs, a better way of scaling would be to scale only the length of the arrow by a quantity instead of the whole arrow (shaf...From UserVoice.
The glyph filter has the nice property which allows to scale the glyph. However, for all arrow glyphs, a better way of scaling would be to scale only the length of the arrow by a quantity instead of the whole arrow (shaft and tip thickness). This simply gives a much clearer overview if there are regions with big and small arrows in one domain.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/16901Save State and Data2023-06-15T11:28:31-04:00W. Alan ScottSave State and DataFrom UserVoice. Good idea.
Add the ability to save both the state file and copy the data file(s) into the same directory.From UserVoice. Good idea.
Add the ability to save both the state file and copy the data file(s) into the same directory.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/16893mouse zoom is confusing/ wrong with animation/ follow data2018-02-26T13:15:57-05:00W. Alan Scottmouse zoom is confusing/ wrong with animation/ follow dataThe mouse zoom is confusing/ wrong with the animation view/ add camera track/ follow data. The primary issue is that zooming with the left mouse button and zooming with the wheel act differently. This is extremely confusing to users, a...The mouse zoom is confusing/ wrong with the animation view/ add camera track/ follow data. The primary issue is that zooming with the left mouse button and zooming with the wheel act differently. This is extremely confusing to users, and needs to be fixed. Two options would work - some type of a popup warning telling users they are zooming with the wheel rather than the right button, or make the behavior the same.
Here is how to replicate.
* Linux, master, local server.
* Open can.exo. Apply.
* Rotate the can around. Select a half dozen cells on the lower part of the can.
* Extract selection. Apply.
* Reset.
* (Note that ExtractSelection should still be selected in the Pipeline Browser)
* View/ Animation View/ New track/ Camera/ Follow Data/ +
* Turn visibility on for can.exo in the pipeline browser.
* Not necessary, but definately pretty - change variable to GlobalNodeId.
* Play. Note that we stay zoomed on the extract selection elements. This is as it should be.
* Zoom out with the right mouse button. Play. Note what happens to the view - it resets to have the Extract Selection fill the view. This is as it should be.
* Zoom out with the mouse wheel. Play. Notice what happens to the view - nothing. This is NOT as it should be.https://gitlab.kitware.com/paraview/paraview/-/issues/16887Catalyst Live with SOA data arrays causes segfault2021-03-23T12:42:42-04:00Andrew BauerCatalyst Live with SOA data arrays causes segfaultSteps to reproduce:
Use the CxxSOADataArrayExample example and run it with a Python script that has Live enabled. Connect the GUI to a run and then extract one of the outputs. This should cause the simulation to segfault. This is due to ...Steps to reproduce:
Use the CxxSOADataArrayExample example and run it with a Python script that has Live enabled. Connect the GUI to a run and then extract one of the outputs. This should cause the simulation to segfault. This is due to using vtkDataWriter to pass the information to the GUI since vtkDataWriter doesn't support the SOA array layout.https://gitlab.kitware.com/paraview/paraview/-/issues/16870Cleanup ParaView installations on Linux.2022-07-25T20:54:25-04:00Utkarsh AyachitCleanup ParaView installations on Linux.Refactoring tasks:
* [x] disable shared forwarding by default and use rpaths. All relevant linux systems now support rpath. ParaView executables should have rpath set to `$ORIGIN/../lib`. This will affect how we presently support `--mesa...Refactoring tasks:
* [x] disable shared forwarding by default and use rpaths. All relevant linux systems now support rpath. ParaView executables should have rpath set to `$ORIGIN/../lib`. This will affect how we presently support `--mesa-llvm` etc. Need a workaround for that.
* [x] don't put libraries under `<prefix>/lib/paraview-$version`, instead just use `<prefix>/lib`. This will make it easier with putting together ParaView-based application packages. Those other apps, don't need to separately deal with locating ParaView libraries under the version specific directory.
* [x] all libraries installed under `<prefix>/lib` should be versioned.
* [x] all plugins are installed under `<prefix>/lib/paraview-$version/plugins`. Plugins `so`s are not versioned i.e. don't have ParaView version suffix on them. The plugins configuration file (currently `.plugins`) should be under this directory as well.
* [x] all shared resources e.g. PDFs, config files, icons, appdata etc. should be installed `<prefix>/share/paraview-$version`.
* [x] Python modules including Python-C libraries are installed under `<prefix>/lib/python$pyversion/site-packages`(note the absence of ParaView version number).
* [x] make build and install directories as consistent as possible. It's annoying to have to determine if we are running from the build dir or the install location and then do tasks accordingly. Why can't we have them be the same?
* [ ] add documentation for what goes where so that we can refer developer to it when adding any new install rules.
* [ ] ensure that `make|ninja install` target works when `BUILD_DOCUMENTATION` is `ON`.
Other issues:
* [x] Xdmf install rules are bad (#16871)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/16869Cleanup ParaView installation rules (master bug)2018-01-07T03:59:29-05:00Utkarsh AyachitCleanup ParaView installation rules (master bug)Cleanup ParaView installation rules for.
1. Linux (#16870)
2. Windows (#16872)
3. OsXCleanup ParaView installation rules for.
1. Linux (#16870)
2. Windows (#16872)
3. OsXhttps://gitlab.kitware.com/paraview/paraview/-/issues/16858For SPH filters make sure that `Mass Array` is `None` by default. Currently i...2022-06-09T14:09:53-04:00Utkarsh AyachitFor SPH filters make sure that `Mass Array` is `None` by default. Currently it picks the first one.For SPH filters make sure that `Mass Array` is `None` by default. Currently it picks the first one.For SPH filters make sure that `Mass Array` is `None` by default. Currently it picks the first one.https://gitlab.kitware.com/paraview/paraview/-/issues/16834Paraview vtkClientServerInterpreter can be uninitialized in some circumstance...2021-03-23T12:31:06-04:00Stefano BoriniParaview vtkClientServerInterpreter can be uninitialized in some circumstances (delete + new at the same address)Version affected: verified on 3.14, but the same code is present in 5.1, so I expect a similar behavior.
I experienced occasional crashes in our product's testsuite resulting in the following (or similar) message
```
vtkSIProxy (0...Version affected: verified on 3.14, but the same code is present in 5.1, so I expect a similar behavior.
I experienced occasional crashes in our product's testsuite resulting in the following (or similar) message
```
vtkSIProxy (0x7e23040): Failed to create vtkPolyDataMapper. Aborting for debugging purposes.
/home/travis/build.sh: line 45: 4392 Aborted
```
I was able to track down the problem to an uninitialized vtkClientServerInterpreter, specifically the fact that the generated Init functions (see `ParaView-3.14.1-Source/Utilities/VTKClientServer/Wrapping/vtkWrapClientServer.c` and equivalent in ParaView 5.1) creates as:
```
1043 fprintf(fp,"void %s_Init(vtkClientServerInterpreter* csi);\n",classes[i]);
1044 }
1045 fprintf(fp,
1046 "\n"
1047 "//-------------------------------------------------------------------------auto\n"
1048 "void VTK_EXPORT %s_Init(vtkClientServerInterpreter* csi)\n"
1049 "{\n"
1050 " static vtkClientServerInterpreter* last = NULL;\n"
1051 " if(last != csi)\n"
1052 " {\n"
1053 " last = csi;\n", data->ClassName);
1054 for (i=0; i < totalClasses; ++i)
1055 fprintf(fp," %s_Init(csi);\n",classes[i]);
1056 if(!data->IsAbstract)
1057 fprintf(fp," csi->AddNewInstanceFunction(\"%s\", %sClientServerNewCommand);\n",
1058 data->ClassName,data->ClassName);
1059 fprintf(fp," csi->AddCommandFunction(\"%s\", %sCommand);\n",
1060 data->ClassName,data->ClassName);
1061 fprintf(fp, " }\n}\n");
```
The problematic code is the resulting output code:
```
static vtkClientServerInterpreter* last = NULL;
if(last != csi)
```
This code skips the registration of the new instance function if the passed ClientServerInterpreter pointer is the same as the previously done (whose pointer is stored as a static local variable). This has probably been made to prevent double initialization. Unfortunately, the comparison of pointers does not consider the possibility that the Interpreter has been deleted and reinstantiated again, and it also happens to be at the exact same memory address. The comparison will therefore skip the initialization and the Interpreter will be left uninitialized, resulting in the abort() given above.
Not being well versed in the underlying design, I am unable to say if this is a bug or an intentional choice that is exposed by some incorrect usage upstream, but my testing code is not doing anything complicated: simply calling paraview.simple.Connect and Disconnect many times.
Please let me know if any more relevant information is needed. [A few more details on the investigation are available here](https://github.com/simphony/simphony-paraview/issues/34).https://gitlab.kitware.com/paraview/paraview/-/issues/16827Loading plugins with representations doesn't work correctly in Python2020-12-10T15:48:25-05:00Utkarsh AyachitLoading plugins with representations doesn't work correctly in PythonThe following script doesn't work, when it should.
```python
from paraview.simple import *
LoadDistributedPlugin("SurfaceLIC", ns=globals())
Sphere()
r = Show()
print r.NormalizeVectors
```The following script doesn't work, when it should.
```python
from paraview.simple import *
LoadDistributedPlugin("SurfaceLIC", ns=globals())
Sphere()
r = Show()
print r.NormalizeVectors
```https://gitlab.kitware.com/paraview/paraview/-/issues/16820convert projects to the third party update scripts2020-07-20T08:28:38-04:00Ben Boeckelconvert projects to the third party update scriptsProjects:
* [x] protobuf (submodule)
* [ ] CosmoHaloFinder
* [ ] FreezePython
* [ ] IceT
* [x] lz4
* [x] pugixml
* [x] pygments
* [x] GitSetupProjects:
* [x] protobuf (submodule)
* [ ] CosmoHaloFinder
* [ ] FreezePython
* [ ] IceT
* [x] lz4
* [x] pugixml
* [x] pygments
* [x] GitSetup