ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T09:15:17-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22178tkinter fails to import in ParaView binary release2023-06-15T09:15:17-04:00Mathieu Westphal (Kitware)tkinter fails to import in ParaView binary releasetkinter fails to import in ParaView binary release
```
>>> import tkinter
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/glow/dev/paraview/others/ParaView-master-5.11.1-1280-gd982f83420-MPI-Linux-...tkinter fails to import in ParaView binary release
```
>>> import tkinter
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/glow/dev/paraview/others/ParaView-master-5.11.1-1280-gd982f83420-MPI-Linux-Python3.9-x86_64/lib/python3.9/tkinter/__init__.py", line 37, in <module>
import _tkinter # If this fails your Python may not be configured for Tk
ModuleNotFoundError: No module named '_tkinter'
>>> vim /home/glow/dev/paraview/others/ParaView-master-5.11.1-1280-gd982f83420-MPI-Linux-Python3.9-x86_64/lib/python3.9/tkinter/__init__.py
File "<stdin>", line 1
vim /home/glow/dev/paraview/others/ParaView-master-5.11.1-1280-gd982f83420-MPI-Linux-Python3.9-x86_64/lib/python3.9/tkinter/__init__.py
^
SyntaxError: invalid syntax
```
tkinter files are shipped but it seems non-fonctionnal.
Works perfectly with a local buildhttps://gitlab.kitware.com/paraview/paraview/-/issues/22159REQUIRED_PLUGINS mechanism is non fonctionnal on Windows2023-06-01T06:51:19-04:00Mathieu Westphal (Kitware)REQUIRED_PLUGINS mechanism is non fonctionnal on WindowsREQUIRED_PLUGINS mechanism (in `paraview_client_add` CMake macro) is non fonctionnal on Windows.
Steps to reproduce (on Windows):
- compile and install ParaView
- compile SimpleParaView example
- run simple_paraview
- MyElevation filte...REQUIRED_PLUGINS mechanism (in `paraview_client_add` CMake macro) is non fonctionnal on Windows.
Steps to reproduce (on Windows):
- compile and install ParaView
- compile SimpleParaView example
- run simple_paraview
- MyElevation filter is not available
FYI @ben.boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22157ParaView 5.11 crashes when opening vth file2023-06-02T04:01:19-04:00Xiaowen ShanParaView 5.11 crashes when opening vth file[crash.zip](/uploads/31c4efb6046bb929ebfaf63efc4f71d1/crash.zip)
As the title says, the window disappears while clicking the vth file. the vti files that the vth refers to are OK.
Moving the vti files to the folder of vth file won't he...[crash.zip](/uploads/31c4efb6046bb929ebfaf63efc4f71d1/crash.zip)
As the title says, the window disappears while clicking the vth file. the vti files that the vth refers to are OK.
Moving the vti files to the folder of vth file won't help. Hand-editing the vth file to remove the directory part of the file names won't help either. But, if remove all the Blocks except the first one (level 0), it won’t crash.
The files and directories were created by vtkXMLPUniformGridAMRWriter.https://gitlab.kitware.com/paraview/paraview/-/issues/22155Segfault when loading ASCII PVTU2023-06-15T15:01:43-04:00FG-TUMSegfault when loading ASCII PVTUThis issue is a follow-up to the discussion over at the ParaView forums: https://discourse.paraview.org/t/segfault-when-loading-pvtu/12082.
TL;Dr:
Opening a pvtu file, which references 64 vtu files with 20MB each, can cause segfaults. T...This issue is a follow-up to the discussion over at the ParaView forums: https://discourse.paraview.org/t/segfault-when-loading-pvtu/12082.
TL;Dr:
Opening a pvtu file, which references 64 vtu files with 20MB each, can cause segfaults. The stack trace suggests that it has to do with the data being in ASCII format.
Data to reproduce: https://send.kitware.io/download.php?id=2037&token=qfJiGxmcc4FltggysAjMqhVkCNtZG2h3https://gitlab.kitware.com/paraview/paraview/-/issues/22152master builds with mesa have black screen2023-05-31T09:41:09-04:00W. Alan Scottmaster builds with mesa have black screenThere is an issue with nightly and mesa. The screen ends up this weird, moving blackness. Screenshot attached.
* Linux, nightly (ParaView-master-5.11.1-1210-g085d19f636-MPI-Linux-Python3.9-x86_64.tar.gz).
* ssh -Y your favorite land...There is an issue with nightly and mesa. The screen ends up this weird, moving blackness. Screenshot attached.
* Linux, nightly (ParaView-master-5.11.1-1210-g085d19f636-MPI-Linux-Python3.9-x86_64.tar.gz).
* ssh -Y your favorite landing point to software render.
* ./paraview --mesa --backend llvmpipe
@cory.quammen @ben.boeckel
![Screenshot_2023-05-23_at_11.33.51_AM](/uploads/a016aad70244e7ac332500ee92905bc2/Screenshot_2023-05-23_at_11.33.51_AM.png)5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/22142viewports are missing a render2023-07-07T10:41:07-04:00W. Alan Scottviewports are missing a renderWe are missing a refresh when running multiple viewports and changing colormaps. Here is how to replicate.
* 5.11.1, Linux, builtin.
* can.exo. Apply.
* (Move forward a few frames. Not necessary, but it's prettier.)
* Color by ACCL.
*...We are missing a refresh when running multiple viewports and changing colormaps. Here is how to replicate.
* 5.11.1, Linux, builtin.
* can.exo. Apply.
* (Move forward a few frames. Not necessary, but it's prettier.)
* Color by ACCL.
* Split screen horizontally.
* Turn visibility on for this view. Paint by ACCL also.
* Color Map Editor. Preset. Black Body Radiation. Apply. Close.
The two viewports are painted by different color maps.
* Place your mouse on the left viewport, and drag around with the left mouse button. Correct color map is then used.
ParaView is missing a render when color maps are changed.
![Screenshot_2023-05-16_at_2.48.57_PM](/uploads/1fed68ed57b32e2aa2469841507b34fe/Screenshot_2023-05-16_at_2.48.57_PM.png)5.12 (Winter 2023)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22137Saving font settings as default doesn't work in charts2023-05-10T04:16:30-04:00Thomas GallandSaving font settings as default doesn't work in chartsWhen saving current view settings as default with charts, text properties are well saved, except of the font.
![image](/uploads/126be81e71e9521c738d9811df824d4f/image.png)
Steps to reproduce:
- Open a `Wavelet`
- Apply the `Plot Over L...When saving current view settings as default with charts, text properties are well saved, except of the font.
![image](/uploads/126be81e71e9521c738d9811df824d4f/image.png)
Steps to reproduce:
- Open a `Wavelet`
- Apply the `Plot Over Line` filter, a new `Line Char View` is created
- In the `View` properties, `Legend Properties` category, change the font to `Courier`
- Hit the `Save current view settings ...` button
- Open a new chart view, show the result of `Plot Over Line` in it
- Font is back to Arial
Notes:
- Concerns all font properties in the view (title, legend, axis).
- Other properties (bold, font color, etc.) are well saved.
- Note that the copy / paste of properties works well with fonts.https://gitlab.kitware.com/paraview/paraview/-/issues/22136Using Time Manager crashes Paraview when connected to Catalyst2023-11-08T21:11:22-05:00Louis GombertUsing Time Manager crashes Paraview when connected to CatalystHello, I have randomly found a crash in Paraview nightly build, which has to do with the time manager.
Here are the steps reproduce the crash :
- Open a time-varying dataset (for example `can.ex2`)
- Click on `Apply` to view it in th...Hello, I have randomly found a crash in Paraview nightly build, which has to do with the time manager.
Here are the steps reproduce the crash :
- Open a time-varying dataset (for example `can.ex2`)
- Click on `Apply` to view it in the main render view
- Display the new time manager (View > Time Manager)
- Start Catalyst (Catalyst > Connect)
- change the time to 0.11111 (for can.ex2) in the Time Manager using the drop-down menu
- manually change the view orientation in the render view using the mouse
- Click on the settings wheel of the time manager on the right of the panel
At this step, Paraview segfaults.
Environment : Linux Mint 21.1 x86_64, on latest binary Paraview nightly build
I can provide more information if needed.https://gitlab.kitware.com/paraview/paraview/-/issues/22125vtkSMStateVersionController missing animated property update2023-05-02T11:08:08-04:00Mathieu Westphal (Kitware)vtkSMStateVersionController missing animated property updateAs discussed here: https://gitlab.kitware.com/paraview/paraview/-/issues/21782#note_1354051, vtkSMStateVersionController (and _backwards_compatibility_helper.py for that matter) do not take care of update animated properties names, hence...As discussed here: https://gitlab.kitware.com/paraview/paraview/-/issues/21782#note_1354051, vtkSMStateVersionController (and _backwards_compatibility_helper.py for that matter) do not take care of update animated properties names, hence making older state files with animated properties unusable in newer versions of ParaView.
@cory.quammen @thomas.gallandhttps://gitlab.kitware.com/paraview/paraview/-/issues/22123Pick Center does not work after a Custom Filter2023-10-31T08:43:34-04:00Tiffany ChhimPick Center does not work after a Custom FilterThe "**Pick Center**" action does not seem to work on the **output of a Custom Filter**.
The center is **set to the origin instead of landing on the surface of the mesh**.
Steps to reproduce:
- Create a simple Custom Filter with a Wav...The "**Pick Center**" action does not seem to work on the **output of a Custom Filter**.
The center is **set to the origin instead of landing on the surface of the mesh**.
Steps to reproduce:
- Create a simple Custom Filter with a Wavelet
- Generate the newly created Custom Filter to create a Wavelet
- Apply
- Click on the Pick Center toolbar icon
- Click on the mesh
![BrokenPickCenterAfterCustomFilter](/uploads/4be092e2bd6a2886e5bb82fdc67b31f3/BrokenPickCenterAfterCustomFilter.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/21856Link Objects: does not work correctly for Render Views2023-06-15T08:11:24-04:00Julien FaustyLink Objects: does not work correctly for Render Views## Problem statement
When using the "Link Manager" to link objects in ParaView, one can link two filters, sources or representations together (i.e. link all their properties) but you cannot do the same thing for "Render Views". The link...## Problem statement
When using the "Link Manager" to link objects in ParaView, one can link two filters, sources or representations together (i.e. link all their properties) but you cannot do the same thing for "Render Views". The link manager shows an `Unknown` entry in properties:
![image](/uploads/3bd9a13fb42d336b20608ebad026f7ad/image.png)
This link between "Render Views" links the cameras of the two views without linking any of their properties.https://gitlab.kitware.com/paraview/paraview/-/issues/21841pvserver interactive points -> tag missmatch -> exit2023-03-28T21:48:46-04:00Dani Schmidpvserver interactive points -> tag missmatch -> exitI use a ParaView 5.11 client (windows/linux give same result) and pvserver on a linux machine. Generally works very well, but with certain types of interactions such as ‘Hover Points On’ I get tag missmatch and pvserver exits. This issue...I use a ParaView 5.11 client (windows/linux give same result) and pvserver on a linux machine. Generally works very well, but with certain types of interactions such as ‘Hover Points On’ I get tag missmatch and pvserver exits. This issues is confirmed by mwestphal (see https://discourse.paraview.org/t/pvserver-interactive-points-tag-missmatch-exit). I have not found a way to reproduce this with a synthetic dataset, so I provide an example dataset. Here are the steps to reproduce the issue:
1. Get the example dataset from https://www.dropbox.com/s/o8pomdziflyfypu/test.tar.gz?dl=1
2. Start pvserver on linux and connect from windows 5.11 ParaView
3. Load pvd data file. 3D model, quite a few variables, several timesteps
4. ‘Hover Points On’ works at this stage
5. I have two materials in my model, the respective domains are marked by phase=0 and phase=1. I only want to see the parts of the model with phase=1 and use a threshold filter set to 0.1 and 1.
6. If I now try to use ‘Hover Points On’ on the shown phase=1 part of the model then I get the tag missmatch. pvserver then states ‘Exiting…’ but gets stuck. Using Ctrl-C at this stage spits out a stack trace. You find the whole command line output below.
Thanks
Dani
```
Client connected.
( 572.906s) [pvserver ]vtkSocketCommunicator.c:849 ERR| vtkSocketCommunicator (0x1268d70): Tag mismatch: got 1, expecting 10.
( 572.942s) [pvserver ]vtkSocketCommunicator.c:849 ERR| vtkSocketCommunicator (0x1268d70): Tag mismatch: got 1, expecting 41235.
( 572.942s) [pvserver ]vtkSocketCommunicator.c:849 ERR| vtkSocketCommunicator (0x1268d70): Tag mismatch: got 1, expecting 41235.
( 585.484s) [pvserver ]vtkSocketCommunicator.c:783 ERR| vtkSocketCommunicator (0x1268d70): Could not receive tag. 1
( 585.484s) [pvserver ]vtkTCPNetworkAccessMana:295 ERR| vtkTCPNetworkAccessManager (0x1178c60): Some error in socket processing.
Exiting…
^C
Loguru caught a signal: SIGINT
Stack trace:
21 0x40196d /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x40196d]
20 0x7f5af397ad0a __libc_start_main + 234
19 0x40188e /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x40188e]
18 0x7f5af24e5654 vtkInitializationHelper::Finalize() + 100
17 0x7f5af13a8ae2 vtkProcessModule::Finalize() + 98
16 0x7f5aedd199fa /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/libvtkCommonCore-pv5.11.so.1(+0x6ae9fa) [0x7f5aedd199fa]
15 0x7f5aedbc0b29 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
14 0x7f5aeb3131b6 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libvtkRemotingViews-pv5.11.so.1(+0x1e81b6) [0x7f5aeb3131b6]
13 0x7f5ad7b44a89 vtkOSOpenGLRenderWindow::~vtkOSOpenGLRenderWindow() + 9
12 0x7f5ad7b44a1c vtkOSOpenGLRenderWindow::~vtkOSOpenGLRenderWindow() + 28
11 0x7f5ad7b449e3 vtkOSOpenGLRenderWindow::Finalize() + 83
10 0x7f5ad7b44914 vtkOSOpenGLRenderWindow::DestroyOffScreenWindow() + 36
9 0x7f5ad610866b OSMesaDestroyContext + 27
8 0x7f5ad61373e8 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0x1a93e8) [0x7f5ad61373e8]
7 0x7f5ad6135e38 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0x1a7e38) [0x7f5ad6135e38]
6 0x7f5ad6c33acb /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xca5acb) [0x7f5ad6c33acb]
5 0x7f5ad6ade9c5 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xb509c5) [0x7f5ad6ade9c5]
4 0x7f5ad6d9b544 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xe0d544) [0x7f5ad6d9b544]
3 0x7f5ad6c611a5 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xcd31a5) [0x7f5ad6c611a5]
2 0x7f5ad6c34a6b /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xca6a6b) [0x7f5ad6c34a6b]
1 0x7f5aed6577b2 pthread_cond_wait + 482
0 0x7f5af398fd60 /lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f5af398fd60]
( 613.056s) [pvserver ] :0 FATL| Signal: SIGINT
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21828categorical colormap does not update ranges2023-07-10T16:06:03-04:00Boonthanome Nouanesengsycategorical colormap does not update rangesWhen a variable is set to be shown with a categorical colormap, and the range changes over time, the colormap is not updated. If the variable is set to be shown normally, then the range does update. Example screenshots are below. Please ...When a variable is set to be shown with a categorical colormap, and the range changes over time, the colormap is not updated. If the variable is set to be shown normally, then the range does update. Example screenshots are below. Please have the colormap updated over time.
In the first screenshot, the cell variable `block_id` is shown, and the option `Interpret Values as Categories` is turned on. It is the first timestep, and the range is 0-1.
In the second screenshot, the second timestep is shown. The range of `block_id` is now 0-2, but the colormap has not updated, and the range is still 0-1.
Here is the example dataset shown in the screenshots: [grid.tar.gz](/uploads/674e991da64e09ec18633dc0f4652eb1/grid.tar.gz)
Steps to reproduce:
- Load the `grid` example dataset as a time series in Paraview
- Color by `block_id`
- Open the `Color Map Editor`, and click on `Interpret Values as Categories`
- Click forward in time in the VCR controls, and see if the color map range has been updated
- When going to the second timestep, the color map range should be 0-2, but it remains 0-1
@patchett2002 @yohann.bearzi @cory.quammen
![timestep0](/uploads/aa40caab81c2a3aa844bafbdefab9945/timestep0.png)
![timestep1](/uploads/b84bca4945044d9e1dc16f096d828655/timestep1.png)5.12 (Winter 2023)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21821Axis labels/titles carry shadow in LineChartView2023-03-16T11:42:26-04:00PfiffikusAxis labels/titles carry shadow in LineChartViewAs depicted in the screenshot at the bottom of the axis annotations mysterious pixels occur; visible on Windows/linux version of 5.11.0
![LabelShadow](/uploads/4910b7b60427a9a620cdceda8d66999f/LabelShadow.png)As depicted in the screenshot at the bottom of the axis annotations mysterious pixels occur; visible on Windows/linux version of 5.11.0
![LabelShadow](/uploads/4910b7b60427a9a620cdceda8d66999f/LabelShadow.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21807Plot Over Line Crash in recent versions (working fine in version 5.4.1)2023-03-09T11:33:24-05:00Joshua ObradorsPlot Over Line Crash in recent versions (working fine in version 5.4.1)I'm using ParaView 5.11.0 on Windows and noticed Plot Over Line leads to a crash under certain circumstances e.g. when the line intersects parts of the model that contain different properties (in my files POL crashes if done from top to ...I'm using ParaView 5.11.0 on Windows and noticed Plot Over Line leads to a crash under certain circumstances e.g. when the line intersects parts of the model that contain different properties (in my files POL crashes if done from top to bottom of the column but will not crash if done from Y=1200 to top).
I have verified that this does not happen in ParaView 5.4.1.
Any help on that would be much appreciated.
[Test_POL_015.plt](/uploads/0c6aef36996b541c0b4fd4560e43905d/Test_POL_015.plt)[Test_POL_015.xmf](/uploads/64bd736f6c277249ecbad7cf45bfaf1d/Test_POL_015.xmf)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21795ExtractSurface causes the whole pipeline to execute twice when using MPI2024-02-02T15:27:53-05:00Eve Le GuillouExtractSurface causes the whole pipeline to execute twice when using MPIHi all,
I have noticed that sometimes Paraview executes twice some filters even when it is not needed when using MPI. This happens when the ExtractSurface filter is present in the Pipeline.
I use MPI 4.0.3 and Paraview 5.10.1 to which...Hi all,
I have noticed that sometimes Paraview executes twice some filters even when it is not needed when using MPI. This happens when the ExtractSurface filter is present in the Pipeline.
I use MPI 4.0.3 and Paraview 5.10.1 to which I added a line of code:
std::cout<< "In Here"<<std::endl;
The line is added at the beginning of the RequestData function of the file VTK/Filters/Core/vtkThreshold.cxx and is only here to show that Threshold executes twice.
Here is my pipeline (with the file [here](/uploads/4319772311bdc9cb46291b381a9d5e60/double_execution.pvsm)):
Wavelet > Threshold > ExtractSurface
Both Threshold and ExtractSurface are visible. I then execute this on Paraview, using:
mpirun -n 2 pvserver
and
paraview
When this is executed, I can see that the message "In Here" appears 4 times, even though it is only supposed to be shown twice. Threshold is therefore executed twice. This also happens when the Pipeline is in Python code and executed with `pvbatch`. However, if executed on only one process, the bug doesn't appear.
This is a problem for me as my Paraview plugin cashes information and the second execution can cause errors.
This was confirmed by @mwestphal
Thanks for any help.
==========================================================
Steps to reproduce (master and 5.11)
- mpiexec -np 2 ./bin/pvserer
- ./bin/paraview
- connect to server
- Wavelet, Apply
- Treshold, Apply
- Hide wavelet
- Extract Surface, Apply
- Show Treshold
- Tools -> TimerLog -> Refresh/Clear/ShowAll
- Change the treshold value slightly, Apply
- Refresh timer log
```
Execute Threshold1 id: 31612, 0.001968 seconds
Execute Threshold1(UnstructuredGridRepresentation)/SurfaceRepresentation id: 31836, 0.001843 seconds
Execute Threshold1(ExtractSelection:0) id: 31613, 1.9e-05 seconds
Execute Threshold1 id: 31612, 0.000968 seconds
```
The last line is supplementary, shows that it is run two times and should not happen.
If you change any of the following parameters, the bug does not happen.
- Do not add the extract surface
- Replace the extract surface by any other filter (eg AppendDataset)
- run the server without MPI or builtinSpiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21792Screenshot taken with split view containing a spreadsheetview is wrongly fram...2023-03-02T03:33:15-05:00Will BainbridgeScreenshot taken with split view containing a spreadsheetview is wrongly framed and has wrong resolutionTo reproduce, load some data, split the view, create a spreadsheet view, and frame the data nicely in one render view.
![Screenshot1](/uploads/4a44dee95f10e3bdb0d9e88786837ba2/Screenshot1.png)
Select the render view and go to File > Sa...To reproduce, load some data, split the view, create a spreadsheet view, and frame the data nicely in one render view.
![Screenshot1](/uploads/4a44dee95f10e3bdb0d9e88786837ba2/Screenshot1.png)
Select the render view and go to File > Save Screenshot.
![Screenshot2_](/uploads/9b2a78ed75457b5196655b989d80de5f/Screenshot2_.png)
Enter a file name and hit OK. Note now that the views shift to the left and reduce in size.
![Screenshot3_](/uploads/31cdf72b0932dc2057ffd2067ddd4412/Screenshot3_.png)
Retain the default resolution and such and hit OK. The resulting image has a reduced size, and parts have been clipped out of the image.
![Result_](/uploads/a1b7ffc785ed865358c99bc3f66fad71/Result_.png)
Edit: We first noticed this in 5.8.1. This bug was not present in 5.6.3.https://gitlab.kitware.com/paraview/paraview/-/issues/21791Bounds from CGNS zone are based on all coordinates array, not on actual cells2023-03-16T03:27:19-04:00Pierre CrepierBounds from CGNS zone are based on all coordinates array, not on actual cellsHello,
First, my apologies for that strange title, I am not sure how I can put what I am seeing into words.
So here is the complete story, in less compact format:
We use the CGNS format as output of our CFD solver.
The files contain tw...Hello,
First, my apologies for that strange title, I am not sure how I can put what I am seeing into words.
So here is the complete story, in less compact format:
We use the CGNS format as output of our CFD solver.
The files contain two zones: Volume and Surfaces
These two zones contain arrays defining all vertices present in the zone.
This means that the Volume zone contains all vertices, and the Surfaces zone contains all boundary vertices.
Both zones can contain multiple sub-zone: various grids for the Volume zone, and the boundary cells for the surfaces.
To extract a specific boundary, I use the extract block filter, and choose the blocks I want.
The issue I am seeing now with version 5.11 is that if I extract only one zone, the bounds still correspond to all vertices, and not to the vertices shown on the screen.
This was not happening in 5.9
To reproduce:
1. Read the file, using the CGNS reader
2. extract the first block
3. look at the bounds: they are not what one expect it to be
So I have a feeling that the CGNS reader was changed and now only relies on the complete array of vertices to define the bounds instead of relying on the cells that are actually declared in the specific block.
I hope that makes the issue clearer. (and I attached an example file file too)
[cube.cgns](/uploads/fef0c968792bc24bf26243a26db568fd/cube.cgns)https://gitlab.kitware.com/paraview/paraview/-/issues/21790Default position of legend is not preserved2023-02-27T04:04:16-05:00Petr KryslDefault position of legend is not preservedThe problem has been described in the forum: https://discourse.paraview.org/t/default-settings-of-legend-not-saved/11480The problem has been described in the forum: https://discourse.paraview.org/t/default-settings-of-legend-not-saved/11480https://gitlab.kitware.com/paraview/paraview/-/issues/21780Obj Files cannot Play Sequentially2023-02-22T03:55:29-05:00Fan FengObj Files cannot Play SequentiallyAfter automatically loading an obj group with 4 digits as the suffix, the obj file is not switched based on the current frame number. It only stuck on the first obj file in the group.
[mesh0000.obj](/uploads/ae3f5bd2ae6c488700ac028eff99...After automatically loading an obj group with 4 digits as the suffix, the obj file is not switched based on the current frame number. It only stuck on the first obj file in the group.
[mesh0000.obj](/uploads/ae3f5bd2ae6c488700ac028eff997fb3/mesh0000.obj)
[mesh0001.obj](/uploads/0f95e5b8a4ee832bb213e5efe33fc069/mesh0001.obj)
[mesh0002.obj](/uploads/c64131d6a08b96a56e9ad6d9e22d670b/mesh0002.obj)
[mesh0003.obj](/uploads/76788c92af1edc67e42708a0819e29ff/mesh0003.obj)
[mesh0004.obj](/uploads/21745d991403d79e61efa7c99dd9c6ba/mesh0004.obj)
[mesh0005.obj](/uploads/040508ff3220a9b8b3155c774e32f6d5/mesh0005.obj)
[mesh0006.obj](/uploads/3049924681ca664f72eb15a753d36ee3/mesh0006.obj)
[mesh0007.obj](/uploads/7b798a7e3597725e4229cf008810f074/mesh0007.obj)
[mesh0008.obj](/uploads/cd253eb794835eedf2b25f0c01e23f81/mesh0008.obj)