ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-11-21T10:25:43-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21634[5.11.0-RC2] Random crashes with "Pick Center"2022-11-21T10:25:43-05:00Menno Deij - van Rijswijk[5.11.0-RC2] Random crashes with "Pick Center"I have seen this now a couple of times: after a few steps in a filter pipeline, I use `Pick Center` and click on a visible cell. Then ParaView freezes and crashes.
I'll try to see if I can reproduce this reliably.I have seen this now a couple of times: after a few steps in a filter pipeline, I use `Pick Center` and click on a visible cell. Then ParaView freezes and crashes.
I'll try to see if I can reproduce this reliably.5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21624Delaunay 3D filter crashes on empty data2022-10-27T14:01:20-04:00Kenneth MorelandDelaunay 3D filter crashes on empty dataThe `Delaunay 3D` filter crashes if the input data has no points. To replicate, do the following:
1. Open this empty data file: [empty.vtk](/uploads/2c5a550db66b102ed598549dc80ecb41/empty.vtk)
2. Add the `Delaunay 3D` filter. Apply. (cr...The `Delaunay 3D` filter crashes if the input data has no points. To replicate, do the following:
1. Open this empty data file: [empty.vtk](/uploads/2c5a550db66b102ed598549dc80ecb41/empty.vtk)
2. Add the `Delaunay 3D` filter. Apply. (crash)5.12 (Winter 2023)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/21620Cell Data is not supported in exporting to GLTF model2022-10-25T23:07:23-04:00Jimmy-KLCell Data is not supported in exporting to GLTF modelIf we use cell data to color the model, the exported gltf model will have an error. Please check the question that I submitted at the community support: [export-glft-error-from-paraview](https://discourse.paraview.org/t/export-glft-error...If we use cell data to color the model, the exported gltf model will have an error. Please check the question that I submitted at the community support: [export-glft-error-from-paraview](https://discourse.paraview.org/t/export-glft-error-from-paraview/10585)
And also I found the coordinate system will be different in gltf model from in paraview. It seems the y and z axis is changed.https://gitlab.kitware.com/paraview/paraview/-/issues/21614visualization problems for Feature Edges2024-01-22T11:55:51-05:00Theo Igavisualization problems for Feature EdgesFeature Edges visualization sometimes seems to detect wrong edges (working with Paraview 5.10.0 Windows).
In the next figure, I would expect **Feature Edges** only along the boundary lines, and not the four internal lines.
![edges](/up...Feature Edges visualization sometimes seems to detect wrong edges (working with Paraview 5.10.0 Windows).
In the next figure, I would expect **Feature Edges** only along the boundary lines, and not the four internal lines.
![edges](/uploads/98c3dd821c7731796c464ef76a24c10f/edges.png)
Here annexed the configuration (and the state file `edges.pvsm`) for reproducing the issue.
[edges.zip](/uploads/1cddf13eb6b275f548aefe7a9ce00bfc/edges.zip)
Thanks in advance.
Theohttps://gitlab.kitware.com/paraview/paraview/-/issues/21605Cannot Load Time-Series Ensight Data (*.case file format)2022-10-18T04:33:55-04:00Andrew CarlsonCannot Load Time-Series Ensight Data (*.case file format)Opening an ensight case file formatted for a single data point (i.e. transient or single point in time) works fine...
Having a *.case file that points several data files does not work.
I can open it with a work around. And that is:
...Opening an ensight case file formatted for a single data point (i.e. transient or single point in time) works fine...
Having a *.case file that points several data files does not work.
I can open it with a work around. And that is:
1. Replace the wildcard * with ****
2. Replace the "filename numbers file:" with "filename numbers:" and the list of numbers
3. Repalce the "time values file:" with "time values:" and the times that correspond to each of the filenames
For example, see the attached original ensight data and adjusted to get it working.
- 01_transient_original_ensight_results
- 02_transient_modified_ensight_results
Also there, as a comparison is results from a steady state run (00_steadyState_ensight_results), to show it also works if only a single data point is indicted
My ensight data was created from CFD software Simerics... but this should not be relevant.https://gitlab.kitware.com/paraview/paraview/-/issues/21600Camera animation data not stored in pvsm when using macro to insert keyframes2023-06-15T10:45:19-04:00Devin BaylyCamera animation data not stored in pvsm when using macro to insert keyframesI'm finding that the keyframes that I'm inserting using my macro method (https://discourse.paraview.org/t/animation-keytime-integer-error/10454) don't survive a save, close and reload of the pvsm file. Any ideas about how to make these a...I'm finding that the keyframes that I'm inserting using my macro method (https://discourse.paraview.org/t/animation-keytime-integer-error/10454) don't survive a save, close and reload of the pvsm file. Any ideas about how to make these animation keyframes stick?
Here's a link to a screen cap with the issue shown.
https://drive.google.com/file/d/17EeDeTmN5fDGOg7LpN0GxM1fja47of6_/view?usp=sharing
I'm using paraview 5.11.
This is a copy of the issue from the community forum https://discourse.paraview.org/t/camera-animation-state-isnt-saving/10486.
In case it's helpful I have run a diff between these pvsms and I see a number of differences https://github.com/DevinBayly/paraview_code/commit/b778261f3fdabd23cc3baa2cb268d5234f5f91c9 but I'm not sure how to reconcile them in my macro since my paraview knowledge is early days.https://gitlab.kitware.com/paraview/paraview/-/issues/21585Rescale to visible data range fails2022-11-01T21:43:14-04:00W. Alan ScottRescale to visible data range failsRescale to visible data range fails. Here is how to replicate:
* 5.11.0-RC1. Builtin server.
* Can.ex2. Apply. Don't rotate it.
* Paint by ACCL.
* Move forward one timestep.
* Rescale to visible data range.
Nothing happens. This is...Rescale to visible data range fails. Here is how to replicate:
* 5.11.0-RC1. Builtin server.
* Can.ex2. Apply. Don't rotate it.
* Paint by ACCL.
* Move forward one timestep.
* Rescale to visible data range.
Nothing happens. This is a bug.
@cory.quammen5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21571Use of RandomAttributes after GenerateIds makes Paraview drop scalar field of...2022-09-21T22:49:19-04:00Eve Le GuillouUse of RandomAttributes after GenerateIds makes Paraview drop scalar field of idsHi all,
I use Paraview 5.10.1.
I execute the following pipeline:
#### import the simple module from the paraview
from paraview.simple import *
# create a new 'Wavelet'
wavelet1 = Wavelet(registrationName='Wavelet1')...Hi all,
I use Paraview 5.10.1.
I execute the following pipeline:
#### import the simple module from the paraview
from paraview.simple import *
# create a new 'Wavelet'
wavelet1 = Wavelet(registrationName='Wavelet1')
# create a new 'Generate Ids'
generateIds1 = GenerateIds(registrationName='GenerateIds1', Input=wavelet1)
# create a new 'Random Attributes'
randomAttributes1 = RandomAttributes(registrationName='RandomAttributes1', Input=generateIds1)
randomAttributes1.GeneratePointScalars = 1
When looking at the produced results, instead of finding two scalar fields for the points, there is only one: RandomPointScalars. If RandomAttributes is used before GenerateIds, then it is PointIds that is found. But whatever the order of the two filters, a scalar field is dropped unintentionally.
When each filter is used with another filter, such as Elevation, the bug disappears.https://gitlab.kitware.com/paraview/paraview/-/issues/215695.11-RC1 crash - clip+box, then reset-bounds2022-10-18T10:17:43-04:00Menno Deij - van Rijswijk5.11-RC1 crash - clip+box, then reset-boundsSteps to reproduce:
- Sources > Sphere > Apply
- Filters > Clip
- Choose Box
- Click "Reset Bounds".
Hourglass -> Crash.Steps to reproduce:
- Sources > Sphere > Apply
- Filters > Clip
- Choose Box
- Click "Reset Bounds".
Hourglass -> Crash.5.11 (Spring 2022)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/215525.11.0-RC1: Cannot save VTH extract of AMR datasets2024-02-13T21:46:14-05:00Miren Radia5.11.0-RC1: Cannot save VTH extract of AMR datasets### Brief description
When I try and save a VTH extract of an AMR dataset with the pre-built v5.11.0-RC1 Linux package, I get an error message and the file does not save.
### Steps to reproduce
1. Open ParaView v5.11.0-RC1 GUI.
2. Creat...### Brief description
When I try and save a VTH extract of an AMR dataset with the pre-built v5.11.0-RC1 Linux package, I get an error message and the file does not save.
### Steps to reproduce
1. Open ParaView v5.11.0-RC1 GUI.
2. Create an 'AMR GaussianPulse Source' and hit 'Apply'.
3. Add a 'VTH' extract to the pipeline.
4. Click 'File' -> 'Save Extracts'.
5. Click 'OK' in the dialog box that comes up.
### Observed behavior
Several error messages are printed that are all like
```
( 710.585s) [paraview ]vtkCompositeDataPipelin:155 ERR| vtkPVCompositeDataPipeline (0x17fd6d20): Can not execute simple algorithm vtkXMLPUniformGridAMRWriter (0x17c49270) without output ports
```
and no files are saved.
### Expected behavior
No error message and the extract is successfully saved. This is the case with the pre-built v5.10.1 Linux package.
### Comments
* I first came across this problem when trying to save a VTH extract of some Chombo HDF5 data that I read in to ParaView using the VisitChomboReader so it's definitely not unique to the 'AMR GaussianPulse Source'.
* I realise this may be a VTK issue but I'm not too familiar with using VTK directly so though I'd report here.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21550Problem with Paraview reading direction dependent degrees for a `VTK_LAGRANGE...2022-11-24T08:29:00-05:00Lucas C WilcoxProblem with Paraview reading direction dependent degrees for a `VTK_LAGRANGE_QUADRILATERAL`I am having problems loading the following data in Paraview that contains direction dependent degrees for a `VTK_LAGRANGE_QUADRILATERAL`.
[lquad.vtu](/uploads/78c8175a7d59a1d4a00a8159666cea30/lquad.vtu)
```xml
<VTKFile type="Unstructur...I am having problems loading the following data in Paraview that contains direction dependent degrees for a `VTK_LAGRANGE_QUADRILATERAL`.
[lquad.vtu](/uploads/78c8175a7d59a1d4a00a8159666cea30/lquad.vtu)
```xml
<VTKFile type="UnstructuredGrid" version="1.0" byte_order="LittleEndian" header_type="UInt64">
<UnstructuredGrid>
<Piece NumberOfPoints="12" NumberOfCells="1">
<PointData>
</PointData>
<CellData>
<DataArray type="Int64" Name="HigherOrderDegrees" NumberOfComponents="3" format="ascii">
2 3 12
</DataArray>
<DataArray type="Int64" Name="CellNumber" format="ascii">
1
</DataArray>
</CellData>
<Points>
<DataArray type="Float64" Name="Points" NumberOfComponents="3" format="ascii">
0 0 0 0.5 0 0
1 0 0 0 0.3333333333333334 0
0.5000000000000001 0.3333333333333334 0 1.0000000000000002 0.3333333333333334 0
0 0.6666666666666666 0 0.5 0.6666666666666666 0
1 0.6666666666666666 0 0 1 0
0.5 1 0 1 1 0
</DataArray>
</Points>
<Cells>
<DataArray type="Int64" Name="connectivity" format="ascii">
0 2 11 9 1 5
8 10 3 6 4 7
</DataArray>
<DataArray type="Int64" Name="offsets" format="ascii">
12
</DataArray>
<DataArray type="UInt8" Name="types" format="ascii">
70
</DataArray>
</Cells>
</Piece>
</UnstructuredGrid>
</VTKFile>
```
Reading the mesh works in Paraview 5.9.1 and fails in Paraview 5.10.0 (and later versions) on Ubuntu 22.04.1 with the following error message.
```
( 4.656s) [paraview ]vtkHigherOrderQuadrilat:598 ERR| vtkLagrangeQuadrilateral (0x1ca4dd90): The degrees are direction dependents, and should be set in the input file.
( 4.659s) [paraview ]vtkHigherOrderQuadrilat:623 ERR| vtkLagrangeQuadrilateral (0x1ca4dd90): The degrees might be direction dependents, and should be set before GetOrder is called. numPts is 12 and Order[2] 9
( 4.660s) [paraview ]vtkHigherOrderQuadrilat:623 ERR| vtkLagrangeQuadrilateral (0x1ca4dd90): The degrees might be direction dependents, and should be set before GetOrder is called. numPts is 12 and Order[2] 9
```
Did something change with how to specify the degrees of the cells? I am using `HigherOrderDegrees` `CellData`. I checked the release notes for Paraview 5.10 but didn’t see any discussion of this.
Thanks for any help you can provide!https://gitlab.kitware.com/paraview/paraview/-/issues/21549Segfault when computing gradient of a vector on polyhedral cells2022-09-12T23:53:05-04:00LukaszSegfault when computing gradient of a vector on polyhedral cellsI am working on a grid that contains also polyhedral cells and my Paraview (5.10) crashes whenever I compute gradient of the velocity vector. I reduced my mesh to just 4 poly cells and can always reproduce the error. The cellst themselve...I am working on a grid that contains also polyhedral cells and my Paraview (5.10) crashes whenever I compute gradient of the velocity vector. I reduced my mesh to just 4 poly cells and can always reproduce the error. The cellst themselves look okay in terms of VTK format and I can compute gradients of a scalar and also gradient of a vector provided that I use up to 3 cells. With 4 connected polys I get the above mentioned segfault.
```
> Loguru caught a signal: SIGSEGV
> Stack trace:
> 13 0x7fa56673688d clone + 109
> 12 0x7fa55b130e65 /usr/lib64/libpthread.so.0(+0x7e65) [0x7fa55b130e65]
> 11 0x7fa55aee8196 /home/caldron-b/g478040/linux/Software/Paraview/v5.10.1/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/../lib/libtbb.so.2(+0x1d196) [0x7fa55aee8196]
> 10 0x7fa55aee8206 /home/caldron-b/g478040/linux/Software/Paraview/v5.10.1/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/../lib/libtbb.so.2(+0x1d206) [0x7fa55aee8206]
> 9 0x7fa55aeec56f /home/caldron-b/g478040/linux/Software/Paraview/v5.10.1/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/../lib/libtbb.so.2(+0x2156f) [0x7fa55aeec56f]
> 8 0x7fa55aeee760 /home/caldron-b/g478040/linux/Software/Paraview/v5.10.1/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/../lib/libtbb.so.2(+0x23760) [0x7fa55aeee760]
> 7 0x7fa55aef45ea /home/caldron-b/g478040/linux/Software/Paraview/v5.10.1/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/../lib/libtbb.so.2(+0x295ea) [0x7fa55aef45ea]
> 6 0x7fa55f092fba /home/caldron-b/g478040/linux/Software/Paraview/v5.10.1/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/../lib/libvtkFiltersGeneral-pv5.10.so.1(+0x24bfba) [0x7fa55f092fba]
> 5 0x7fa55f09286a /home/caldron-b/g478040/linux/Software/Paraview/v5.10.1/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/../lib/libvtkFiltersGeneral-pv5.10.so.1(+0x24b86a) [0x7fa55f09286a]
> 4 0x7fa55dabe921 vtkPolyhedron::Derivatives(int, double const*, double const*, int, double*) + 641
> 3 0x7fa55da29c0c vtkMeanValueCoordinatesInterpolator::ComputeInterpolationWeights(double const*, vtkPoints*, vtkCellArray*, double*) + 236
> 2 0x7fa55da2783d vtkMeanValueCoordinatesInterpolator::ComputeInterpolationWeightsForPolygonMesh(double const*, vtkPoints*, vtkMVCPolyIterator&, double*) + 109
> 1 0x7fa55da20ffd /home/caldron-b/g478040/linux/Software/Paraview/v5.10.1/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/../lib/libvtkCommonDataModel-pv5.10.so.1(+0x286ffd) [0x7fa55da20ffd]
> 0 0x7fa56666e3b0 /usr/lib64/libc.so.6(+0x363b0) [0x7fa56666e3b0]
> ( 64.034s) [ 813F4700] :0 FATL| Signal: SIGSEGV
```
Link to a small testcase:
https://discourse.paraview.org/uploads/short-url/bDsHwPH5WzMlyG4m93ygx8TIwwU.zsthttps://gitlab.kitware.com/paraview/paraview/-/issues/21544Broken volume rendering on MacOS Monterey 12.1 M1 Max2023-06-07T22:12:31-04:00Linnea PalmstromBroken volume rendering on MacOS Monterey 12.1 M1 MaxTo reproduce, load fast uniform grid source and apply a threshold from -10 to 10 (the default settings) in ParaView 5.11.0 RC1. Then switch to a volume representation. It does not appear to clear the last frames as you move the camera an...To reproduce, load fast uniform grid source and apply a threshold from -10 to 10 (the default settings) in ParaView 5.11.0 RC1. Then switch to a volume representation. It does not appear to clear the last frames as you move the camera and the background color changes to black.
@patchett2002
@ethan.stam
@maxwelljackson002
![Screen_Shot_2022-09-08_at_1.17.53_PM](/uploads/a5029a0e6a545398f1972683ce707992/Screen_Shot_2022-09-08_at_1.17.53_PM.png)5.12 (Winter 2023)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21537Cell Vertex Ordering is wrong for a Y=0 Slice of a HyperTreeGrid2022-09-09T06:00:04-04:00Julien FaustyCell Vertex Ordering is wrong for a Y=0 Slice of a HyperTreeGrid# Description
When slicing a `vtkHyperTreeGrid` using a plane normal to the Y direction the generated PolyData has cells with bad vertex ordering. This does not occur when the direction is X or Z.
![screenshot_issue](/uploads/650630b76...# Description
When slicing a `vtkHyperTreeGrid` using a plane normal to the Y direction the generated PolyData has cells with bad vertex ordering. This does not occur when the direction is X or Z.
![screenshot_issue](/uploads/650630b76f22f85102aed17befdaf4ec/screenshot_issue.png)
# Steps to reproduce
1. Generate a random HyperTreeGrid using the "RandomHyperTreeGridSource" filter
2. Slice the data with a Y = 0 plane
State file: [y_slice_issue_htg.pvsm](/uploads/7f90067cd7242ab4f830a0fe6b708039/y_slice_issue_htg.pvsm)https://gitlab.kitware.com/paraview/paraview/-/issues/21531v5.11.0RC1 Rectilinear cannot be displayed in "Slice" mode2024-03-07T20:23:51-05:00Jean M. Favrev5.11.0RC1 Rectilinear cannot be displayed in "Slice" mode[paraview ]vtkDemandDrivenPipeline:776 ERR| vtkPVDataRepresentationPipeline (0x5565003282a0): Input for connection index 0 on input port index 0 for algorithm vtkImageSliceRepresentation (0x5564fd5b7820) is of type vtkRectiline...[paraview ]vtkDemandDrivenPipeline:776 ERR| vtkPVDataRepresentationPipeline (0x5565003282a0): Input for connection index 0 on input port index 0 for algorithm vtkImageSliceRepresentation (0x5564fd5b7820) is of type vtkRectilinearGrid, but a vtkImageData is required
The Representation mode "Slice" should be either disabled for rectilinear grids, or fixed.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/215245.11-RC1: Setting default reader does not work as expected2024-03-07T20:23:51-05:00Menno Deij - van Rijswijk5.11-RC1: Setting default reader does not work as expectedWhen I open a CGNS file there are two readers: CGNS Series reader and IOSS reader. PV 5.11 now has a "Set reader as default" button.
When I click this, the file opens as expected.
But the next time, I still get the dialog to choose a ...When I open a CGNS file there are two readers: CGNS Series reader and IOSS reader. PV 5.11 now has a "Set reader as default" button.
When I click this, the file opens as expected.
But the next time, I still get the dialog to choose a reader.
I expected not to see the dialog again.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21515Paraview does not seem to be able to read adios bp4 format in parallel2022-10-27T11:46:42-04:00F. S.Paraview does not seem to be able to read adios bp4 format in parallelI have tried to read in parallel the attached bp4 case with all the paraview versions (built and not) from 5.8. It always works in sequential, it sometimes works until 4-5 processors, but never beyond. The issue comes with all the cases ...I have tried to read in parallel the attached bp4 case with all the paraview versions (built and not) from 5.8. It always works in sequential, it sometimes works until 4-5 processors, but never beyond. The issue comes with all the cases that I have tested. Here is a simple 2D test case. I assume that if there were mistakes in my output, paraview would not be able to read it at all, even in sequential. That is why I assume that the error comes from paraview.
[serpentine_000001_bp4.tar.xz](/uploads/c14cd6395316ae05ab1dc7159d4d92d6/serpentine_000001_bp4.tar.xz)Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/21504Subtract point selection doesn't work on the attached model2022-08-12T01:50:06-04:00Petr MelnikovSubtract point selection doesn't work on the attached model**Steps to reproduce**
1. Open the data set [case1_step0001_substep0001.vtu](/uploads/e42b59b155f4b4b103122184bfa4e2b3/case1_step0001_substep0001.vtu) from attachments
2. Select some points:
![Screenshot_from_2022-08-11_21-51-48](/upload...**Steps to reproduce**
1. Open the data set [case1_step0001_substep0001.vtu](/uploads/e42b59b155f4b4b103122184bfa4e2b3/case1_step0001_substep0001.vtu) from attachments
2. Select some points:
![Screenshot_from_2022-08-11_21-51-48](/uploads/e3209f00f5ae324350eea05354914955/Screenshot_from_2022-08-11_21-51-48.png)
3. Substract selection:
![Screenshot_from_2022-08-11_21-54-41](/uploads/1bae110fcab4e8655458b544514e8c27/Screenshot_from_2022-08-11_21-54-41.png)
4. But the points are still selected:
![Screenshot_from_2022-08-11_21-53-42](/uploads/3f90a9ec102567603efad9b37a9e99da/Screenshot_from_2022-08-11_21-53-42.png)
PS.
On the same file, there is a problem with the lack of a pop-up information window (Hover Points On) when the mouse pointer is over the selected point. Perhaps the issues are related.https://gitlab.kitware.com/paraview/paraview/-/issues/21466ParaView crashes when selecting "Use Window Location" for Text Source positio...2024-03-07T20:23:50-05:00Artem BodrinParaView crashes when selecting "Use Window Location" for Text Source position after a state loadIf Text Source was saved with "AnyLocation" property set, switching it to "Use Window Location" in Display dock after a state load crashes ParaView.
Affected versions: 5.9.1, 5.10.1
![paraview_crash](/uploads/5c1d683f2cdb7dee606b38128...If Text Source was saved with "AnyLocation" property set, switching it to "Use Window Location" in Display dock after a state load crashes ParaView.
Affected versions: 5.9.1, 5.10.1
![paraview_crash](/uploads/5c1d683f2cdb7dee606b38128ef23aa8/paraview_crash.mp4)
One of the possible solutions (no crash):
```c++
//-----------------------------------------------------------------------------
void pqTextLocationWidget::radioButtonLocationClicked()
{
auto button = this->Internals->Ui.buttonGroupLocation->checkedButton();
// --- there can be no checked button after a state loaded
if (!button)
{
button = this->Internals->Ui.toolButtonUL;
button->setChecked(true);
}
QString locationStr(button->property("location").toString());
this->setWindowLocation(locationStr);
}
```
The other one is to set a default checked button in UI file. Did not tested that.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21454Feature Edges does not take into account ghostcells in parallel2022-10-18T09:41:14-04:00Eloise BFeature Edges does not take into account ghostcells in parallelHello,
I have this script which generate a data, generate ghostcells and display in feature edges two views: the original data (left) and data with ghotcells (right).
[testFeaturesEdges.py](/uploads/57e404961776d6b5cdf79abb47756c3c/tes...Hello,
I have this script which generate a data, generate ghostcells and display in feature edges two views: the original data (left) and data with ghotcells (right).
[testFeaturesEdges.py](/uploads/57e404961776d6b5cdf79abb47756c3c/testFeaturesEdges.py)
When I execute this script in builtin we can see in both renderviews a cube, however, when I execute it in parallel, we can see even after ghostcells generation, the cube stays "splitted".
Is there something I do wrong ?
I reproduce this with a paraview@master (built yesterday).
Regards,
Eloïse5.11 (Spring 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)