ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-23T13:26:07-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17458Multiple renders when loading a state file2021-03-23T13:26:07-04:00Utkarsh AyachitMultiple renders when loading a state fileHere's a simple state file [sphere.pvsm](/uploads/ba8c729a658954cee96af99ce5151898/sphere.pvsm)
When one loads this file in ParaView UI, there are 3 render calls that happen. There should only be 1.Here's a simple state file [sphere.pvsm](/uploads/ba8c729a658954cee96af99ce5151898/sphere.pvsm)
When one loads this file in ParaView UI, there are 3 render calls that happen. There should only be 1.https://gitlab.kitware.com/paraview/paraview/-/issues/17452Getting "Called attribute on invalid object" warnings2024-03-07T20:47:44-05:00Kenneth MorelandGetting "Called attribute on invalid object" warningsI don't know if it's just me, but I am getting a message in the output window with the text "Called attribute on invalid object" followed by an integer id whenever I load disk_out_ref. To get the error, I just open disk_out_ref.ex2 and h...I don't know if it's just me, but I am getting a message in the output window with the text "Called attribute on invalid object" followed by an integer id whenever I load disk_out_ref. To get the error, I just open disk_out_ref.ex2 and hit apply. I get the following response:
![Screen_Shot_2017-05-18_at_4.38.43_PM](/uploads/c7011444baba4bb544f4e5db694482e2/Screen_Shot_2017-05-18_at_4.38.43_PM.png)
This is on ParaView 5.4 RC2 (binary downloaded from Kitware) on a Mac 10.11.6.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17443Using Paraview ParticleTracer crashes program2024-03-07T20:47:43-05:00Nolan Dyck (NauticalMile)Using Paraview ParticleTracer crashes programI have been experiencing this issue with:
- Paraview 5.2.0 and 5.4.0 on Windows 7
- Paraview 5.2.0 on Fedora
I have run a simple, transient flow case using Ansys CFX and exported the results to the ensight (Gold, ASCII) format using ...I have been experiencing this issue with:
- Paraview 5.2.0 and 5.4.0 on Windows 7
- Paraview 5.2.0 on Fedora
I have run a simple, transient flow case using Ansys CFX and exported the results to the ensight (Gold, ASCII) format using the export option from CFX-solve. I have imported the ensight case file into Paraview and verified the solution can be visualized by stepping through the timesteps and watching the fields change on a `Slice` filter.
I then used the `ExtractSelection` filter to select the inlet boundary (from the vtkMultiBlockDataSet). I then created the `ParticleTracer` filter using the .case file object as the `Input` and the `ExtractSelection` filter as the `Seed Source`. Paraview is fine up until this point, but as soon as I hit reply I get the 'Paraview has stopped working` message on Windows while Paraview instantly closes without any messages in the terminal or otherwise on Fedora.
Here is a link to a .zip file containing all the Ensight files as well as the Paraview state file (27.3 MB):
https://drive.google.com/open?id=0B36AnwxERxoHSk96a0ZwR0tTQ3c
I have tried two workarounds:
- Using the `Slice` filter as the `Seed Source` instead of the `ExtractSelection` filter. Same error.
- Exporting the data to the .vtm file format and reloading it. Didn't load the timesteps properly.
I'm not sure whether this is related to this issue: https://gitlab.kitware.com/paraview/paraview/issues/12317 but that issue was closed because the OP did not provide data, which means the respondents could not reproduce the bug.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17436FindData and SpreadsheetView show negative (truncated) 64-bit IdType numbers ...2021-03-24T16:55:14-04:00Jean M. FavreFindData and SpreadsheetView show negative (truncated) 64-bit IdType numbers when running in parallelTesting 5.4-RC2:
I have a reader code for particles with PointIds of 64bit size.
When running FindData to do extraction in parallel, Ids seems truncated to 32-bit size both in the FindData spreadsheet and in a regular Spreadsheet view....Testing 5.4-RC2:
I have a reader code for particles with PointIds of 64bit size.
When running FindData to do extraction in parallel, Ids seems truncated to 32-bit size both in the FindData spreadsheet and in a regular Spreadsheet view. When NOT running in parallel, everything looks good. I have included a small test script with artificial data
![SerialRun](/uploads/81146cfba70b54ba7709a605cd85dde6/SerialRun.png)
![ParallelRun](/uploads/e3273b3f0e529a79899d1b0ce9e6270e/ParallelRun.png)
[UnstructuredGridWithIds.04.py](/uploads/0aa36542bd779755479a733305e65a04/UnstructuredGridWithIds.04.py)https://gitlab.kitware.com/paraview/paraview/-/issues/17432problem exporting to pdf2021-03-23T13:28:51-04:00Gwang-Jin Leeproblem exporting to pdfDear ParaView Developer,
I have used ParaView 5.2 in mac. In 5.2 version, x/y label with latex is well shown exporting to pdf. But in 5.3 and 5.4 x/y label with latex doesn't work when exporting to pdf.[test5.2.pdf](/uploads/ebc83dff547...Dear ParaView Developer,
I have used ParaView 5.2 in mac. In 5.2 version, x/y label with latex is well shown exporting to pdf. But in 5.3 and 5.4 x/y label with latex doesn't work when exporting to pdf.[test5.2.pdf](/uploads/ebc83dff547357d816bf81b4592abe29/test5.2.pdf)
[test5.4.pdf](/uploads/a6b1454188783ac96d59f3bd5f01aad6/test5.4.pdf)
Best regards,
Gwang-Jinhttps://gitlab.kitware.com/paraview/paraview/-/issues/17431Volume rendering frequent refresh2018-02-26T13:16:35-05:00W. Alan ScottVolume rendering frequent refresh@utkarsh.ayachit @kmorel I think I have replicated the too frequent refresh volume rendering using can.exo. I believe this happens other times, but this is a start. I am sure we can create a simpler scenario, but here is the one I know...@utkarsh.ayachit @kmorel I think I have replicated the too frequent refresh volume rendering using can.exo. I believe this happens other times, but this is a start. I am sure we can create a simpler scenario, but here is the one I know shows the refresh (both on the client side, and server side). By the way, this refresh takes about 15 seconds every time it goes off on my big data. It is maddeningly slow.
* Linux, 5.3.0, remote server (16 ranks).
* can.exo. All vars on. Apply. Move forward 1 timestep. Paint by DISPL. Opacity 0.4.
* can.exo. All vars on. Apply. Paint by VEL. Volume Render.
* Sources/ Text. Apply.
* Sources/ Annotate Time. Apply. Place in the lower left corner.
* Now, for the meat of the bug. Tools/ Timer log. Change Tim Threshold to 0.001. Clear. Close.
* Drag your mouse across the Text, towards the Tools. Click on Tools. Bring up Timer Log.
* BUG - you will see entries (Still Renders) in the local, and remote side in the timer log. This should not have happened.
* This also occurs if you move across the color legend, annotate time, etc.
* Side bug - it is incredibly easy to leave the white focus block around the text. Please get rid of this unless a user has his mouse down.
Suggestion - don't draw a focus around ANY text on the screen if you are using a preset location, or the mouse isn't down.
* Next way to create refreshes. Make ParaView somewhat smaller. Open the Timer Log, place it left of ParaView. Timer Log. Clear.
* Now, move your mouse onto the Pipeline Browser, click on the first can. Click on the second can. Back to the Timer Log. Refresh.
* Bug - more Still Renders.
Summary
-------
1. [ ] mouse-over renders triggered by annotations around 2D text
2. [x] render triggered from clicks in UI entities e.g. Pipeline Browser.
3. [ ] side-bug: it is incredibly easy to leave the white focus block around the texthttps://gitlab.kitware.com/paraview/paraview/-/issues/17429Preserve selection state in Multiblock Inspector even when data changes2023-06-15T16:04:40-04:00Utkarsh AyachitPreserve selection state in Multiblock Inspector even when data changes* Open can.ex2, Apply
* Go to **multiblock inspector** and click on **Unnamed block ID: 1..**. The should get highlighted in the widget and in the render view
* Now change some reader parameter e.g. toggle arrays that are loaded. Hit App...* Open can.ex2, Apply
* Go to **multiblock inspector** and click on **Unnamed block ID: 1..**. The should get highlighted in the widget and in the render view
* Now change some reader parameter e.g. toggle arrays that are loaded. Hit Apply.
The selection shown in the **multiblock inspector** gets cleared. This is a bug.
Relates to paraview/paraview#17421https://gitlab.kitware.com/paraview/paraview/-/issues/17427Increase width of the float over messages2018-02-26T13:17:02-05:00W. Alan ScottIncrease width of the float over messagesPlease increase the width of the messages that appear when you float your mouse over items in the GUI. An example is
* Wavelet. Apply.
* Programmable filter. Now, float over the Script area. The message is too narrow.Please increase the width of the messages that appear when you float your mouse over items in the GUI. An example is
* Wavelet. Apply.
* Programmable filter. Now, float over the Script area. The message is too narrow.https://gitlab.kitware.com/paraview/paraview/-/issues/17419Hierarchical fractal and extract AMR blocks errors in parallel.2020-05-05T03:24:10-04:00W. Alan ScottHierarchical fractal and extract AMR blocks errors in parallel.I am now seeing the following. Replicate as follows:
Linux, master (), remote server. I am running 16 ranks. Debug build client and server.
create Hierarchical Fractal source, apply
create Extract AMR Blocks
Now, turn on only ...I am now seeing the following. Replicate as follows:
Linux, master (), remote server. I am running 16 ranks. Debug build client and server.
create Hierarchical Fractal source, apply
create Extract AMR Blocks
Now, turn on only level 4. Then, try turning all levels on. Both times we get the following. Should this be fixed also?
```
ERROR: In /projects/viz/paraview/src/ParaView/5.4.0-junk-sb/ParaView5/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 377
vtkMultiBlockDataSet (0x2ff1060): Structure does not match. You must use CopyStructure before calling this method.
ERROR: In /projects/viz/paraview/src/ParaView/5.4.0-junk-sb/ParaView5/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 377
vtkMultiBlockDataSet (0x3b97d20): Structure does not match. You must use CopyStructure before calling this method.
```
Utkarsh's comments:
That's a bug with the filter. More likely that the AMR fractal is buggy in parallel -- a less critical concern since that source has limited impact.https://gitlab.kitware.com/paraview/paraview/-/issues/17412Comments and discussion on the new color legend2024-03-07T20:47:43-05:00W. Alan ScottComments and discussion on the new color legend@utkarsh.ayachit @cory-quammen @kmorel Instead of blasting everyone with e-mail, I thought we could have a discussion here. I am looking at the new color legend, and have two topics of discussion. I am using master, can.exo, painting b...@utkarsh.ayachit @cory-quammen @kmorel Instead of blasting everyone with e-mail, I thought we could have a discussion here. I am looking at the new color legend, and have two topics of discussion. I am using master, can.exo, painting by displacement magnitude and Z. One way to quickly look at the numbers is to flip to File/ Settings/ Reset and clamp every timestep.
1) My first blush is that the color bar is too thin. It is somewhat hard to read. In the new color legend editor, we can change the width. It is currently 10. I would like the default changed to somewhere between 15 and 20. (I think I prefer 16). Thoughts?
2) I had to look carefully at the dashes to the left of the numbers, to make sure they weren't negative values. I worry this is confusing. I just had a ParaView non user take a look at can/ displacement magnitude, and she guessed they were all negative. Unfortunately, I don't have any great ideas... One possible idea would be to move the numbers further to the right. Another would be to lengthen the dash, and have it cover some of the color bar. Thoughts?
- [x] Clicking the color legend does not change its **Window Location** to "Any Location"
- [ ] The "grab area" is incorrectly placed for the case of Ticks left/bottom.
- [x] Change default width of the color bar to 16
- [x] Change dash from current to what Cory presents below - i.e., make the dashes longer, and touching the color bar.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17409ParaView is unable to properly read a transient Ensight case file using the c...2021-10-11T11:48:38-04:00Dave CorsonParaView is unable to properly read a transient Ensight case file using the change_coords_only optionWhen reading the attached EnSight case file, Paraview does not properly acknowledge the "change_coords_only" option which eliminates the need to re-write the connectivity at each time step of a transient moving mesh simulation. When the...When reading the attached EnSight case file, Paraview does not properly acknowledge the "change_coords_only" option which eliminates the need to re-write the connectivity at each time step of a transient moving mesh simulation. When the data is read, Paraview shows the first time step properly, but will not sweep through time.[ensightReaderIssue.7za](/uploads/a515641713921419cfe7895c816f17da/ensightReaderIssue.7za)Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/17400Unable to delete source from pipeline browser with special characters on wind...2020-05-06T22:55:26-04:00RustemUnable to delete source from pipeline browser with special characters on windows.1. Create any Source
2. Rename it to "μ"
3. Try to delete it
Also in the Edit section we can see "Undo Delete ?"
Windows 8.11. Create any Source
2. Rename it to "μ"
3. Try to delete it
Also in the Edit section we can see "Undo Delete ?"
Windows 8.1https://gitlab.kitware.com/paraview/paraview/-/issues/17399OSPRay: volume rendering is not displayed before an interaction event2024-03-07T20:47:43-05:00Joachim PouderouxOSPRay: volume rendering is not displayed before an interaction eventThe problem appears with the OSPRay volume mapper in PV 5.3:
Rendering is not performed or not performed correctly when enabling the "OSPRay Based" volume rendering mode.
To reproduce: Create a Wavelet, show it with Volume representati...The problem appears with the OSPRay volume mapper in PV 5.3:
Rendering is not performed or not performed correctly when enabling the "OSPRay Based" volume rendering mode.
To reproduce: Create a Wavelet, show it with Volume representation and select "OSPRay Based": image is cleared and the cube won't appear until you perform a mouse action in the view.5.13 (Summer 2024)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17392Qt 5: 3D widgets not working correctly in Comparative View2020-05-22T13:56:37-04:00Utkarsh AyachitQt 5: 3D widgets not working correctly in Comparative ViewThis is Qt 5 issue; not present with built with Qt 4 (ParaView version: 5.3.0-374-g54c6f9c)
Steps:
* Start paraview, close active view and create a **Render View (Comparative)**.
* Sphere, Apply,
* Elevation --- the 3D widget won't...This is Qt 5 issue; not present with built with Qt 4 (ParaView version: 5.3.0-374-g54c6f9c)
Steps:
* Start paraview, close active view and create a **Render View (Comparative)**.
* Sphere, Apply,
* Elevation --- the 3D widget won't show up in all the views or raise OpenGL errors as follows:
```
ERROR: In /home/utkarsh/Kitware/ParaView3/ParaView/ParaViewCore/VTKExtensions/Rendering/vtkPVDefaultPass.cxx, line 59
vtkPVDefaultPass (0x55c6730): failed after Render 1 OpenGL errors detected
0 : (1282) Invalid operation
```https://gitlab.kitware.com/paraview/paraview/-/issues/17388Surface LIC fails with zero values2021-03-23T13:20:10-04:00Mathieu Westphal (Kitware)Surface LIC fails with zero valuesSurface LIC fails to generate anything with zero values.
How to reproduce :
- Open ParaView
- Load SurfaceLIC plugin
- Open multicomb_2.vts
- Set Representation to SurfaceLIC
![licfails](/uploads/d17e0697422b1bfc69369ad7692afb29/licfai...Surface LIC fails to generate anything with zero values.
How to reproduce :
- Open ParaView
- Load SurfaceLIC plugin
- Open multicomb_2.vts
- Set Representation to SurfaceLIC
![licfails](/uploads/d17e0697422b1bfc69369ad7692afb29/licfails.png)https://gitlab.kitware.com/paraview/paraview/-/issues/17383Add option to python calculator to perform an operation on all arrays2021-03-23T13:20:23-04:00Shawn WaldonAdd option to python calculator to perform an operation on all arrays#16838 should really be solved by the Python calculator having an option to "divide * by volume". We should add support for performing an operation like this on all arrays.#16838 should really be solved by the Python calculator having an option to "divide * by volume". We should add support for performing an operation like this on all arrays.https://gitlab.kitware.com/paraview/paraview/-/issues/17380non-orthogonal axes not being transformed in pvpython2021-11-30T23:41:47-05:00Steven Hahnnon-orthogonal axes not being transformed in pvpythonIn pvpython, the grid axes are not being transformed by the change-of-basis matrix. Below is a trace of generating and transforming a sheared wavelet source, enabling the axes grid and creating a screenshot (update the plugins directory ...In pvpython, the grid axes are not being transformed by the change-of-basis matrix. Below is a trace of generating and transforming a sheared wavelet source, enabling the axes grid and creating a screenshot (update the plugins directory and screenshot location before running).
[NonOrthogonalSource.py](/uploads/dc19bd7f6a461e46bc50868b0e5f509e/NonOrthogonalSource.py)
From the python shell inside ParaView GUI, the axes grid is transformed.
![NonOrthogonalSourceInParaView](/uploads/339b0a4db0039a55f538812355c51f4a/NonOrthogonalSourceInParaView.png)
Running the same script with pvpython generated an orthogonal axes grid.
![NonOrthogonalSourceInPVPython](/uploads/b579d69f2e14718372e77cbb4ac63d80/NonOrthogonalSourceInPVPython.png)
I think the view isn't being added to the [pqModelTransformSupportBehavior](https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/ApplicationComponents/pqModelTransformSupportBehavior.cxx#L126) class, but am not how to fix and/or work around this issue.https://gitlab.kitware.com/paraview/paraview/-/issues/17377timeseries reader/writer workflow runs out of memory and hangs2024-03-07T20:47:43-05:00John Patchetttimeseries reader/writer workflow runs out of memory and hangsMost recently seen with the following workflow on the yA31 dataset (dssdata.org) on 48 cores it made it through 76 files before hanging and at least the first two machines showed the pvserver processes combined using nearly 100% of the m...Most recently seen with the following workflow on the yA31 dataset (dssdata.org) on 48 cores it made it through 76 files before hanging and at least the first two machines showed the pvserver processes combined using nearly 100% of the machines memory. Time steps 76 and 77 don't use that much memory alone.
1. Load a file series of *.vtm files that contain only vtus.
2. Merge blocks -> Threshold
3. Save Data, Select pvtu, write all timesteps as file series, Appended, zlib compression5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/17373Don't default X, Y and Z on for quartile plots2018-02-26T13:17:02-05:00W. Alan ScottDon't default X, Y and Z on for quartile plots* 5.3.0, Linux, local server.
* can.exo. All vars on. Apply.
* Select a point.
* Plot selection over Time.
Notice that the X, Y and Z locations are plotted. Don't do that by default.* 5.3.0, Linux, local server.
* can.exo. All vars on. Apply.
* Select a point.
* Plot selection over Time.
Notice that the X, Y and Z locations are plotted. Don't do that by default.https://gitlab.kitware.com/paraview/paraview/-/issues/17367missing display with very large points dataset2023-02-10T09:46:04-05:00Jean M. Favremissing display with very large points datasetI have some big comology data which I cannot share easily since it is big. 368 million points
When using regular ParaView "Points" display, a lot of the dataset is missing (see attached image).
When using OSPRay points, everything look...I have some big comology data which I cannot share easily since it is big. 368 million points
When using regular ParaView "Points" display, a lot of the dataset is missing (see attached image).
When using OSPRay points, everything looks good (see attached image) . The OSPRay rendering confirms my data is loaded correctly. However, because of the higher memory cost, OSPRay is not trivial to use. So, something is going wrong in the standard Points rendering (1-pixel Points). I am using ParaView master.
I have noticed that I can go up to 340 millions points, everything looks good. Beyond that threshold (I am not sure exactly where because my next dataset is 368 millions points), ParaView fails to render.
![points](/uploads/1876c37f89a6aadf09d6dea7f5c670cb/points.png)
![ospray](/uploads/31fa2229b4713e1c0c5879605ee221ec/ospray.png)