ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T10:57:51-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17237State file is bad if selection is on2023-06-15T10:57:51-04:00W. Alan ScottState file is bad if selection is onIf a user saves a state file when selection is on, that state file is broken. Replicate as follows:
* Master, Linux, local server.
* Sources/ Wavelet. Apply. Surface. RTData.
* Select Cells On. DON'T DO THE SELECTION. Just proceed ...If a user saves a state file when selection is on, that state file is broken. Replicate as follows:
* Master, Linux, local server.
* Sources/ Wavelet. Apply. Surface. RTData.
* Select Cells On. DON'T DO THE SELECTION. Just proceed to next step.
* File/ Save State.
* Reset Session.
* File/ Load State.
Your mouse controls are bad.https://gitlab.kitware.com/paraview/paraview/-/issues/17119"Dashed" line when superposed with geometry2020-05-07T13:36:54-04:00Mathieu Westphal (Kitware)"Dashed" line when superposed with geometryLines appears "dashed" when superposed with geometry, even though they are not.
How to reproduce :
* Open ParaView
* Create a wavelet, apply
* Representation -> Surface with edges
* lines DOES NOT appear dashed
* Representation ->...Lines appears "dashed" when superposed with geometry, even though they are not.
How to reproduce :
* Open ParaView
* Create a wavelet, apply
* Representation -> Surface with edges
* lines DOES NOT appear dashed
* Representation -> Surface
* Add an axes grid
* Axes grid line appears dashed, especially wheen zooming and unzooming.
![bug](/uploads/c66c9f8a1b89a410a0edd46dff8d6f66/bug.png)![bug2](/uploads/4420fa690dd1afaf2f882277e34ae733/bug2.png)![bug3](/uploads/f4fe498e921e00a5afcd78bccec96201/bug3.png)https://gitlab.kitware.com/paraview/paraview/-/issues/11976Calculator errors with autoapply on2022-01-20T12:58:12-05:00Kitware RobotCalculator errors with autoapply on**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11976). Further discussion may take place here.**
---
The calculator is showing errors when used with autoapply turned on.
* ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11976). Further discussion may take place here.**
---
The calculator is showing errors when used with autoapply turned on.
* Trunk, Windows, local server.
* can.exo, all vars on, apply.
* Turn auto apply on.
* Calculator filter.
* In the equation, type 1e7*(), then use the mouse to place the curser between the ( )'s. Next, click on Scalars and try to put in coordsX. The following error will occur:
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax error: expecting a variable name; see position 5
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax error: expecting a variable name; see position 5
Warning: In ..\..\..\..\src\ParaView3\VTK\Graphics\vtkArrayCalculator.cxx, line 401
vtkPVArrayCalculator (06D35EE8): An error occured when parsing the calculator's function. See previous errors.
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax error: expecting a variable name; see position 5
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax error: expecting a variable name; see position 5
Warning: In ..\..\..\..\src\ParaView3\VTK\Graphics\vtkArrayCalculator.cxx, line 401
vtkPVArrayCalculator (06D35EE8): An error occured when parsing the calculator's function. See previous errors.
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax error: expecting a variable name; see position 5
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax error: expecting a variable name; see position 5
Warning: In ..\..\..\..\src\ParaView3\VTK\Graphics\vtkArrayCalculator.cxx, line 401
vtkPVArrayCalculator (06D35EE8): An error occured when parsing the calculator's function. See previous errors.
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax error: expecting a variable name; see position 5
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax error: expecting a variable name; see position 5
Warning: In ..\..\..\..\src\ParaView3\VTK\Graphics\vtkArrayCalculator.cxx, line 401
vtkPVArrayCalculator (06D35EE8): An error occured when parsing the calculator's function. See previous errors.
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax Error: missing closing parenthesis; see position 12
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax Error: missing closing parenthesis; see position 12
Warning: In ..\..\..\..\src\ParaView3\VTK\Graphics\vtkArrayCalculator.cxx, line 401
vtkPVArrayCalculator (06D35EE8): An error occured when parsing the calculator's function. See previous errors.
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax Error: missing closing parenthesis; see position 12
ERROR: In ..\..\..\..\src\ParaView3\VTK\Common\vtkFunctionParser.cxx, line 1461
vtkFunctionParser (0C5D30B8): Syntax Error: missing closing parenthesis; see position 12
Warning: In ..\..\..\..\src\ParaView3\VTK\Graphics\vtkArrayCalculator.cxx, line 401
vtkPVArrayCalculator (06D35EE8): An error occured when parsing the calculator's function. See previous errors.https://gitlab.kitware.com/paraview/paraview/-/issues/22545OverlappingAMR: memory leaks after Convert AMRdataset to Multiblock2024-03-26T05:02:53-04:00Lucas GivordOverlappingAMR: memory leaks after Convert AMRdataset to MultiblockSome memory leaks when closing paraview after an ConvertAMRdatasettoMultiblock.
Tested with paraview master.
### To Reproduce
- create an AMR Gaussian Pulse source
- apply the ConvertAMRdatasettoMultiblock filter
- close paraview
<de...Some memory leaks when closing paraview after an ConvertAMRdatasettoMultiblock.
Tested with paraview master.
### To Reproduce
- create an AMR Gaussian Pulse source
- apply the ConvertAMRdatasettoMultiblock filter
- close paraview
<details><summary>memory leaks</summary>
```bash
vtkDebugLeaks has detected LEAKS!
Class "vtkTypeFloat64Array" has 3 instances still around.
Class "vtkUniformGrid" has 3 instances still around.
Class "16vtkImplicitArrayIN22vtkStructuredCellArray24vtkStructuredCellBackendEE" has 3 instances still around.
Class "vtkDoubleArray" has 15 instances still around.
Class "vtkInformationIntegerPointerValue" has 3 instances still around.
Class "vtkPointData" has 3 instances still around.
Class "16vtkImplicitArrayI25vtkStructuredPointBackendIdEE" has 3 instances still around.
Class "vtkGenericCell" has 3 instances still around.
Class "16vtkImplicitArrayI26vtkConstantImplicitBackendIiEE" has 3 instances still around.
Class "vtkInformationIntegerValue" has 3 instances still around.
Class "9vtkBufferIhE" has 3 instances still around.
Class "vtkCellData" has 3 instances still around.
Class "vtkStructuredCellArray" has 3 instances still around.
Class "vtkIdList" has 6 instances still around.
Class "9vtkBufferIdE" has 18 instances still around.
Class "vtkCommand or subclass" has 3 instances still around.
Class "vtkUnsignedCharArray" has 3 instances still around.
Class "vtkInformation" has 3 instances still around.
Class "vtkMatrix3x3" has 3 instances still around.
Class "vtkMatrix4x4" has 6 instances still around.
Class "vtkEmptyCell" has 3 instances still around.
Class "vtkFieldData" has 3 instances still around.
Class "vtkPoints" has 6 instances still around.
```
</details>https://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/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/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/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/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/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)https://gitlab.kitware.com/paraview/paraview/-/issues/22496Mesh geometry corrupted by Temporal Interpolator with Xdmf3 readers2024-03-01T05:26:48-05:00Maxime RenaultMesh geometry corrupted by Temporal Interpolator with Xdmf3 readersHere is what my geometry becomes after a few timesteps when reading HDF5/XDMF3 files and applying Temporal Interpolation:
![Capture_d_écran_du_2024-02-27_08-00-29](/uploads/a5f0a57c39f1d2cffbbda9ce403c3b62/Capture_d_écran_du_2024-02-27_0...Here is what my geometry becomes after a few timesteps when reading HDF5/XDMF3 files and applying Temporal Interpolation:
![Capture_d_écran_du_2024-02-27_08-00-29](/uploads/a5f0a57c39f1d2cffbbda9ce403c3b62/Capture_d_écran_du_2024-02-27_08-00-29.png)
[Here](https://drive.google.com/drive/folders/1nBibQJRCW-EyKmJGWXFLc7noqpwECgNx?usp=sharing) are the data to reproduce.
I’m using ParaView 5.11.2 on Ubuntu 22.04.4. Here are the steps to follow :
1. Open xdmf file with Xdmf3Reader (S or T) and Apply.
2. Apply TemporalInterpolator to it, and choose any resample factor >1 (tried 2, 5, 10 and 100).
3. Click play. It will go through a few timesteps with no problem then the geometry will disappear, or change position, or completely collapse.
The issue only occurs on interpolated timesteps.
XDMF Reader doesn't show this behavior, but the fields are all wrong. An example of pressure fields: left is correct, read by Xdmf3ReaderS, and right is wrong, read by Xdmf Reader.
![Capture_d_écran_du_2024-02-27_15-48-46](/uploads/2ab8c7f6c118a6db68bcbfa1bd8075b6/Capture_d_écran_du_2024-02-27_15-48-46.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22488Wrong outline representation for ImageData2024-02-28T07:29:34-05:00Arnaud BotellaWrong outline representation for ImageDataI have an ImageData saved as a vti file. In this file, one of the directions is negative. This leads to an accurate Surface representation but a wrong Outline representation. I am unsure if this is Paraview or VTK related and if this dat...I have an ImageData saved as a vti file. In this file, one of the directions is negative. This leads to an accurate Surface representation but a wrong Outline representation. I am unsure if this is Paraview or VTK related and if this data is supported but I guess the result should be consistent between different representations.
Here is the file
```
<VTKFile type="ImageData" version="1.0" byte_order="LittleEndian" header_type="UInt64" compressor="vtkZLibDataCompressor">
<ImageData WholeExtent="0 1 0 1 0 1" Origin="0 0 0" Spacing="1 1 1" Direction="-1 0 0 0 1 0 0 0 1">
<Piece Extent="0 1 0 1 0 1">
</Piece>
</ImageData>
</VTKFile>
```
[file.vti](/uploads/f866f6b662bd008a7e107b3f5616d250/file.vti)
And here are the results
Outline result
![image](/uploads/76d7b737cbe1d541e6c9f5bafc4e3416/image.png)
Surface result
![image](/uploads/2145eec56d9236e61663006f6549e74e/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22487PHTG Reader segfault with Ghost Cell data2024-02-20T11:06:34-05:00Louis GombertPHTG Reader segfault with Ghost Cell dataSteps to reproduce:
- Run pvserver with 2 MPI ranks
- Launch client and connect
- Create HTG Random source
- Generate Ghost Cells
- Save to .phtg
- (Reset)
- Load .phtg file
- :boom:
Individual .htg files load fine, but not the...Steps to reproduce:
- Run pvserver with 2 MPI ranks
- Launch client and connect
- Create HTG Random source
- Generate Ghost Cells
- Save to .phtg
- (Reset)
- Load .phtg file
- :boom:
Individual .htg files load fine, but not the .phtg, which is likely to be an issue with the PHTG Readerhttps://gitlab.kitware.com/paraview/paraview/-/issues/22480ResampleWithDataset is unreliable with quadratic elements2024-02-12T07:37:16-05:00Loïc BertheResampleWithDataset is unreliable with quadratic elementsI tried to interpolate fields from an UnstructuredGrid model to a node set with the ResampleWithDataset filter:
![image](/uploads/ee7714c107d944a6ac4ce01adcf4b1c9/image.png)
Interpolation fails at certain points:
![image](/uploads/b24...I tried to interpolate fields from an UnstructuredGrid model to a node set with the ResampleWithDataset filter:
![image](/uploads/ee7714c107d944a6ac4ce01adcf4b1c9/image.png)
Interpolation fails at certain points:
![image](/uploads/b2427f97104e267a02702c6b08182259/image.png)
Increasing the tolerance or changing the cell locator mode does not improve the result.
This problem seems linked to the type of cells used in the source mesh: if we use an "Extract Surface" filter to linearize the mesh, the problem seems to disappear.
It therefore seems that there is a problem with the robustness of the "Resample With Dataset" filter in the presence of quadratic elements.
Please find below the data to reproduce this issue:
[dest_mesh.vtk](/uploads/c0ab0fa4bedb61082e6910d225a202a0/dest_mesh.vtk) [source_mesh.vtu](/uploads/626b4482c811064616265e41358133a9/source_mesh.vtu)https://gitlab.kitware.com/paraview/paraview/-/issues/22475slice widget needs click to start highlight behavior2024-02-28T20:19:35-05:00Dan Lipsaslice widget needs click to start highlight behaviorI tried this on ParaView 5.11.2 on Windows, but it was true in older slice widgets on ParaView 5.8.
The interior of the slice widget (the interior of the circle) is highlighted with you move the mouse over it, to show the user that it c...I tried this on ParaView 5.11.2 on Windows, but it was true in older slice widgets on ParaView 5.8.
The interior of the slice widget (the interior of the circle) is highlighted with you move the mouse over it, to show the user that it can drag on it to move the slice along its normal. However this does not happen the first time you add the slice. You have to click on the circle for the highlight behavior to start happening.
Same happens on ParaView master on Linux.https://gitlab.kitware.com/paraview/paraview/-/issues/22474Paraview crashing when selecting cells2024-02-08T03:47:41-05:00Luke HirlParaview crashing when selecting cellsI converted output files from SPARTA with the tool grid2paraview.py provided by it. This creates the file structure that can be seen in the attached zip. everything works fine until I try to select cells with the (interactive) select Ce...I converted output files from SPARTA with the tool grid2paraview.py provided by it. This creates the file structure that can be seen in the attached zip. everything works fine until I try to select cells with the (interactive) select Cells On functionality (the green triangle with the arrow pointing to it, wether its the one with dottet line around or without makes no difference).
Zip: https://www.dropbox.com/scl/fi/iqfjnlvoud5lv4tr805oy/result0_1_2_20.rar?rlkey=q7ubmnju4ec6a1i0y1mkmiu6i&dl=0
I’ve also tried using a Linux version (5.10.0-RC1) under WSL. This leads to crashes as well however.
Issue seems to be restricted to the Windows version according to Mathieu Westphal (see following Topic in Paraview Support Forum: https://discourse.paraview.org/t/paraview-crashing-when-selecting-cells/13844)
Under WSL it puts out the following error (can be seen in Forum, as gitlab declares this ticket as Spam when i trty to include it)https://gitlab.kitware.com/paraview/paraview/-/issues/22471pvtu with polyhedra segfault2024-02-13T01:29:29-05:00Kirill Terekhovpvtu with polyhedra segfaultDear developers,
Opening an issue as suggested in discussion: https://discourse.paraview.org/t/pvtu-with-polyhedra-issue/13858
The display of polyhedra in Paraview depends on the order of pieces in the pvtu file.
In the attached exam...Dear developers,
Opening an issue as suggested in discussion: https://discourse.paraview.org/t/pvtu-with-polyhedra-issue/13858
The display of polyhedra in Paraview depends on the order of pieces in the pvtu file.
In the attached example [parallel_polyhedron.pvtu](/uploads/5af0951c12da380600d2974cd61bb6eb/parallel_polyhedron.pvtu), there are 3 hexahedra. In the first piece [parallel_polyhedron_0.vtu](/uploads/928ac87aa4bbc23661908dd2a2198e9c/parallel_polyhedron_0.vtu), there is the usual hexahedron of type 12. In the following two [parallel_polyhedron_1.vtu](/uploads/d25858bf3f8820d67147a32c3e272fff/parallel_polyhedron_1.vtu) and [parallel_polyhedron_2.vtu](/uploads/65e4a6fb24487e4d87c51e1b3b6fc9f1/parallel_polyhedron_2.vtu), there are two hexes stored as polyhedra of type 42 with additional “faces” and “faceoffsets” arrays.
In the original order of pieces in the example, Paraview displays a gap in the middle of the mesh, whereas there should be three tight hexahedra. If the order of the pieces in the pvtu file is changed with parallel_polyhedron_0.vtu going last, the mesh is displayed correctly.
It appears that Paraview renders the mesh correctly if the pieces with polyhedra are followed by the pieces without polyhedra. It skips rendering the polyhedra if the piece without polyhedra is followed by the piece with polyhedra. This is verified in a large mesh example with numerous pieces.
Encountered with Paraview 5.11.1 on windows and tested with the latest ParaView-5.12.0-RC2-Windows-Python3.10-msvc2017-AMD64.msi.
The next issue with the attached example is encountered when applying a “Clip” filter. It will give a warning “A cell with a non-manifold triangulation has been encountered. This cell cannot be contoured.”. Only the top cell is rendered in this case. However, if you check “Crinkle clip”, it will show the cell in the middle (this was a gap) and wouldn’t render the cell at the bottom.
This works as described with Paraview 5.11.1 on windows. ParaView-5.12.0-RC2-Windows-Python3.10-msvc2017-AMD64.msi crashes at “Clip” filter.
Regards,
Kirillhttps://gitlab.kitware.com/paraview/paraview/-/issues/22441Dash (-) ignored in selector'name2024-01-15T17:05:40-05:00Edoardo alinoviDash (-) ignored in selector'nameHello,
I just would like to flag a bug or at least I believe so. In vtkMultiblockDataSet, the dash inside names is ignored while using selectors.
For example:
my_filter.Selectors = ['test-1']
does the same selection as:
my_filter.Se...Hello,
I just would like to flag a bug or at least I believe so. In vtkMultiblockDataSet, the dash inside names is ignored while using selectors.
For example:
my_filter.Selectors = ['test-1']
does the same selection as:
my_filter.Selectors = [‘test1’]
The annoying thing is that if you have a data set with some coordinate in the name (e.g. x_-1, x_0, x_1), selecting only x_-1 would trigger the selection of the x_1 at the same time.
You can find this behaviour in the latest nightly version of Paraview.
Let me know if you know a workaroud to this for the time being :slight_smile:
Thank you very muchhttps://gitlab.kitware.com/paraview/paraview/-/issues/22402ResetSession() breaks GetLayout()2024-03-27T08:01:49-04:00baloeResetSession() breaks GetLayout()running the following through `pvbatch`
```python
from paraview.simple import *
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
ResetSession()
renderView1 = GetActiveViewOrCreate('RenderView')
la...running the following through `pvbatch`
```python
from paraview.simple import *
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
ResetSession()
renderView1 = GetActiveViewOrCreate('RenderView')
layout1 = GetLayout()
print(layout1)
```
prints
```
<paraview.servermanager.ViewLayout object at 0x7f841067ffd0>
None
```
I am expecting another Viewlayout reference instead of that None in the second line.
This renders `ResetSession()` useless for me right now, and I have needed `ResetSession()` in the past to mitigate memory leakage issues when iterating over time steps. So I think it is a feature worth having just in case.