ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-26T05:02:02-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22544OverlappingAMR: crash when using Convert To Multiblock2024-03-26T05:02:02-04:00Lucas GivordOverlappingAMR: crash when using Convert To MultiblockParaView segfault when we use the `Convert To Multiblock` filter on an overlappingAMR.
tested with master and the binary release 5.12.0.
### To Reproduce
- create an `AMRGaussianPulseSource`
- apply the `Convert to Multiblock`
- parav...ParaView segfault when we use the `Convert To Multiblock` filter on an overlappingAMR.
tested with master and the binary release 5.12.0.
### To Reproduce
- create an `AMRGaussianPulseSource`
- apply the `Convert to Multiblock`
- paraview segfault
<details>
<summary>trace on master</summary>
```bash
( 15.927s) [paraview ] vtkDataObjectTree.cxx:442 ERR| vtkMultiBlockDataSet (0x55d10fc87f80): Invalid iterator location.
[jafar:339091] *** Process received signal ***
[jafar:339091] Signal: Segmentation fault (11)
[jafar:339091] Signal code: Address not mapped (1)
[jafar:339091] Failing at address: 0x50
[jafar:339091] [ 0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7f2be2d51420]
[jafar:339091] [ 1] /home/jafar/dev/paraview/build/bin/../lib/libvtkCommonCore-pv5.12.so.1(_ZN14vtkInformation4CopyEPS_i+0x22)[0x7f2be4423be2]
[jafar:339091] [ 2] /home/jafar/dev/paraview/build/bin/../lib/libvtkFiltersCore-pv5.12.so.1(_ZN29vtkConvertToMultiBlockDataSet7ExecuteEP13vtkDataObjectP20vtkMultiBlockDataSet+0xbb)[0x7f2be62c763b]
[jafar:339091] [ 3] /home/jafar/dev/paraview/build/bin/../lib/libvtkFiltersCore-pv5.12.so.1(_ZN29vtkConvertToMultiBlockDataSet11RequestDataEP14vtkInformationPP20vtkInformationVectorS3_+0x34)[0x7f2be62c7774]
[jafar:339091] [ 4] /home/jafar/dev/paraview/build/bin/../lib/libvtkFiltersParallel-pv5.12.so.1(_ZN30vtkPConvertToMultiBlockDataSet11RequestDataEP14vtkInformationPP20vtkInformationVectorS3_+0xa1)[0x7f2bdd04cb81]
[jafar:339091] [ 5] /home/jafar/dev/paraview/build/bin/../lib/libvtkCommonExecutionModel-pv5.12.so.1(_ZN12vtkExecutive13CallAlgorithmEP14vtkInformationiPP20vtkInformationVectorS3_+0x5d)[0x7f2be5f7cfad]
[jafar:339091] [ 6] /home/jafar/dev/paraview/build/bin/../lib/libvtkCommonExecutionModel-pv5.12.so.1(_ZN23vtkDemandDrivenPipeline11ExecuteDataEP14vtkInformationPP20vtkInformationVectorS3_+0x3d)[0x7f2be5f7324d]
[jafar:339091] [ 7] /home/jafar/dev/paraview/build/bin/../lib/libvtkCommonExecutionModel-pv5.12.so.1(_ZN24vtkCompositeDataPipeline1
1ExecuteDataEP14vtkInformationPP20vtkInformationVectorS3_+0x81)[0x7f2be5f6fac1]
[jafar:339091] [ 8] /home/jafar/dev/paraview/build/bin/../lib/libvtkCommonExecutionModel-pv5.12.so.1(_ZN23vtkDemandDrivenPipeline14ProcessRequestEP14vtkInformationPP20vtkInformationVectorS3_+0x30d)[0x7f2be5f7654d]
[jafar:339091] [ 9] /home/jafar/dev/paraview/build/bin/../lib/libvtkCommonExecutionModel-pv5.12.so.1(_ZN32vtkStreamingDemandDrivenPipeline14ProcessRequestEP14vtkInformationPP20vtkInformationVectorS3_+0x549)[0x7f2be5fbc259]
[jafar:339091] [10] /home/jafar/dev/paraview/build/bin/../lib/libvtkCommonExecutionModel-pv5.12.so.1(_ZN24vtkCompositeDataPipeline15ForwardUpstreamEP14vtkInformation+0x182)[0x7f2be5f6e902]
[jafar:339091] [11] /home/jafar/dev/paraview/build/bin/../lib/libvtkCommonExecutionModel-pv5.12.so.1(_ZN23vtkDemandDrivenPipeline14ProcessRequestEP14vtkInformationPP20vtkInformationVectorS3_+0x13a)[0x7f2be5f7637a]
```
<details>https://gitlab.kitware.com/paraview/paraview/-/issues/22543SpreadSheet: not updated correctly for the first timestep2024-03-26T05:12:22-04:00Lucas GivordSpreadSheet: not updated correctly for the first timestepThe SpreadSheetView isn't correctly updated for temporal data when we go to the first timestep after another one.
Tested with master and the binary release (5.12.0) of paraview.
### To reproduce
- open can.ex2
- open the spreadsheetvi...The SpreadSheetView isn't correctly updated for temporal data when we go to the first timestep after another one.
Tested with master and the binary release (5.12.0) of paraview.
### To reproduce
- open can.ex2
- open the spreadsheetview
- magnitude for `ACCL[0]` is equal to 0
- move to the next timestep
- magnitude will be equal to `3.21417e+07`
- move to the timestep 0
- magnitude is always equal to `3.21417e+07` <----- WRONG
- click inside the spreadsheetview
- each value will be correctly updated
<details>
<summary>demo</summary>
![spreadsheetview](/uploads/33e3d4ac3b159e1fcce55d6767c3007d/spreadsheetview.gif)
</details>https://gitlab.kitware.com/paraview/paraview/-/issues/22542ParaView Catalyst2 regression for vtkRectilinearGrid's grid bounds2024-03-26T05:12:59-04:00Jean M. FavreParaView Catalyst2 regression for vtkRectilinearGrid's grid boundsI observe problems with grid bounds not being properly set. It used to work perfectly well in v5.11.2, it no longer works in v5.12
Since there is no example for RectilinearGrids, I have adapted the existing Catalyst2/CxxImageDataExample...I observe problems with grid bounds not being properly set. It used to work perfectly well in v5.11.2, it no longer works in v5.12
Since there is no example for RectilinearGrids, I have adapted the existing Catalyst2/CxxImageDataExample to make a new directory example called Catalyst2/CxxRectilinearGridExample
when properly integrated, using ParaView 5.11.2, the following script will generate output such as:
`./bin/CxxRectilinearGridExample /local/apps/ParaView/ParaView-v5.11.2/Examples/Catalyst2/CxxRectilinearGridExample/catalyst_pipeline.py`
```
executing (cycle=99, time=9.9)
-----
pipeline parameters:
parameter0
parameter1=42
parameter2=doThing
timeParam=9.900000
-----
bounds: (0.0, 60.900000000000006, 0.0, 68.2, 0.0, 75.89999999999999)
```
when properly integrated using ParaView v5.12.0, the same source code will generate the following output:
```
executing (cycle=99, time=9.9)
-----
pipeline parameters:
parameter0
parameter1=42
parameter2=doThing
timeParam=9.900000
-----
bounds: (5.0357343538016e-310, 60.900000000000006, 5.0357281778762e-310, 68.2, 0.0, 6.6157622673887e-310)
```
using the built-in --output option, such as `./bin/CxxRectilinearGridExample --output datasets/datasets-%04ts.vtpd` results in disk files which ParaView itself cannot read properly.
I am contributing a the reproducing code. Updating the parent Examples/CMakeLists.txt is necessary to compile the new example.
[CxxRectilinearGridExample.tar](/uploads/e3bfad6197c7099e6a176076780d1ca5/CxxRectilinearGridExample.tar)5.12.1 (Spring 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22541Surface LIC and UseLight = 0 => wrong image2024-03-25T08:10:53-04:00Frank BlumSurface LIC and UseLight = 0 => wrong image[In discourse:](https://discourse.paraview.org/t/problem-with-surface-lic-and-uselight-0-wrong-image/14255)
renderView1.UseLight = 0 the Surface LIC is incorrect.
with
renderView1.UseLight = 1 everything is fine.
Correct Image using ...[In discourse:](https://discourse.paraview.org/t/problem-with-surface-lic-and-uselight-0-wrong-image/14255)
renderView1.UseLight = 0 the Surface LIC is incorrect.
with
renderView1.UseLight = 1 everything is fine.
Correct Image using UseLight = 1
![test_UseLight1.png](/uploads/3c2f9d4ef49e03e528ccd3ed713e29ca/test_UseLight1.png)
Wrong Image using UseLight = 0
![test_UseLight0.png](/uploads/2c8a299b1e463c110a0eac8d22524bdb/test_UseLight0.png)
```
# state file generated using paraview version 5.12.0
import paraview
paraview.compatibility.major = 5
paraview.compatibility.minor = 12from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()materialLibrary1 = GetMaterialLibrary()
renderView1 = CreateView('RenderView')
renderView1.ViewSize = [500, 500]
renderView1.AxesGrid = 'GridAxes3DActor'
renderView1.CenterOfRotation = [0.0, 0.0, 0.0]
renderView1.StereoType = 'Crystal Eyes'
renderView1.CameraPosition = [40., -10., 0.0]
renderView1.CameraFocalPoint = [0.0, 0.0, 0.0]
renderView1.CameraViewUp = [0.0, 0.0, 1.]
renderView1.CameraFocalDisk = 1.0
renderView1.CameraParallelScale = 12.951115722667065
renderView1.CameraParallelProjection = 1
renderView1.Background = [0.32, 0.34, 0.43]
renderView1.BackEnd = 'OSPRay raycaster'
renderView1.OSPRayMaterialLibrary = materialLibrary1
SetActiveView(None)
layout1 = CreateLayout(name='Layout #1')
layout1.AssignView(0, renderView1)
layout1.SetSize(500, 500)SetActiveView(renderView1)# Load Data out of
# https://www.paraview.org/Wiki/images/5/5d/ParaViewTutorialData.tar.gz
disk_out_refex2 = IOSSReader(registrationName='disk_out_ref.ex2', FileName=['disk_out_ref.ex2'])
disk_out_refex2.ElementBlocks = ['block_1']
disk_out_refex2.NodeBlockFields = ['V']vTF2D = GetTransferFunction2D('V')
vLUT = GetColorTransferFunction('V')
vLUT.TransferFunction2D = vTF2D
vLUT.RGBPoints = [0.0, 0.231373, 0.298039, 0.752941, 11.209410083552676, 0.865003, 0.865003, 0.865003, 22.418820167105352, 0.705882, 0.0156863, 0.14902]
vLUT.ScalarRangeInitialized = 1.0
vPWF = GetOpacityTransferFunction('V')
vPWF.Points = [0.0, 0.0, 0.5, 0.0, 20.0, 1.0, 0.5, 0.0]
vPWF.ScalarRangeInitialized = 1# create a new 'Slice'
slice1 = Slice(registrationName='Slice1', Input=disk_out_refex2)
slice1.SliceType = 'Plane'
slice1.HyperTreeGridSlicer = 'Plane'
slice1.SliceOffsetValues = [0.0]
slice1.SliceType.Origin = [0.0, 0.0, 0.0]
slice1.HyperTreeGridSlicer.Origin = [0.0, 0.0, 0.0]# show data from slice1
slice1Display = Show(slice1, renderView1, 'GeometryRepresentation')
slice1Display.Representation = 'Surface LIC' # without Surface LIC everything is ok
slice1Display.ColorArrayName = ['POINTS', 'V']
slice1Display.LookupTable = vLUTSetActiveSource(slice1)# save screenshot
renderView1.UseLight = 1 #"Surface LIC" is ok
SaveScreenshot('test_UseLight1.png', renderView1, ImageResolution=[500, 500])
renderView1.UseLight = 0 #produces wrong image for "Surface LIC"
SaveScreenshot('test_UseLight0.png', renderView1, ImageResolution=[500, 500])
if __name__ == '__main__':
# generate extracts
SaveExtracts(ExtractsOutputDirectory='extracts')
```https://gitlab.kitware.com/paraview/paraview/-/issues/22539Markers and lines can go out of sync with charts2024-03-22T07:49:59-04:00W. Alan ScottMarkers and lines can go out of sync with chartsIt is possible for markers and lines to go out of sync with charts. Here is how to replicate (and it isn't easy).
* 5.12.0, MacOS ARM, builtin server.
* can.exo. Apply
* Plot global data over time. Apply.
* Turn off everything other t...It is possible for markers and lines to go out of sync with charts. Here is how to replicate (and it isn't easy).
* 5.12.0, MacOS ARM, builtin server.
* can.exo. Apply
* Plot global data over time. Apply.
* Turn off everything other than tmstep. Turn on Diamond markers.
* With the Chart View, play around zooming, panning, etc. If you play around long enough, all of a sudden the diamonds won't line up with the lines.
*https://gitlab.kitware.com/paraview/paraview/-/issues/22538Image reader "File operation failed" for large raw files2024-03-22T07:09:28-04:00James HiltonImage reader "File operation failed" for large raw filesReading a raw file using the 'Image Reader' seems to fail for files larger than 2^30 cells in Paraview v5.12.0-RC3.
Steps to repoduce:
1. Unpack the attached 7z file, this is a 3D raw file of 32-bit floats with dimensions 2048 x 2048 x ...Reading a raw file using the 'Image Reader' seems to fail for files larger than 2^30 cells in Paraview v5.12.0-RC3.
Steps to repoduce:
1. Unpack the attached 7z file, this is a 3D raw file of 32-bit floats with dimensions 2048 x 2048 x 256. Each x-y slice holds a single value of the z index (i.e. the first x-y slice is all 0, second 1 etc.).
[TEST.7z](/uploads/682f2c5db27a329e954fa3b754221500/TEST.7z)
2. Drag and drop into Paraview and pick 'Image Reader'.
3. Settings as below:
![image](/uploads/9d0adf721a9d44132cfd9668635541d9/image.png)
4. Error:
```
Generic Warning: In vtkImageReader.cxx, line 275
File operation failed. row = 0, Tried to Read = 8192, Read = 0, Skip0 = 0, Skip1 = 0, FilePos = -1
```
Changing the z-extent to 63 (i.e. 63 rather than 255) works and reads in the first 63 layers. Changing to 64 triggers the error message.
I thought this may be to do with a file pointer storing the offset byte in a signed integer (i.e. an overflow at 2^31), but this seems to also fail for other data types, e.g. the attached unsigned char raw file with dimensions 2048 x 2048 x 256 also fails to read after layer 63. The only thing in common seems to be they fail after reading 2^30 cells.
[TEST_8.7z](/uploads/de2c4db2a7c7be0828a5785fa4c54d48/TEST_8.7z)https://gitlab.kitware.com/paraview/paraview/-/issues/22535Assembly Hierarchy empty on Information properties of vtkPartitionedDataSetCo...2024-03-19T04:31:15-04:00WillIsbackAssembly Hierarchy empty on Information properties of vtkPartitionedDataSetCollectionDear Community,
# Issue : Assembly information window empty:
While I tried to manually edit a **3 level tree** vtkPartitionedDataSetCollection composed of multiples vtkPartitionedDataSet each composed of two unstructuredGrid object.
I...Dear Community,
# Issue : Assembly information window empty:
While I tried to manually edit a **3 level tree** vtkPartitionedDataSetCollection composed of multiples vtkPartitionedDataSet each composed of two unstructuredGrid object.
I would like to use the new DataAssambly + vtkPartitionedDataSetCollection and not depracated MultiBlock to manage Tree organize object.
However it seems my assembly windows does not work, as I am not able to retrieve the same 3 level hierarchy and even don't see anything as **assembly window is empty**.
I code c++ plugin from the ParaView superbuild 5.11.1 [Context](https://gitlab.kitware.com/paraview/paraview-plugin-windows-binary-compatible-guide), Please find below pictures to help the understanding of this issue:
## Hierarchy of my vtkPartitionedDataSetCollection object
![bug_paraview_0](/uploads/a383d348cf3fd449d8b2e411d177721c/bug_paraview_0.png)
## Assembly of my vtkPartitionedDataSetCollection object
![bug_paraview_1](/uploads/2ebbf47389407eb5ef8003526684d88b/bug_paraview_1.png)
## Hierarchy of the same construction but made all with MultiBockDataSet object (expected view in assembly)
![bug_paraview_3](/uploads/987fa28d2904034796215649065415cc/bug_paraview_3.png)
Best regards,
Williamhttps://gitlab.kitware.com/paraview/paraview/-/issues/22534DATCOM Tecplot Files in Paraview2024-03-15T06:33:55-04:00Dillon PierceDATCOM Tecplot Files in ParaviewI am trying to load the attached flow field visualization files as well as a rocket mesh into Paraview. I have no issues loading them into Tecplot, but they do not render in Paraview as shown with the screen shot. Any advice would be muc...I am trying to load the attached flow field visualization files as well as a rocket mesh into Paraview. I have no issues loading them into Tecplot, but they do not render in Paraview as shown with the screen shot. Any advice would be much appreciated. Thank you very much for your time and support!
![Screenshot_2024-03-14_at_10.35.31_AM](/uploads/9466fb2f7a9e7073b81bd72ff1802fa8/Screenshot_2024-03-14_at_10.35.31_AM.jpg)
[LargeCanardRedesign.Run0001.MDC.202403.FOR022.OUT](/uploads/5dc27f5ec64c32349522103a7ff9fd13/LargeCanardRedesign.Run0001.MDC.202403.FOR022.OUT)
[LargeCanardRedesign.Run0001.MDC.202403.vpath_a0.00_m0.60_c001.dat](/uploads/79c05ead9431154613ab4222311ca574/LargeCanardRedesign.Run0001.MDC.202403.vpath_a0.00_m0.60_c001.dat)https://gitlab.kitware.com/paraview/paraview/-/issues/22530Reload Python Algorithms through Python Shell2024-03-13T14:07:18-04:00Patrick LaurinReload Python Algorithms through Python ShellWhen loading a state containing a module of python algorithms, it is possible to reload the module using the "Reload Python Module" command button in the property panel:
![image](/uploads/7e1270036bc39e8bf266017265e92d08/image.png)
If ...When loading a state containing a module of python algorithms, it is possible to reload the module using the "Reload Python Module" command button in the property panel:
![image](/uploads/7e1270036bc39e8bf266017265e92d08/image.png)
If one wishes to repeat the operation in python using the Python Shell, the following commands would replicate the above (to the best of my knowledge):
```python
python_algorithm = FindSource("PythonAlgorithmExample1")
python_algorithm.SMProxy.RecreateVTKObjects()
```
but weirdly enough, the following error is raised:
```
Warning: In vtkSIPythonSourceProxy.cxx, line 421
vtkSIPythonSourceProxy (000002428C49E620): Failed to re-import module 'PythonAlgorithmExample'.
```
## Additional Details
Python Algorithm used in this issue: [PythonAlgorithmExample.py](/uploads/8280c48bb41176f7f69391946867eefa/PythonAlgorithmExample.py)
To reproduce, load the given plugin above and apply it to a sphere. To instantiate the filter, simply search for "Python Algorithm Example"https://gitlab.kitware.com/paraview/paraview/-/issues/22526update example visualizations to incude new palette and fast color map2024-03-12T22:33:46-04:00W. Alan Scottupdate example visualizations to incude new palette and fast color mapupdate example visualizations to include new palette and fast color map. Test on all 3 OSs.update example visualizations to include new palette and fast color map. Test on all 3 OSs.5.13 (Summer 2024)W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/22525New example visualizations2024-03-12T22:31:58-04:00W. Alan ScottNew example visualizationsAdd 3 new examples to the Example Visualizations. Have them be: 1) One or more of the examples found in the Examples/ vtk folder. 2) a vtkhdf example. 3) A data analysis example, possibly with a python calculator, histogram, plot and ...Add 3 new examples to the Example Visualizations. Have them be: 1) One or more of the examples found in the Examples/ vtk folder. 2) a vtkhdf example. 3) A data analysis example, possibly with a python calculator, histogram, plot and spreadsheet.5.14 (Fall 2024)W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/22524Add VTKHDF examples to ParaView Examples directory2024-03-13T08:41:22-04:00W. Alan ScottAdd VTKHDF examples to ParaView Examples directoryPlease add some VTKHDF examples to the ParaView Examples directory. A good idea would be to add all of the examples at the bottom of the document here: https://www.paraview.org/Wiki/ParaView/Data_formats. Make sure they can be loaded a...Please add some VTKHDF examples to the ParaView Examples directory. A good idea would be to add all of the examples at the bottom of the document here: https://www.paraview.org/Wiki/ParaView/Data_formats. Make sure they can be loaded and run.5.14 (Fall 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22523Help menu - Moving data into and out of ParaView2024-03-12T22:24:32-04:00W. Alan ScottHelp menu - Moving data into and out of ParaViewPlease add a new Help menu line. Please bounce this name by Cory Q (who is better at names than I am). Possibly name the help menu "Moving data into and out of ParaView". Have this menu point at a paraview.org webpage, much as the Onl...Please add a new Help menu line. Please bounce this name by Cory Q (who is better at names than I am). Possibly name the help menu "Moving data into and out of ParaView". Have this menu point at a paraview.org webpage, much as the Online Tutorials line does (i.e., https://www.paraview.org/tutorials/).
In this new webpage, include at least the following links:
* VTK File formats: https://docs.vtk.org/en/latest/design_documents/VTKFileFormats.html
* PVD file format: This needs a new page. The best I can find is something I created maybe 10 years ago. https://www.paraview.org/Wiki/ParaView/Data_formats.
* ParaView supported file formats for read: https://docs.vtk.org/en/latest/supported_data_formats.html
* ParaView supported file formats for write: Page probably needs to be created. Note, have two sections on this page - Save Data and Export scene. Explain both.5.14 (Fall 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22521Avoid properties that change the output of a filter2024-03-26T05:23:25-04:00Mathieu Westphal (Kitware)Avoid properties that change the output of a filterIn ParaView, there are a few properties that can change the output type of a filter.
Some of them are handled in a such a way that the output type should be set before the first apply, eg all Programmable filters and sources.
Other can...In ParaView, there are a few properties that can change the output type of a filter.
Some of them are handled in a such a way that the output type should be set before the first apply, eg all Programmable filters and sources.
Other can switch type on the fly, especially:
- AppendDataSet: OutputDataSetType
- GroupDataSet: OutputType
- MergeBlocks: OutputDataSetType
- Slice: CrinkleSlice/SliceType (HTG only)
- SliceWithPlane: SliceType (AMR Only)
- ExtractSelection: HyperTreeGridToUnstructuredGrid (HTG only)
This is an issue because once the output of this filter has been connected to another filter, there is no way to ensure the output type will never change and this can causes errors and even crashes.
Lets try to improve this situation with the following:
1. Avoid adding new filters and new properties that change their output types depending of an input. That include going from vtkDataSet to/from vtkCompositeDataSet
2. Add a warning mechanism (based on https://gitlab.kitware.com/paraview/paraview/-/blob/3130fddfdacbadbefadaea86fe60f76ed7d72eaf/Utilities/Doxygen/pages/PropertyHints.md#warnonpropertychange) so that the user know that changing this property may have unintended consequences
3. Separate filters in multiples filters a depracate filters when possible
Please note PassInput type algorithm are fine, even though one can have the same behavior using the "ChangeInput" feature, this is a much more advanced feature, although a warning should be added in the "ChangeInput" dialog to inform the user would make sense.https://gitlab.kitware.com/paraview/paraview/-/issues/22517Volume rendering of Image data with ghost cell and points2024-03-08T11:42:20-05:00Charles GueunetVolume rendering of Image data with ghost cell and points## Description
Volume rendering on an image data with ghost cells and ghost **points** leads to missing row of cells:
![volume.png](/uploads/4d860c0fb564e53c5873e0e8510f84d6/volume.png){width=620 height=393}
## How to reproduce
On a ...## Description
Volume rendering on an image data with ghost cells and ghost **points** leads to missing row of cells:
![volume.png](/uploads/4d860c0fb564e53c5873e0e8510f84d6/volume.png){width=620 height=393}
## How to reproduce
On a paraview connected to a pvserver running with mpi and 4 ranks:
* Create a wavelet (Here, volume rendering is OK
* Add a **GhostCellGenerator** a row of cell is now missing like in the revious screenshot
## Investigation
In order to understand further the issue, I have saved the data set and loaded each bloc independently to inspect how they are rendered and their ghost cells.
Here is the top right block of my data in volume rendering, plus the ghost cells extracted in solid rendering:
![part1.png](/uploads/dbb5512010a85198c5734536bed08f5b/part1.png){width=451 height=444}
From this perspective, the missing row of voxels is clearly visible. It is not composed of ghost cells, but of voxels in contact with the ghost... so having ghost points ?
Let's try to load the same top right block with the vtkGhostType attached to the cells, but **discarding** the one attached to the points:
![part2.png](/uploads/7d4ccc95df979a6a77ff81fa1c953925/part2.png){width=448 height=451}
This time the rendering is correct.
I have also tried the same for the image as a whole and I can confirm the result is the right one.https://gitlab.kitware.com/paraview/paraview/-/issues/22516Backports needed for ParaView 5.12.12024-03-08T10:24:06-05:00Cory Quammencory.quammen@kitware.comBackports needed for ParaView 5.12.1For VTK's `paraview/release` branch:
- [ ] https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10938
For ParaView's `release` branch:For VTK's `paraview/release` branch:
- [ ] https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10938
For ParaView's `release` branch:5.12.1 (Spring 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22515Transformation (rotation) of tensor variables2024-03-08T07:43:50-05:00cmorsbachTransformation (rotation) of tensor variablesAs suggested by @mwestphal in https://discourse.paraview.org/t/transformation-of-tensor-variables/14112, I'm opening a ticket for this feature request:
Currently, the _Transform_ filter in ParaView applies the correct transformation (ro...As suggested by @mwestphal in https://discourse.paraview.org/t/transformation-of-tensor-variables/14112, I'm opening a ticket for this feature request:
Currently, the _Transform_ filter in ParaView applies the correct transformation (rotation) to vectors stored as 3-component float arrays. As there is support for Cartesian rank 2 tensors (6-component symmetric and 9-component general) in ParaView, it would be good, if these were transformed as well. Currently (ParaView 5.11), they are not, which leads to an inconsistent dataset when _Transform_ or _AngularPeriodicFilter_ are applied.https://gitlab.kitware.com/paraview/paraview/-/issues/22514polygonal meshes do not get exported correctly to CGNS2024-03-08T07:33:17-05:00Alexandre Minotpolygonal meshes do not get exported correctly to CGNSPolygonal meshes do not get exported correctly to CGNS, at least in 1D. The coordinates and data look right, but there are no elements in the CGNS files. This can be reproduced by creating a line source and saving the result to CGNS. My ...Polygonal meshes do not get exported correctly to CGNS, at least in 1D. The coordinates and data look right, but there are no elements in the CGNS files. This can be reproduced by creating a line source and saving the result to CGNS. My guess is that each segment of the polygon will need to be split into individual BAR elements.
In particular, this means that streamtracer results cannot be saved to CGNS
[line.cgns](/uploads/9f23b0f4a992a80f445f84ee1704b116/line.cgns)
[line.py](/uploads/d544edb3528f433fb10e6c019a5988c8/line.py)https://gitlab.kitware.com/paraview/paraview/-/issues/22513Memory leaks when using ParaView Catalyst2024-03-08T07:27:33-05:00Spiros TsalikisMemory leaks when using ParaView Catalyst```
=================================================================
==17446==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4180894 byte(s) in 2337 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/peo...```
=================================================================
==17446==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4180894 byte(s) in 2337 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0cad in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0cad in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
Direct leak of 160 byte(s) in 2 object(s) allocated from:
#0 0x5175d8 in operator new(unsigned long) /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:92
#1 0x7fa4bd3bcc2d in catalyst_conduit_node_create (/usr/people/shared/tools/centos/7/catalyst/HPCX/2.0.0/lib64/libcatalyst.so.3+0xedc2d)
#2 0x6080000655d7 (<unknown module>)
Direct leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa4b25470cb (<unknown module>)
Direct leak of 64 byte(s) in 2 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495dd1294 in PyThread_allocate_lock /home/foo/Downloads/Python-3.7.0/build/../Python/thread_pthread.h:257:21
Direct leak of 12 byte(s) in 1 object(s) allocated from:
#0 0x442048 in strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:407
#1 0x7fa4a08f89de in vtkloguru::init(int&, char**, vtkloguru::Options const&) (/usr/people/shared/tools/centos/7/paraview/HPCX/paraview/5.11.0-mesa/lib64/catalyst/libcatalyst-paraview.so+0x87a69de)
Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x442048 in strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:407
#1 0x7fa4a08f93a6 in vtkloguru::set_thread_name(char const*) (/usr/people/shared/tools/centos/7/paraview/HPCX/paraview/5.11.0-mesa/lib64/catalyst/libcatalyst-paraview.so+0x87a73a6)
Direct leak of 1 byte(s) in 1 object(s) allocated from:
#0 0x442558 in __strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:423
#1 0x7fa4b094a7f0 (<unknown module>)
Indirect leak of 1361576 byte(s) in 1124 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0cad in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0cad in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
Indirect leak of 12508 byte(s) in 2 object(s) allocated from:
#0 0x4e0010 in realloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:107
#1 0x7fa495cde4f8 in resize_compact /home/foo/Downloads/Python-3.7.0/build/../Objects/unicodeobject.c:929:31
Indirect leak of 544 byte(s) in 1 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0edc in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0edc in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
#3 0x7fa495cc0edc in pymalloc_realloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1882
#4 0x7fa495cc0edc in _PyObject_Realloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1901
Indirect leak of 128 byte(s) in 2 object(s) allocated from:
#0 0x5175d8 in operator new(unsigned long) /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:92
#1 0x7fa4bd3412ec in catalyst_conduit::Node::Node() (/usr/people/shared/tools/centos/7/catalyst/HPCX/2.0.0/lib64/libcatalyst.so.3+0x722ec)
#2 0x6080000655d7 (<unknown module>)
Indirect leak of 15 byte(s) in 1 object(s) allocated from:
#0 0x442558 in __strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:423
#1 0x7fa4b254713e (<unknown module>)
SUMMARY: AddressSanitizer: 5555974 byte(s) leaked in 3475 allocation(s).
```
```
cmake /usr/people/shared/tools/centos/7/paraview/installer/src/paraview/Examples -DCMAKE_BUILD_TYPE=ASAN -DOPENGL_xmesa_INCLUDE_DIR:PATH=IGNORE -DOPENGL_gl_LIBRARY:FILEPATH=IGNORE -DOSMESA_INCLUDE_DIR:PATH=$MESA_INC -DOSMESA_LIBRARY:FILEPATH=$MESA_LIB/libOSMesa.so -DCMAKE_INSTALL_PREFIX="/work/foo/cases/053_Catalyst_Standalone/001_Polyhedra/install/"
cd Catalyst2/CxxPolyhedra
make install
```
```
cmake /usr/people/shared/tools/centos/7/paraview/installer/src/paraview/Examples -DCMAKE_BUILD_TYPE=ASAN -DOPENGL_xmesa_INCLUDE_DIR:PATH=IGNORE -DOPENGL_gl_LIBRARY:FILEPATH=IGNORE -DOSMESA_INCLUDE_DIR:PATH=$MESA_INC -DOSMESA_LIBRARY:FILEPATH=$MESA_LIB/libOSMesa.so -DCMAKE_INSTALL_PREFIX="/work/foo/cases/053_Catalyst_Standalone/001_Polyhedra/install/" -DCMAKE_CXX_FLAGS_ASAN="-g -O3 -DNDEBUG -DASAN_ENABLED -fsanitize=address -fno-omit-frame-pointer"
```
```
./build/bin/CxxPolyhedraV2 catalyst_pipeline.py
```
[catalyst_pipeline.py](/uploads/939c786c80b9afd83b0d490c28067551/catalyst_pipeline.py)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22512vtkOverlappingAMR: rendering artifacts with Wireframe and FeatureEdges repres...2024-03-07T08:37:24-05:00Lucas GivordvtkOverlappingAMR: rendering artifacts with Wireframe and FeatureEdges representationIn `Feature Edges` and `Wireframe` representations there are some rendering artifacts when we have overlap between the border of multiple levels:
![image](/uploads/4d5dce5ed815a0cf1220c0b83f48d5ed/image.png)
This issue can be reproduc...In `Feature Edges` and `Wireframe` representations there are some rendering artifacts when we have overlap between the border of multiple levels:
![image](/uploads/4d5dce5ed815a0cf1220c0b83f48d5ed/image.png)
This issue can be reproduce by loading this data and set the level to `2`:
[overlapping_amr_artifacts.vthb](/uploads/6e7797e0f62d8890962a2309fb3954ed/overlapping_amr_artifacts.vthb)