ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:47:06-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/18965Reset session in trace, when run batch, appears bad2024-03-07T20:47:06-05:00W. Alan ScottReset session in trace, when run batch, appears badHere's a weird one. We have a trace, and when we run it in Paraview (View/ Python View/ Run Script), all is well. When we run it in batch mode, it dies. I will attached a sanitized version. You will need to add correct directories in...Here's a weird one. We have a trace, and when we run it in Paraview (View/ Python View/ Run Script), all is well. When we run it in batch mode, it dies. I will attached a sanitized version. You will need to add correct directories in the script. Search for "edit".
* 5.6.0, Linux, builtin server AND 5.6.0, Linux, pvbatch.
* Run the script. It will die in batch mode with the following error. This happens AFTER the Reset Session, where it runs the same code again.
Note that I can't test master, since #18964 and #18963 are possibly hiding this one.
Traceback (most recent call last):
File "/ snip /camera-C-composite-batch.py", line 444, in <module>
layout1.SplitHorizontal(0, 0.5)
AttributeError: 'NoneType' object has no attribute 'SplitHorizontal'
This is a showstopper for the 5.7 release. We need to run pvbatch in a for loop dozens of times. (Note update comment below.)
[camera-C-composite-batch.py](/uploads/39624067c3b263190a4b3c207d6941f1/camera-C-composite-batch.py)
@cory.quammen @utkarsh.ayachit5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18919Add ability to label contour surfaces and lines2024-03-07T20:47:06-05:00W. Alan ScottAdd ability to label contour surfaces and linesPlease add the ability to label contours.
This is evidentally already in VTK, as per https://vtk.org/Wiki/VTK/Examples/Cxx/Visualization/LabelContours.
It is a very popular uservoice request: https://paraview.uservoice.com/forums/1...Please add the ability to label contours.
This is evidentally already in VTK, as per https://vtk.org/Wiki/VTK/Examples/Cxx/Visualization/LabelContours.
It is a very popular uservoice request: https://paraview.uservoice.com/forums/11350-general/suggestions/1350851-create-the-ability-to-automatically-label-contour
An example of what is requested is on discource, here: https://discourse.paraview.org/t/is-it-possible-to-add-labels-to-contour-lines/1466
This bug is not the same as, but a sibling of https://gitlab.kitware.com/paraview/paraview/issues/15810.
It is fine to push this to 5.9, spring 2020.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18901Buildbot Path Information Carried to Deployed Executable2024-03-07T20:47:06-05:00Joel A. KuleszaBuildbot Path Information Carried to Deployed ExecutableThis is a minor bug in the build/deployment process.
I'm attempting to drive ParaView batch processing of XDMF files. One of the `Attribute`s were assigned an invalid type. Using the ParaView GUI is silent on this. However, via `pvba...This is a minor bug in the build/deployment process.
I'm attempting to drive ParaView batch processing of XDMF files. One of the `Attribute`s were assigned an invalid type. Using the ParaView GUI is silent on this. However, via `pvbatch` this error is exposed with many lines of
```
> /local/ParaView-5.6.0.app/Contents/bin/pvbatch test.py
XDMF Error in /Users/kitware/dashboards/buildbot-slave/8275bd07/build/superbuild/paraview/src/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfAttribute.cxx line 183 (Unknown Attribute Type None)
.
.
.
XDMF Error in /Users/kitware/dashboards/buildbot-slave/8275bd07/build/superbuild/paraview/src/VTK/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfAttribute.cxx line 183 (Unknown Attribute Type None)
```
where the fully resolved path clearly refers to the Kitware build versus anything on my machine. Can this confounding information be removed?
CC: @patchett2002 @ethan.stam
@ethan.stam Also, I resolved the downstream issue from this for the case we spoke about, so there shouldn't be any need for you to track this down further. However, thanks for you willingness to do this!5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18899Rename "Point Gaussian" representation to something more accurate2024-03-07T20:47:06-05:00Cory Quammencory.quammen@kitware.comRename "Point Gaussian" representation to something more accurateThe Point Gaussian representation offers a Gaussian splat as just one type of point sprite to render, but it is much more versatile than that. Rename it to something more appropriate.
Suggestions:
* Point Sprite
* Point GlyphThe Point Gaussian representation offers a Gaussian splat as just one type of point sprite to render, but it is much more versatile than that. Rename it to something more appropriate.
Suggestions:
* Point Sprite
* Point Glyph5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18897Lagrange hexahedron Gradient and Vorticity fails2024-03-07T20:47:06-05:00vrkssaiLagrange hexahedron Gradient and Vorticity failsIn regard to the below discourse post:
https://discourse.paraview.org/t/vorticity-and-gradient-calculation-numerics-gives-wrong-result/1514?u=vrkssai
The filter "Gradient of Unstructured data" and Vorticity Calculation using python calc...In regard to the below discourse post:
https://discourse.paraview.org/t/vorticity-and-gradient-calculation-numerics-gives-wrong-result/1514?u=vrkssai
The filter "Gradient of Unstructured data" and Vorticity Calculation using python calculator for Lagrange Hexahedron Grids give erroneous results. I have laid down the steps to reproduce it in the post.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18871Add Apply to All Variables to Choose Preset2024-03-07T20:47:06-05:00W. Alan ScottAdd Apply to All Variables to Choose PresetPlease add another button to the Choose Preset dialog. Make this button be Apply to All Vars. Alternatively, add a checkbox in the Actions on selected, saying Apply to all vars.Please add another button to the Choose Preset dialog. Make this button be Apply to All Vars. Alternatively, add a checkbox in the Actions on selected, saying Apply to all vars.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18834Extract block should output a single grid for one block2024-03-07T20:47:06-05:00W. Alan ScottExtract block should output a single grid for one blockPlease add the option, default on, to always output a single grid block if only one block is selected for the Extract Block filter.Please add the option, default on, to always output a single grid block if only one block is selected for the Extract Block filter.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18833Ability to color histogram by X or Y axis2024-03-07T20:47:06-05:00W. Alan ScottAbility to color histogram by X or Y axisPlease add the ability to color the histogram by either X or Y axis. Allow this to be either categorical colors or by color map. Example would be:
* disk_out_ref.exo. Load all variables. Apply.
* Histogram filter. Color by Temp. ...Please add the ability to color the histogram by either X or Y axis. Allow this to be either categorical colors or by color map. Example would be:
* disk_out_ref.exo. Load all variables. Apply.
* Histogram filter. Color by Temp. Apply.
* Now, I want to change the color going left to right.
* Alternatively, I want to color by magnitude of each of the bins.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18804[Module] External Plugins build architecture is hard to understand2024-03-07T20:47:06-05:00Mathieu Westphal (Kitware)[Module] External Plugins build architecture is hard to understandExternal plugin build architecture are hard to understand in ParaView
How to reproduce :
```
cp -r paraview/Examples/ElevationFilter ~/
cd ~/ElevationFilter
mkdir build
cd build
cmake -DParaView_DIR=/path/to/paraview_build/ -...External plugin build architecture are hard to understand in ParaView
How to reproduce :
```
cp -r paraview/Examples/ElevationFilter ~/
cd ~/ElevationFilter
mkdir build
cd build
cmake -DParaView_DIR=/path/to/paraview_build/ -DBUILD_SHARED_LIBS=ON ../
make
```
Note: without BUILD_SHARED_LIBS, only static libs are generated, that should not be the case for an example plugin.
It then contains two .so file
`~/ElevationFilter/build/lib64/libElevationFilters.so`
and
`~/ElevationFilter/build/lib64/paraview/plugins/ElevationFilters.so`
The second one is the one that can be loaded. Not easy to understand. This should be improved.
@ben.boeckel @utkarsh.ayachit5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18795Descriptive Statistics needs cleanup2024-03-07T20:47:05-05:00W. Alan ScottDescriptive Statistics needs cleanupPlease clean up the Descriptive Statistics filter.
Example run:
* 5.6.0, Linux, remote server (NOT builtin server).
* Load g1s1-10fps.e.16.[0-15]. All variables on. Apply.
* Filters/ Descriptive Statistics.
So, what I expect to see ...Please clean up the Descriptive Statistics filter.
Example run:
* 5.6.0, Linux, remote server (NOT builtin server).
* Load g1s1-10fps.e.16.[0-15]. All variables on. Apply.
* Filters/ Descriptive Statistics.
So, what I expect to see is statistics (mean, median, max, min, possibly standard deviation) for each variable. So, here are modifications I want to see:
* We want to see statistics over the whole DATASET, NOT each core or processor. (OK, if necessary, statistics per block is acceptable.) Users want to know about their dataset, not how the cluster partitioned their data!
* Please add in, and optionally calculate magnitudes of vectors, default on. Optionally present the coordinates of vectors (such as Displacement), default off.
* Please make M2, M3 and M4 an advanced output. In other words, standard deviation, skewness and kertosus should be advanced outputs.
* Add a one sentence explination for each of M2, M3 and M4. I believe M2 is standard deviation, M3 is skewness and M4 is kertosus. https://www.paraview.org/Wiki/Statistical_analysis#Descriptive_Statistics.
* Reorder the columns to be Block number, Row number, Variable name, Max, Min, Mean, Median, Standard Deviation, etc.
* This filter needs to work correctly in parallel, taking into account processor boundaries. We don't want to double count the same points.
Don't forget that this filter will be used by statiticians that understand this stuff, but also by engineers, scientists and students that may not know this stuff. Remember a person that took statistics 10 years ago may know what they are looking for, but may not remember the terminology. Further, M2, M3 and M4 are generic enough that they are impossible to google.5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/18762too many update information requests2024-03-07T20:47:05-05:00Utkarsh Ayachittoo many update information requestsAs I am adding logging support to ParaView, simple tasks can cause too many update-pipeline-information requests. While these are often no-ops, they can slow the UI down when in client-server configurations. We should look into it.
Here...As I am adding logging support to ParaView, simple tasks can cause too many update-pipeline-information requests. While these are often no-ops, they can slow the UI down when in client-server configurations. We should look into it.
Here's the log on simply changing the Clip plane and hitting Apply.
```
( 27.035s) [paraview ] vtkSISourceProxy.cxx:229 INFO| { Clip1: update pipeline(0, 0.000000, true)
( 27.036s) [paraview ] vtkSISourceProxy.cxx:308 INFO| . { execute vtkPVMetaClipDataSet id: 6663
( 27.037s) [paraview ] vtkSISourceProxy.cxx:308 INFO| . } 0.001 s: execute vtkPVMetaClipDataSet id: 6663
( 27.037s) [paraview ] vtkSISourceProxy.cxx:229 INFO| } 0.002 s: Clip1: update pipeline(0, 0.000000, true)
( 27.043s) [paraview ] vtkSISourceProxy.cxx:229 INFO| { Clip1: update pipeline(0, 0.000000, true)
( 27.044s) [paraview ] vtkSISourceProxy.cxx:229 INFO| } 0.000 s: Clip1: update pipeline(0, 0.000000, true)
( 27.046s) [paraview ] vtkSISourceProxy.cxx:229 INFO| { Clip1: update pipeline(0, 0.000000, true)
( 27.046s) [paraview ] vtkSISourceProxy.cxx:229 INFO| } 0.000 s: Clip1: update pipeline(0, 0.000000, true)
( 27.443s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkArrowSource id: 6723
( 27.443s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkArrowSource id: 6723
( 27.444s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkConeSource id: 6734
( 27.444s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkConeSource id: 6734
( 27.445s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkCubeSource id: 6745
( 27.445s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkCubeSource id: 6745
( 27.446s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkCylinderSource id: 6756
( 27.446s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkCylinderSource id: 6756
( 27.447s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkLineSource id: 6767
( 27.448s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkLineSource id: 6767
( 27.449s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkSphereSource id: 6778
( 27.449s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkSphereSource id: 6778
( 27.450s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkGlyphSource2D id: 6789
( 27.450s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkGlyphSource2D id: 6789
( 27.451s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkPassThrough id: 6800
( 27.451s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkPassThrough id: 6800
( 27.546s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkPVMetaClipDataSet id: 6663
( 27.546s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkPVMetaClipDataSet id: 6663
( 27.547s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkGeometryRepresentationWithFaces id: 6869
( 27.548s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.001 s: execute vtkGeometryRepresentationWithFaces id: 6869
( 27.549s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkPVExtractSelection id: 6664
( 27.549s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.000 s: execute vtkPVExtractSelection id: 6664
( 113.068s) [paraview ] vtkSISourceProxy.cxx:268 INFO| { update pipeline information vtkPVMetaClipDataSet id: 6663
( 113.068s) [paraview ] vtkSISourceProxy.cxx:268 INFO| } 0.000 s: update pipeline information vtkPVMetaClipDataSet id: 6663
( 113.070s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkPVMetaClipDataSet id: 6663
( 113.071s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.001 s: execute vtkPVMetaClipDataSet id: 6663
( 113.071s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkGeometryRepresentationWithFaces id: 6869
( 113.074s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.002 s: execute vtkGeometryRepresentationWithFaces id: 6869
( 113.075s) [paraview ] vtkSISourceProxy.cxx:308 INFO| { execute vtkPVExtractSelection id: 6664
( 113.075s) [paraview ] vtkSISourceProxy.cxx:308 INFO| } 0.000 s: execute vtkPVExtractSelection id: 6664
```
Notice the 3 UpdatePipeline requests on Clip itself and several update information requests.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18715Annotate Attribute Data does not work with multiblock data2024-03-07T20:47:05-05:00W. Alan ScottAnnotate Attribute Data does not work with multiblock dataThe Annotate Attribute Data filter does not work with multiblock data.
* Linux, 5.6.0, builtin server. (Also, test remote server.)
* can.exo. All vars on. Apply.
* the Filters/ Annotation/ Annotate Attribute Data filter is grayed o...The Annotate Attribute Data filter does not work with multiblock data.
* Linux, 5.6.0, builtin server. (Also, test remote server.)
* can.exo. All vars on. Apply.
* the Filters/ Annotation/ Annotate Attribute Data filter is grayed out. This should be fixed.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18654modernize labels2024-03-07T20:47:05-05:00David E. DeMarlemodernize labelsLabels in ParaView are cumbersome to use, inexact, and slow. End users enable labels on the data within selections and further subsampling occurs behind the scenes to limit the number of labels. Colormaps by contrast are a simple pull do...Labels in ParaView are cumbersome to use, inexact, and slow. End users enable labels on the data within selections and further subsampling occurs behind the scenes to limit the number of labels. Colormaps by contrast are a simple pull down in the active variables toolbar.
We should add a new label interface that starts as a simple "Draw Labels" checkbox in the display tab to make it really easy for the user to add labels to any object in the pipeline. The user should be able to pick from any of the cell or point arrays as they can for colormapping. The use should have some control over the subsampling algorithm that goes on to reduce clutter and overlap. The user should be able to control the font characteristics as well.
Existing capabilities to label selections should remain with an eye toward unifying the UI between old and new style labels.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18653enable different labels in different views2024-03-07T20:47:05-05:00David E. DeMarleenable different labels in different viewsUsers want the ability to label different objects in different views. You can not in ParaView currently because labels are tied to the active selection and the active selection is tied to one particular item in the pipeline browser. We s...Users want the ability to label different objects in different views. You can not in ParaView currently because labels are tied to the active selection and the active selection is tied to one particular item in the pipeline browser. We should break the dependence of labels on the selection to allow this and other use cases.
To demonstrate: open the example visualization with two clips on can.ex2. Split the view, link the cameras and show both clips in both views. Make a selection inside one clip in one view and turn on labels via the Selection Display Inspector. You can label the same selection by a different array in the other view. However you can not make a selection on the other clip to label those nodes/elements without destroying the first selection and its labels.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18651color legend size changes for screenshots with different size2024-03-07T20:47:05-05:00W. Alan Scottcolor legend size changes for screenshots with different sizeWhen saving screenshots that are a different size than the Viewport, the Color Legend is strangely larger. Here is how to replicate:
* ParaView 5.6.0, builtin server, Linux.
* Sources/ Wavelet. Apply. Surface. RTData.
* Save Screensh...When saving screenshots that are a different size than the Viewport, the Color Legend is strangely larger. Here is how to replicate:
* ParaView 5.6.0, builtin server, Linux.
* Sources/ Wavelet. Apply. Surface. RTData.
* Save Screenshot. I locked the X and Y, then added say 10% or 20% to the size. Save.
Now, compare this to the original. The Color Legend is a lot wider, and the characters are also disproportionately large.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18589Replace unsafe C string functions.2024-03-07T20:47:05-05:00W. Alan ScottReplace unsafe C string functions.Please replace strcpy, sprintf, gets and other "unsafe" C string functions with safer alternatives.
Good website on best practices: https://security.web.cern.ch/security/recommendations/en/codetools/c.shtml
Good website on how buffer...Please replace strcpy, sprintf, gets and other "unsafe" C string functions with safer alternatives.
Good website on best practices: https://security.web.cern.ch/security/recommendations/en/codetools/c.shtml
Good website on how buffer overflow exploits work: http://www.cse.scu.edu/~tschwarz/coen152_05/Lectures/BufferOverflow.html
This is a large enough task that I marked it as Spring 2019, with the expectation it will delay until Fall 2019. I want to get ahead of the game before we have a fire drill.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/18569It is confusing to have so many "clean" filters2024-03-07T20:47:04-05:00Kenneth MorelandIt is confusing to have so many "clean" filtersParaView currently has three versions of "clean":
* `Clean`
* `Clean to Grid`
* `Clean Cells to Grid`
Although all three do something similar, it is almost always the case that there is a specific one you want, and it is impossib...ParaView currently has three versions of "clean":
* `Clean`
* `Clean to Grid`
* `Clean Cells to Grid`
Although all three do something similar, it is almost always the case that there is a specific one you want, and it is impossible to figure out which one is correct. I recommend the following name changes:
* `Clean` --> `Clean Poly Data`
* `Clean to Grid` --> `Clean to Unstructured Grid`
* `Clean Cells to Grid` --> `Remove Degenerate Cells`
Frankly, it would be nice to remove the `Clean Cells to Grid` altogether and simply make it an option of the other two clean filters.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18560Advanced performance features in FastUniformGrid2024-03-07T20:47:04-05:00W. Alan ScottAdvanced performance features in FastUniformGridPlease add the following advanced features to the FastUniformGrid source. This can be used for performance testing. Obviously, all default off.
* Multiple timesteps. Allow user to create multiple timesteps. Make each timestep's varia...Please add the following advanced features to the FastUniformGrid source. This can be used for performance testing. Obviously, all default off.
* Multiple timesteps. Allow user to create multiple timesteps. Make each timestep's variable data add the timestep. In other words, if data for timetep 0 goes from 0 to 10, make timestep 10 go from 10 to 20.
* Multiple blocks. Replicate the FastUniformGrid along the X axis, for as many blocks as the user wants.
* Multiple variables. Allow the X variable to be replicated as many times as the user desires. If the user is replicating variables, add a count. Thus, we would have X0, X1, X2, ...5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22447ParaView 5.12.0-RC2 build failure on Fedora Rawhide2024-03-07T20:23:59-05:00Orion PoplawskiParaView 5.12.0-RC2 build failure on Fedora RawhideTest building the Fedora ParaView package with 5.12.0-RC2 tarball I'm getting:
```
[100%] Building CXX object Clients/ParaView/CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o
cd /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-bu...Test building the Fedora ParaView package with 5.12.0-RC2 tarball I'm getting:
```
[100%] Building CXX object Clients/ParaView/CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o
cd /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Clients/ParaView && /usr/bin/g++ -DFMT_SHARED -DPARAVIEW_ENABLE_EMBEDDED_DOCUMENTATION=1 -DPARAVIEW_USE_MATERIALEDITOR=0 -DPARAVIEW_USE_PYTHON=1 -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGLWIDGETS_LIB -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -Dkiss_fft_scalar=double -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Clients/ParaView/paraview_autogen/include -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Clients/ParaView -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Clients/ParaView -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/ApplicationComponents -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/ApplicationComponents -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/Components -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/Components -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/Widgets -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/Widgets -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/ThirdParty/QtTesting/vtkqttesting -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/ThirdParty/QtTesting/vtkqttesting -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Utilities/Versioning -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Utilities/Versioning -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/GUISupport/Qt -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/GUISupport/Qt -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/token/vtktoken/token -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/token/vtktoken/token -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/token/vtktoken -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/token/vtktoken -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/DataModel -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/DataModel -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/Math -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/Math -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/kissfft/vtkkissfft -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/kissfft/vtkkissfft -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/Transforms -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/Transforms -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/ExecutionModel -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/ExecutionModel -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Filters/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Filters/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Common/Misc -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Common/Misc -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/OpenGL2 -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/OpenGL2 -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Filters/General -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Filters/General -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/IO/Image -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/IO/Image -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Imaging/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Imaging/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/HyperTreeGrid -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/HyperTreeGrid -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/UI -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/UI -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Interaction/Widgets -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Interaction/Widgets -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Filters/Sources -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Filters/Sources -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Rendering/Context2D -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Rendering/Context2D -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Remoting/ServerManager -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Remoting/ServerManager -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Remoting/ClientServerStream -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Remoting/ClientServerStream -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Remoting/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Remoting/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTKExtensions/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTKExtensions/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/IO/XML -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/IO/XML -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/IO/XMLParser -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/IO/XMLParser -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/fmt/vtkfmt -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/fmt/vtkfmt -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Parallel/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Parallel/Core -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/CMakeFiles/ParaView_paraview_plugins -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Remoting/Settings -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Remoting/Settings -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/include/paraview/pvpythonmodules -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/include/paraview/vtkpythonmodules -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/include/paraview/pvincubatorpythonmodules -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Qt/Python -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Qt/Python -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Utilities/PythonInterpreter -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Utilities/PythonInterpreter -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Utilities/Python -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Utilities/Python -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Wrapping/PythonCore -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Wrapping/PythonCore -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/Utilities/PythonInitializer -I/builddir/build/BUILD/ParaView-v5.12.0-RC2/Utilities/PythonInitializer -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Utilities/KWSys -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Utilities/KWSys -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/Utilities/KWIML -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/Utilities/KWIML -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/token -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/token -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/nlohmannjson -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/nlohmannjson -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/kissfft -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/kissfft -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/glew -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/glew -isystem /usr/include/qt6/QtOpenGL -isystem /usr/include/qt6 -isystem /usr/include/qt6/QtCore -isystem /usr/lib64/qt6/mkspecs/linux-g++ -isystem /usr/include/qt6/QtGui -isystem /usr/include/qt6/QtWidgets -isystem /usr/include/qt6/QtOpenGLWidgets -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/ThirdParty/protobuf -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/ThirdParty/protobuf -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/cli11 -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/cli11 -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/fmt -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/fmt -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/redhat-linux-build-serial/VTK/ThirdParty/jsoncpp -isystem /builddir/build/BUILD/ParaView-v5.12.0-RC2/VTK/ThirdParty/jsoncpp -isystem /usr/include/qt6/QtCore5Compat -isystem /usr/include/python3.12 -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fcommon -m64 -march=z13 -mtune=z14 -fasynchronous-unwind-tables -fstack-clash-protection -DNDEBUG -DOMPI_SKIP_MPICXX -std=c++17 -fPIE -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT Clients/ParaView/CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o -MF CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o.d -o CMakeFiles/paraview.dir/ParaViewMainWindow.cxx.o -c /builddir/build/BUILD/ParaView-v5.12.0-RC2/Clients/ParaView/ParaViewMainWindow.cxx/builddir/build/BUILD/ParaView-v5.12.0-RC2/Clients/ParaView/ParaViewMainWindow.cxx:41:10: fatal error: ParaViewDocumentationInitializer.h: No such file or directory
41 | #include "ParaViewDocumentationInitializer.h"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
```
RC1 I think built fine.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22421Molecule representation: crash when creating new view with ParaView 5.12-RC12024-03-07T20:23:59-05:00Francois MazenMolecule representation: crash when creating new view with ParaView 5.12-RC1The second output of the PDB Reader has to be a Molecule representation. When I create a new 3D render view and try to show the second output (forcing molecule representation), then ParaView crashes.
To reproduce with ParaView 5.12-RC1:...The second output of the PDB Reader has to be a Molecule representation. When I create a new 3D render view and try to show the second output (forcing molecule representation), then ParaView crashes.
To reproduce with ParaView 5.12-RC1:
- Open the file 3GQP.pdb available here: https://data.kitware.com/#item/5afd92b68d777f15ebe1aad4
- Click apply, the "Output-1" is displayed with Molecule representation in the 3D render view
- Create a new view (new layout or split current view)
- Click "Render View" for the view type
- Click on the eye of the "Output-1" item in the pipeline browser
- Crash in `pqColorMapEditor::renderViews` because the `representation` variable is null
ParaView 5.11.0 does not crash and the new render view switch to Molecule representation as expected.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.com