ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-01-03T12:08:13-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21367Move Python quick start tutorials to ReadTheDocs2023-01-03T12:08:13-05:00W. Alan ScottMove Python quick start tutorials to ReadTheDocsI am breaking out this bullet from #20118, as we are not sure how to proceed. We will start a discussion on Discourse. When ready, please move the ParaView Python Quick Start Docuentation to ReadTheDocs.
ParaView Python Documentation ...I am breaking out this bullet from #20118, as we are not sure how to proceed. We will start a discussion on Discourse. When ready, please move the ParaView Python Quick Start Docuentation to ReadTheDocs.
ParaView Python Documentation (generated through ParaView): https://kitware.github.io/paraview-docs/nightly/python/quick-start.html
Discourse Post: https://discourse.paraview.org/t/paraview-python-documentation-future-updates/9490https://gitlab.kitware.com/paraview/paraview/-/issues/21361paraview-config issue with CMake v3.232023-08-16T18:28:30-04:00Miren Radiaparaview-config issue with CMake v3.23When I build ParaView (either straight from this repository or using the superbuild) using CMake v3.23, the created `paraview-config` script seems to fail with errors although the configuration and build completes with no issues.
For ex...When I build ParaView (either straight from this repository or using the superbuild) using CMake v3.23, the created `paraview-config` script seems to fail with errors although the configuration and build completes with no issues.
For example, [here](https://github.com/mirenradia/paraview-build/blob/dbe89812092512388c31ac7b3cbd4fcbe3571533/.github/workflows/build-and-release.yml) are the steps I used with the superbuild for a GitHub action on the Ubuntu 20.04 GitHub runner (which used CMake v3.23.0 at the time of the run). The relevant CMake options are:
```
-GNinja \
-DPARAVIEW_BUILD_EDITION=CATALYST_RENDERING \
-DENABLE_osmesa=ON \
-DUSE_SYSTEM_osmesa=ON \
-DENABLE_python3=ON \
-DUSE_SYSTEM_python3=ON \
-DENABLE_mpi=ON \
-DUSE_SYSTEM_mpi=ON \
-DENABLE_llvm=ON \
-DUSE_SYSTEM_llvm=ON \
-Dparaview_SOURCE_SELECTION=5.10.1 \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
```
and the error messages I got from the command (in this [run](https://github.com/mirenradia/paraview-build/runs/6021335870))
```
./paraview-config --cppflags -c PythonCatalyst
```
are
```
CMake Error at /home/runner/work/paraview-build/paraview-build/build/install/lib/cmake/paraview-5.10/vtk/VTK-targets.cmake:485 (set_target_properties):
The link interface of target "VTK::mpi" contains:
MPI::MPI_C
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
/home/runner/work/paraview-build/paraview-build/build/install/lib/cmake/paraview-5.10/vtk/vtk-config.cmake:138 (include)
/home/runner/work/paraview-build/paraview-build/build/install/lib/cmake/paraview-5.10/paraview-config.cmake:66 (find_package)
CMakeLists.txt:5 (find_package)
CMake Error at /home/runner/work/paraview-build/paraview-build/build/install/lib/cmake/paraview-5.10/vtk/VTK-targets.cmake:583 (set_target_properties):
The link interface of target "VTK::opengl" contains:
OSMesa::OSMesa
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
/home/runner/work/paraview-build/paraview-build/build/install/lib/cmake/paraview-5.10/vtk/vtk-config.cmake:138 (include)
/home/runner/work/paraview-build/paraview-build/build/install/lib/cmake/paraview-5.10/paraview-config.cmake:66 (find_package)
CMakeLists.txt:5 (find_package)
CMake Generate step failed. Build files cannot be regenerated correctly.
Traceback (most recent call last):
File "./paraview-config", line 267, in <module>
extract_paraview_flags(opts.components, cmake=opts.cmake,
File "./paraview-config", line 165, in extract_paraview_flags
subprocess.check_call(configure_cmd, cwd=builddir,
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '-GUnix Makefiles', '/tmp/tmptlbajkm6/src', '-DCMAKE_PREFIX_PATH:STRING=/home/runner/work/paraview-build/paraview-build/build/install']' returned non-zero exit status 1.
```
Manually installing CMake v3.21.6 (like [this](https://github.com/mirenradia/paraview-build/blob/4cf8d70822b072442b4ab70e4b88b5eb4f983b3f/.github/workflows/build-and-release.yml#L22-L24)) resolves the issue (see [this run](https://github.com/mirenradia/paraview-build/actions/runs/2168383629)).
I have also been able to reproduce this from a normal (i.e. non-superbuild) build on a SLES 12 system (with relevant packages built by Spack) and CMake v3.23.0 with the following build options
```
-GNinja \
-DPARAVIEW_BUILD_EDITION=CATALYST_RENDERING \
-DVTK_USE_X=OFF \
-DVTK_OPENGL_HAS_OSMESA=ON \
-DPARAVIEW_USE_PYTHON=ON \
-DPARAVIEW_USE_MPI=ON \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DVTK_SMP_IMPLEMENTATION_TYPE=OpenMP
```
Have I missed something obvious or has something in CMake v3.23 broken this script?Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/21359Fonts don't scale in split view screenshots saved using Macro2023-03-17T09:46:10-04:00Maxwell JacksonFonts don't scale in split view screenshots saved using MacroFontScaling=‘Scale fonts proportionally’ in SaveScreenshot function does not work in split views, but only when screenshot is saved from a macro script. The color bar labels and title comes out very large. Tested in 5.10.1 on MacOS.
To ...FontScaling=‘Scale fonts proportionally’ in SaveScreenshot function does not work in split views, but only when screenshot is saved from a macro script. The color bar labels and title comes out very large. Tested in 5.10.1 on MacOS.
To reproduce:
1. Use wavelet, add contour
2. Split the view horizontally (both render views), check eyeball on for wavelet and contour
3. Link cameras
4. Start Trace (default settings) and change to a smaller layout size (Lock View Size Custom in Tools, make sure to press Apply) and save a screenshot
5. Stop Trace and save trace as macro
6. Reset Session
7. Redo Steps 1-3
8. Run macro and compare screenshots
Image from Manual Screenshot
![6febdf1387963ff02011390e21522bf81b8a6009](/uploads/ccf8e11ffe9b435d592a80317d13f7ac/6febdf1387963ff02011390e21522bf81b8a6009.png)
Image from Macro Screenshot
![c85061c03846b48773d186c5bd052f7ffab44ccf](/uploads/46c2f38b693fcb0ad75241248068fa44/c85061c03846b48773d186c5bd052f7ffab44ccf.png)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21358Volume rendering of multiblock of images does not work2024-03-07T20:23:50-05:00Utkarsh AyachitVolume rendering of multiblock of images does not work* Wavelet, set Z extents to -10, 0, Apply
* Wavelet, set Z extents to 0, 10, Apply
* Select both and add "Group DataSets" filter. Apply. Color by "RTData"
* Switch representation to "Volume", nothing renders and you get errors like the f...* Wavelet, set Z extents to -10, 0, Apply
* Wavelet, set Z extents to 0, 10, Apply
* Select both and add "Group DataSets" filter. Apply. Color by "RTData"
* Switch representation to "Volume", nothing renders and you get errors like the following:
```
( 217.667s) [paraview ]vtkCompositeDataPipelin:155 ERR| vtkPVDataRepresentationPipeline (0x1fe0e310): Can not execute simple algorithm vtkImageVolumeRepresentation without output ports
```
We support volume rendering of composite datasets for unstructured grid, why not for image datasets?5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21355PIO reader parallel performance Space and Time2024-03-07T20:23:50-05:00John PatchettPIO reader parallel performance Space and TimeThe PIO reader currently reads an entire scalar field on process zero then redistributes that across the ranks. This is slow and causes a bad malloc on large datasets. The reader needs to have multiple ranks simultaneously perform partia...The PIO reader currently reads an entire scalar field on process zero then redistributes that across the ranks. This is slow and causes a bad malloc on large datasets. The reader needs to have multiple ranks simultaneously perform partial reads and appropriately distribute the read fraction.5.13 (Summer 2024)Patricia FaselPatricia Fasel2022-08-31https://gitlab.kitware.com/paraview/paraview/-/issues/21353OSPRay rendering artifacts for volumes in parallel2023-02-24T04:13:40-05:00Miren RadiaOSPRay rendering artifacts for volumes in parallelThere seem to be artifacts between process boundaries when using ray-traced volume rendering with OSPRay in parallel. Here are some steps to reproduce (with v5.10.1):
1. Launch a ParaView Server with multiple MPI ranks (I used 32) and co...There seem to be artifacts between process boundaries when using ray-traced volume rendering with OSPRay in parallel. Here are some steps to reproduce (with v5.10.1):
1. Launch a ParaView Server with multiple MPI ranks (I used 32) and connect a ParaView client to it.
2. Create a 'Fast Uniform Grid' source.
3. Change the representation to 'Volume'.
4. Enable Ray Tracing and set the Back End to 'OSPRay raycaster'
Here's a screenshot of the result (with v5.10.1):
![ospray_parallel_artifacts_v5.10.1](/uploads/9260d06f1e177d1aa8cc5d9634474173/ospray_parallel_artifacts_v5.10.1.png)
I don't get these artifacts without ray tracing and am able to reproduce them with v5.6.0, v5.8.1 and v5.10.1. Changing the OSPRay parameters such as 'Ambient Samples' or 'Samples Per Pixel' doesn't seem to fix this problem.
@demarle has also reproduced this issue with all versions from v5.4 to v5.10.https://gitlab.kitware.com/paraview/paraview/-/issues/21350Reading ensight binary files with few points2022-04-11T04:10:05-04:00Jay PBReading ensight binary files with few pointsAttached, you find a simple program, which is a very strong simplification of how we write out the results of our research code (written in Fortran) as Ensight 6 binary files.
With this simplified code (and our full code) we observe, th...Attached, you find a simple program, which is a very strong simplification of how we write out the results of our research code (written in Fortran) as Ensight 6 binary files.
With this simplified code (and our full code) we observe, that Paraview is unable to read case files whenever the number of points is small. For example, in the attached program, if nb_points = 1 is set, Paraview will not be able to load the case file, while there is no error message when setting nb_points = 100. In both cases the ens_checker utility returns with a successful verification. Thus, the error doesn't seem to be in the Ensight files themselves, but rather in the reader used by Paraview.
* Reading the created Ensight files into Paraview has been tested with ParaView versions 5.9.1 and 5.10.1, but this problem has been known in our group for quite a while. So it should not be limited to recent versions.
* The Fortran test code has been compiled with Intel oneapi_2021.4.0.3422, but the same has occured in the past with older Intel Fortran compilers.
* The error message shown is:
[paraview ]vtkEnSight6BinaryReader:2831 ERR| vtkEnSight6BinaryReader (0x1d3b7f70): Read failed.
[main.f90](/uploads/e98e370178f25037b5289a3f99cc2a92/main.f90)https://gitlab.kitware.com/paraview/paraview/-/issues/21341Paraview 5.10.0 crashes while opening Fluent file2022-04-06T05:40:07-04:00Miguel AguirreParaview 5.10.0 crashes while opening Fluent fileHello,
I’m trying to open **Fluent **files on **ParaView 5.10.0** but it always crashes when I click on “Apply” button. In older versions (**5.5** and **5.7**) in opens the file without problems. The issue is related to the variable nam...Hello,
I’m trying to open **Fluent **files on **ParaView 5.10.0** but it always crashes when I click on “Apply” button. In older versions (**5.5** and **5.7**) in opens the file without problems. The issue is related to the variable name "SV_DPM_PARTITION" that do not exist in vtkFluentReader. In older ParaView versions this was not an issue but in the latest version it directly crashes while loading the data file (Just for info: the ".cas" file is correctly read).
There is a workaround to solve this problem (by deleting this variable from the native Fluent data) file but this approach is not possible for large 3D data (See the following link for details: https://discourse.paraview.org/t/paraview-5-10-0-crashes-while-open-fluent-file/9267/2).
Please, find in the attached file a simple test case to reproduce the error.
Thanks in advance
Miguel AGUIRRE
[PV_ERROR_TEST.cas](/uploads/d8ac9c8aad2325d6e7598e9e5f9c9023/PV_ERROR_TEST.cas)
[PV_ERROR_TEST.dat](/uploads/65728db34d42dab547d8a1bacf682342/PV_ERROR_TEST.dat)https://gitlab.kitware.com/paraview/paraview/-/issues/21337pvserver segmentation fault when reading AMReX input files2022-04-05T04:52:18-04:00Ben Wibkingpvserver segmentation fault when reading AMReX input filesI get a segmentation fault on the server end when reading in my simulation files (AMReX grid format). Both client and server are running Paraview 5.10.1. This can be reproduced with these input files: https://cloudstor.aarnet.edu.au/plus...I get a segmentation fault on the server end when reading in my simulation files (AMReX grid format). Both client and server are running Paraview 5.10.1. This can be reproduced with these input files: https://cloudstor.aarnet.edu.au/plus/s/pM333ijq9pr1QMQ
```
$ pvserver
Waiting for client...
Connection URL: cs://gadi-cpu-clx-2631.gadi.nci.org.au:11111
Accepting connection(s): gadi-cpu-clx-2631.gadi.nci.org.au:11111
Client connected.
Loguru caught a signal: SIGSEGV
Stack trace:
33 0x40190e pvserver() [0x40190e]
32 0x1503d9da3493 __libc_start_main + 243
31 0x40181b pvserver() [0x40181b]
30 0x1503d795f3a2 vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) + 658
29 0x1503d685f911 vtkMultiProcessController::ProcessRMIs(int, int) + 705
28 0x1503d685f138 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 312
27 0x1503d8130236 vtkPVSessionServer::OnClientServerMessageRMI(void*, int) + 278
26 0x1503d8127f85 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
25 0x1503d8128e9b vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
24 0x1503d8129062 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
23 0x1503d746ecdd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
22 0x1503d746ec1e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1054
21 0x1503d746e7ad vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1101
20 0x1503d746e1f9 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 473
19 0x1503d8ab8faf vtkSIMetaReaderProxyCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 335
18 0x1503d746e1f9 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 473
17 0x1503d8abe773 vtkSISourceProxyCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 2179
16 0x1503d815bb0c vtkSISourceProxy::UpdatePipeline(int, double, bool) + 460
15 0x1503d63d0b5a vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 282
14 0x1503d6394af6 vtkDemandDrivenPipeline::UpdateData(int) + 134
13 0x1503d63cf87d vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 813
12 0x1503d6395b7c vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 284
11 0x1503d638ee0a vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 330
10 0x1503d63cf87d vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 813
9 0x1503d6395f73 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1299
8 0x1503d638ffa1 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 113
7 0x1503d6393547 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 55
6 0x1503d639906e vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 62
5 0x1503d0a30b71 vtkFileSeriesReader::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 433
4 0x1503d0a3092b vtkFileSeriesReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 107
3 0x1503c62624f1 vtkAMRBaseReader::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 273
2 0x1503c25acce8 vtkParallelAMRUtilities::BlankCells(vtkOverlappingAMR*, vtkMultiProcessController*) + 56
1 0x1503d604c540 vtkAMRInformation::HasRefinementRatio() + 0
0 0x1503d9db7400 /lib64/libc.so.6(+0x37400) [0x1503d9db7400]
( 44.667s) [pvserver ] :0 FATL| Signal: SIGSEGV
Segmentation fault
```https://gitlab.kitware.com/paraview/paraview/-/issues/21335Visual bug for Image data with hidden cell2022-04-01T15:36:46-04:00Yohann Bearzi (Kitware)Visual bug for Image data with hidden cell![image_data_hidden](/uploads/bf7a602b3aaf7c38e9b88d8a04efba86/image_data_hidden.png)
To reproduce:
* Open disk_out_ref.ex2
* ResampleToImage (resolution set to 50x50x50)
Faces orthogonal with the Y axis are not shown.![image_data_hidden](/uploads/bf7a602b3aaf7c38e9b88d8a04efba86/image_data_hidden.png)
To reproduce:
* Open disk_out_ref.ex2
* ResampleToImage (resolution set to 50x50x50)
Faces orthogonal with the Y axis are not shown.https://gitlab.kitware.com/paraview/paraview/-/issues/21332interactive clip plane widget is always hide when hide properties panel2022-03-26T04:55:29-04:00Jeff0821interactive clip plane widget is always hide when hide properties panelI found when I close properties panel, the interactive clip plane widget will hide, even through I checked the "show plane" checkbox.
What i expected is just hide properties plane, but interactive plane widget is visible when i check th...I found when I close properties panel, the interactive clip plane widget will hide, even through I checked the "show plane" checkbox.
What i expected is just hide properties plane, but interactive plane widget is visible when i check the "Show Plane" checkbox.https://gitlab.kitware.com/paraview/paraview/-/issues/21331Hyper Tree Grid Cell Centers: Invalid cells lead to segfault2022-05-10T09:59:16-04:00Charles GueunetHyper Tree Grid Cell Centers: Invalid cells lead to segfault## Step to reproduce
1. Hyper Tree Grid (Random)
* Apply
2. Hyper Tree Grid - Cell Centers
* Apply
3. Display Properties:
* Point Gaussian representation
The third step can be replaced by a Glyph filter for examples.
This m...## Step to reproduce
1. Hyper Tree Grid (Random)
* Apply
2. Hyper Tree Grid - Cell Centers
* Apply
3. Display Properties:
* Point Gaussian representation
The third step can be replaced by a Glyph filter for examples.
This may be related to the data statistics: `# of Cells 0`
## Fix ?
We may want to add the cell array to the output polygonal mesh. Applying a `Convert To Point Cloud` currently solve the issue.
@mwestphal FYIhttps://gitlab.kitware.com/paraview/paraview/-/issues/21329AMReX grid data set shows artifacts when rendered as volume2022-06-22T22:42:13-04:00Erik PalmerAMReX grid data set shows artifacts when rendered as volumeWhen viewing the attached AMReX plotfile, slices of the volume are missing from the rendered image. Moreover, when representation->surface is selected, the missing data appear correctly. The issue exists in versions, 5.9.1, 5.10.0, and 5...When viewing the attached AMReX plotfile, slices of the volume are missing from the rendered image. Moreover, when representation->surface is selected, the missing data appear correctly. The issue exists in versions, 5.9.1, 5.10.0, and 5.10.1. I have not tested other versions.
Steps to recreate:
- start Paraview
- open the folder plt00007 with AMReX/Boxlib Grid Reader
- click the tracer box, press apply
- select representation: Volume
My system:
Paraview 5.10.1 on Ubuntu 21.1 Linux 5.13.0-37
Attached is a side-by-side of screenshots showing the different renders of volume and surface, the plotfile data, and a picture showing how the volume should look (although from a different angle)
![pv_output](/uploads/79c37d06ec7c03f0b8d1de8109386b02/pv_output.png)
![volume](/uploads/b709b5c6b4a86d398422cce95fca89b6/volume.png)
[plt00007.tar.gz](/uploads/566256a7718084756c0db5bf1331da8e/plt00007.tar.gz)
Thanks for any advice!
Erikhttps://gitlab.kitware.com/paraview/paraview/-/issues/21328Is Paraview relocatable?2024-03-07T20:23:50-05:00autoantwortIs Paraview relocatable?For vcpkg packages must be relocatable because of binary caching. One future post build check checks if there are absolute paths in the build results. The check have found the following occurrences:
`paraview-5.9/vtkCPConfig.h`:
```c...For vcpkg packages must be relocatable because of binary caching. One future post build check checks if there are absolute paths in the build results. The check have found the following occurrences:
`paraview-5.9/vtkCPConfig.h`:
```c++
#ifndef vtkCPPythonScriptPipelineConfig_h
#define vtkCPPythonScriptPipelineConfig_h
// These variables are used to locate the python module files since we cannot
// reply on the executable path to locate python module files.
#define PARAVIEW_BINARY_DIR "/Users/leanderSchulten/git_projekte/Lichtsteuerung/vcpkg/buildtrees/paraview/arm64-osx-rel"
#define PARAVIEW_INSTALL_DIR "/Users/leanderSchulten/git_projekte/Lichtsteuerung/vcpkg/packages/paraview_arm64-osx"
#endif
```
It seems that only `PARAVIEW_BINARY_DIR` is used in the code.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21327Extract AMR Blocks filter does not work2022-03-25T10:16:08-04:00Miren RadiaExtract AMR Blocks filter does not workSince ParaView v5.10.0 onwards, I've been unable to use the "Extract AMR Blocks" filter as I did in earlier versions.
Here are some steps to reproduce
1. Create an "AMR GaussianPulse Source".
2. Apply the "Extract AMR Blocks" filter and...Since ParaView v5.10.0 onwards, I've been unable to use the "Extract AMR Blocks" filter as I did in earlier versions.
Here are some steps to reproduce
1. Create an "AMR GaussianPulse Source".
2. Apply the "Extract AMR Blocks" filter and add some level and dataset index pairs (e.g. "(0,0)").
After doing this, there doesn't seem to be any output from this filter. It's possible I'm not setting these pairs correctly but then I would argue that this interface is far less intuitive than v5.9.1 and earlier which offered a list of datasets on each level and allowed you to select/deselect them with checkboxes. I think there should at least be an easy way to access a list of possible pairs.
I've tested this on Linux with prebuilt versions v5.10.1 and v5.8.1, as well as my own builds of v5.10.0 and v5.9.1.https://gitlab.kitware.com/paraview/paraview/-/issues/21324Add an example plugin showing how to add a new interactive widget in ParaView2022-03-23T04:29:39-04:00Mathieu Westphal (Kitware)Add an example plugin showing how to add a new interactive widget in ParaViewAdd an example plugin showing how to add a new interactive widget in ParaView.
Similar to the PropertyWidget example plugin but adding a interactive 3D (or even 2D) widget in ParaView.
FYI @timothee.chabatAdd an example plugin showing how to add a new interactive widget in ParaView.
Similar to the PropertyWidget example plugin but adding a interactive 3D (or even 2D) widget in ParaView.
FYI @timothee.chabathttps://gitlab.kitware.com/paraview/paraview/-/issues/21322PIO reader: support DUMP_FILE keyword2024-03-07T20:23:49-05:00Cory Quammencory.quammen@kitware.comPIO reader: support DUMP_FILE keyword5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21321Reflect filter on triangle strips produce ill-formed cells2022-03-22T09:11:17-04:00Thomas GallandReflect filter on triangle strips produce ill-formed cellsSteps to reproduce :
- Superquadric, apply
- Reflect Filter, apply \
![strips1](/uploads/1ca6fc9d6d1d2c5a6037205265315dd3/strips1.png)
![strips2](/uploads/e75854f2445453e15a3e42ed04ff45ed/strips2.png)
\
Remarks :
- The result is good if...Steps to reproduce :
- Superquadric, apply
- Reflect Filter, apply \
![strips1](/uploads/1ca6fc9d6d1d2c5a6037205265315dd3/strips1.png)
![strips2](/uploads/e75854f2445453e15a3e42ed04ff45ed/strips2.png)
\
Remarks :
- The result is good if the `Copy Input` property is disabled.
- Seems to be a problem with triangle strips onlyhttps://gitlab.kitware.com/paraview/paraview/-/issues/21320Python trace generation on load state with arguments is failing2023-01-05T08:19:08-05:00laurent90gitPython trace generation on load state with arguments is failingParaView fails to generate a correct trace with Loading a state with arguments.
Steps to reproduce:
- Open ParaView
- Open any file, apply
- File -> Save State
- Reset Session
- Tools -> StartTrace
- File -> Loade State -> Search...ParaView fails to generate a correct trace with Loading a state with arguments.
Steps to reproduce:
- Open ParaView
- Open any file, apply
- File -> Save State
- Reset Session
- Tools -> StartTrace
- File -> Loade State -> Search files under specified dir
- Tools -> StopTrace
- Trace is empty and error is shown:
```
Traceback (most recent call last):
File "/home/glow/work/paraview/others/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/lib/python3.9/site-packages/paraview/smtrace.py", line 1811, in _stop_trace_internal
trace = str(Trace.Output)
File "/home/glow/work/paraview/others/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/lib/python3.9/site-packages/paraview/smtrace.py", line 116, in __str__
return '\n'.join(self.__data)
TypeError: sequence item 17: expected str instance, bool found
```
Trace should have been:
```
LoadState("path/to/state/file", "path/to/dir", True)
```
Note: Save state is not traced at all.https://gitlab.kitware.com/paraview/paraview/-/issues/21318Newer ParaView Exodus Reader Fails on exodus file read2024-03-07T20:23:49-05:00John PatchettNewer ParaView Exodus Reader Fails on exodus file readThis exodus file example fails on read in ParaView 5.10.0 and 5.10.1
[mixed_element_mesh.exo](/uploads/3d24cc1db2a734c9fd83f0216a62d8e3/mixed_element_mesh.exo)
with the error from 5.10.1:
```
ERROR: In /opt/glr/paraview/paraview-ci/build...This exodus file example fails on read in ParaView 5.10.0 and 5.10.1
[mixed_element_mesh.exo](/uploads/3d24cc1db2a734c9fd83f0216a62d8e3/mixed_element_mesh.exo)
with the error from 5.10.1:
```
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/VTK/IO/IOSS/vtkIOSSReader.cxx, line 852
vtkIOSSReader (0x7fae24fc4c30): Error in UpdateTimeInformation:
ERROR: The topology type 'nsided66283' is not supported on 'faceblock_1' in file '/Users/patchett/Downloads/mixed_element_mesh.exo'
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 753
vtkPVCompositeDataPipeline (0x6000025c5420): Algorithm vtkIOSSReader(0x7fae24fc4c30) returned failure for request: vtkInformation (0x6000005c4bc0)
Debug: Off
Modified Time: 300472
Reference Count: 1
Registered Events: (none)
Request: REQUEST_INFORMATION
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```
It loads with defaults fine on 5.6.1 and 5.9.1 (on mac).
@wascott @berkgeveci5.13 (Summer 2024)