ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-09-25T04:46:36-04:00https://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/22308Error in clip closed surface filter over contour filter2023-10-24T09:36:08-04:00fashingError in clip closed surface filter over contour filterThe `clip closed surface filter` is not working over `contour filter`, the output surface is not closed.
Here is the corresponding [post](https://discourse.paraview.org/t/clip-closed-surface-filter-over-contour-filter/12901) on Paraview ...The `clip closed surface filter` is not working over `contour filter`, the output surface is not closed.
Here is the corresponding [post](https://discourse.paraview.org/t/clip-closed-surface-filter-over-contour-filter/12901) on Paraview discourse.
Output of contour filter | Output of clip closed surface filter
:-------------------------:|:-------------------------:
![image](/uploads/351e3901c24271ddd8f79cb43d286286/image.png) | ![image](/uploads/01dd418551c1448bd69dbce60235b34d/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22307Build Dependencies for Ubuntu 22.04 LTS2023-09-25T10:10:08-04:00Jonathan HodgesBuild Dependencies for Ubuntu 22.04 LTSBuild instructions for Paraview are based on Ubuntu 18.04 LTS. qt5-default is no longer available in newer Ubuntus. In Ubuntu 22.04 LTS I needed to replace it with the following (new packages at the end):
sudo apt-get install git cmake ...Build instructions for Paraview are based on Ubuntu 18.04 LTS. qt5-default is no longer available in newer Ubuntus. In Ubuntu 22.04 LTS I needed to replace it with the following (new packages at the end):
sudo apt-get install git cmake build-essential libgl1-mesa-dev libxt-dev libqt5x11extras5-dev libqt5help5 qttools5-dev qtxmlpatterns5-dev-tools libqt5svg5-dev python3-dev python3-numpy libopenmpi-dev libtbb-dev ninja-build qtbase5-dev qtchooser qt5-qmake qtbase5-dev-toolshttps://gitlab.kitware.com/paraview/paraview/-/issues/22306smTestDriver crashes when QT_QPA_PLATFORMTHEME variable is set2023-09-22T03:23:21-04:00Louis GombertsmTestDriver crashes when QT_QPA_PLATFORMTHEME variable is setSteps to reproduce on Linux :
- install a Qt theme
- set environment variable `$QT_QPA_PLATFORMTHEME`, either manually or through qt5ct
- run a rendering test (eg `ctest -R pv.PythonShellRunScript`)
Running the test manually using `...Steps to reproduce on Linux :
- install a Qt theme
- set environment variable `$QT_QPA_PLATFORMTHEME`, either manually or through qt5ct
- run a rendering test (eg `ctest -R pv.PythonShellRunScript`)
Running the test manually using `paraview` executable works fine, but not using `smTestDriver` executable or `ctest`.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/22303OSPRay and ToneMapping create a remanent ghost image, related to OSPRay "accu...2023-09-22T03:26:51-04:00Charles GueunetOSPRay and ToneMapping create a remanent ghost image, related to OSPRay "accumulation" featureWhen disabling OSPray volume rendering while Tone mapping has been enabled, a negative remnant image pollute the volume rendering. Here is a small video to illustrate:
![tone-mapping.gif](/uploads/8330cc76c3a57de28cde6cef831a3bed/tone-m...When disabling OSPray volume rendering while Tone mapping has been enabled, a negative remnant image pollute the volume rendering. Here is a small video to illustrate:
![tone-mapping.gif](/uploads/8330cc76c3a57de28cde6cef831a3bed/tone-mapping.gif)
@lucas.givord FYIhttps://gitlab.kitware.com/paraview/paraview/-/issues/22302XRInterface pipeline interface corruption (Monado OpenXR)2023-09-19T01:33:21-04:00Tyson WhiteheadXRInterface pipeline interface corruption (Monado OpenXR)### Issue
The XCInterface plugin works okay until I click on any of the pipeline objects. Then the interface window gets shrunk down to part of the panel with the extra space filled with garbage.
It doesn't freeze or anything, and if y...### Issue
The XCInterface plugin works okay until I click on any of the pipeline objects. Then the interface window gets shrunk down to part of the panel with the extra space filled with garbage.
It doesn't freeze or anything, and if you inteface with the areas on the wider window where the buttons and such would be if they hadn't been shrunk down, it still works and updates the shrunk down bit.
Here is a screenshot of the shrunk interface
![paraview](/uploads/2d77dd0ad7889dd7285e6375ad27c8ac/paraview.png)
### Client Information
```
Version: 5.11.0
VTK Version: 9.2.20220823
Qt Version: 5.15.10
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: /nix/store/xs0nw11xzxm875vma7cn31haiqvhrbg7-python3-3.10.12-env/lib/python3.10
Python Library Version: 3.10.12 (main, Jun 6 2023, 22:43:10) [GCC 12.2.0]
Python Numpy Support: On
Python Numpy Path: /nix/store/xs0nw11xzxm875vma7cn31haiqvhrbg7-python3-3.10.12-env/lib/python3.10/site-packages/numpy
Python Numpy Version: 1.24.2
Python Matplotlib Support: On
Python Matplotlib Path: /nix/store/xs0nw11xzxm875vma7cn31haiqvhrbg7-python3-3.10.12-env/lib/python3.10/site-packages/matplotlib
Python Matplotlib Version: 3.7.0
Python Testing: Off
MPI Enabled: On
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 4
OpenGL Vendor: AMD
OpenGL Version: 4.6 (Core Profile) Mesa 23.0.3
OpenGL Renderer: AMD Radeon RX 6600 XT (navi23, LLVM 15.0.7, DRM 3.52, 6.4.12)
Accelerated filters overrides available: No
```
### Connection Information
```
Remote Connection: No
```
### OpenXR Information
I don't really see how to query my OpenXR setup (there doesn't seem to be any tool like `openxr-info`). But here is the output from the `openxr_runtime_list` program that is included with the openxr loader package
```
LOG in xrCreateInstance: Instance created
createInfo->applicationInfo.applicationName: List
createInfo->applicationInfo.applicationVersion: 1
createInfo->applicationInfo.engineName: List Engine
createInfo->applicationInfo.engineVersion: 1
appinfo.detected.engine.name: (null)
appinfo.detected.engine.version: 0.0.0
quirks.disable_vulkan_format_depth_stencil: false
LOG in xrCreateInstance: Selected devices
Head: 'Valve Index (libsurvive)'
Left: 'Valve Index Left Controller (libsurvive)'
Right: 'Valve Index Right Controller (libsurvive)'
Hand-Tracking Left: 'Valve Index Left Controller (libsurvive)'
Hand-Tracking Right: 'Valve Index Right Controller (libsurvive)'
Evaluating system
name: 'Monado: Valve Index (libsurvive)'
vendorId: 0x2a
systemId: 0x1
systemName: Monado: Valve Index (libsurvive)
List instance extensions
XR_KHR_binding_modification 1
XR_KHR_composition_layer_cube 8
XR_KHR_composition_layer_cylinder 4
XR_KHR_composition_layer_depth 6
XR_KHR_composition_layer_equirect 3
XR_KHR_composition_layer_equirect2 1
XR_KHR_convert_timespec_time 1
XR_KHR_opengl_enable 10
XR_KHR_opengl_es_enable 8
XR_KHR_swapchain_usage_input_attachment_bit 3
XR_KHR_vulkan_enable 8
XR_KHR_vulkan_enable2 2
XR_EXT_dpad_binding 1
XR_EXT_hand_tracking 4
XR_FB_display_refresh_rate 1
XR_MND_headless 2
XR_MND_swapchain_usage_input_attachment_bit 2
XR_EXTX_overlay 5
XR_MNDX_egl_enable 1
XR_MNDX_force_feedback_curl 1
XR_EXT_debug_utils 4
List API layer properties
```
Here are the various version numbers for OpenXR related components
```
openxr-loader: 1.0.27
vulkan-loader: 1.3.249
amdvlk: 2023.Q2.1
libsurvive: 1.01
openhmd: 0.3.0
monado: unstable-2023-01-14
```https://gitlab.kitware.com/paraview/paraview/-/issues/22301Colormaps: consider adding color deficient-friendly colormaps from Fabio Crameri2023-10-03T20:24:42-04:00Cory Quammencory.quammen@kitware.comColormaps: consider adding color deficient-friendly colormaps from Fabio CrameriThese colormaps are available here: https://www.fabiocrameri.ch/colourmaps/
They include ParaView colormap files.These colormaps are available here: https://www.fabiocrameri.ch/colourmaps/
They include ParaView colormap files.https://gitlab.kitware.com/paraview/paraview/-/issues/22300Clip filter tetrahedralizes the whole mesh whenever a complex cell is present2023-09-19T15:37:22-04:00Tiffany ChhimClip filter tetrahedralizes the whole mesh whenever a complex cell is presentWhen **at least one complex cell** such as a polygon, polyhedron, high-order cell, etc. is present in a mesh, the Clip filter will call `vtkClipDataSet` internally.
The latter **tetrahedralizes the entire clipped dataset**, including r...When **at least one complex cell** such as a polygon, polyhedron, high-order cell, etc. is present in a mesh, the Clip filter will call `vtkClipDataSet` internally.
The latter **tetrahedralizes the entire clipped dataset**, including regular cells such as hexahedra or wedges, which should be left intact or simply clipped.
**Before ParaView 5.11.0**, only complex cells were tetrahedralized instead of the entire dataset.
This change seems to have been introduced in vtk/vtk!9310.Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22299"Interpret Values as categories" does not work with Volume rendering for TIFF...2023-11-29T10:40:35-05:00niklas netter"Interpret Values as categories" does not work with Volume rendering for TIFF series readerHi,
I have a 3d array saved in a tiff file whose contents I want to look at in Paraview. The array contains categorical data, so each pixel is either 0, 1, or 2. I import the tiff file in Paraview with the TIFF Series Reader and it is co...Hi,
I have a 3d array saved in a tiff file whose contents I want to look at in Paraview. The array contains categorical data, so each pixel is either 0, 1, or 2. I import the tiff file in Paraview with the TIFF Series Reader and it is correctly displayed when switching Volume Representation. However, when I click Interpret Values As Categories in the Color Map Editor the colors of the different regions do not change. I am using Paraview 5.10.1 as in this post ("Interpret values as categories" not working for string properties (PV 5.11.0 RC2)) it was suggested that the Interpret Values As Categories function might not work in 5.11.0.
As you can see in the image, the Colorbar changes to the categorical style, but the colors are not correctly displayed. The hemisphere has values of 1, the cube has values of 2, and the surrounding has values of 0.
![78a074e4d317fa086dd27d6ca4fc21dc6c7f59b9](/uploads/0689632cc771a16a05bb00da5db077b1/78a074e4d317fa086dd27d6ca4fc21dc6c7f59b9.jpeg)
[Download link to example file](https://filesender.switch.ch/filesender2/?s=download&token=947a265c-b981-43ba-b104-692e6f799644) (might expire)
It seems that "Interpret Values as categories" does not work with Volume rendering for TIFF series readers.
I am using Windows 11 and I downloaded Paraview from the official website.
PS: I reported that behaviour already in the [discourse forum](https://discourse.paraview.org/t/interpret-values-as-categories-does-not-work-with-tiff-series-reader/11313).
Best,
Niklashttps://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/22297Loading a file with a ';' in the filename corrupts paraview `ini` file2023-11-08T09:11:56-05:00Joachim KruithofLoading a file with a ';' in the filename corrupts paraview `ini` fileSteps to reproduce:
- load a file with a ';' in the filename
- quit paraview
- launch paraview
- loading any file fails with a segfault
Root cause identified as loading the list of recently opened files that fails at parsing stage with...Steps to reproduce:
- load a file with a ';' in the filename
- quit paraview
- launch paraview
- loading any file fails with a segfault
Root cause identified as loading the list of recently opened files that fails at parsing stage with a segfault.
Can be remediated by adding `\` before ';' in the faulty filename in the paraview `ini` file. (or deleting the `ini` file)Aron HelserAron Helserhttps://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/22294Spreadsheet view crashes remote server2024-03-25T14:07:36-04:00W. Alan ScottSpreadsheet view crashes remote serverSpreadsheet view is crashing remote server after slice. Here is how to replicate.
* Master (v5.11.1-1679-g a2b48e7dbb), Linux, remote server (16 ranks)
* Open g1s1. Apply.
* Slice. Apply.
* Split Horizontal. Spreadsheet.
Crash
@co...Spreadsheet view is crashing remote server after slice. Here is how to replicate.
* Master (v5.11.1-1679-g a2b48e7dbb), Linux, remote server (16 ranks)
* Open g1s1. Apply.
* Slice. Apply.
* Split Horizontal. Spreadsheet.
Crash
@cory.quammen @spiros.tsalikis
If you guys can find this for 5.12.0, great. OK to slip to 5.12.1. Must be fixed for 5.12.1.5.12.1 (Spring 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22293Generating a geometry from a table wil trigger whole pipeline a second time w...2023-09-28T03:14:10-04:00Mathieu Westphal (Kitware)Generating a geometry from a table wil trigger whole pipeline a second time when working with a distributed server because of ghost cellsGenerating a geometry from a table wil trigger whole pipeline a second time when working with a distributed server because of ghost cells.
It is caused by the fact the the geometry representation (through vtkSIProxy code) is requesting ...Generating a geometry from a table wil trigger whole pipeline a second time when working with a distributed server because of ghost cells.
It is caused by the fact the the geometry representation (through vtkSIProxy code) is requesting ghost cells that the table source cannot provide.
Steps to reproduce:
- run distributed pvserver
- run paraview, connect to distributed pvserver
- Tools -> TimerLog
- open [a.csv](/uploads/604f1556e9ab9773f62b5abbfda84ca5/a.csv), Apply
- Refresh TimerLog, see the the `Execute a.csv` line.
- TableToPoints, apply
- Refresh TimerLog, see the the `Execute a.csv` line a second time in server 0, this is a bugMathieu Westphal (Kitware)Mathieu Westphal (Kitware)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/22291IOSS writer doesn't write time data.2023-09-14T15:55:33-04:00W. Alan ScottIOSS writer doesn't write time data.The IOSS writer is no longer writing time data. Here is how to replicate.
* Master (v5.11.1-1679-g a2b48e7dbb), builtin server, Linux.
* Read can.exo. Apply.
* File/ Write Data/ IOSS writer. canOutput.exo. Apply.
* Read in canOutput...The IOSS writer is no longer writing time data. Here is how to replicate.
* Master (v5.11.1-1679-g a2b48e7dbb), builtin server, Linux.
* Read can.exo. Apply.
* File/ Write Data/ IOSS writer. canOutput.exo. Apply.
* Read in canOutput.exo. Apply.
* Play.
The new dataset does not offset correctly. This is a bug.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://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 Tsalikis