ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-08-24T21:09:49-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20862Open ParaView File Fatal error if paraview launched with –multi-servers option2021-08-24T21:09:49-04:00Nabil G.Open ParaView File Fatal error if paraview launched with –multi-servers optionDear experts,
running paraview with **–multi-servers** option generates a fatal error if user opens a file, after disconnecting from a server.
The issue can be reproduced as follows:
- in a terminal, start pvserver
- in a second termin...Dear experts,
running paraview with **–multi-servers** option generates a fatal error if user opens a file, after disconnecting from a server.
The issue can be reproduced as follows:
- in a terminal, start pvserver
- in a second terminal, type: **paraview --multi-servers**
- in the main menu bar, click on connect and connect to server
- in the pipeline, select the server and click on disconnect
- in the main menu bar, select File - Open
**==> Paraview crash.**
Digging this out, it seems that in method **pqLoadDataReaction::loadData()**,
**pqServer* server = pqActiveObjects::instance().activeServer();**
returns **NULL** which leads to the crash.
Replacing :
pqServer* server = pqActiveObjects::instance().activeServer()
with :
pqServer* server = pqApplicationCore::instance()->getActiveServer()
seems to fix the issue which can be reproduced with Paraview 5.9
Thanks.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20860Ghost cell generator crashes with SIGSEGV in Wavelet -> Threshold -> Aggregat...2021-10-04T17:34:24-04:00Ethan StamGhost cell generator crashes with SIGSEGV in Wavelet -> Threshold -> Aggregate Data -> Generate Ghost Cells pipeline@yohann.bearzi @cory.quammen @utkarsh.ayachit @patchett2002
Local linux client from [here](https://open.cdash.org/upload/c40a054ee43b11b15a90698c6bf9b0385f057222/ParaView-5.9.1-1451-g686e45e-MPI-Linux-Python3.9-x86_64.tar.gz)
Server i...@yohann.bearzi @cory.quammen @utkarsh.ayachit @patchett2002
Local linux client from [here](https://open.cdash.org/upload/c40a054ee43b11b15a90698c6bf9b0385f057222/ParaView-5.9.1-1451-g686e45e-MPI-Linux-Python3.9-x86_64.tar.gz)
Server is intel, openmpi, osmesa build with spack of ParaView @ 686e45ea1c890c370960498dcbc7c44b54b4dc56
The server crashed on Apply of the ghost cell generator after this pipeline with `Loguru caught a signal: SIGSEGV`
To reproduce:
1. Default wavelet source (36 MPI ranks)
2. Threshold filter (capture everything)
3. Aggregate Dataset filter (Down to 8 MPI ranks)
4. Default Generate Ghost Cells filter -> Apply
Stack trace:
```console
Stack trace:
26 0x403589 /yellow/usr/projects/paraview/pilotlight/tmp_snow_master_intel_19.0.4.243/spack/opt/spack/linux-rhel7-broadwell/intel-19.0.4.243/paraview-master-2ryfgurki4x53k4cdbmnehmtt7repmgi/bin/pvserver() [0x403589]
25 0x2b1ace8c8555 __libc_start_main + 245
24 0x403828 /yellow/usr/projects/paraview/pilotlight/tmp_snow_master_intel_19.0.4.243/spack/opt/spack/linux-rhel7-broadwell/intel-19.0.4.243/paraview-master-2ryfgurki4x53k4cdbmnehmtt7repmgi/bin/pvserver() [0x403828]
23 0x2b1ac5f86711 vtkMultiProcessController::ProcessRMIs(int, int) + 657
22 0x2b1ac5f86fb4 vtkMultiProcessController::BroadcastProcessRMIs(int, int) + 164
21 0x2b1ac5f86d33 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 963
20 0x2b1ac4eb8f9a vtkPVSessionCore::ExecuteStreamSatelliteCallback() + 170
19 0x2b1ac4eb8417 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 167
18 0x2b1ac4391309 vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 41
17 0x2b1ac438dc72 vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1922
16 0x2b1ac438fd5d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 301
15 0x2b1ac4391697 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 855
14 0x2b1ac21997fc vtkSISourceProxyCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 1772
13 0x2b1ac4efcdc6 vtkSISourceProxy::UpdatePipeline(int, double, bool) + 326
12 0x2b1aca472bd5 vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 261
11 0x2b1aca408acf vtkDemandDrivenPipeline::UpdateData(int) + 143
10 0x2b1aca4726d1 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1809
9 0x2b1aca4078fc vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 252
8 0x2b1aca402c3a vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 314
7 0x2b1aca4726d1 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1809
6 0x2b1aca4079aa vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 426
5 0x2b1aca403240 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 64
4 0x2b1aca408e59 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 57
3 0x2b1aca40cc7d vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 61
2 0x2b1ac5d09494 vtkGhostCellsGenerator::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 3156
1 0x2b1ac5d12434 int vtkDIYGhostUtilities::GenerateGhostCells<vtkUnstructuredGrid>(std::vector<vtkUnstructuredGrid*>&, std::vector<vtkUnstructuredGrid*>&, int, vtkMultiProcessController*) + 2100
0 0x2b1ac5d82c6c vtkDIYGhostUtilities::SetupBlockSelfInformation(vtkdiy2::Master&, std::vector<vtkUnstructuredGrid*>&) + 1084
```5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20856Catalyst2/CxxImageDataExample has incorrect parallel output2021-08-11T07:42:28-04:00Andrew BauerCatalyst2/CxxImageDataExample has incorrect parallel outputWhen running the Catalyst2/CxxImageDataExample with `mpirun -np 4 bin/CxxImageDataExampleV2 --output datasets/dataset-%04ts.vtpd` and the fix at https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8221 either the extent or the origin for...When running the Catalyst2/CxxImageDataExample with `mpirun -np 4 bin/CxxImageDataExampleV2 --output datasets/dataset-%04ts.vtpd` and the fix at https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8221 either the extent or the origin for the datasets is wrong. On input to Catalyst/Conduit the extents are:
- proc 0: [0, 18, 0, 60, 0, 44]
- proc 1: [17, 36, 0, 60, 0, 44]
- proc 2: [35, 53, 0, 60, 0, 44]
- proc 3: [52, 70, 0, 60, 0, 44]
The origin is [0, 0, 0] on each process. Based on the output each process has the minimum extent of [0, 0, 0] and still has the origin at [0, 0, 0] so the datasets for each process are overlapping as seen in the attached file: [dataset.tgz](/uploads/782963702772818f728fcbf9af78310f/dataset.tgz)5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20855conduit_cpp::cpp_node creates a copy instead of a wrapper2021-08-10T16:46:51-04:00Francois Mazenconduit_cpp::cpp_node creates a copy instead of a wrapperWhen modify the `conduit_cpp::Node` created via `conduit_cpp::cpp_node(conduit_node* n)`, then the original `conduit_node` is not modified. It seems that we are modifying a copy of the underlying `conduit_node` instead of pointing to the...When modify the `conduit_cpp::Node` created via `conduit_cpp::cpp_node(conduit_node* n)`, then the original `conduit_node` is not modified. It seems that we are modifying a copy of the underlying `conduit_node` instead of pointing to the same data.
To reproduce:
```cpp
conduit_cpp::Node first_node;
conduit_node* first_node_c_node = conduit_cpp::c_node(&first_node);
conduit_cpp::Node second_node = conduit_cpp::cpp_node(first_node_c_node);
second_node["test"] = 2;
std::cout << "first_node:" << std::endl;
first_node.print();
std::cout << "second_node:" << std::endl;
second_node.print();
```
produces this output:
```
first_node:
null
second_node:
{
"test": 2
}
```
we expect the same values for first_node and second_node.
The same unwanted behavior could be reproduced using the C API:
```c
conduit_node* n = conduit_node_create();
conduit_node* n2 = conduit_node_create();
conduit_node_set_external_node(n2, n);
conduit_node* child_node = conduit_node_fetch(n2, "test");
conduit_node_set_int(child_node, 2);
std::cout << "n:" << std::endl;
conduit_node_print(n);
std::cout << "n2:" << std::endl;
conduit_node_print(n2);
```
Same output:
```
n:
null
n2:
{
"test": 2
}
```
(In case of this is intended behavior, what method can create a real C++ wrapper of a `conduit_node*`?)5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20850Texture files not found when loading state file from new location2021-11-15T18:19:37-05:00Ken MartinTexture files not found when loading state file from new locationWhen loading a statefile and using the "search for data files under this directory" option texture files are not located requiring the state file to be manually edited or to re-find the textures when loading the state file.When loading a statefile and using the "search for data files under this directory" option texture files are not located requiring the state file to be manually edited or to re-find the textures when loading the state file.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20848Dataset shows bad load of assemblies2021-08-05T21:16:04-04:00W. Alan ScottDataset shows bad load of assembliesI have a dataset that shows bad loads of assemblies. This is with the IOSS reader. Mesh looks OK in Cubit, and user believes it is OK in EnSight and VisIt. Here is how to replicate:
* ParaView master, builtin server, Linux.
* Load Cy...I have a dataset that shows bad loads of assemblies. This is with the IOSS reader. Mesh looks OK in Cubit, and user believes it is OK in EnSight and VisIt. Here is how to replicate:
* ParaView master, builtin server, Linux.
* Load Cylinder_NS.e. (Utkarsh has this dataset.) Apply.
* I'm probably misunderstanding what is going on. Anyway, turn off all blocks. Now, turn them on and then off one by one. With the blocks off, turn the Assemblies on and off one by one.
* I don't know if this is the intent, but the assemblies are assemblies of sidesets, not blocks.
* Now, what I believe is the original "bug" is replicated as follows. Turn all blocks on. Turn assembly Outer_134 on. Notice that the outside surface has Z fighting. This is due to the blocks, and the assembly (which is a sideset) are at the same Z value.
Note, I am having my user verify that this is still a bug, and/or acts differently on EnSight/Visit than ParaView.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20847zoom to box failing with linked views2021-09-21T18:07:31-04:00W. Alan Scottzoom to box failing with linked viewsZoom to box is failing with linked views. Here is how to replicate:
* 5.9.1, Linux, builtin server. (There is currently another bug causing Zoom to box to fail in master. #20831 Thus, use both master and 5.9.1 to show/test this.)
* S...Zoom to box is failing with linked views. Here is how to replicate:
* 5.9.1, Linux, builtin server. (There is currently another bug causing Zoom to box to fail in master. #20831 Thus, use both master and 5.9.1 to show/test this.)
* Sources/ Fast Uniform Grid. Apply.
* Split Horizontal.
* Turn visibility on for Fast Uniform Grid for this view. Now, both are visible.
* Link views.
* In the left view, zoom to box on the upper left corner.
Master: The left view will resize, the right one won't. This is a bug.
For 5.9.1: The left view and right view won't resize to show the same view. This is a bug.5.10 (Fall 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20846Using servermanager.Fetch after some threshold settings has no data2021-08-18T13:12:24-04:00Christopher M. BiwerUsing servermanager.Fetch after some threshold settings has no dataIt seems when trying to access the data:
```
src = GetActiveSource()
data = servermanager.Fetch(src)
data.GetPointData().GetNumberOfArrays()
```
That for some threshold filter settings there is no accessible data from servermanager.
For...It seems when trying to access the data:
```
src = GetActiveSource()
data = servermanager.Fetch(src)
data.GetPointData().GetNumberOfArrays()
```
That for some threshold filter settings there is no accessible data from servermanager.
For example, here's the wavelet source and I show in the Python shell window trying to access the data. This works as expected, I see that there is 1 array:
![wavelet_threshold_0](/uploads/0aab4d29d015dfd3badbb0148fe94859/wavelet_threshold_0.png)
However, if I change the range and repeat, there is no data. It seems to only be for some data ranges on other data sets I am looking at. Though clearly it is rendering some data in the Render view:
![wavelet_threshold_1](/uploads/ebac1a3958d63f87188afbbc8b34e39c/wavelet_threshold_1.png)
Perhaps I am not accessing the VTK array data in the preferred manner? It seems to work as expected in 5.8.1.
@patchett2002 @ethan.stam @dhr5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20844Box widget for Point Volume Interpolator makes no sense2021-08-10T16:36:29-04:00Kenneth MorelandBox widget for Point Volume Interpolator makes no senseThe `Point Volume Interpolator` filter allows you to select the volume in which you want to interpolate values. However, the 3D widget showing the box does not correspond with the volume actually interpolated. To replicate, do the follow...The `Point Volume Interpolator` filter allows you to select the volume in which you want to interpolate values. However, the 3D widget showing the box does not correspond with the volume actually interpolated. To replicate, do the following:
1. Load this file: [points.vtk](/uploads/d85bcc6fa722fc20a4aec9ca4e447e29/points.vtk). Apply.
2. Add the `Point Volume Interpolator`. Note that the 3D widget doesn't seem right.
3. Apply. Note that the volume interpolated is not the same as the 3D widget.
![Screen_Shot_2021-07-19_at_6.32.53_AM](/uploads/1cc2ee19b08453d5a66ef7caabc34063/Screen_Shot_2021-07-19_at_6.32.53_AM.png)5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20842pvtr files appear to not load rectilinear grids properly2021-11-21T15:51:03-05:00W. Alan Scottpvtr files appear to not load rectilinear grids properlypvtr files appear to not load rectilinear grids properly. Attached is a toy dataset that shows this.
* Master, builtin server, Linux.
* Load blockRectilinearGrid.pvtr. It will load the files block0.vtr and block1.vtr.
They should...pvtr files appear to not load rectilinear grids properly. Attached is a toy dataset that shows this.
* Master, builtin server, Linux.
* Load blockRectilinearGrid.pvtr. It will load the files block0.vtr and block1.vtr.
They should be offset, but are not. It appears that only the first .vtr file read has it's Coordinates read. Unless I am wrong (and don't understand), this is a bad bug.
* To see what I believe it should look like, load both block0.vtr and block1.vtr individually.5.10 (Fall 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20841partitioned dataset writer doesn't work with Catalyst V2 in parallel2021-09-24T09:41:21-04:00Andrew Bauerpartitioned dataset writer doesn't work with Catalyst V2 in parallelThe partitioned dataset writer is mangling the meta-file when outputting from Catalyst V2 in parallel. I'm using the Catalyst2/CxxImageDataExample and running with `mpirun -np 4 bin/CxxImageDataExampleV2 --output datasets/dataset-%04ts.v...The partitioned dataset writer is mangling the meta-file when outputting from Catalyst V2 in parallel. I'm using the Catalyst2/CxxImageDataExample and running with `mpirun -np 4 bin/CxxImageDataExampleV2 --output datasets/dataset-%04ts.vtpd`. The dataset-0001.vtpd file looks like:
```
<VTKFile type="vtkPartitionedDataSet" version="1.0" byte_order="LittleEndian" header_type="UInt64">
<vtkPartitionedDataSet>
<DataSet index="0" file="dataset-0001/dataset-0001_0.vti"/>
<DataSet ind format="binary" RangeMin="0.1" RangeMax="0.1">
CAAAAAAAAACamZmZmZm5Pw==
</DataArray>
<DataArray type="Float64" Name="time" NumberOfTuples="1" format="binary" RangeMin="0.1" RangeMax="0.1">
CAAAAAAAAACamZmZmZm5Pw==
</DataArray>
<DataArray type="Int32" Name="cycle" NumberOfTuples="1" format="binary" RangeMin="1" RangeMax="1">
BAAAAAAAAAABAAAA
</DataArray>
<DataArray type="Int32" Name="timestep" NumberOfTuples="1" format="binary" RangeMin="1" RangeMax="1">
BAAAAAAAAAABAAAA
</DataArray>
<Array type="String" Name="__CatalystChannel__" NumberOfTuples="1" format="binary">
BQAAAAAAAABncmlkAA==
</Array>
</FieldData>
</VTKFile>
e="Int32" Name="timestep" NumberOfTuples="1" format="binary" RangeMin="1" RangeMax="1">
BAAAAAAAAAABAAAA
</DataArray>
<Array type="String" Name="__CatalystChannel__" NumberOfTuples="1" format="binary">
BQAAAAAAAABncmlkAA==
</Array>
</FieldData>
</VTKFile>
```5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20840"bin/CxxImageDataExampleV2 --output dataset-%04ts.vtpd" doesn't work for Cata...2021-09-13T11:24:49-04:00Andrew Bauer"bin/CxxImageDataExampleV2 --output dataset-%04ts.vtpd" doesn't work for Catalyst2 exampleWhen I try to run the Catalyst2 CxxImageDataExample with `bin/CxxImageDataExampleV2 --output dataset-%04ts.vtpd` I get the errors:
```
( 1.570s) [pvbatch ]vtkXMLPartitionedDataSe:89 ERR| vtkXMLPartitionedDataSetWriter (0x2b...When I try to run the Catalyst2 CxxImageDataExample with `bin/CxxImageDataExampleV2 --output dataset-%04ts.vtpd` I get the errors:
```
( 1.570s) [pvbatch ]vtkXMLPartitionedDataSe:89 ERR| vtkXMLPartitionedDataSetWriter (0x2b99af0): Failed to create directory ''.
( 1.570s) [pvbatch ] vtkXMLWriter2.cxx:126 INFO| { DeleteArtifacts
( 1.570s) [pvbatch ] vtkXMLWriter2.cxx:126 INFO| } 0.000 s: DeleteArtifacts
```5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20835Ensight reader does not support undefined and partial variables for ascii2021-08-23T19:23:16-04:00Boonthanome NouanesengsyEnsight reader does not support undefined and partial variables for asciiThe Ensight reader for ascii data will load numerical values for undefined and partial variables. This is annoying in that Paraview will calculate incorrect ranges. Instead, undefined and partial values should be NaN.
Here is a syntheti...The Ensight reader for ascii data will load numerical values for undefined and partial variables. This is annoying in that Paraview will calculate incorrect ranges. Instead, undefined and partial values should be NaN.
Here is a synthetic Ensight dataset that contains both undefined and partial variables:
ascii version: [grid.tar.gz](/uploads/12fc297d138b844a667015c68bf9b18e/grid.tar.gz)
This is a follow-up to this issue (Ensight reader does not support undefined and partial variables): https://gitlab.kitware.com/paraview/paraview/-/issues/20747.
@patchett2002 @utkarsh.ayachit @cory.quammen5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20831Zoom to box is broken2021-10-15T03:45:50-04:00W. Alan ScottZoom to box is brokenZoom to box is broken in master.
* Master, Linux, builtin server.
* Sources/ Wavelet.
* Surface
* Zoom to box. Zoom to a corner of the wavelet.
You will end up in the center of the wavelet. This is very wrong.
I bet this happene...Zoom to box is broken in master.
* Master, Linux, builtin server.
* Sources/ Wavelet.
* Surface
* Zoom to box. Zoom to a corner of the wavelet.
You will end up in the center of the wavelet. This is very wrong.
I bet this happened when the Reset Camera Closest and Zoom Closest to Data was implemented.
Showstopper for the 5.10 release.5.10 (Fall 2021)Sankhesh JhaveriSankhesh Jhaverihttps://gitlab.kitware.com/paraview/paraview/-/issues/20827Spack builds of paraview@master failing to find CLI11 external dependency2021-08-10T16:56:59-04:00Ethan StamSpack builds of paraview@master failing to find CLI11 external dependency@utkarsh.ayachit @cory.quammen
On July 2nd (July 1st builds passed), our spack builds of `paraview@master` started failing. Checking the logs for today's builds, they all failed during the configure step for paraview with:
```console
...@utkarsh.ayachit @cory.quammen
On July 2nd (July 1st builds passed), our spack builds of `paraview@master` started failing. Checking the logs for today's builds, they all failed during the configure step for paraview with:
```console
CMake Warning at VTK/CMake/vtkModule.cmake:4360 (find_package):
By not providing "FindCLI11.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "CLI11", but
CMake did not find one.
Could not find a package configuration file provided by "CLI11" with any of
the following names:
CLI11Config.cmake
cli11-config.cmake
Add the installation prefix of "CLI11" to CMAKE_PREFIX_PATH or set
"CLI11_DIR" to a directory containing one of the above files. If "CLI11"
provides a separate development package or SDK, be sure it has been
installed.
Call Stack (most recent call first):
VTK/CMake/vtkModule.cmake:4960 (vtk_module_find_package)
VTK/CMake/vtkModule.cmake:4831 (vtk_module_third_party_external)
VTK/ThirdParty/cli11/CMakeLists.txt:1 (vtk_module_third_party)
CMake Error at VTK/CMake/vtkModule.cmake:4366 (message):
Could not find the CLI11 external dependency.
Call Stack (most recent call first):
VTK/CMake/vtkModule.cmake:4960 (vtk_module_find_package)
VTK/CMake/vtkModule.cmake:4831 (vtk_module_third_party_external)
VTK/ThirdParty/cli11/CMakeLists.txt:1 (vtk_module_third_party)
-- Configuring incomplete, errors occurred!
```5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20821vtkPVDiscretizableColorTransferFunction: Index out of range !2021-10-04T19:20:19-04:00Ghost UservtkPVDiscretizableColorTransferFunction: Index out of range !Warnings are raised everytime you move your mouse over the Opacity transfer function in a certain case.
### Reproduce:
- enable volume rendering on something (just to have the mapping data show up)
- In mapping data: **add more points (...Warnings are raised everytime you move your mouse over the Opacity transfer function in a certain case.
### Reproduce:
- enable volume rendering on something (just to have the mapping data show up)
- In mapping data: **add more points (nodes) in the opacity transfer function than in the Color transfer functions**
- hover your mouse over the Opacity transfer function graph: you get
```
(1712.476s) [paraview ]vtkColorTransferFunctio:1277 ERR| vtkPVDiscretizableColorTransferFunction (0x55e84103da50): Index out of range!
```
### Brief analysis
Warning is raised here:
https://gitlab.kitware.com/vtk/vtk/-/blob/4b9e1acc53af9ccf54df4b0c78909ff172319a71/Rendering/Core/vtkColorTransferFunction.cxx#L1274
The issue here is that the `this->Internal->Nodes.size()` there always returns the number of nodes in the color transfer function (try it out yourself with a print), even when used in the opacity transfer functions. I tried for quite some time to figure out why but eventually couldn't so I'm raising this issue.
Have a great day5.10 (Fall 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20818Remove Apply button in Save Extracts and Save Catalyst State options2021-09-29T11:54:10-04:00Ethan StamRemove Apply button in Save Extracts and Save Catalyst State options@utkarsh.ayachit @cory.quammen
The Apply button feels out of place in the `Save Extracts Options`. Since when you have the options set up as you want, you are going to save them with `Ok`. Could it be removed, or does it serve a purpos...@utkarsh.ayachit @cory.quammen
The Apply button feels out of place in the `Save Extracts Options`. Since when you have the options set up as you want, you are going to save them with `Ok`. Could it be removed, or does it serve a purpose that I'm not seeing?
![Screen_Shot_2021-06-29_at_9.31.39_AM](/uploads/fa909f171018cae7f391eb72c0d54d7d/Screen_Shot_2021-06-29_at_9.31.39_AM.png)5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20816catalyst 2.0 Python fails when using VTK_PYTHON_OPTIONAL_LINK2021-08-11T13:47:40-04:00Utkarsh Ayachitcatalyst 2.0 Python fails when using VTK_PYTHON_OPTIONAL_LINKIf `VTK_PYTHON_OPTIONAL_LINK` is ON, which is default, all Catalyst 2.0 tests with Python fails with
```
ImportError: /home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/python3.8/site-packages/paraview/modules/vtkRemotingCore.so: undef...If `VTK_PYTHON_OPTIONAL_LINK` is ON, which is default, all Catalyst 2.0 tests with Python fails with
```
ImportError: /home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/python3.8/site-packages/paraview/modules/vtkRemotingCore.so: undefined symbol: _Py_NoneStruct
```
This happens is overcome is VTK_PYTHON_OPTIONAL_LINK is OFF, or dlopening with RTLD_GLOBAL.
```diff
diff --git a/src/catalyst/catalyst_api.c b/src/catalyst/catalyst_api.c
index c5cd99b..283bfc2 100644
--- a/src/catalyst/catalyst_api.c
+++ b/src/catalyst/catalyst_api.c
@@ -363,7 +363,7 @@ catalyst_handle_t handle_open(const char* directory, const char* libname)
snprintf(full_library_path, path_len, "%s/libcatalyst-%s.so", directory, libname);
- catalyst_handle_t handle = dlopen(full_library_path, RTLD_LAZY | RTLD_LOCAL);
+ catalyst_handle_t handle = dlopen(full_library_path, RTLD_LAZY | RTLD_GLOBAL);
if (!handle)
{
printf("failed to open library: %s\n", dlerror());
```
Not sure what's the best way to address this. This is causing the Catalyst2 tests to fail: https://open.cdash.org/viewTest.php?onlyfailed&buildid=73109845.10 (Fall 2021)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20811Find data - Edit Properties is redundant2021-08-05T21:10:41-04:00W. Alan ScottFind data - Edit Properties is redundantThe Find Data - Edit Properties button is listed twice in Find Data. One is below Cell and Point labels, one is below Interactive Selection. I bet the lower one was suppose to edit the Interactive Selection, not Labels.
This is with m...The Find Data - Edit Properties button is listed twice in Find Data. One is below Cell and Point labels, one is below Interactive Selection. I bet the lower one was suppose to edit the Interactive Selection, not Labels.
This is with master, June 25, 2021.5.10 (Fall 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20809Incorrect box widget placement for PointVolumeInterpolator filter2021-08-10T16:36:52-04:00Utkarsh AyachitIncorrect box widget placement for PointVolumeInterpolator filterSteps:
* Open disk_out_ref.ex2, all variables, Apply
* Create **Point Volume Interpolator**, the box widget will be placed incorrectly.Steps:
* Open disk_out_ref.ex2, all variables, Apply
* Create **Point Volume Interpolator**, the box widget will be placed incorrectly.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachit