ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-09-27T06:21:20-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22318XRInterface: OpenXR should be default2023-09-27T06:21:20-04:00Mathieu Westphal (Kitware)XRInterface: OpenXR should be defaultOpenXR should be default with the XRInterface plugin, and OpenVR should be considered for deprecation.OpenXR should be default with the XRInterface plugin, and OpenVR should be considered for deprecation.https://gitlab.kitware.com/paraview/paraview/-/issues/22317XRInterface: Cleanup Imago support2023-09-27T06:21:56-04:00Mathieu Westphal (Kitware)XRInterface: Cleanup Imago supportImago support is barely used in the XRInterface.
Clean it up, improve testing, remove unused code.Imago support is barely used in the XRInterface.
Clean it up, improve testing, remove unused code.https://gitlab.kitware.com/paraview/paraview/-/issues/22316XRInterface: Rework collaboration/mineview logic2023-09-27T06:21:56-04:00Mathieu Westphal (Kitware)XRInterface: Rework collaboration/mineview logicXRInterface contain logic that works with the mineview collaborative server.
Put all this logic in a dedicated folder to be provided within ParaView instead of relying on mineview
https://gitlab.kitware.com/ken-martin/mineviewXRInterface contain logic that works with the mineview collaborative server.
Put all this logic in a dedicated folder to be provided within ParaView instead of relying on mineview
https://gitlab.kitware.com/ken-martin/mineviewhttps://gitlab.kitware.com/paraview/paraview/-/issues/22315Add option to disable point merging in STL reader2023-09-27T04:28:18-04:00Kenneth MorelandAdd option to disable point merging in STL readerThe STL reader applies a point merging algorithm after reading the data. This is usually what you want, but there are instances when you might wish to merge the points.
The VTK reader has an option to turn off the point merging, but thi...The STL reader applies a point merging algorithm after reading the data. This is usually what you want, but there are instances when you might wish to merge the points.
The VTK reader has an option to turn off the point merging, but this option is not exposed in the ParaView servermanager XML. It is an easy fix to add this option. See https://discourse.paraview.org/t/avoid-merging-duplicated-points/12905 for a discussion on how to update the XML. (Note that, unlike in the discourse discussion, the point merging feature should be defaulted to 1 to maintain backward compatibility.)https://gitlab.kitware.com/paraview/paraview/-/issues/22314Selection labels of partial arrays is broken2023-09-25T22:03:52-04:00W. Alan ScottSelection labels of partial arrays is brokenSelection labels of partial arrays are broken.
First, I made a dataset. This dataset replicates a user's dataset, so I don't think the issue is with my voodoo'd dataset. Load can.exo. Load only the first block. Turn ACCL off. Save ...Selection labels of partial arrays are broken.
First, I made a dataset. This dataset replicates a user's dataset, so I don't think the issue is with my voodoo'd dataset. Load can.exo. Load only the first block. Turn ACCL off. Save with the IOSS writer. Load the second block only. Turn only VEL off. Save with the IOSS writer. Change files to be can3.e.2.\[0,1\]. Now, we should have two blocks with partial arrays.
* Linux, master, builtin server.
* Load can3.e.2.\[0,1\]. Apply.
* Find Data. Selection labels. Display ACCL.
* Multiblock inspector. Select first block. Select last block. Select all blocks.
What should happen is that if the data is missing, nothing shows without an error. If the data is present, it should show. Finally, if the data is only one one of the two blocks, that block should have annotations, but not both. This fails.
Attaching can3.e.2.\[0,1\]5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22313Allow "selection labels" without selection2023-09-25T21:11:08-04:00W. Alan ScottAllow "selection labels" without selectionThe Selection Labels functionality is extremely powerful. Currently it shows variable data on cells/points that are selected. However, it should also be available for all of the cells and points being shown, without selection. Selecti...The Selection Labels functionality is extremely powerful. Currently it shows variable data on cells/points that are selected. However, it should also be available for all of the cells and points being shown, without selection. Selection adds a pink highlight around selected cells or on points, and users may want to show their mesh, with some variable labeled, without this pink highlight.
Please add a checkbox on the Find Data dialog/ Selection Labels section named "label without selection" or somesuch.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22311feature request: streamtracers able to sample (or interpolate) CellData2023-09-25T11:39:19-04:00Javier Garcia-Pintadofeature request: streamtracers able to sample (or interpolate) CellDataHello,
I commonly work with ExodusII files in paraview, and it would be great if the stream tracers [for me it is commonly the StreamTracerWithCustomSource] were are able to interpolate CellData along the trajectories.
Best wishes
JavierHello,
I commonly work with ExodusII files in paraview, and it would be great if the stream tracers [for me it is commonly the StreamTracerWithCustomSource] were are able to interpolate CellData along the trajectories.
Best wishes
Javierhttps://gitlab.kitware.com/paraview/paraview/-/issues/22310default axes colors2023-09-25T04:46:36-04:00Theo Igadefault axes colorsI know that this is not a bug but rather a conventional choice, but as a regular user of various 3D graphical software, I'm always puzzled by the default axes colors of paraview.
I refer to the docs: [...The X axis will be drawn as a b...I know that this is not a bug but rather a conventional choice, but as a regular user of various 3D graphical software, I'm always puzzled by the default axes colors of paraview.
I refer to the docs: [...The X axis will be drawn as a blue line, the Y axis as a green line, and the Z axis as a red line...](https://kitware.github.io/paraview-docs/latest/python/paraview.simple.Axes.html)
Even if to my knowledge there is no mandatory color mapping, paraview is the only software with this color default.
Please consider setting the axes colors to the way all graphical software are mapping, i.e.
* X -\> Red
* Y -\> Green
* Z -\> Blue
There is an old mnemonic reason, as is explained [here](https://ux.stackexchange.com/questions/79561/why-are-x-y-and-z-axes-represented-by-red-green-and-blue) .https://gitlab.kitware.com/paraview/paraview/-/issues/22309Nvidia IndeX plugin not supports VDB file2023-09-22T03:20:05-04:00fashingNvidia IndeX plugin not supports VDB fileThe plugin might have to handle casting the `Partitioned Dataset`.
Here is the corresponding [post](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817) on Paraview discourse.
Example dataset: https://arti...The plugin might have to handle casting the `Partitioned Dataset`.
Here is the corresponding [post](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817) on Paraview discourse.
Example dataset: https://artifacts.aswf.io/io/aswf/openvdb/models/bunny_cloud.vdb/1.0.0/bunny_cloud.vdb-1.0.0.zip
Expected output:
![image](/uploads/75cbec900554c4fbf4305e8e136c6d5a/image.png)
Actual output:
Empty with warning:
`( 99.569s) [paraview ] vtkDataObject.cxx:488 WARN| vtkImageData (0x277291a0): Attempted to ShallowCopy from null.`https://gitlab.kitware.com/paraview/paraview/-/issues/22305Color maps for multiple representations in single pqRenderView in custom appl...2023-09-27T08:52:11-04:00Pietersielie PColor maps for multiple representations in single pqRenderView in custom application remain synchronised even when "UseSeparateColorMap" property is trueI have a custom Paraview client application that is used to display astronomical data (with the data living on a standard `pvserver` instance). As part of it, I display multiple 2D images in the same renderview (an instance of `pqRenderV...I have a custom Paraview client application that is used to display astronomical data (with the data living on a standard `pvserver` instance). As part of it, I display multiple 2D images in the same renderview (an instance of `pqRenderView*`). The images are loaded and controlled through a container class that owns the object and redirects commands to the proxies. The images are all instantiated and loaded separately, to make sure that arbitrary numbers of images can be loaded.
Here is a snippet from the container class header to define some of the variables referred to later on:
```
vtkSMSessionProxyManager* serverProxyManager;
pqObjectBuilder* builder;
pqPipelineSource* imageSource;
pqDataRepresentation* imageRep;
vtkSMProxy* imageProxy;
vtkSMTransferFunctionProxy* lutProxy;
pqRenderView* viewImage;
```
The renderview and objectBuilder are passed through from the class that initialises the server connection, creates the view, and governs the user interaction. It keeps a vector array of the container class that controls the images.
The images are created as follows:
```
QString filename;
imageSource = pqLoadDataReaction::loadData({ filename });
imageRep = builder->createDataRepresentation(this->imageSource->getOutputPort(0), viewImage);
imageProxy = imageRep->getProxy();
vtkSMPropertyHelper(imageProxy, "Representation").Set("Slice");
auto separateProperty = vtkSMPVRepresentationProxy::SafeDownCast(imageProxy)->GetProperty("UseSeparateColorMap");
vtkSMPropertyHelper(separateProperty).Set(1);
vtkSMPVRepresentationProxy::SetScalarColoring(imageProxy, "FITSImage", vtkDataObject::POINT);
imageProxy->UpdateVTKObjects();
```
The colour map for each image is initialised by the following:
```
vtkNew<vtkSMTransferFunctionManager> mgr;
lutProxy = vtkSMTransferFunctionProxy::SafeDownCast(mgr->GetColorTransferFunction("FITSImage", imageProxy->GetSessionProxyManager()));
```
When the user changes the colour map, this is what I use to change the colour map:
```
if (vtkSMProperty *lutProperty = imageProxy->GetProperty("LookupTable")) {
auto presets = vtkSMTransferFunctionPresets::GetInstance();
lutProxy->ApplyPreset(presets->GetFirstPresetWithName(name.toStdString().c_str()));
vtkSMPropertyHelper(lutProperty).Set(lutProxy);
lutProxy->UpdateVTKObjects();
vtkSMPVRepresentationProxy::RescaleTransferFunctionToDataRange(imageProxy, false, false);
vtkSMPVRepresentationProxy::SetScalarBarVisibility(imageProxy, viewImage->getProxy(), true);
imageProxy->UpdateVTKObjects();
this->colourMap = name;
return 1;
}
```
If the user chooses to select log scale, that is changed by this snippet:
```
if (auto logProperty = lutProxy->GetProperty("UseLogScale"))
{
double range[2];
vtkSMTransferFunctionProxy::GetRange(lutProxy, range);
vtkSMCoreUtilities::AdjustRangeForLog(range);
this->logScale = true;
vtkSMTransferFunctionProxy::RescaleTransferFunction(lutProxy, range);
vtkSMPropertyHelper(logProperty).Set(1);
changeColorMap(this->getColourMap());
lutProxy->UpdateVTKObjects();
imageProxy->UpdateVTKObjects();
return 1;
}
```
For some reason, if I just change the log scaling property, the actual colour map resets to the default, which is why I change the colour map again after setting the scaling property.
Each image is initialised separately and added to the pqRenderView. However, despite setting the “UseSeparateColorMap” property to true on initialising the image, all the images in the renderview has their colour maps synchronised. If any of the images have their colour maps changed, all the others will follow suit.
I have tested the value of the "UseSeparateColourMap" property at various points in my program after first initialisation using the below code snippet, and at every point after initialisation it returns true.
```
int sep;
vtkSMPropertyHelper(vtkSMPVRepresentationProxy::SafeDownCast(imageProxy)->GetProperty("UseSeparateColorMap")).Get(&sep);
if (sep == 1)
std::cerr << "Setting colour map with \"UseSeparateColourMap\" set to true!" << std::endl;
```
This issue was initially reported on the [Paraview discourse](https://discourse.paraview.org/t/separate-colour-maps-for-multiple-representations-in-single-render-view-in-custom-application/12882) before being referred here.https://gitlab.kitware.com/paraview/paraview/-/issues/22298"Crystal Eyes" stereo mode can't be selected via the GUI2023-10-10T11:05:05-04:00Thomas Galland"Crystal Eyes" stereo mode can't be selected via the GUIWhen launching ParaView with `--stereo` without the `--stereo-type="Crystal Eyes"` option, selecting `Crystal Eyes` afterwards in the GUI does nothing.
Steps to reproduce:
- Launch ParaView with `--stereo` launch option
- In the `Stereo...When launching ParaView with `--stereo` without the `--stereo-type="Crystal Eyes"` option, selecting `Crystal Eyes` afterwards in the GUI does nothing.
Steps to reproduce:
- Launch ParaView with `--stereo` launch option
- In the `Stereo` options in the `View` section of the `Properties` panel, set `Stereo Type` to `Crystal Eyes`
- Nothing happens.
When launching ParaView with `--stereo` with the `--stereo-type="Crystal Eyes"` option, selecting any other stereo mode afterwards in the GUI does apply only on the left eye (the right eye image freezes).
Steps to reproduce:
- Launch ParaView with `--stereo --stereo-type="Crystal Eyes"` launch options
- In the `Stereo` options in the `View` section of the `Properties` panel, set `Stereo Type` to `None`
- Right eye image freezes.
Tested in builtin mode.
This seems to be somehow a more generic issue of the 3rd one reported here: https://gitlab.kitware.com/paraview/paraview/-/issues/19484https://gitlab.kitware.com/paraview/paraview/-/issues/22296ParaView can hang in a distributed context when there is no data on at least ...2023-09-13T04:03:41-04:00Julien FaustyParaView can hang in a distributed context when there is no data on at least one of the processes## Steps to reproduce
* start a distributed server on 2 procs: `mpirun -np 2 pvserver`
* connect a paraview client to the server
* open `disk_out_ref.ex2` from the test data
* run `GhostCellsGenerator`
* ParaView should hang on the ghos...## Steps to reproduce
* start a distributed server on 2 procs: `mpirun -np 2 pvserver`
* connect a paraview client to the server
* open `disk_out_ref.ex2` from the test data
* run `GhostCellsGenerator`
* ParaView should hang on the ghost cell generation
## Probable cause
I believe that the executive for each algorithm takes the decision to execute without communicating with executives on other processes. This means that an executive may decline to execute a filter that necessitates distributed communication on a process where no data exists. If the filter does not take this into account, then on the first global communication, the execution will hang on all processes executing the filter waiting for the processes that decided to not execute the filter.
It is either:
* the responsibility of the executive to ensure that a filter gets executed on all ranks if executed on any rank,
* the responsibility of all filters to take into account that all processes might not enter into their request data,
* or, the responsibility of the controller to create sub communicators for each algorithmic execution that are coherent
As of the time of writing of this issue, this responsibility is not clearly stated or I have not found where in the documentation it is.https://gitlab.kitware.com/paraview/paraview/-/issues/22295`2D Transfer Function checkbox` volume rendering not working with .vdb file (...2023-09-13T03:45:37-04:00fashing`2D Transfer Function checkbox` volume rendering not working with .vdb file (partial arrays partitioned dataset)As stated in [discourse](https://discourse.paraview.org/t/is-it-possible-to-choose-multiple-girds-in-the-coloring-select/12831),
I ran into these errors while enabling the `2D Transfer Function checkbox` for volume rendering.
![image](/...As stated in [discourse](https://discourse.paraview.org/t/is-it-possible-to-choose-multiple-girds-in-the-coloring-select/12831),
I ran into these errors while enabling the `2D Transfer Function checkbox` for volume rendering.
![image](/uploads/880599da531d76843547fd5181280628/image.png)
I tried several testcases [here](https://www.openvdb.org/download/) and got the same result.https://gitlab.kitware.com/paraview/paraview/-/issues/22292Changing SMP_IMPLEMENTATION_TYPE triggers a complete rebuild of ParaView2023-09-08T12:05:16-04:00Mathieu Westphal (Kitware)Changing SMP_IMPLEMENTATION_TYPE triggers a complete rebuild of ParaViewChanging SMP_IMPLEMENTATION_TYPE triggers a complete rebuild of ParaView
```
cmake -GNinja -DVTK_SMP_ENABLE_SEQUENTIAL=ON -DVTK_SMP_ENABLE_STDTHREAD=ON -DVTK_SMP_IMPLEMENTATION_TYPE=STDThread ../src
ninja
cmake -DVTK_SMP_IMPLEMENTATION_...Changing SMP_IMPLEMENTATION_TYPE triggers a complete rebuild of ParaView
```
cmake -GNinja -DVTK_SMP_ENABLE_SEQUENTIAL=ON -DVTK_SMP_ENABLE_STDTHREAD=ON -DVTK_SMP_IMPLEMENTATION_TYPE=STDThread ../src
ninja
cmake -DVTK_SMP_IMPLEMENTATION_TYPE=Sequential ./
ninja -> >15000 targets, this is a bug
```
VTK does not have this issue, it triggers a few hundreds targets instead.https://gitlab.kitware.com/paraview/paraview/-/issues/22290ioss writer incorrectly switches to the exodus writer2023-09-07T17:07:27-04:00W. Alan Scottioss writer incorrectly switches to the exodus writer If you try to write a legal exodus file using the IOSS writer, but the extension isn't .exo, the writer magically switches to the Exodus writer without notice. This is incorrect - the IOSS writer should just print out a warning and clo... If you try to write a legal exodus file using the IOSS writer, but the extension isn't .exo, the writer magically switches to the Exodus writer without notice. This is incorrect - the IOSS writer should just print out a warning and close.
* Master from July 2023, Linux, builtin server.
* Open can.exo. Apply.
* File/ Save Data. Save as canRS.e. A new dialog will open up. At the top of the dialog will state that we are using the Exodus writer.
This is a bug.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22289Plugin for projecting Latitude Longitude grids into other forms: Robinson, Me...2023-12-16T08:25:58-05:00John PatchettPlugin for projecting Latitude Longitude grids into other forms: Robinson, Mercator, Stereographic, Lambert Conformal Conic@berkgeveci We, @linneapalmstrom , LANL, RAPIDS2, would like to see a new plugin, Latitude Longitude reproject that leverages the new default superbuild inclusion of vtkGeovisCore. Our uses have requested Robinson, Mercator, Stereograp...@berkgeveci We, @linneapalmstrom , LANL, RAPIDS2, would like to see a new plugin, Latitude Longitude reproject that leverages the new default superbuild inclusion of vtkGeovisCore. Our uses have requested Robinson, Mercator, Stereographic, Lambert Conformal Conic projections. In addition they requested a cartesian projection on a sphere (which we will add a separate issue for).John PatchettJohn Patchetthttps://gitlab.kitware.com/paraview/paraview/-/issues/22288add_pv_test testing function undefined but still used2023-09-08T03:18:01-04:00Louis Gombertadd_pv_test testing function undefined but still usedThe CMake function/macro `add_pv_test` does not seem to be defined anymore even though it is used 4 times throughout the file [Clients/Testing/XML/CMakeLists.txt](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Clients/ParaVie...The CMake function/macro `add_pv_test` does not seem to be defined anymore even though it is used 4 times throughout the file [Clients/Testing/XML/CMakeLists.txt](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Clients/ParaView/Testing/XML/CMakeLists.txt), which could indicate dead tests and unused CMake code paths.
It is probably a leftover from this cleanup commit https://gitlab.kitware.com/paraview/paraview/-/commit/2c00d068f8d523e494d2173399980f8ce647e1a3
cc @mwestphal @ben.boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22287information/FileProperties section does not display correct filename correspo...2023-09-07T03:28:29-04:00이상준 / 학생 / 에너지시스템공학부information/FileProperties section does not display correct filename corresponding to the one being rendered.In the <Information> Panel, the Name section under <File Properties> should have displayed the file that is currently being rendered. However, the most new release 5.11.1 only shows the very first file of the series.
At least up to Para...In the <Information> Panel, the Name section under <File Properties> should have displayed the file that is currently being rendered. However, the most new release 5.11.1 only shows the very first file of the series.
At least up to ParaView 5.6.2, it was showing the correct file.
Related forum post is https://discourse.paraview.org/t/file-name-does-not-appear-in-information-fileproperties-section-y/12821https://gitlab.kitware.com/paraview/paraview/-/issues/22285ProcessIds cannot be shown in ParaView when using local rendering2023-09-06T04:58:24-04:00Mathieu Westphal (Kitware)ProcessIds cannot be shown in ParaView when using local renderingProcessIds are a recently introduced attributes data, similar to GlobalIds. The filter `GenerateProcessIds` can generate such ideas,
however, they are not copied to the client when using client/server with local rendering.
Step to repro...ProcessIds are a recently introduced attributes data, similar to GlobalIds. The filter `GenerateProcessIds` can generate such ideas,
however, they are not copied to the client when using client/server with local rendering.
Step to reproduce:
- run pvserver, run paraview
- Connect to pvserver
- Make sure remote rendering threshold is higher than 20Mb
- Sphere, Apply
- GenerateProcessIds, Apply
- Try to color with ProcessIds, no data is visible and solid color is used, this is a bug
- A simple work around is to use calculator to copy the array in a non ProcessIds arrays
This is probably caused by the copy of the surfacic data from the server to the client which probably ignore the ProcessIds
Note: The following tests are impacted by this bug and should be modified whenever this bug is fixed:
- DistributePoints
- GenerateProcessIds
- GhostCellsGeneratorSynchronizehttps://gitlab.kitware.com/paraview/paraview/-/issues/22284Issue while reading data from lagrangian particles generated by OpenFOAM usin...2023-09-05T11:42:41-04:00franco otaolaIssue while reading data from lagrangian particles generated by OpenFOAM using the OpenFOAM readerHello,
when opening a simulation with lagrangian particles done in OpenFOAM, there is an issue with the time stamps of the particles which blocks the possibility of using for example the temporal particles pathlines filter to create the ...Hello,
when opening a simulation with lagrangian particles done in OpenFOAM, there is an issue with the time stamps of the particles which blocks the possibility of using for example the temporal particles pathlines filter to create the path that the particles followed during the simulation, even though the data 'is there'. Here is the discussion of about the issue: https://discourse.paraview.org/t/lagrangianparticletracker-example-file/571 , the error that I am getting (using paraview 5.11.1 with OpenFOAM 2306) is the following:
```
ERROR: In vtkTemporalPathLineFilter.cxx, line 343
vtkTemporalPathLineFilter (000001E683425760): The input dataset did not have a valid DATA_TIME_STEPS information key
ERROR: In vtkExecutive.cxx, line 741
vtkPVCompositeDataPipeline (000001E692199690): Algorithm vtkTemporalPathLineFilter (000001E683425760) returned failure for request: vtkInformation (000001E690439420)
Debug: Off
Modified Time: 2518182
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FROM_OUTPUT_PORT: 0
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1
```
here the files of the case with some data can be downloaded, the data was to large to upload directly to the gitlab [link](https://filesender.utc.fr/filesender/?s=download&token=30fc3d13-37cb-47d4-aab3-d82b8632b53e)
best regards