ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-05-20T16:04:18-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19916Export Inspector: allow selecting of root directory for pvserver configs2020-05-20T16:04:18-04:00Utkarsh AyachitExport Inspector: allow selecting of root directory for pvserver configsThis is extracted from [#19073](https://gitlab.kitware.com/paraview/paraview/-/issues/19073#note_720701)
step 1: let's get the "export now" working, however clunky. For remote connections, we accept two separate Root Directories, one fo...This is extracted from [#19073](https://gitlab.kitware.com/paraview/paraview/-/issues/19073#note_720701)
step 1: let's get the "export now" working, however clunky. For remote connections, we accept two separate Root Directories, one for client side and one for server side. Data Extracts will export using the server-side root directory while Image Extracts including cinema/png/etc. will use the client side root directory.5.8.1Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19918PolyLine source points can't be changed manually in the GUI2020-06-04T21:41:06-04:00Mathieu Westphal (Kitware)PolyLine source points can't be changed manually in the GUI * run ParaView
* Sources -> PolyLine Source
* Points location can be edited be on validation, the value is reseted
A workaround is to use python with
```
p = GetActiveSource()
p.Points = [0.0, 1.0, 0.0, 1.0, 0.0, 0.0]
```
5.8.0 an... * run ParaView
* Sources -> PolyLine Source
* Points location can be edited be on validation, the value is reseted
A workaround is to use python with
```
p = GetActiveSource()
p.Points = [0.0, 1.0, 0.0, 1.0, 0.0, 0.0]
```
5.8.0 and master.5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19919Preview size not preserved in Save Screenshot for multiple views2020-05-13T16:57:37-04:00Utkarsh AyachitPreview size not preserved in Save Screenshot for multiple viewsSteps:
* Start paraview, builtin
* from view | preview, choose 1280x800 -- any size larger than your window size. You shuold get a "requested resolution too big for window" prompt. hit ok.
* select file | save screenshot and pick a fil...Steps:
* Start paraview, builtin
* from view | preview, choose 1280x800 -- any size larger than your window size. You shuold get a "requested resolution too big for window" prompt. hit ok.
* select file | save screenshot and pick a filename. The **Save Screenshot Options** dialog shows incorrect window size. Hit the ![image](/uploads/f7f531127584935e10a885856eb1fec2/image.png) button and then it shows the correct size. This is a bug.5.8.1Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19921Intermittent errors in Cell Centers2020-05-19T21:26:49-04:00Kenneth MorelandIntermittent errors in Cell Centers[A thread on discourse](https://discourse.paraview.org/t/paraview-cell-centers-possible-unstable-program-behavior/4310) has brought up a problem with the `Cell Centers` filter. The filter seems to be unstable in that it intermittently cr...[A thread on discourse](https://discourse.paraview.org/t/paraview-cell-centers-possible-unstable-program-behavior/4310) has brought up a problem with the `Cell Centers` filter. The filter seems to be unstable in that it intermittently creates bad centers. Here is a video from some data provided by the user. The geometry of the source does not change, but you can see the centers "sparkling" as in each frame you see an error in the computation.
![cell-centers-errors](/uploads/e671ea41df315c77b82106a5326128a6/cell-centers-errors.mp4)
I believe the issue is that this data stores its connectivity array as int32 values. In this condition, it causes the `vtkCellCenters` filter to get cell connections in a thread-unsafe way. That in turn causes threads to interfere with each other.
Diving in more deeply, I point to this code in `vtkUnstructuredGrid.cxx`, which is supposed to be thread safe.
```cpp
void vtkUnstructuredGrid::GetCell(vtkIdType cellId, vtkGenericCell* cell)
{
int cellType = static_cast<int>(this->Types->GetValue(cellId));
cell->SetCellType(cellType);
vtkIdType numPts;
const vtkIdType* pts;
this->Connectivity->GetCellAtId(cellId, numPts, pts);
```
The problem is with this last line. `GetCellAtId` is sometimes thread safe, but not always thread safe. It is thread safe if the connectivity array is a simple array of type `vtkIdType`. However, if the array is of a different type, the values get copied to an object-local space (which is shared among threads), and this becomes very thread unsafe.5.8.1Kenneth MorelandKenneth Morelandhttps://gitlab.kitware.com/paraview/paraview/-/issues/19923selecting data to view causes the gui to do weird things2020-05-14T00:34:24-04:00Kurt Sansomselecting data to view causes the gui to do weird thingson windows 10 release from zip file. ParaView-5.8.0-Windows-Python3.7-msvc2015-64bit
after importing a vtu file that is ascii xml format and selecting arrays to view from the toolbar e.g. dxdu causes the gui to mess up completely. it do...on windows 10 release from zip file. ParaView-5.8.0-Windows-Python3.7-msvc2015-64bit
after importing a vtu file that is ascii xml format and selecting arrays to view from the toolbar e.g. dxdu causes the gui to mess up completely. it doesn't crash, but the resolution changes and the toolbars look weird. this behavior occurs whether the array is selected from the properties view or the bar or the active variables toolbar.
I can drag around the window, but the render view no longer fits inside the view panel and doesn't adjust properly.
![image](/uploads/8cf5cab9cb01e14a1b843ba2e4bfd155/image.png)
after shrinking the window it looks like.
![image](/uploads/5da22859d47de178a4b1303de9200af4/image.png)
here is another view
![image](/uploads/9f29c17c37a7fb798d6a51b09121cbfd/image.png)
I tried saving the file to a different format but the same issue occurred, and appears to have the same behavior, but the view can mess up differently depending on whats selected or the view size when a data array is activated.
[clipped_test.vtu](/uploads/d7680b2bebcabae24db8c21a34345fb4/clipped_test.vtu)https://gitlab.kitware.com/paraview/paraview/-/issues/19924Datatype of Points and Cells is not visible in ParaView2021-04-16T20:22:55-04:00Mathieu Westphal (Kitware)Datatype of Points and Cells is not visible in ParaViewThere is no way to know what is the type of of the points and cells of a dataset in ParaView.
Not in the information panel, not in the spreadsheet view.
I think adding it to the information panel like this would make sense :
`Number o...There is no way to know what is the type of of the points and cells of a dataset in ParaView.
Not in the information panel, not in the spreadsheet view.
I think adding it to the information panel like this would make sense :
`Number of points : 1000 (float)`https://gitlab.kitware.com/paraview/paraview/-/issues/19925Glyph filter and stream tracer filter do not propagate Global Field Data2020-06-29T20:49:03-04:00John PatchettGlyph filter and stream tracer filter do not propagate Global Field DataLoad can.ex2 select all variables including global field data variables.
select glyph filter all defaults
information panel shows that no global field data was propagated.Load can.ex2 select all variables including global field data variables.
select glyph filter all defaults
information panel shows that no global field data was propagated.5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19926cannot select python version during configure of Paraview 5.8 (and master)2020-05-19T10:41:24-04:00Jonathan Stickelcannot select python version during configure of Paraview 5.8 (and master)I have multiple versions of python installed on my Mac via Macports. When running ccmake with Parview 5.8, my selections for:
```
Python3_LIBRARY_RELEASE
_Python3_EXECUTABLE
_Python3_INCLUDE_DIR
_Python3_LIBRARY_RELEASE
```
Are all ign...I have multiple versions of python installed on my Mac via Macports. When running ccmake with Parview 5.8, my selections for:
```
Python3_LIBRARY_RELEASE
_Python3_EXECUTABLE
_Python3_INCLUDE_DIR
_Python3_LIBRARY_RELEASE
```
Are all ignored. I am trying to select python-3.6 (`/opt/local/bin/python3.6`), but python-3.8 (also Macports) is always populated after running configure. I also tried the master branch and my selections are again ignored (interestingly, Xcode python-3.7 is found instead).https://gitlab.kitware.com/paraview/paraview/-/issues/19927BUG RectilinearGrid pvtr data with ghost cells not displayed correctly2020-05-14T21:39:10-04:00Dan LipsaBUG RectilinearGrid pvtr data with ghost cells not displayed correctlySee a description of this bug together with data at:
https://discourse.paraview.org/t/bug-rectilineargrid-pvtr-data-with-ghost-cells-not-displayed-correctly/1566
I tried this in ParaView 5.8.See a description of this bug together with data at:
https://discourse.paraview.org/t/bug-rectilineargrid-pvtr-data-with-ghost-cells-not-displayed-correctly/1566
I tried this in ParaView 5.8.https://gitlab.kitware.com/paraview/paraview/-/issues/19929window layout 'zooms' irreversibly on changing display properties?2020-05-17T22:10:07-04:00Nicholas Jankowskiwindow layout 'zooms' irreversibly on changing display properties?I'm experiencing odd behavior with ParaView where the entire window is acting like a zoom operation occurred when changing the display options for a dataset. Everything seems to function correctly, except the mouse pointer also seems 's...I'm experiencing odd behavior with ParaView where the entire window is acting like a zoom operation occurred when changing the display options for a dataset. Everything seems to function correctly, except the mouse pointer also seems 'shifted' where I have to click below an item for it to register, and I have to close and reopen Paraview to have the window appear correctly again. I was running 5.6.0 on Windows 10, and thought it was a version bug, so installed 5.8.0 and am seeing the same thing (using zip package not executable installer). I've attached screenshots and the dataset in question.
First, opening paraview looks fine:
![Capture1](/uploads/b44f809c5c2ab66cf45fcc898afbdcb9/Capture1.PNG)
I open the VTU file in question, and select Apply for it to display the domain.
![Capture2](/uploads/f2a6aea97c84f68eb766f40ff2dff1b5/Capture2.PNG)
Then I change the Coloring from Solid Color to temperature, and it does so, but the whole window interior 'zooms in' a bit, enough that I cannot see the menubar and some areas near the border.
![Capture3](/uploads/a88f30b1c7e8dbb196e9d60a29e4b14c/Capture3.PNG)
I have been unable to find any way to revert the effect. I've tried with a few other VTU files and they do the same thing. They were all generated by the same program (Elmer at https://www.csc.fi/web/elmer). VTU filed attached
[tbhsvtu0001.vtu](/uploads/777edb943cf570b416a3ee8b35f25f26/tbhsvtu0001.vtu)
I've been able to reproduce the issue with one of the Examples: Help/Example Visualizations - select "Exodus II file with timesteps, Clip filter", then click on Clip2 in the Pipeline Browser. the same window zoom occurs. I'm not sure what function is actually occurring when selecting Clip2.
Have tried a reboot and a reinstall. Haven't noticed any other particular machine issues.https://gitlab.kitware.com/paraview/paraview/-/issues/19931Proposal: Exports Inspector 2.02020-09-01T14:55:11-04:00Utkarsh AyachitProposal: Exports Inspector 2.0This issue proposes a new design for the **Export Inspector** panel introduced in ParaView 5.8.
Panel
----
* **Exports Inspector** panel is a dock panel that allows users to inspect/add/modify exports defined in the application.
* Simil...This issue proposes a new design for the **Export Inspector** panel introduced in ParaView 5.8.
Panel
----
* **Exports Inspector** panel is a dock panel that allows users to inspect/add/modify exports defined in the application.
* Similar to the **Properties** panel, the **Exports Inspector** panel shows information about exports defined on the active source and active view.
![New_Mockup_4](/uploads/b352a1c764caa0fd171d0ded7de4aeca/New_Mockup_4.png)
* There are two groups of extracts, **Data Extracts** and **Image Extracts**. The Data Extracts reflect the extracts defined on the active source while the Image Extracts reflect the extracts defined on the active view.
* New extracts can be added by clicking on the + button next to the type of extract. The + button will expose a drop-down menu on press to let the user choose which specific type of data or image extract to add. For example Data extracts menu will show all supported writers for the active source, while Image extract menu will show supported image formats, and view export formats such as Cinema database, X3D etc. <br/>
![New_Mockup_5](/uploads/aa75b7f5720ee4eb685b4ae25da1828a/New_Mockup_5.png)<br/>
Multiple extracts of the same time can be added for the same active source/view.
* Once an extract is added, its properties will be shown in the under the appropriate extract group in the panel. Thus, all data extracts will be shown under **Data Extracts** group and image extracts under **Image Extracts**.
Export properties
----
Now, let’s look at how the properties for individual extracts are structured. The following mockup shows a sample data extract.
![New_Mockup_6](/uploads/d6976a089b9fff6749b14ed6b58306ae/New_Mockup_6.png)
* Each extract will have a group header/separator with a delete button to allow the user to delete that extract, if not needed.
* **Enable Extract** is a checkbox that allows the user to enable/disable the extract. Disabled extracts will be skipped by **Export Now** or **Catalyst** runs. They are still saved in state and thus recoverable, just not active.
* Each extract has two groups of parameters. The first group, called the **Trigger Parameters** helps define when the extract generates output. We can support arbitrary types of triggers, but in the first pass we limit to time or time-step based triggers where the user indicates which timesteps to generate the extract for. The second group is for parameters specific to the chosen extract type. In the above example, the properties for the CSV writer will be shown here.
Export Now
----
* **Export Now** from the File menu is used to generate the extracts immediately.
* When the user triggers **Export Now**, the user will be presented with a dialog where the user configures the “Export Now” properties. These include options like **Root Directory** i.e the location under which to generate the extracts.
Export Catalyst Script
----
* **Export Catalyst Script** from File menu (or Catalyst menu) can be used to generate a Catalyst script.
* When triggered, a dialog with Catalyst specific options is shown. This will include options like **Root Directory**, **Enable Live Connections**, etc. Thus, Catalyst specific options are delayed till the user requests a Catalyst script.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19932Support Python View2020-05-18T22:14:30-04:00Mark ZhukovSupport Python ViewParaview 5.8 (master)
When I try create some plot using matplotlib in python view - properties - code are or just in python shell, PythonView rendering only black screen and my plot output open new window with name 'Figure 1' and draws t...Paraview 5.8 (master)
When I try create some plot using matplotlib in python view - properties - code are or just in python shell, PythonView rendering only black screen and my plot output open new window with name 'Figure 1' and draws there.
How can I fix python view render or save figure image and close window 'figure 1' using only python shell?https://gitlab.kitware.com/paraview/paraview/-/issues/19933Filters --> alphabetical --> only first column visible, rest is white on Fedo...2020-05-18T22:10:47-04:00Alexandre HalbachFilters --> alphabetical --> only first column visible, rest is white on Fedora 30The large multicolumn panel appearing when choosing Filter --> alphabetical is mostly only white except for the first column of filter names (other column filter names are empty), see attached picture!
I have had this issue only on Fedo...The large multicolumn panel appearing when choosing Filter --> alphabetical is mostly only white except for the first column of filter names (other column filter names are empty), see attached picture!
I have had this issue only on Fedora 30, be it with the packaged version or with the latest (2 weeks ago) compiled source code.
A colleague does not seem to have this issue on Fedora 30, same laptop model.
[paraviewissue](/uploads/8c946e54740cbd44e24997f9595382df/paraviewissue.png).https://gitlab.kitware.com/paraview/paraview/-/issues/19936Proposal: Filter Factory2020-06-11T18:40:50-04:00Utkarsh AyachitProposal: Filter FactoryVTK often has multiple filters that perform the same logical operation. There are several reasons why these multiple versions exist; one common one being that they are intended for different input data types. In ParaView, we often don't ...VTK often has multiple filters that perform the same logical operation. There are several reasons why these multiple versions exist; one common one being that they are intended for different input data types. In ParaView, we often don't like to expose each individual VTK filter implementation as a separate filter in the application, instead we like to group them together into a meta-filter. We put together a `vtkPV...` class that chooses in the correct implementation based on the input dataset type (or other criteria) at runtime.
There are several issues with such meta filters:
* they are cumbersome to write and annoying to debug
* since all internal filters don't often share exactly the same public interface, we end up with proxies that have properties that only make sense for a specific input type. While we often hide them from the UI, the Python trace/state ends up looking ugly and confusing. e.g. here's a python trace generated from the Slice filter:
```python
# create a new 'Slice'
slice1 = Slice(Input=canex2)
slice1.SliceType = 'Plane'
slice1.HyperTreeGridSlicer = 'Plane' #<--- this is extraneous
slice1.SliceOffsetValues = [0.0]
```
* they are not extensible by plugins.
This issue proposes a new mechanism to handle such use-cases.
Concept: Filter Factory
---------
Similar to reader/writer factories, we introduce a filter factory to create new filters. Any UI component like common filters toolbar, filter menu will not directly create a filter proxy based on its name instead use the filter factory to create a appropriate proxy for the given input(s). Similarly with Python API, request to create a filter for example `Slice(Input=..)` will use the filter factory.
Implementation
----------
To help explain the implementation, let's consider the "Slice" filter and say we have two internal implementations "DataSetSlice" and "HyperTreeGridSlice" to pick from based on the input type.
We introduce a new type of `vtkSMSourceProxy` subclass, called `vtkSMSourceProxyFactory`. We use this new proxy to define a class of filters e.g. for the Slice filter, this can be done in the XML definition as follows:
```xml
<ProxyGroup name="filters">
<SourceProxyFactory name="Slice">
</SourceProxyFactory>
</ProxyGroup>
```
Concrete types can be defined as regular filter proxies which a special hint as follows:
```xml
<ProxyGroup name="filters">
<SourceProxy name="DataSetSlice" ...>
<InputProperty .. />
<Hints>
<Factory group="filters" type="Slice" />
</Hints>
</SourceProxy>
<SourceProxy name="HyperTreeGridSlice" ...>
<InputProperty .. />
<Hints>
<Factory group="filters" type="Slice" />
</Hints>
</SourceProxy>
</ProxyGroup>
```
When `(filters, Slice)` proxy is created, it scans for all proxies for appropriate hints and creates them as subproxies.
For every `InputProperty` with a unique name, an InputProperty is created on with a domain that is a boolean OR of all input property domains from the subproxies.
As far as the application is concerned, post-creation, "Slice" will have an Input property with a domain that is an OR of the domains from the Input property on DataSetSlice and HypertreeGridSlice. Thus, the application can use standard logic to set input property and check is-in-domain to see if the filter is applicable for the given input.
Then, during `vtkSMParaViewPipelineController::PostInitializeProxy`, which is called after the Input has been set, the vtkSMSourceProxyFactory which "activate" one of its subproxies by finding one that accepts the input specified and then exposing all properties on that subproxy alone (except Input properties that were already exposed). Thus the public interface of the proxy gets defined in PostInitializeProxy call and is limited to the chosen internal filter proxy. This is the stage where vtkSMSourceProxyFactory makes it so that its output ports are simply the output ports of the activated sub-proxy. Thus, from this point on, this acts as if the activated subproxy was the one that application explicitly created.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19937AggregateDataSet filter runs into MPI size constraint2020-07-14T11:25:49-04:00Boonthanome NouanesengsyAggregateDataSet filter runs into MPI size constraintThere have been occasions where an mpi error is encountered where mpi is trying to send a message that is too large. The error looks like "This operation not yet supported for more than <x> bytes".
This error was last encountered with t...There have been occasions where an mpi error is encountered where mpi is trying to send a message that is too large. The error looks like "This operation not yet supported for more than <x> bytes".
This error was last encountered with the AggregateDataSet filter, in which Bob Kares was going from 30K procs to 200 procs. I've also encountered this error in the past, too. Bob has got it working now, but I'm not sure what he is doing differently.
@patchett2002 @cory.quammen @utkarsh.ayachit5.8.1Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19938HTG mapper for camera dependent refinement2022-03-28T16:38:51-04:00Yohann Bearzi (Kitware)HTG mapper for camera dependent refinement`vtkHyperTreeGrid` allows to have a control on the scale of the data being visualized. This feature could be used to adapt maximum depth refinement of the trees depending on the size of tree nodes vs size of pixels on the screen. This co...`vtkHyperTreeGrid` allows to have a control on the scale of the data being visualized. This feature could be used to adapt maximum depth refinement of the trees depending on the size of tree nodes vs size of pixels on the screen. This could be done by creating a mapper, which we could call `vtkHyperTreeGridMapper`.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/19939filedriver.py inconsistently seg faulting2020-10-06T10:34:11-04:00Ethan Stamfiledriver.py inconsistently seg faulting@utkarsh.ayachit @cory.quammen
Using the filedriver.py from the current master branch to test catalyst scripts is inconsistently seg faulting. I am running MacOS 10.14.6 with pvbatch from the 5.8.0 binary. The catalyst script used is g...@utkarsh.ayachit @cory.quammen
Using the filedriver.py from the current master branch to test catalyst scripts is inconsistently seg faulting. I am running MacOS 10.14.6 with pvbatch from the 5.8.0 binary. The catalyst script used is gridwriter.py from the ParaView source.
Using a bash script:
```
#!/bin/bash
rm -rf input_0*
rm *pyc
/Applications/ParaView-5.8.0.app/Contents/bin/pvbatch \
-sym -dr /Users/stam/projects/paraview/src/Examples/Catalyst/SampleScripts/filedriver.py \
/Users/stam/projects/data-paraview/vtm_can_ex2/can_ex2_0.vtm \
/Users/stam/projects/paraview/src/test_filedriver/gridwriter.py
```
when running that bash script repeatedly (~6 to 10 times in a row), sometimes it works, sometimes I get the error:
```
Reading in ['/Users/stam/projects/data-paraview/vtm_can_ex2/can_ex2_0.vtm']
Adding script /Users/stam/projects/paraview/src/Examples/Catalyst/SampleScripts/gridwriter.py
The channel name is input
Loguru caught a signal: SIGSEGV
Stack trace:
8 0x6 12 ??? 0x0000000000000006 0x0 + 6
7 0x7fff5ebda3dc start + 8
6 0x7fff5ec806b3 exit + 55
5 0x7fff5ec803cf __cxa_finalize_ranges + 319
4 0x7fff5be0ed42 std::__shared_weak_count::__release_shared() + 40
3 0x122b3fa75 ospray::api::ISPCDevice::~ISPCDevice() + 37
2 0x122f6ab91 rtcReleaseDevice + 385
1 0x122f53c35 embree::Device::process_error(embree::Device*, RTCError, char const*) + 453
0 0x0 4 ??? 0x0000000000000000 0x0 + 0
( 1.618s) [pvbatch ] :0 FATL| Signal: SIGSEGV
./test_filedriver.sh: line 13: 74978 Segmentation fault: 11 /Applications/ParaView-5.8.0.app/Contents/bin/pvbatch -sym -dr /Users/stam/projects/paraview/src/Examples/Catalyst/SampleScripts/filedriver.py /Users/stam/projects/data-paraview/vtm_can_ex2/can_ex2_0.vtm /Users/stam/projects/paraview/src/Examples/Catalyst/SampleScripts/gridwriter.py
```
Are you able to reproduce? Do you have guidance for what to do/what not to do?5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19940Error exporting to CGNS2020-10-28T16:50:31-04:00Eilon ShimshiError exporting to CGNSI'm trying to save CFD data to the CGNS format and get the following error:
```
ERROR: In /home/ubuntu/OpenFOAM/ThirdParty-dev/ParaView-5.6.0/ParaViewCore/VTKExtensions/CGNSWriter/vtkCGNSWriter.cxx, line 804
vtkCGNSWriter (0x564de63a755...I'm trying to save CFD data to the CGNS format and get the following error:
```
ERROR: In /home/ubuntu/OpenFOAM/ThirdParty-dev/ParaView-5.6.0/ParaViewCore/VTKExtensions/CGNSWriter/vtkCGNSWriter.cxx, line 804
vtkCGNSWriter (0x564de63a7550): Writing failed: Invalid input: VertexSize[2]=1 and CellSize[2]=1
ERROR: In /home/ubuntu/OpenFOAM/ThirdParty-dev/ParaView-5.6.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 782
vtkPVCompositeDataPipeline (0x564de88acc20): Algorithm vtkCGNSWriter(0x564de63a7550) returned failure for request: vtkInformation (0x564de6457110)
Debug: Off
Modified Time: 10928956
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FROM_OUTPUT_PORT: -1
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```
What is the problem?https://gitlab.kitware.com/paraview/paraview/-/issues/19944Block ID selection broken in FindData2020-06-25T12:07:50-04:00Mathieu Westphal (Kitware)Block ID selection broken in FindDataLooks like the Block ID is broken in Find Data and selects from all blocks.
Steps to reproduce :
* Run ParaView
* Open CompositeGlyphTree.vtm, Apply
* Edit -> FindData
* BlockID is 3
* ID is 0
* Select
* CellID 0 is selected on ...Looks like the Block ID is broken in Find Data and selects from all blocks.
Steps to reproduce :
* Run ParaView
* Open CompositeGlyphTree.vtm, Apply
* Edit -> FindData
* BlockID is 3
* ID is 0
* Select
* CellID 0 is selected on all blocks
![2020-05-21-113934_1524x934_scrot](/uploads/85b16d2ee96bfe487c82fb08f1fdbd4e/2020-05-21-113934_1524x934_scrot.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19949Load State File should not show PVSMs as a time dependent series2020-05-24T22:42:19-04:00Dan LipsaLoad State File should not show PVSMs as a time dependent seriesWhen using the SaveStateAndScreenshot plugin, we save many state files with similar names in the same directory. When using the File / Load State command, the Load State File dialog shows those state files as a time series. That should n...When using the SaveStateAndScreenshot plugin, we save many state files with similar names in the same directory. When using the File / Load State command, the Load State File dialog shows those state files as a time series. That should not be the case as time series don't exist for state files.
Here is an example for a list of state files that are shown as a time series.![pvsm-time-series]![pvsm-time-series.png](/uploads/d063937770dba451d9f4b8451040d3c7/pvsm-time-series.png.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19952PartitionedDataSetCollection: context menu doesn't show correct block name2021-09-03T17:19:21-04:00Utkarsh AyachitPartitionedDataSetCollection: context menu doesn't show correct block name* Open can.ex2 using Ioss reader
* right click on any block in the render view, you get something like this:
![image](/uploads/0686ba4ed1054750287634ad32d3ce45/image.png)
The block name is not show correctly.
------
Ioss Reader pendi...* Open can.ex2 using Ioss reader
* right click on any block in the render view, you get something like this:
![image](/uploads/0686ba4ed1054750287634ad32d3ce45/image.png)
The block name is not show correctly.
------
Ioss Reader pending issue (paraview/paraview!4139)5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19953Weird progress events on delete2020-10-01T21:17:29-04:00Utkarsh AyachitWeird progress events on delete* Open SAND2017-5827O-FSM_Residual_good-eigen.e, select all variable, apply
* Now delete it, you'll see progress bar updating as the delete happens! that's a bug!
Reverting f107c6b740279a47fa348bee6b99365c59b22106 fixes the issue. Thus...* Open SAND2017-5827O-FSM_Residual_good-eigen.e, select all variable, apply
* Now delete it, you'll see progress bar updating as the delete happens! that's a bug!
Reverting f107c6b740279a47fa348bee6b99365c59b22106 fixes the issue. Thus, caused by fix for #193765.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19955Volume rendering multiblock on unstructured grids2021-09-23T20:09:29-04:00Utkarsh AyachitVolume rendering multiblock on unstructured gridsAdd support to volume render composite datasets comprising of unstructured grids.
Steps:
* open can.ex2, apply
* Color by "ids",
* Change representation type to Volume
Only 1 block can be rendered at a time. This is limitation that we ...Add support to volume render composite datasets comprising of unstructured grids.
Steps:
* open can.ex2, apply
* Color by "ids",
* Change representation type to Volume
Only 1 block can be rendered at a time. This is limitation that we can now overcome. Let's fix it.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19957Spreadsheet view: add support for partial arrays2020-06-01T20:53:26-04:00Utkarsh AyachitSpreadsheet view: add support for partial arraysSpreadsheet view should show partial arrays.
When an array is missing on block, we simply leave the cell blank.
When user chooses **File > Export Scene** to export the data from the spreadsheet view to a CSV file, we popup an options d...Spreadsheet view should show partial arrays.
When an array is missing on block, we simply leave the cell blank.
When user chooses **File > Export Scene** to export the data from the spreadsheet view to a CSV file, we popup an options dialog that lets user choose what to do with partial arrays. One can either discard them, or add them as an empty cell. One thing to note that when importing this file back in ParaView empty cells will just get interpreted as 0 for numeric columns.
ref: [discouse](https://discourse.paraview.org/t/showing-partial-arrays-in-spreadsheet-view/4401)
Other related issues:
* [ ] paraview/paraview#18618
* [ ] paraview/paraview#188805.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19958Background color should be preserved and set by pvsm infrastructure2020-06-01T21:27:54-04:00John PatchettBackground color should be preserved and set by pvsm infrastructureUsecase: user creates a visualization in ParaView, setting the background color by any mechanism in the ParaView GUI. The user saves the ParaView state. The user restarts ParaView, switches computers, or otherwise uses ParaView. The user...Usecase: user creates a visualization in ParaView, setting the background color by any mechanism in the ParaView GUI. The user saves the ParaView state. The user restarts ParaView, switches computers, or otherwise uses ParaView. The user then loads the saved state file. The background color that was in the original visualization should be recreated in the renderview(s) of the loaded ParaView state.5.8.1Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19959ParaView Preview Resolution not set on PVSM reload2020-06-11T21:56:21-04:00John PatchettParaView Preview Resolution not set on PVSM reloadin paraview/release as of 5/26/2020 if you set a preview resolution, then save a state file, upon reload of that state file:
view->preview shows the resolution checked, but the actual renderview does not show that resolution.
Workaround:...in paraview/release as of 5/26/2020 if you set a preview resolution, then save a state file, upon reload of that state file:
view->preview shows the resolution checked, but the actual renderview does not show that resolution.
Workaround: view->preview click on the checked resolution (to turn it off) then view->preview to reselect that resolution.5.8.1Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19960Examples\Plugins\MyTiffWriter incorrectly named2021-04-16T21:43:03-04:00W. Alan ScottExamples\Plugins\MyTiffWriter incorrectly namedthe example writer Examples\Plugins\MyTiffWriter is incorrectly named as MyTiffReader. Details here: https://discourse.paraview.org/t/paraview-support-for-completely-customized-application/4406/3the example writer Examples\Plugins\MyTiffWriter is incorrectly named as MyTiffReader. Details here: https://discourse.paraview.org/t/paraview-support-for-completely-customized-application/4406/3Francois MazenFrancois Mazenhttps://gitlab.kitware.com/paraview/paraview/-/issues/19961MergeBlocks Filter Coincident Point Merging Decision2020-11-23T16:54:49-05:00John PatchettMergeBlocks Filter Coincident Point Merging DecisionWe need a scheme for managing multiblock datasets and merging blocks. We have data sets that have physically discontinuous meshes that might have coincident points that should never be merged. We have a scalar field that has values that ...We need a scheme for managing multiblock datasets and merging blocks. We have data sets that have physically discontinuous meshes that might have coincident points that should never be merged. We have a scalar field that has values that would determine whether any given point could be merged and we could create a bitmask of the same. We want to be able to merge points to manage parallel distributed created datasets and run things like ghost cell generator for distributed analysis. Although the meshes are discontinuous they are represented in the same unstructured grid dataset.5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19963ParaView 5.8 crashes when slicing nested multi-block in parallel2024-02-27T05:02:02-05:00Jean M. FavreParaView 5.8 crashes when slicing nested multi-block in parallelCreating the first slice works fine, but ParaView crashes as soon as I interactively drag the slicing plane. My dataset is a nested multi-block with empty blocks except one block, which is an Unstructuredgrid. I have extracted a very sma...Creating the first slice works fine, but ParaView crashes as soon as I interactively drag the slicing plane. My dataset is a nested multi-block with empty blocks except one block, which is an Unstructuredgrid. I have extracted a very small version of the data to use as a reproducer.
untar the file and load in parallel (2 pvserver tasks are enough to crash)
[crash.vtm.tar](/uploads/d11717d0228e2333bd62f3b719ff0d4f/crash.vtm.tar)5.8.1Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19964flicker when making selection2021-04-19T21:36:14-04:00Utkarsh Ayachitflicker when making selectionReproducible in master (v5.8.0-810-g186bdbdcf4) and not with 5.8.0
Steps:
* start paraview, right click to show context menu in the render view -- screen goes black.
![Peek_2020-05-28_09-31](/uploads/ea68ca4801bc1c2a746e4a7a1a0d7e0a/Pee...Reproducible in master (v5.8.0-810-g186bdbdcf4) and not with 5.8.0
Steps:
* start paraview, right click to show context menu in the render view -- screen goes black.
![Peek_2020-05-28_09-31](/uploads/ea68ca4801bc1c2a746e4a7a1a0d7e0a/Peek_2020-05-28_09-31.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/19965OSPRay Background/Env Map colors too bright when in C/S mode2020-11-18T10:58:08-05:00Marston OSPRay Background/Env Map colors too bright when in C/S modeIssue with new OSPRay features in the dev build. Currently testing with build 5.8.0-611-gf6f72baa39 but this bug has been around for a while.
**Bug:**
When running in client server mode with OSPRay Pathtracer on, the background images ...Issue with new OSPRay features in the dev build. Currently testing with build 5.8.0-611-gf6f72baa39 but this bug has been around for a while.
**Bug:**
When running in client server mode with OSPRay Pathtracer on, the background images and colors (for both Backplates and Env Maps) are way brighter than they should be. I believe from previous conversations with the Paraview team this may be to both the client and server loading the images on top of each other?
This does not happen when running in regular client mode, so it is a C/S bug.
**How to replicate:**
Fortunately, this is very easy to test. Run in C/S mode, and just turn on the Pathtracing. The standard grey background will change color. I’ve got some screenshots below showing this.
Regular Color:
![image](/uploads/792c390c6f1bf49375d9ce89412e8a67/image.png)
Brightened Colors:
![image](/uploads/175f003dc45b2802aba2794ad5f93c64/image.png)5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19967Camera position ignored when using parallel projection2020-06-01T15:38:35-04:00Dennis OgiermannCamera position ignored when using parallel projectionHi,
I cannot find any information about setting the camera position through a script for a camera with parallel projection enabled. I tried to approach this through the tracing mechanism in paraview, but setting the camera position prog...Hi,
I cannot find any information about setting the camera position through a script for a camera with parallel projection enabled. I tried to approach this through the tracing mechanism in paraview, but setting the camera position programatically keeps getting ignored when in parallel projection mode and I cannot track down futher why this happens or whether I do something wrong.
To reproduce I execute the following script in Paraview 5.8.0 (current release)
```python
# trace generated using paraview version 5.8.0
#
# To ensure correct image size when batch processing, please search
# for and uncomment the line `# renderView*.ViewSize = [*,*]`
#### import the simple module from the paraview
from paraview.simple import *
#### disable automatic camera reset on 'Show'
paraview.simple._DisableFirstRenderCameraReset()
# create a new 'Sphere'
sphere1 = Sphere()
# get active view
renderView1 = GetActiveViewOrCreate('RenderView')
# uncomment following to set a specific view size
# renderView1.ViewSize = [1372, 791]
# show data in view
sphere1Display = Show(sphere1, renderView1, 'GeometryRepresentation')
# trace defaults for the display properties.
sphere1Display.Representation = 'Surface'
# update the view to ensure updated data information
renderView1.Update()
# Properties modified on renderView1
renderView1.CameraParallelProjection = 1
#### saving camera placements for all active views
# current camera placement for renderView1
renderView1.CameraPosition = [0.0, 0.0, 1.0]
#### uncomment the following to render all views
# RenderAllViews()
SaveScreenshot("screenshot.png", renderView1)
```
gives me the following result.
![screenshot](/uploads/14406eeeea96e99a33d46abd3a1475d3/screenshot.png)
Now, commenting ``renderView1.CameraParallelProjection = 1`` allows me to freely move the camera by changing ``CameraPosition``.https://gitlab.kitware.com/paraview/paraview/-/issues/19968Spreadsheet columns are sometimes incorrect2020-06-16T23:03:54-04:00Utkarsh AyachitSpreadsheet columns are sometimes incorrectBug introduced by paraview/paraview!4154
* Open can.ex2 in spreasheet
* Click on "Variable to show"
* Uncheck PointID
* Block Numbers appears, unexpected.Bug introduced by paraview/paraview!4154
* Open can.ex2 in spreasheet
* Click on "Variable to show"
* Uncheck PointID
* Block Numbers appears, unexpected.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19969return vtkPythonView to shell2020-06-02T22:32:17-04:00Mark Zhukovreturn vtkPythonView to shellHi, I try work with python view without GUI from jupyter. I wanna write matplotlib script in notebook.
```python
image = figure_to_image(figure)
v = FindViewOrCreate('PythonView1', viewtype='PythonView')
v.SetImageData(image)
```
I fo...Hi, I try work with python view without GUI from jupyter. I wanna write matplotlib script in notebook.
```python
image = figure_to_image(figure)
v = FindViewOrCreate('PythonView1', viewtype='PythonView')
v.SetImageData(image)
```
I found that FindOrCreate() returns proxy object paraview.servermanager.PythonView
```python
v.SMProxy.GetClientSideView()
```
reterns vtkPVView and paraview tells me
```python
AttributeError
:
'paraview.modules.vtkRemotingViews.vtkPVView' object has no attribute 'SetImageData'
```
How can I get vtkPythonView object?
Thank You!https://gitlab.kitware.com/paraview/paraview/-/issues/19970return vtkPythonView to Python Shell2020-06-02T22:32:24-04:00Mark Zhukovreturn vtkPythonView to Python ShellHi, I try work with python view using python shell,
i have problem with dispaly figure.
```python
image = figure_to_image(figure)
v = FindViewOrCreate('PythonView1', viewtype='PythonView')
v.SetImageData(image)
```
I found that FindOr...Hi, I try work with python view using python shell,
i have problem with dispaly figure.
```python
image = figure_to_image(figure)
v = FindViewOrCreate('PythonView1', viewtype='PythonView')
v.SetImageData(image)
```
I found that FindOrCreate() returns proxy object paraview.servermanager.PythonView
```python
v.SMProxy.GetClientSideView()
```
reterns vtkPVView and paraview tells me
```python
AttributeError
:
'paraview.modules.vtkRemotingViews.vtkPVView' object has no attribute 'SetImageData'
```
How can I get vtkPythonView object?
Thank You!https://gitlab.kitware.com/paraview/paraview/-/issues/19971ShowInMenu has incorrect behavior in custom apps2020-06-11T21:53:19-04:00Mathieu Westphal (Kitware)ShowInMenu has incorrect behavior in custom appsIn custom application, it is quite standard in only declare a subset of ParaViewFilters.
However, any filters declared in ParaView with a ShowInMenu hints would still appears in their menu and in alphabetical, even when not listed as a f...In custom application, it is quite standard in only declare a subset of ParaViewFilters.
However, any filters declared in ParaView with a ShowInMenu hints would still appears in their menu and in alphabetical, even when not listed as a filter of the application.
This is due to the way definitions are updated for plugins in pqProxyGroupMenuManager.
IMO, there is no reason to use ShowInMenu within ParaView and it should be used only in the context of plugins.
I will fix this by removing these ShowInMenu entries (and improving the related doc). Do you agree @utkarsh.ayachit ?Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19973Errors saving Hypertree grids and reloading into Paraview2020-10-26T13:18:31-04:00Boonthanome NouanesengsyErrors saving Hypertree grids and reloading into ParaviewWe have found some issues with some tasks about saving hypertree (HTG) grids as either .htg or .vtm, and reloading them in Paraview. I tested on both the master branch and release branch. I'll detail the results of each branch. Perhaps s...We have found some issues with some tasks about saving hypertree (HTG) grids as either .htg or .vtm, and reloading them in Paraview. I tested on both the master branch and release branch. I'll detail the results of each branch. Perhaps some of these issues may be that things have not moved over to the master branch, yet.
Task #1: Load a .pio file as a HTG, save data as vtm file, and load that vtm file into Paraview. Here is the data I used: [todd2.zip](/uploads/0c4b9749b2a8fb2c8309239c43ddc179/todd2.zip)
Master branch: when loading the vtm file, I got the following error:
```
ERROR: In /Users/boonth/workspace/ParaView-git/VTK/IO/XMLParser/vtkXMLParser.cxx, line 379
vtkXMLDataParser (0x7fe87869e830): Error parsing XML in stream at line 1, column 9, byte index 9: not well-formed (invalid token)
ERROR: In /Users/boonth/workspace/ParaView-git/VTK/IO/XML/vtkXMLReader.cxx, line 517
vtkXMLHyperTreeGridReader (0x7fe87868e6f0): Error parsing input file. ReadXMLInformation aborting.
ERROR: In /Users/boonth/workspace/ParaView-git/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 753
vtkCompositeDataPipeline (0x60000259be20): Algorithm vtkXMLHyperTreeGridReader(0x7fe87868e6f0) returned failure for request: vtkInformation (0x60000027da40)
Debug: Off
Modified Time: 598096
Reference Count: 1
Registered Events: (none)
Request: REQUEST_INFORMATION
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```
Release branch: this worked fine
Task #2: Create a random HTG source. Save as a .htg file. Load .htg into Paraview
Master branch: Able to save .htg file. When trying to open .htg file, Paraview does not know how to load it, and gives me a list of readers.
Release branch: Works fine in release branch
Task #3: Create a random HTG source. Save as a .vtm file. Load .vtm file into Paraview.
Master branch: Does not have an option to save as vtm file.
Release branch: When trying to save the vtm file, gives the following error:
ERROR: In /Users/boonth/workspace/ParaView-git-release/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 760
vtkPVCompositeDataPipeline (0x60000302da40): Input for connection index 0 on input port index 0 for algorithm vtkXMLPMultiBlockDataWriter(0x7feb8f1451c0) is of type vtkHyperTreeGrid, but a vtkMultiBlockDataSet is required.
@patchett2002 @cory.quammen @pkfYohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19974error reading cgns time data2020-07-09T13:15:45-04:00W. Alan Scotterror reading cgns time dataWe have an error reading variable data from different time steps in a cgns file. I will send file to Utkarsh and Cory. This works correctly in 5.7.0, but not correctly with 5.8.0 or master.
* ParaView 5.8.0, Linux, remote server.
* Loa...We have an error reading variable data from different time steps in a cgns file. I will send file to Utkarsh and Cory. This works correctly in 5.7.0, but not correctly with 5.8.0 or master.
* ParaView 5.8.0, Linux, remote server.
* Load vol-hofd-stg.cgns.4.*. Turn on all variables. Apply.
* Surface.
* Paint by primitives_1.
* Last time step.
* Rescale to data range.
Notice that the min and max don't change. They do with ParaView 5.7.0. This is a bug.
Note, there is an error in the file. It appears that the last two timesteps have the same time. Don't know if this is important...5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19975Incorporate the Velodyne AMR Reader into Paraview2020-06-29T20:35:07-04:00Andrey AndreyevIncorporate the Velodyne AMR Reader into ParaviewI have merged the vtkAMRVelodyneReader into VTK. We no need to update VTK in paraview to make sure that change is reflected and modify the reader.xml file to complete the task.
The SHA for the VTK commit is:
9ba9d060eadef57d81f03addd791...I have merged the vtkAMRVelodyneReader into VTK. We no need to update VTK in paraview to make sure that change is reflected and modify the reader.xml file to complete the task.
The SHA for the VTK commit is:
9ba9d060eadef57d81f03addd791e039653eb8b4https://gitlab.kitware.com/paraview/paraview/-/issues/19976Strange splash screen during client/server connect2021-11-09T13:39:52-05:00W. Alan ScottStrange splash screen during client/server connectI am seeing a strange splash screen during client/server connects. Here is how to replicate:
* Linux, master, remote server.
Attached image shows the splash screen I am seeing.
![Screen_Shot_2020-05-19_at_12.24.07_PM](/uploads/d13d713...I am seeing a strange splash screen during client/server connects. Here is how to replicate:
* Linux, master, remote server.
Attached image shows the splash screen I am seeing.
![Screen_Shot_2020-05-19_at_12.24.07_PM](/uploads/d13d713a8180d2ba06ef76b9addbd686/Screen_Shot_2020-05-19_at_12.24.07_PM.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19978DoubleRangeDomain and IntRangeDomain behavior is not coherent2021-12-13T05:29:00-05:00Mathieu Westphal (Kitware)DoubleRangeDomain and IntRangeDomain behavior is not coherentAssuming single component.
DoubleRangeDomain with a min and a max :
* slider goes from min to max
* <min values **cannot** be entered manually (imo, this is a bug -> actually, **it is <0 values that can't be entered**)
* \>max values c...Assuming single component.
DoubleRangeDomain with a min and a max :
* slider goes from min to max
* <min values **cannot** be entered manually (imo, this is a bug -> actually, **it is <0 values that can't be entered**)
* \>max values can be entered manually
DoubleRangeDomain with only a min
* <min values can be entered manually
DoubleRangeDomain with only a max :
* \>max values can be entered manually
IntRangeDomain with a min and a max :
* slider goes from min to max
* <min values can be entered manually
* \>max values can be entered manually
IntRangeDomain with only a min
* <min values can be entered manually
IntRangeDomain with only a max :
* \>max values can be entered manually
According to the doc :
https://kitware.github.io/paraview-docs/latest/cxx/classvtkSMRangeDomainTemplate.html
It is supposed to be a
> domains that constrain a value within a min and max.
But do we actually want the constraint to be strong or just indicative as it is the case with the slider ?
IMO, the developer should be able to choose via a hint or attribute.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19979Add ResampleFactor property to TemporalFilter2020-06-24T16:08:20-04:00Kenneth MorelandAdd ResampleFactor property to TemporalFilterThe underlying implementation of `TemporalFilter` (specifically `vtkAdaptiveTemporalInterpolator`) has a property named `ResampleFactor` option that sometimes makes it easier to specify new timesteps. Unfortunately, this property is not ...The underlying implementation of `TemporalFilter` (specifically `vtkAdaptiveTemporalInterpolator`) has a property named `ResampleFactor` option that sometimes makes it easier to specify new timesteps. Unfortunately, this property is not exposed in the ParaView proxy, so cannot be used from within ParaView.
A `ResampleFactor` property should be added to the `TemporalFilter` `SourceProxy` (in the `Remoting/Application/Resources/filters_filtersparallel.xml` file). I suggest making this an "advanced" property.Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19981Remove unnecessary Python 2 conflict in ParaView's Spack file2020-08-05T12:25:08-04:00Ethan StamRemove unnecessary Python 2 conflict in ParaView's Spack file@utkarsh.ayachit @patchett2002 @pflarr
In ParaView's Spack package file, there is a conflict preventing users from building newer ParaView versions with Python 2. This should be removed, because it is an unnecessary conflict and a boun...@utkarsh.ayachit @patchett2002 @pflarr
In ParaView's Spack package file, there is a conflict preventing users from building newer ParaView versions with Python 2. This should be removed, because it is an unnecessary conflict and a boundary preventing LANL code teams from moving to newer ParaView versions.
https://github.com/spack/spack/blob/2421d903b034c92660fbe999b7d486e6f21a7417/var/spack/repos/builtin/packages/paraview/package.py#L545.8.1Ethan StamEthan Stamhttps://gitlab.kitware.com/paraview/paraview/-/issues/19982Add filter to compute statistics on connected components2022-05-13T11:27:44-04:00Cory Quammencory.quammen@kitware.comAdd filter to compute statistics on connected componentsAssume we have loaded a polygonal dataset that has different connected components. ParaView should have a filter that computes the connected components and saves them as a composite dataset, one dataset per component. ParaView already ha...Assume we have loaded a polygonal dataset that has different connected components. ParaView should have a filter that computes the connected components and saves them as a composite dataset, one dataset per component. ParaView already has the **Connectivity** filter, but it just adds region ID labels to the output point and cell data and optionally extracts a single block. The new filter would break the components into different datasets held by a common composite dataset (probably a vtkPartitionedDataSetCollection).
In addition, add a filter that takes a vtkPolyData and computes the surface area, volume contained by the surface, and the volume-weighted centroid of the shape. The filter will add these computed attributes as field data associated with the dataset at each block and pass through the input vtkPolyData.
The spreadsheet view can be used to view the computed attributes for each block.5.10 (Fall 2021)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/19983Inconsistent folder name for config files on Windows and Linux2020-06-29T20:50:02-04:00Axel GerstenbergerInconsistent folder name for config files on Windows and LinuxIn vtkInitilizationHelper::GetUserSettingsDirectory, the folder name for the config files is set to vtkInitializationHelper::GetOrganizationName() on Windows and vtkInitializationHelper::GetApplicationName() on Linux.
I am not sure if t...In vtkInitilizationHelper::GetUserSettingsDirectory, the folder name for the config files is set to vtkInitializationHelper::GetOrganizationName() on Windows and vtkInitializationHelper::GetApplicationName() on Linux.
I am not sure if that is on purpose or not and for Paraview, APPLICATION_NAME and ORGANIZATION are both set to "ParaView", so the difference is not visible. But when creating custom applications with a ORGANIZATION name different from APPLICATION_NAME, this seems confusing.
Attached is a patch that fixed it on PV 5.6, but the master branch still has this issue.
[0900-fix_organization_name_on_windows.patch](/uploads/c1f717927d67f9c93e289beaeedcc9ae/0900-fix_organization_name_on_windows.patch)5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19984Create a property group for combining a standard property widget with a check...2020-06-25T07:27:24-04:00Utkarsh AyachitCreate a property group for combining a standard property widget with a checkbox.Load the [attached plugin xml](/uploads/b52f30cd1b3987a7ba3965abd6984db6/CustomSource.xml) from **Tools | Manage Plugins**, **Load New...**.
This adds a new source called **CustomSource**. Create this source from the Sources menu.
The...Load the [attached plugin xml](/uploads/b52f30cd1b3987a7ba3965abd6984db6/CustomSource.xml) from **Tools | Manage Plugins**, **Load New...**.
This adds a new source called **CustomSource**. Create this source from the Sources menu.
The panel looks as follows:
![image](/uploads/2c0c95b1d87ff3134356a9ea3cccac38/image.png)
We don't want it to look like that. What we want is to add a new custom property group widget that combines the checkbox and a corresponding property (in this example, the checkbox for **Enable Property A** and **Property A**, or **Enable Property B** and **Property B**) so that the check is placed next to the main property widget e.g.
![image](/uploads/c663c62287fe8e620828b3bb71303c53/image.png)
Notice how the widget is disabled when the checkbox is unchecked.
Developer notes
-------
In the plugin XML, I've added a potential property group as follows:
```xml
<PropertyGroup panel_widget="EnablePair">
<Property name="PropertyA" function="Property" />
<Property name="EnablePropertyA" function="Enable" />
</PropertyGroup>
<PropertyGroup panel_widget="EnablePair">
<Property name="PropertyB" function="Property" />
<Property name="EnablePropertyB" function="Enable" />
</PropertyGroup>
```
You need to add a custom `pqPropertyWidget` subclass to support this new widget type that I am calling `EnablePair`. Feel free to choose a better name.
Custom property group widgets are defined/added in [`pqStandardPropertyWidgetInterface::createWidgetForPropertyGroup`](https://kitware.github.io/paraview-docs/nightly/cxx/classpqStandardPropertyWidgetInterface.html#a1c95b6df9dd9d9e9e54956c58d6244bb). Your `pqPropertyWidget` subclass must be registered with this method so that ParaView will use it when it encounters `panel_widget="EnablePair"` for a property-group.Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19985Bad vtkCell.GetFace() issue2020-08-25T21:15:59-04:00W. Alan ScottBad vtkCell.GetFace() issueWe have discovered a really bad vtkCell.GetFace() issue. Instantiated objects are not protecting their internal state. Here is how to replicate:
* 5.8.0, Linux, builtin server.
* Sources Wavelet. Apply.
* Open a View/ Python Shell. H...We have discovered a really bad vtkCell.GetFace() issue. Instantiated objects are not protecting their internal state. Here is how to replicate:
* 5.8.0, Linux, builtin server.
* Sources Wavelet. Apply.
* Open a View/ Python Shell. Here is what goes inside:
```
ww = GetActiveSource().GetClientSideObject().GetOutputDataObject(0)
cc = ww.GetCell(137)
ff1 = cc.GetFace(2)
print(ff1.GetPointIds().GetId(0))
```
143
```
ff2 = cc.GetFace(5)
print(ff2.GetPointIds().GetId(0))
```
584
```
print(ff1.GetPointIds().GetId(0))
```
584 <<<<<< This is an error.
From Jeff: You well see that the first point index for face ff1 has been changed to match the first point index for face ff2 after the call to set ff2 to face 5. In fact all of ff1 has been changed to match ff2. The also happens if the cell is different. It's like GetCell is one of those functions (python side or c side) which has a single internal state and you are only getting a reference to the internal state.
This is either a bug or an intentional behavior that is completely undocumented (and probably bad).
By the way, Jeff says "aaaarrrrgggggggghh"5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19986Proxies in nested ProxyProperty are missing from XML State2020-09-01T14:59:53-04:00Lutz HofmannProxies in nested ProxyProperty are missing from XML StateProxies, that are set by a `ProxyProperty` and have a `ProxyProperty` themselves are missing their proxies in the XML state.
For example, the following `MyStreamTracer` proxy has a `SplineSource` attached to a InputProperty, which has a...Proxies, that are set by a `ProxyProperty` and have a `ProxyProperty` themselves are missing their proxies in the XML state.
For example, the following `MyStreamTracer` proxy has a `SplineSource` attached to a InputProperty, which has a `Spline` proxy attached to a ProxyProperty.
```xml
<SourceProxy name="MyStreamTracer"
class="vtkStreamTracer">
<InputProperty command="SetSourceConnection" name="Source">
<ProxyListDomain name="proxy_list">
<Proxy group="sources" name="SplineSource" />
</ProxyListDomain>
</InputProperty>
...
<SourceProxy class="vtkParametricFunctionSource"
name="SplineSource">
<ProxyProperty command="SetParametricFunction" name="ParametricFunction">
<ProxyListDomain name="proxy_list">
<Proxy group="parametric_functions" name="Spline" />
</ProxyListDomain>
</ProxyProperty>
```
Saving a state containing a `MyStreamTracer` will correctly save the `SplineSource` proxy:
```xml
<Proxy group="sources" type="SplineSource" id="17080" servers="1">
<Property name="ParametricFunction" id="17080.ParametricFunction" number_of_elements="1">
<Proxy value="17079"/>
```
but the proxy with ID 17079 is missing from the XML state. This could be related to it not being registered as helper proxy of `MyStreamTracer1`.
### Steps to reproduce
1. Load [plugin.xml](/uploads/7bf98f5154d1aa6bd03ad66ca49c4b61/plugin.xml)
2. Create Wavelet source, attach MyStreamTracer filter
3. Save state (produces [state.pvsm](/uploads/e4e894cef27476ee205878a43600432c/state.pvsm))
4. Load state
The loaded `MyStreamTracer1` has now an empty Parametric Function property.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19987Paraview 5.8 crashes on open with windows 102020-06-11T17:45:22-04:00thomasgallenbergerParaview 5.8 crashes on open with windows 10About 75% of the time I would open Paraview, it would crash immediately. The other 25% of the time it would let me open a vtk file after which Paraview would crash when I hit apply to the properties. I know the vtk file is fine because a...About 75% of the time I would open Paraview, it would crash immediately. The other 25% of the time it would let me open a vtk file after which Paraview would crash when I hit apply to the properties. I know the vtk file is fine because a friend was able to open it. I tried uninstalling and reinstalling but that didn't work. I tried Paraview 5.7 and it works.https://gitlab.kitware.com/paraview/paraview/-/issues/19988d3 or ghost cell generator enhancement2020-06-12T13:22:40-04:00W. Alan Scottd3 or ghost cell generator enhancementThere are times when we want to remove processor - or file - boundaries - within multiblock datasets. We need to do one of the following:
* Speed up the D3 filter. This filter freezes up (running WAY slow) when running in parallel (16 ...There are times when we want to remove processor - or file - boundaries - within multiblock datasets. We need to do one of the following:
* Speed up the D3 filter. This filter freezes up (running WAY slow) when running in parallel (16 ranks), on many dozens to hundreds of blocks. Sometimes, users want to keep these blocks, so they can color by block color.
* Add the ability for the Ghost Cell Generator to work on multiple blocks.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19989Ghost Cell Generator needs to work on multiblock datasets2021-08-10T16:51:05-04:00W. Alan ScottGhost Cell Generator needs to work on multiblock datasetsThe new, fancy Ghost Cell Generator needs to work on multiblock datasets. The reason is sometimes users will want to display a wireframe, with each block colored differently. However, they then want to remove internal file and processo...The new, fancy Ghost Cell Generator needs to work on multiblock datasets. The reason is sometimes users will want to display a wireframe, with each block colored differently. However, they then want to remove internal file and processor boundaries.
This needs to be done before D3 disappears.5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19990Extracts + Live2020-06-30T07:09:44-04:00Utkarsh AyachitExtracts + LiveIn Live sessions, the Extracts Inspector cannot be used as expected to view the extract generators defined in the Catalyst pipeline.
related to paraview/paraview!4178In Live sessions, the Extracts Inspector cannot be used as expected to view the extract generators defined in the Catalyst pipeline.
related to paraview/paraview!4178https://gitlab.kitware.com/paraview/paraview/-/issues/19992PIO Reader - Choose Time Array2020-08-20T22:25:42-04:00Boonthanome NouanesengsyPIO Reader - Choose Time ArrayGive the PIO Reader the ability to choose between Simulation Time or Cycle Index as the time array used. The user should be able to choose in the gui which one to use with a combo box.
When first introduced, the PIO Reader used Cycle I...Give the PIO Reader the ability to choose between Simulation Time or Cycle Index as the time array used. The user should be able to choose in the gui which one to use with a combo box.
When first introduced, the PIO Reader used Cycle Index as time, and there was no way to change it. With MRs https://gitlab.kitware.com/vtk/vtk/-/merge_requests/6975 and https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4176, this feature was introduced and works in the master branch.
In the release branch, additional commits were needed for this to work properly. These commits were in master, but not in the release branch. Yohann backported some commits in MR https://gitlab.kitware.com/vtk/vtk/-/merge_requests/6990#note_777033. This fixed some issues, but some issues still were present.
There are currently two issues:
1. The combo box in the gui to choose time array does not work. If you choose Cycle Index, then hit Apply, the Simulation Time still loads.
2. Switching to a different time array after initially loading the file does not work.
The MR https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4187 backports more commits and seemed to fix these issues, but @utkarsh.ayachit did not want more commits backported, as it was introducing bugs. So the MR has not been merged, yet.
cc @patchett2002 @cory.quammenhttps://gitlab.kitware.com/paraview/paraview/-/issues/19993Release ParaView 5.8.1-RC12020-06-17T11:41:47-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.8.1-RC1# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.8.1.pdf
- [x] Upload to www.paraview.org/files/v5.8
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.8.1.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.8.1.pdf
- [x] Upload to www.paraview.org/files/v5.8
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.8.1.pdf
- [x] Upload to www.paraview.org/files/v5.8
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.8.1.pdf
- [x] Upload to www.paraview.org/files/v5.8
- Assemble release notes into `Documentation/release/ParaView-5.8.1`.
- [ ] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.8.1-RC1
echo 5.8.1-RC1 > version.txt
git commit -m 'Update version number to 5.8.1-RC1' version.txt
git tag -a -m 'ParaView 5.8.1-RC1' v5.8.1-RC1 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.8.1-RC1:release v5.8.1-RC1`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.8.1-RC1`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.8/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update
git checkout -b update-to-v5.8.1-RC1
```
- Update `CMakeLists.txt`
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.8.1-RC1" CACHE STRING "Force version to 5.8.1-RC1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.8.1-RC1
- [x] ARG SUPERBUILD_TAG=v5.8.1-RC1
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/Dockerfile
git commit -m "Update the default version to 5.8.1-RC1"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [x] Build binaries (`Do: test`)
- [x] Download the binaries that have been generated in the dashboard results. They will be deleted within 24 hours.
- [x] Remove explicit version forcing added in CMakeLists.txt, amend the commit, and force push
```
git add CMakeLists.txt
git commit --amend --no-edit
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.8.1-RC1' v5.8.1-RC1 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.8.1-RC1:release v5.8.1-RC1`
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.8.1-RC1.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.8.1-RC1.app/`
# Validating binaries
- For each binary, check
- [x] Getting started guide opens
- [x] Examples load and match thumbnails in dialog
- [x] Python
- [x] `import numpy`
- [x] Plugins are present and load properly
- [x] Text source LaTeX `$A^2$`
- [x] OSPRay raycasting and pathtracing runs
- [x] OptiX pathtracing runs
- [x] IndeX runs
- [x] AutoMPI
- Binary checklist
- [x] macOS
- [x] Linux
- [x] Linux osmesa
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.8/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.8
```
- [x] Test download links on https://www.paraview.org/download
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19994Plot Over Line Crash if Inherite Representation Properties enabled2020-10-14T02:50:20-04:00ym jiaPlot Over Line Crash if Inherite Representation Properties enabledTo Reproduce(5.7 or later, 5.6 will not crash):
0. Settings -> General -> Check 'Inherit Representation Properties'
1. load a png image
2. filter->plot over line
3. applyTo Reproduce(5.7 or later, 5.6 will not crash):
0. Settings -> General -> Check 'Inherit Representation Properties'
1. load a png image
2. filter->plot over line
3. applyYohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19995Multiblock inspector segfault with FieldData2020-06-15T23:48:28-04:00Mathieu Westphal (Kitware)Multiblock inspector segfault with FieldDataSegfault when clicking in the multiblock inspector:
* Open [mb_0_0.vtu](/uploads/5aa7b456ef8b0fcbf5342f8339eaff64/mb_0_0.vtu), Apply
* Add a group dataset, apply
* Color by the field data "Index"
* Click on the root item of the mult...Segfault when clicking in the multiblock inspector:
* Open [mb_0_0.vtu](/uploads/5aa7b456ef8b0fcbf5342f8339eaff64/mb_0_0.vtu), Apply
* Add a group dataset, apply
* Color by the field data "Index"
* Click on the root item of the multi-block inspector
* segfault
```
Thread 1 "paraview" received signal SIGSEGV, Segmentation fault.
0x00007ffff6aa9b2a in pqOutputPort::getSource (this=0x0) at /home/glow/work/paraview/paraviewThird/paraview/Qt/Core/pqOutputPort.h:75
75 pqPipelineSource* getSource() const { return this->Source; }
(gdb) bt
#0 0x00007ffff6aa9b2a in pqOutputPort::getSource (this=0x0) at /home/glow/work/paraview/paraviewThird/paraview/Qt/Core/pqOutputPort.h:75
#1 0x00007ffff6af6c75 in pqOutputPort::getSelectedDataInformation (this=0x0, es_port=0) at /home/glow/work/paraview/paraviewThird/paraview/Qt/Core/pqOutputPort.cxx:126
#2 0x00007fffc8157e41 in ExampleDockPanel::selectionChanged (this=0x555557f96620, port=0x0) at /home/glow/work/tampere/dock/DockWidget/Plugin/ExampleDockPanel.cxx:93
#3 0x00007fffc8155ca1 in ExampleDockPanel::qt_static_metacall (_o=0x555557f96620, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fffffffd630)
at /home/glow/work/tampere/dock/DockWidget/build/Plugin/ExampleDockPanel_autogen/EWIEGA46WW/moc_ExampleDockPanel.cpp:84
#4 0x00007ffff5fad940 in ?? () from /usr/lib/libQt5Core.so.5
#5 0x00007ffff6d2da46 in pqSelectionManager::selectionChanged (this=0x55555586de10, _t1=0x0) at Qt/Components/pqComponents_autogen/EWIEGA46WW/moc_pqSelectionManager.cpp:188
#6 0x00007ffff6ee5945 in pqSelectionManager::select (this=0x55555586de10, selectedPort=0x0) at /home/glow/work/paraview/paraviewThird/paraview/Qt/Components/pqSelectionManager.cxx:336
#7 0x00007ffff6e4388c in (anonymous namespace)::MultiBlockInspectorSelectionModel::selectBlocks (this=0x555555b044e0, ids=std::vector of length 0, capacity 1)
at /home/glow/work/paraview/paraviewThird/paraview/Qt/Components/pqMultiBlockInspectorWidget.cxx:570
#8 0x00007ffff6e43423 in (anonymous namespace)::MultiBlockInspectorSelectionModel::select (this=0x555555b044e0, aselection=..., command=...)
at /home/glow/work/paraview/paraviewThird/paraview/Qt/Components/pqMultiBlockInspectorWidget.cxx:511
#9 0x00007ffff7586c97 in QTreeViewPrivate::select(QModelIndex const&, QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/libQt5Widgets.so.5
#10 0x00007ffff75873c2 in QTreeView::setSelection(QRect const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/libQt5Widgets.so.5
#11 0x00007ffff75153b5 in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5
#12 0x00007ffff72efc6e in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5
#13 0x00007ffff739af8f in QFrame::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5
#14 0x00007ffff5f76403 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#15 0x00007ffff72ae6e1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#16 0x00007ffff72b5967 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#17 0x00007ffff5f7669a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#18 0x00007ffff72b484e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /usr/lib/libQt5Widgets.so.5
#19 0x00007ffff73083a2 in ?? () from /usr/lib/libQt5Widgets.so.5
#20 0x00007ffff730b77f in ?? () from /usr/lib/libQt5Widgets.so.5
#21 0x00007ffff72ae6f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#22 0x00007ffff5f7669a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#23 0x00007ffff6350f1c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5
#24 0x00007ffff63266ec in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5
#25 0x00007fffdb784c8c in ?? () from /usr/lib/libQt5XcbQpa.so.5
#26 0x00007fffed81943c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0x00007fffed866fa9 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0x00007fffed818221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0x00007ffff5fcf211 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#30 0x00007ffff5f7501c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#31 0x00007ffff5f7d4a4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#32 0x0000555555562306 in main (argc=1, argv=0x5555556d3b50) at Clients/ParaView/paraview_main.cxx:138
```
FYI : @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19998Paraview creates different images on ARM2022-03-15T12:07:05-04:00Boonthanome NouanesengsyParaview creates different images on ARMThe LANL code Flag has a test which renders an image and tests it against a gold standard. When compiling Flag and Paraview to ARM processors, it seems like Paraview renders the image differently. The main differences are that the XYZ co...The LANL code Flag has a test which renders an image and tests it against a gold standard. When compiling Flag and Paraview to ARM processors, it seems like Paraview renders the image differently. The main differences are that the XYZ coordinate icon is not there, and the surface edges are rendered differently. The standard image was written with Paraview 5.4.1. The ARM image was using Paraview 5.5.2. Is this a known issue?
@patchett2002 @cory.quammen
Below is the standard image, the ARM image, and an image highlighting the differences.
Standard Image (Intel)
![image_0001.std](/uploads/08464184aea8c76214cbad21e07a6aec/image_0001.std.png)
Arm Image
![image_0001.arm](/uploads/f26f7916a24f16cd10cf64155534de21/image_0001.arm.png)
Diff Image
![image.diff](/uploads/ea55ce5f89b9e64701d089ded5db80d7/image.diff.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19999Spack: ParaView installs libraries to prefix/lib64 but creates empty prefix/l...2020-06-26T08:20:33-04:00Ethan StamSpack: ParaView installs libraries to prefix/lib64 but creates empty prefix/lib making ParaView's modulefile invalid@utkarsh.ayachit @patchett2002
Some context for this. CMake is making a decision to set CMAKE_INSTALL_LIBDIR to lib64. Apparently, this is an attempt to match the host install infrastructure. This decision is not handled well with Spac...@utkarsh.ayachit @patchett2002
Some context for this. CMake is making a decision to set CMAKE_INSTALL_LIBDIR to lib64. Apparently, this is an attempt to match the host install infrastructure. This decision is not handled well with Spack. ParaView libraries, VTK libraries, CMake files, and python modules are installed to prefix/lib64, but empty directories are still created in prefix/lib. The Spack generated modulefile for ParaView has a condition:
```
if {[file isdirectory "/path/to/linux-rhel7-x86_64/gcc-7.4.0/paraview-5.8.1-eo5nay2rlcoeghg4pxysx4tubhyqxexv/lib"]} {
setenv PARAVIEW_LIB_DIR "/path/to/linux-rhel7-x86_64/gcc-7.4.0/paraview-5.8.1-eo5nay2rlcoeghg4pxysx4tubhyqxexv/lib"
setenv VTK_DIR "/path/to/linux-rhel7-x86_64/gcc-7.4.0/paraview-5.8.1-eo5nay2rlcoeghg4pxysx4tubhyqxexv/lib/cmake/paraview-5.8"
} elseif {[file isdirectory "/path/to/linux-rhel7-x86_64/gcc-7.4.0/paraview-5.8.1-eo5nay2rlcoeghg4pxysx4tubhyqxexv/lib64"]} {
setenv PARAVIEW_LIB_DIR "/path/to/linux-rhel7-x86_64/gcc-7.4.0/paraview-5.8.1-eo5nay2rlcoeghg4pxysx4tubhyqxexv/lib64"
setenv VTK_DIR "/path/to/linux-rhel7-x86_64/gcc-7.4.0/paraview-5.8.1-eo5nay2rlcoeghg4pxysx4tubhyqxexv/lib64/cmakeparaview-5.8"
}
```
Since there is a prefix/lib, PARAVIEW_LIB_DIR and VTK_DIR are set to the wrong path. This causes issues when building codes against that ParaView with errors like:
```
20 By not providing "FindVTK.cmake" in CMAKE_MODULE_PATH this project has
21 asked CMake to find a package configuration file provided by "VTK", but
22 CMake did not find one.
23
24 Could not find a package configuration file provided by "VTK" with any of
25 the following names:
```5.8.1Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20001IOSS reader questions and issues2021-09-03T17:16:01-04:00W. Alan ScottIOSS reader questions and issuesHere is a bug to track questions and responses to the new IOSS reader. Individual true bugs should have their own bug report.
@utkarsh.ayachitHere is a bug to track questions and responses to the new IOSS reader. Individual true bugs should have their own bug report.
@utkarsh.ayachit5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20002SurfaceLIC segfault with line or polyline cells2021-04-12T11:14:36-04:00Mathieu Westphal (Kitware)SurfaceLIC segfault with line or polyline cells
* run paraview
* Tools -> ManagePlugins -> SurfaceLIC
* Line Source/PolyLine source, Apply
* Random Vectors, Apply
* Select SurfaceLIC
* Segfault
```
( 23.781s) [paraview ] vtkShaderProgram.cxx:452 ERR| vtkShaderPro...
* run paraview
* Tools -> ManagePlugins -> SurfaceLIC
* Line Source/PolyLine source, Apply
* Random Vectors, Apply
* Select SurfaceLIC
* Segfault
```
( 23.781s) [paraview ] vtkShaderProgram.cxx:452 ERR| vtkShaderProgram (0x555560f1a940): 1: #version 150
2: #ifdef GL_ES
3: #ifdef GL_FRAGMENT_PRECISION_HIGH
4: precision highp float;
5: precision highp sampler2D;
6: precision highp sampler3D;
7: #else
8: precision mediump float;
9: precision mediump sampler2D;
10: precision mediump sampler3D;
11: #endif
12: #define texelFetchBuffer texelFetch
13: #define texture1D texture
14: #define texture2D texture
15: #define texture3D texture
16: #else // GL_ES
17: #define highp
18: #define mediump
19: #define lowp
20: #if __VERSION__ == 150
21: #define texelFetchBuffer texelFetch
22: #define texture1D texture
23: #define texture2D texture
24: #define texture3D texture
25: #endif
26: #endif // GL_ES
27: #define varying in
28:
29:
30: /*=========================================================================
31:
32: Program: Visualization Toolkit
33: Module: vtkPolyDataFS.glsl
34:
35: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
36: All rights reserved.
37: See Copyright.txt or http://www.kitware.com/Copyright.htm for details.
38:
39: This software is distributed WITHOUT ANY WARRANTY; without even
40: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
41: PURPOSE. See the above copyright notice for more information.
42:
43: =========================================================================*/
44: // Template for the polydata mappers fragment shader
45:
46: uniform int PrimitiveIDOffset;
47:
48:
49:
50: // VC position of this fragment
51: //VTK::PositionVC::Dec
52:
53: // Camera prop
54: uniform int cameraParallel;
55:
56:
57: // optional color passed in from the vertex shader, vertexColor
58: uniform bool OverridesColor;
59: uniform float ambientIntensity; // the material ambient
60: uniform float diffuseIntensity; // the material diffuse
61: uniform float opacityUniform; // the fragment opacity
62: uniform vec3 ambientColorUniform; // ambient color
63: uniform vec3 diffuseColorUniform; // diffuse color
64:
65:
66: // optional surface normal declaration
67: //VTK::Normal::Dec
68:
69: // extra lighting parameters
70: uniform vec3 lightColor0;
71: uniform vec3 lightDirectionVC0; // normalized
72: uniform vec3 lightColor1;
73: uniform vec3 lightDirectionVC1; // normalized
74: uniform vec3 lightColor2;
75: uniform vec3 lightDirectionVC2; // normalized
76: uniform vec3 lightColor3;
77: uniform vec3 lightDirectionVC3; // normalized
78: uniform vec3 lightColor4;
79: uniform vec3 lightDirectionVC4; // normalized
80: 81:
82: // Texture maps
83: //VTK::TMap::Dec
84:
85: // Texture coordinates
86: uniform int uMaskOnSurface;
87: uniform mat3 normalMatrix;
88: in vec3 tcoordVCVSOutput;
89:
90: // picking support
91: //VTK::Picking::Dec
92:
93: // Depth Peeling Support
94: //VTK::DepthPeeling::Dec
95:
96: // clipping plane vars
97: //VTK::Clip::Dec
98:
99: // the output of this shader
100: out vec4 fragOutput0;
101: out vec4 fragOutput1;
102: out vec4 fragOutput2;
103:
104:
105: // Apple Bug
106: //VTK::PrimID::Dec
107:
108: // handle coincident offsets
109: uniform float cCValue;
110: uniform float cSValue;
111: uniform float cDValue;
112:
113: // Value raster
114: //VTK::ValuePass::Dec
115:
116: // surface with edges
117: //VTK::Edges::Dec
118:
119: void main()
120: {
121: // VC position of this fragment. This should not branch/return/discard.
122: //VTK::PositionVC::Impl
123:
124: // Place any calls that require uniform flow (e.g. dFdx) here.
125: //VTK::UniformFlow::Impl
126:
127: // Set gl_FragDepth here (gl_FragCoord.z by default)
128: float Zdc = gl_FragCoord.z*2.0 - 1.0;
129: float Z2 = -1.0*cDValue/(Zdc + cCValue) + cSValue;
130: float Zdc2 = -1.0*cCValue - cDValue/Z2;
131: gl_FragDepth = Zdc2*0.5 + 0.5;
132:
133:
134: // Early depth peeling abort:
135: //VTK::DepthPeeling::PreColor
136:
137: // Apple Bug
138: //VTK::PrimID::Impl
139:
140: //VTK::Clip::Impl
141:
142: //VTK::ValuePass::Impl
143:
144: vec3 ambientColor = ambientIntensity * ambientColorUniform;
145: vec3 diffuseColor = diffuseIntensity * diffuseColorUniform;
146: float opacity = opacityUniform;
147:
148: if (OverridesColor) {
149: ambientColor = ambientColorUniform * ambientIntensity;
150: diffuseColor = diffuseColorUniform * diffuseIntensity; }
151:
152:
153: //VTK::Edges::Impl
154:
155: // Generate the normal if we are not passed in one
156: //VTK::Normal::Impl
157:
158: fragOutput0 = vec4(ambientColor + diffuseColor, opacity);
159: //VTK::Light::Impl
160:
161:
162: vec3 tcoordLIC = normalMatrix * tcoordVCVSOutput;
163: vec3 normN = normalize(normalVCVSOutput);
164: float k = dot(tcoordLIC, normN);
165: tcoordLIC = (tcoordLIC - k*normN);
166: fragOutput1 = vec4(tcoordLIC.x, tcoordLIC.y, 0.0 , gl_FragCoord.z);
167: if (uMaskOnSurface == 0)
168: {
169: fragOutput2 = vec4(tcoordVCVSOutput, gl_FragCoord.z);
170: }
171: else
172: {
173: fragOutput2 = vec4(tcoordLIC.x, tcoordLIC.y, 0.0 , gl_FragCoord.z);
174: }
175:
176:
177: if (fragOutput0.a <= 0.0)
178: {
179: discard;
180: }
181:
182: //VTK::DepthPeeling::Impl
183:
184: //VTK::Picking::Impl
185:
186: // handle coincident offsets
187: //VTK::Coincident::Impl
188: }
( 23.796s) [paraview ] vtkShaderProgram.cxx:453 ERR| vtkShaderProgram (0x555560f1a940): 0(163) : error C1503: undefined variable "normalVCVSOutput"
Thread 1 "paraview" received signal SIGSEGV, Segmentation fault.
0x00007ffff45f0f5d in vtkOpenGLPolyDataMapper::UpdateShaders (this=0x555560f0ee90, cellBO=..., ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx:2374
2374 if (newShader != cellBO.Program || cellBO.Program->GetMTime() > cellBO.AttributeUpdateTime)
(gdb) bt
#0 0x00007ffff45f0f5d in vtkOpenGLPolyDataMapper::UpdateShaders (this=0x555560f0ee90, cellBO=..., ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLPolyDataMapper.cxx:2374
#1 0x00007ffff450da82 in vtkCompositeMapperHelper2::UpdateShaders (this=0x555560f0ee90, cellBO=..., ren=0x55555d22e7e0, act=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:172
#2 0x00007ffff450e3e2 in vtkCompositeMapperHelper2::DrawIBO (this=0x555560f0ee90, ren=0x55555d22e7e0, actor=0x55555e14c6c0, primType=1, CellBO=..., mode=1, pointSize=0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:319
#3 0x00007ffff450e8ee in vtkCompositeMapperHelper2::RenderPieceDraw (this=0x555560f0ee90, ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:410
#4 0x00007ffff450e31d in vtkCompositeMapperHelper2::RenderPiece (this=0x555560f0ee90, ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:303
#5 0x00007ffff4514f72 in vtkCompositePolyDataMapper2::Render (this=0x55555e141d60, ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCompositePolyDataMapper2.cxx:1816
#6 0x00007fffebbab2ab in vtkCompositeSurfaceLICMapper::Render (this=0x55555e141d60, ren=0x55555d22e7e0, actor=0x55555e14c6c0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/LICOpenGL2/vtkCompositeSurfaceLICMapper.cxx:284
#7 0x00007ffff455f647 in vtkOpenGLActor::Render (this=0x55555e14c6c0, ren=0x55555d22e7e0, mapper=0x55555e141d60) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLActor.cxx:104
#8 0x00007fffef441d74 in vtkPVLODActor::Render (this=0x55555de8b570, ren=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVLODActor.cxx:141
#9 0x00007fffef441f6d in vtkPVLODActor::RenderOpaqueGeometry (this=0x55555de8b570, vp=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVLODActor.cxx:172
#10 0x00007ffff40a0c01 in vtkRenderer::UpdateOpaquePolygonalGeometry (this=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderer.cxx:736
#11 0x00007ffff409fa0d in vtkRenderer::DeviceRenderOpaqueGeometry (this=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderer.cxx:436
#12 0x00007ffff4633788 in vtkOpenGLRenderer::DeviceRenderOpaqueGeometry (this=0x55555d22e7e0, fbo=0x0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx:494
#13 0x00007ffff4632c10 in vtkOpenGLRenderer::UpdateGeometry (this=0x55555d22e7e0, fbo=0x0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx:390
#14 0x00007ffff407f48e in vtkRenderPass::UpdateGeometry (this=0x55555d2ddf30, renderer=0x55555d22e7e0, fbo=0x0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderPass.cxx:93
#15 0x00007fffef409beb in vtkPVDefaultPass::Render (this=0x55555d2ddf30, render_state=0x7fffffffca80) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVDefaultPass.cxx:43
#16 0x00007ffff450a815 in vtkCameraPass::Render (this=0x55555d2dd2b0, s=0x7fffffffca80) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkCameraPass.cxx:144
#17 0x00007ffff4631fa3 in vtkOpenGLRenderer::DeviceRender (this=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx:281
#18 0x00007ffff409f53e in vtkRenderer::Render (this=0x55555d22e7e0) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderer.cxx:377
#19 0x00007ffff40b4866 in vtkRendererCollection::Render (this=0x555558207c80) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRendererCollection.cxx:51
#20 0x00007ffff4082d44 in vtkRenderWindow::DoStereoRender (this=0x55555d59cd10) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderWindow.cxx:337
#21 0x00007ffff4082b1d in vtkRenderWindow::Render (this=0x55555d59cd10) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/Core/vtkRenderWindow.cxx:297
#22 0x00007ffff462fef0 in vtkOpenGLRenderWindow::Render (this=0x55555d59cd10) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2067
#23 0x00007ffff4550d36 in vtkGenericOpenGLRenderWindow::Render (this=0x55555d59cd10) at /home/glow/work/paraview/paraviewThird/paraview/VTK/Rendering/OpenGL2/vtkGenericOpenGLRenderWindow.cxx:218
#24 0x00007fffef475934 in vtkPVRenderView::Render (this=0x55555814f230, interactive=false, skip_rendering=false) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVRenderView.cxx:1601
#25 0x00007fffef474994 in vtkPVRenderView::StillRender (this=0x55555814f230) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkPVRenderView.cxx:1384
#26 0x00007fffefd4a325 in vtkPVRenderViewCommand (arlu=0x55555586ab50, ob=0x55555814f230, method=0x55555ebaf589 "StillRender", msg=..., resultStream=...) at CMakeFiles/vtkRemotingViewsCS/vtkPVRenderViewClientServer.cxx:242
#27 0x00007ffff4e39c83 in vtkClientServerInterpreter::CallCommandFunction (this=0x55555586ab50, cname=0x7fffef5a066e "vtkPVRenderView", ptr=0x55555814f230, method=0x55555ebaf589 "StillRender", msg=..., result=...)
at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:809
#28 0x00007ffff4e38244 in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x55555586ab50, css=..., midx=2) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:424
#29 0x00007ffff4e37754 in vtkClientServerInterpreter::ProcessOneMessage (this=0x55555586ab50, css=..., message=2) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:265
#30 0x00007ffff4e375db in vtkClientServerInterpreter::ProcessStream (this=0x55555586ab50, css=...) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:235
#31 0x00007ffff5881eb4 in vtkPVSessionCore::ExecuteStreamInternal (this=0x55555586bcf0, stream=..., ignore_errors=false) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ServerManager/vtkPVSessionCore.cxx:637
#32 0x00007ffff5881c7f in vtkPVSessionCore::ExecuteStream (this=0x55555586bcf0, location=16, stream=..., ignore_errors=false) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ServerManager/vtkPVSessionCore.cxx:607
#33 0x00007ffff587e214 in vtkPVSessionBase::ExecuteStream (this=0x555555cece70, location=16, stream=..., ignore_errors=false) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ServerManager/vtkPVSessionBase.cxx:165
#34 0x00007ffff59b41e4 in vtkSMProxy::ExecuteStream (this=0x55555c6044b0, stream=..., ignore_errors=false, location=16) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/ServerManager/vtkSMProxy.cxx:2397
#35 0x00007fffef54ac0f in vtkSMViewProxy::StillRender (this=0x55555c6044b0) at /home/glow/work/paraview/paraviewThird/paraview/Remoting/Views/vtkSMViewProxy.cxx:428
#36 0x00007ffff6b52072 in pqView::forceRender (this=0x55555d2e9700) at /home/glow/work/paraview/paraviewThird/paraview/Qt/Core/pqView.cxx:245
#37 0x00007ffff6b51fbe in pqView::tryRender (this=0x55555d2e9700) at /home/glow/work/paraview/paraviewThird/paraview/Qt/Core/pqView.cxx:223
#38 0x00007ffff6a84578 in pqView::qt_static_metacall (_o=0x55555d2e9700, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0x7fffffffe310) at Qt/Core/pqCore_autogen/EWIEGA46WW/moc_pqView.cpp:203
#39 0x00007ffff5fad940 in ?? () from /usr/lib/libQt5Core.so.5
#40 0x00007ffff5fb197b in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/libQt5Core.so.5
#41 0x00007ffff5c7b1f1 in pqTimer::timerEvent (this=0x5555581cbc68, evt=0x7fffffffe4a0) at /home/glow/work/paraview/paraviewThird/paraview/ThirdParty/QtTesting/vtkqttesting/pqTimer.cxx:53
#42 0x00007ffff5fa2fef in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#43 0x00007ffff72ae6f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#44 0x00007ffff5f7669a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#45 0x00007ffff5fce595 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#46 0x00007ffff5fcee42 in ?? () from /usr/lib/libQt5Core.so.5
#47 0x00007fffed81943c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#48 0x00007fffed866fa9 in ?? () from /usr/lib/libglib-2.0.so.0
#49 0x00007fffed818221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#50 0x00007ffff5fcf211 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#51 0x00007ffff5f7501c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#52 0x00007ffff5f7d4a4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#53 0x0000555555562306 in main (argc=1, argv=0x5555556d4b50) at Clients/ParaView/paraview_main.cxx:138
```https://gitlab.kitware.com/paraview/paraview/-/issues/20005Trace recorder missing on view menu commands2022-05-19T16:48:59-04:00W. Alan ScottTrace recorder missing on view menu commandsThe Trace Recorder is missing right mouse menu commands on the 3d view. The one I just tried is changing block opacity. Nothing gets recorded.The Trace Recorder is missing right mouse menu commands on the 3d view. The one I just tried is changing block opacity. Nothing gets recorded.5.11 (Spring 2022)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20006IOSS reader does not work with on view menus2021-08-25T16:19:16-04:00W. Alan ScottIOSS reader does not work with on view menusThe new IOSS reader does not work with right click, on view, menus. For instance, trying to change a block's opacity or color does not work.
A real good dataset for this is g1s1.The new IOSS reader does not work with right click, on view, menus. For instance, trying to change a block's opacity or color does not work.
A real good dataset for this is g1s1.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20007Displayed file size wrong for ParaView-5.8.1-RC1-MPI-Linux-Python3.7-64bit.ta...2020-06-18T10:26:50-04:00Florian MaurinDisplayed file size wrong for ParaView-5.8.1-RC1-MPI-Linux-Python3.7-64bit.tar.gzLook at the image below, the displayed file size for ParaView-5.8.1-RC1-MPI-Linux-Python3.7-64bit.tar.gz is only 50.3MB
https://www.paraview.org/download/
Hopefully, when we get it downloaded, the file size is 442MB, and it works fine. ...Look at the image below, the displayed file size for ParaView-5.8.1-RC1-MPI-Linux-Python3.7-64bit.tar.gz is only 50.3MB
https://www.paraview.org/download/
Hopefully, when we get it downloaded, the file size is 442MB, and it works fine. I am just curious on how a displayed file size that is supposed to be computed automatically can be wrong!
![image](/uploads/ef6dc7cbe94d8291df0dd663ef154316/image.png)
@cory.quammenhttps://gitlab.kitware.com/paraview/paraview/-/issues/20008UnstructuredGrid VolumeRendering with vectors magnitude is incorrect2020-08-31T14:49:32-04:00Mathieu Westphal (Kitware)UnstructuredGrid VolumeRendering with vectors magnitude is incorrectThe results of unstructured grid volume rendering with vectors magnitude is incorrect, compared to Image volume rendering.
Steps to reproduce :
* run paraview
* Wavelet, Apply
* Calculator, "coords", Apply
* Show in a render view, ...The results of unstructured grid volume rendering with vectors magnitude is incorrect, compared to Image volume rendering.
Steps to reproduce :
* run paraview
* Wavelet, Apply
* Calculator, "coords", Apply
* Show in a render view, color by Results, Volume rendering : correct rendering
* Split view in two, create render view
* AppendDatasets, Apply (a simple way to convert to UG)
* Show in a second render view, color by Results, Volume rendering : incorrect rendering
![a](/uploads/6cfc5a78a0ab8052c679e30d144344d1/a.png)
See here for the initial report : https://discourse.paraview.org/t/multi-component-mapping-doesnt-work-with-reflect-filter/4615/4Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20009Unstructured Grid Volume Rendering by component > 0 is incorrect2020-08-31T14:46:55-04:00Mathieu Westphal (Kitware)Unstructured Grid Volume Rendering by component > 0 is incorrectThe results of unstructured grid volume rendering with the **Projected tetrahedra** mapper with vectors of a component > 0 is incorrect
Steps to reproduce :
* run paraview
* Wavelet, Apply
* Calculator, "coords", Apply
* AppendData...The results of unstructured grid volume rendering with the **Projected tetrahedra** mapper with vectors of a component > 0 is incorrect
Steps to reproduce :
* run paraview
* Wavelet, Apply
* Calculator, "coords", Apply
* AppendDatasets, Apply (a simple way to convert to UG)
* Show in a render view, color by Results, component X, Volume rendering : correct rendering
* Color by component Y or Z : nothing changes, incorrect rendering.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20010Image Volume Rendering breaks when changing array and using vectors2020-08-31T13:50:33-04:00Mathieu Westphal (Kitware)Image Volume Rendering breaks when changing array and using vectorsThe results of Image volume rendering with vectors and changing to an array with a different range breaks the rendering
Steps to reproduce :
* run paraview
* Wavelet, Apply
* Calculator, `RTData * 0.1 * iHat`, Apply
* Show in a ren...The results of Image volume rendering with vectors and changing to an array with a different range breaks the rendering
Steps to reproduce :
* run paraview
* Wavelet, Apply
* Calculator, `RTData * 0.1 * iHat`, Apply
* Show in a render view, color by Results, Volume rendering : correct rendering
* Color by RTData : correct rendering
* Color by Results : incorrect rendering (clearly a range issue)
* There is no way to fix the representation, even with playing with the range. Creating a new one fixes the issue.
![image](/uploads/85216baefb8198ce658a02b0901e492a/image.png)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20011vtkPythonAnimationCue: preserve state2020-08-31T15:01:13-04:00Utkarsh AyachitvtkPythonAnimationCue: preserve statevtkPythonAnimationCue should not use `vtkPythonInterpreter::RunSimpleString` instead build a module object from the provided script and then call functions on it.
[discourse](https://discourse.paraview.org/t/how-to-execute-a-python-scri...vtkPythonAnimationCue should not use `vtkPythonInterpreter::RunSimpleString` instead build a module object from the provided script and then call functions on it.
[discourse](https://discourse.paraview.org/t/how-to-execute-a-python-script-every-step-of-an-animation/4621/3)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20012OSPRay volume rendering is not working2020-10-29T15:11:36-04:00Michael MiglioreOSPRay volume rendering is not workingOSPRay volume rendering does not work since c3780eb52c70aa3b421c6ec68920b443944623cc
Steps:
- Create a wavelet
- Select volume representation
- Enable raytracing
@utkarsh.ayachitOSPRay volume rendering does not work since c3780eb52c70aa3b421c6ec68920b443944623cc
Steps:
- Create a wavelet
- Select volume representation
- Enable raytracing
@utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20013Set View Direction icons don't show direction2021-12-23T17:07:41-05:00Dan LipsaSet View Direction icons don't show directionThe Set View Directions -Z and +Z don't show the direction of the Z axis.
While you can see that both -Z and +Z are parallel with the viewing direction (perpendicular on the screen) you don't know which is pointing toward the user and wh...The Set View Directions -Z and +Z don't show the direction of the Z axis.
While you can see that both -Z and +Z are parallel with the viewing direction (perpendicular on the screen) you don't know which is pointing toward the user and which is pointing toward the screen.
This can be fixed by having the X and Y axes overlap the Z axis when Z is pointing toward that screen (+Z).
The same issue is true for -X, +X and -Y, +Y icons.https://gitlab.kitware.com/paraview/paraview/-/issues/20014paraview.exe has stopped working when saving launch configuration command2020-06-22T22:46:56-04:00Oren Mustakiparaview.exe has stopped working when saving launch configuration commandive created a server configuration with client/server ( reverse connection )
when im trying to configure command and save it, paraview crashes with the message
paraview.exe has stopped working
according to the event viewer the faulting m...ive created a server configuration with client/server ( reverse connection )
when im trying to configure command and save it, paraview crashes with the message
paraview.exe has stopped working
according to the event viewer the faulting module name is vtkPVVTKExtensionsCore-pv5.8.dll
Paraview 5.8.0-Windows-Python3.7-msvc2015-64bit - it happens also with paraview 5.7.0
Qt 5.12.3
Windows 10 1709
Intel Graphics 4600 display driver 20.19.15.5126https://gitlab.kitware.com/paraview/paraview/-/issues/20016NetCDFTimeAnnotationFilter error on creation2020-08-31T14:55:53-04:00Cory Quammencory.quammen@kitware.comNetCDFTimeAnnotationFilter error on creationThis is causing dashboard failures like this one: https://open.cdash.org/testDetails.php?test=896617275&build=6608294
The image with annotation appears to be generated correctly, but there are some pipeline errors encountered when the f...This is causing dashboard failures like this one: https://open.cdash.org/testDetails.php?test=896617275&build=6608294
The image with annotation appears to be generated correctly, but there are some pipeline errors encountered when the filter executes:
```
vtkExecutive.cxx:753 ERR| vtkPVCompositeDataPipeline (00000224ABAA7E70): Algorithm vtkPythonProgrammableFilter(00000224ABAA7370) returned failure for request: vtkInformation (00000224ABC9AF80)
Debug: Off
Modified Time: 1066970
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1
```
Setting a breakpoint at `vtkPythonProgrammableFilter.cxx` lines 87 and 109 (where `return 0;` is executed) shows that the `vtkInformation` object passed in is null, so the filter returns 0 and triggers the warning. Note that this error occurs any time the `NetCDFTimeAnnotationFilter` is updated.
The stack trace when the filter is created is:
```
libvtkPVVTKExtensionsFiltersPython-pv5.8.1.dylib!vtkPythonProgrammableFilter::RequestDataObject(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.quammen/src/paraview/VTKExtensions/FiltersPython/vtkPythonProgrammableFilter.cxx:87)
libvtkCommonExecutionModel-pv5.8.1.dylib!vtkPassInputTypeAlgorithm::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.quammen/src/paraview/VTK/Common/ExecutionModel/vtkPassInputTypeAlgorithm.cxx:167)
libvtkPVVTKExtensionsFiltersPython-pv5.8.1.dylib!vtkPythonProgrammableFilter::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.quammen/src/paraview/VTKExtensions/FiltersPython/vtkPythonProgrammableFilter.cxx:166)
libvtkCommonExecutionModel-pv5.8.1.dylib!vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) (/Users/cory.quammen/src/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx:746)
libvtkCommonExecutionModel-pv5.8.1.dylib!vtkCompositeDataPipeline::ExecuteDataObject(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.quammen/src/paraview/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:114)
libvtkCommonExecutionModel-pv5.8.1.dylib!vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.quammen/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:176)
libvtkCommonExecutionModel-pv5.8.1.dylib!vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (/Users/cory.quammen/src/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:368)
libvtkCommonExecutionModel-pv5.8.1.dylib!vtkDemandDrivenPipeline::UpdateDataObject() (/Users/cory.quammen/src/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:353)
libvtkCommonExecutionModel-pv5.8.1.dylib!vtkExecutive::GetOutputData(int) (/Users/cory.quammen/src/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx:449)
libvtkCommonExecutionModel-pv5.8.1.dylib!vtkAlgorithm::GetOutputDataObject(int) (/Users/cory.quammen/src/paraview/VTK/Common/ExecutionModel/vtkAlgorithm.cxx:952)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVDataAssemblyInformation::CopyFromObject(vtkObject*) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVDataAssemblyInformation.cxx:53)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned int) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkPVSessionCore.cxx:804)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkPVSessionCore::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkPVSessionCore.cxx:822)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkPVSessionBase::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkPVSessionBase.cxx:243)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProxy::GatherInformation(vtkPVInformation*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMProxy.cxx:862)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMOutputPort::GatherDataInformation() (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMOutputPort.cxx:139)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMOutputPort::GetDataInformation() (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMOutputPort.cxx:73)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMSourceProxy::GetDataInformation(unsigned int) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMSourceProxy.cxx:547)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMDomain::GetInputDataInformation(char const*, unsigned int) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMDomain.cxx:200)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMFieldDataDomain::Update(vtkSMProperty*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMFieldDataDomain.cxx:174)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProperty::UpdateDomains() (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMProperty.cxx:295)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkObject::vtkClassMemberCallback<vtkSMProperty>::operator()(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.h:370)
libvtkCommonCore-pv5.8.1.dylib!vtkObjectCommandInternal::Execute(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:925)
libvtkCommonCore-pv5.8.1.dylib!vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:626)
libvtkCommonCore-pv5.8.1.dylib!vtkObject::InvokeEvent(unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:795)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkObject::InvokeEvent(unsigned long) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.h:230)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProxyProperty::LoadState(vtkPVXMLElement*, vtkSMProxyLocator*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMProxyProperty.cxx:458)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProxy::LoadXMLState(vtkPVXMLElement*, vtkSMProxyLocator*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMProxy.cxx:2156)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMDeserializerXML::LoadProxyState(vtkPVXMLElement*, vtkSMProxy*, vtkSMProxyLocator*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMDeserializerXML.cxx:92)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMDeserializerXML::NewProxy(unsigned int, vtkSMProxyLocator*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMDeserializerXML.cxx:62)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProxyLocator::NewProxy(unsigned int) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMProxyLocator.cxx:111)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProxyLocator::LocateProxy(unsigned int) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMProxyLocator.cxx:88)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMCompoundSourceProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMCompoundSourceProxy.cxx:235)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMSessionProxyManager::NewProxy(vtkPVXMLElement*, char const*, char const*, char const*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMSessionProxyManager.cxx:337)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMSessionProxyManager::NewProxy(char const*, char const*, char const*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMSessionProxyManager.cxx:313)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMSessionProxyManager::GetPrototypeProxy(char const*, char const*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMSessionProxyManager.cxx:436)
libpqApplicationComponents-pv5.8.1.dylib!pqProxyGroupMenuManager::getAction(QString const&, QString const&) (/Users/cory.quammen/src/paraview/Qt/ApplicationComponents/pqProxyGroupMenuManager.cxx:677)
libpqApplicationComponents-pv5.8.1.dylib!pqProxyGroupMenuManager::populateMenu() (/Users/cory.quammen/src/paraview/Qt/ApplicationComponents/pqProxyGroupMenuManager.cxx:592)
libpqApplicationComponents-pv5.8.1.dylib!pqProxyGroupMenuManager::lookForNewDefinitions() (/Users/cory.quammen/src/paraview/Qt/ApplicationComponents/pqProxyGroupMenuManager.cxx:1016)
libpqApplicationComponents-pv5.8.1.dylib!vtkObject::vtkClassMemberCallback<pqProxyGroupMenuManager>::operator()(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.h:370)
libvtkCommonCore-pv5.8.1.dylib!vtkObjectCommandInternal::Execute(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:925)
libvtkCommonCore-pv5.8.1.dylib!vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:626)
libvtkCommonCore-pv5.8.1.dylib!vtkObject::InvokeEvent(unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:795)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProxyManagerForwarder::Execute(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMSessionProxyManager.cxx:115)
libvtkCommonCore-pv5.8.1.dylib!vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:626)
libvtkCommonCore-pv5.8.1.dylib!vtkObject::InvokeEvent(unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:795)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMSessionProxyManager::ExecuteEvent(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMSessionProxyManager.cxx:1141)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProxyManagerObserver::Execute(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMSessionProxyManager.cxx:97)
libvtkCommonCore-pv5.8.1.dylib!vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:626)
libvtkCommonCore-pv5.8.1.dylib!vtkObject::InvokeEvent(unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:795)
libvtkCommonCore-pv5.8.1.dylib!vtkEventForwarderCommand::Execute(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkEventForwarderCommand.cxx:30)
libvtkCommonCore-pv5.8.1.dylib!vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:626)
libvtkCommonCore-pv5.8.1.dylib!vtkObject::InvokeEvent(unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:795)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkObject::InvokeEvent(unsigned long) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.h:230)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSIProxyDefinitionManager::LoadConfigurationXML(vtkPVXMLElement*, bool) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSIProxyDefinitionManager.cxx:818)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSIProxyDefinitionManager::LoadConfigurationXMLFromString(char const*, bool) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSIProxyDefinitionManager.cxx:770)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSIProxyDefinitionManager::HandlePlugin(vtkPVPlugin*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSIProxyDefinitionManager.cxx:1196)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSIProxyDefinitionManager::OnPluginLoaded(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSIProxyDefinitionManager.cxx:1178)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkObject::vtkClassMemberCallback<vtkSIProxyDefinitionManager>::operator()(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.h:374)
libvtkCommonCore-pv5.8.1.dylib!vtkObjectCommandInternal::Execute(vtkObject*, unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:925)
libvtkCommonCore-pv5.8.1.dylib!vtkSubjectHelper::InvokeEvent(unsigned long, void*, vtkObject*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:626)
libvtkCommonCore-pv5.8.1.dylib!vtkObject::InvokeEvent(unsigned long, void*) (/Users/cory.quammen/src/paraview/VTK/Common/Core/vtkObject.cxx:795)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPluginTracker::RegisterPlugin(vtkPVPlugin*) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPluginTracker.cxx:574)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPlugin::ImportPlugin(vtkPVPlugin*) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPlugin.cxx:52)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPluginLoader::LoadPluginInternal(vtkPVPlugin*) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPluginLoader.cxx:629)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPluginLoader::LoadPluginInternal(char const*, bool) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPluginLoader.cxx:615)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPluginLoader::LoadPlugin(char const*) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPluginLoader.h:57)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPluginTracker::LoadPluginConfigurationXMLHinted(vtkPVXMLElement*, char const*, bool) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPluginTracker.cxx:471)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPluginTracker::LoadPluginConfigurationXML(vtkPVXMLElement*, bool) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPluginTracker.cxx:381)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPluginTracker::LoadPluginConfigurationXMLFromString(char const*, bool) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPluginTracker.cxx:375)
libvtkRemotingCore-pv5.8.1.dylib!vtkPVPluginLoader::LoadPluginConfigurationXMLFromString(char const*) (/Users/cory.quammen/src/paraview/Remoting/Core/vtkPVPluginLoader.cxx:637)
libvtkRemotingApplication-pv5.8.1.dylib!vtkPVPluginLoaderCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) (/Users/cory.quammen/bin/paraview-debug/CMakeFiles/vtkRemotingCoreCS/vtkPVPluginLoaderClientServer.cxx:152)
libvtkRemotingClientServerStream-pv5.8.1.dylib!vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) (/Users/cory.quammen/src/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:809)
libvtkRemotingClientServerStream-pv5.8.1.dylib!vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) (/Users/cory.quammen/src/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:424)
libvtkRemotingClientServerStream-pv5.8.1.dylib!vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) (/Users/cory.quammen/src/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:265)
libvtkRemotingClientServerStream-pv5.8.1.dylib!vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) (/Users/cory.quammen/src/paraview/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:235)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkPVSessionCore.cxx:637)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkPVSessionCore.cxx:607)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkPVSessionBase.cxx:165)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMProxy::ExecuteStream(vtkClientServerStream const&, bool, unsigned int) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMProxy.cxx:2397)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMPluginLoaderProxy::LoadPluginConfigurationXMLFromString(char const*) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMPluginLoaderProxy.cxx:53)
libvtkRemotingServerManager-pv5.8.1.dylib!vtkSMPluginManager::LoadPluginConfigurationXMLFromString(char const*, vtkSMSession*, bool) (/Users/cory.quammen/src/paraview/Remoting/ServerManager/vtkSMPluginManager.cxx:213)
libpqApplicationComponents-pv5.8.1.dylib!pqCommandLineOptionsBehavior::playTests() (/Users/cory.quammen/src/paraview/Qt/ApplicationComponents/pqCommandLineOptionsBehavior.cxx:263)
libpqApplicationComponents-pv5.8.1.dylib!pqCommandLineOptionsBehavior::processCommandLineOptions() (/Users/cory.quammen/src/paraview/Qt/ApplicationComponents/pqCommandLineOptionsBehavior.cxx:210)
libpqApplicationComponents-pv5.8.1.dylib!pqCommandLineOptionsBehavior::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (/Users/cory.quammen/bin/paraview-debug/Qt/ApplicationComponents/pqApplicationComponents_autogen/EWIEGA46WW/moc_pqCommandLineOptionsBehavior.cpp:75)
QtCore!QMetaObject::activate(QObject*, int, int, void**) (Unknown Source:0)
QtCore!QTimer::timerEvent(QTimerEvent*) (Unknown Source:0)
libvtkqttesting-pv5.8.1.dylib!pqTimer::timerEvent(QTimerEvent*) (/Users/cory.quammen/src/paraview/ThirdParty/QtTesting/vtkqttesting/pqTimer.cxx:53)
QtCore!QObject::event(QEvent*) (Unknown Source:0)
QtWidgets!QApplicationPrivate::notify_helper(QObject*, QEvent*) (Unknown Source:0)
QtWidgets!QApplication::notify(QObject*, QEvent*) (Unknown Source:0)
QtCore!QCoreApplication::notifyInternal2(QObject*, QEvent*) (Unknown Source:0)
QtCore!QTimerInfoList::activateTimers() (Unknown Source:0)
libqcocoa.dylib!QCocoaEventDispatcherPrivate::activateTimersSourceCallback(void*) (Unknown Source:0)
CoreFoundation!__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ (Unknown Source:0)
CoreFoundation!__CFRunLoopDoSource0 (Unknown Source:0)
CoreFoundation!__CFRunLoopDoSources0 (Unknown Source:0)
CoreFoundation!__CFRunLoopRun (Unknown Source:0)
CoreFoundation!CFRunLoopRunSpecific (Unknown Source:0)
HIToolbox!RunCurrentEventLoopInMode (Unknown Source:0)
```5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20017backport patches for paraview 5.8.12020-07-02T11:43:56-04:00Julien Schuellerbackport patches for paraview 5.8.1hello,
I noticed 5.8.1-RC1 is out, but these patches are still needed to fix compilation with latest dependencies (eg archlinux) OR cross-compiling (eg mingw):
- https://gitlab.kitware.com/vtk/vtk/merge_requests/6811 (hdf5 1.10.x API...hello,
I noticed 5.8.1-RC1 is out, but these patches are still needed to fix compilation with latest dependencies (eg archlinux) OR cross-compiling (eg mingw):
- https://gitlab.kitware.com/vtk/vtk/merge_requests/6811 (hdf5 1.10.x API fix)
- https://gitlab.kitware.com/paraview/paraview/-/commit/3d48a287141eb911b4888440e09c262743b4db3c (cgns 4.1 fix)
- https://gitlab.kitware.com/vtk/vtk/merge_requests/6406 (ogg/theora cmake fix)
- https://gitlab.kitware.com/vtk/vtk/merge_requests/6301 (vtk wide string path fix)
Could these be backported to the relevant branches so that no patching is necessary on final release ?https://gitlab.kitware.com/paraview/paraview/-/issues/20018Extracts: add support for spatio temporal scripts2020-10-13T14:38:51-04:00Utkarsh AyachitExtracts: add support for spatio temporal scriptsWhen Extract Generator refactor, we have temporarily lost the ability to export spatio-temporal scripts. We need to bring it back.When Extract Generator refactor, we have temporarily lost the ability to export spatio-temporal scripts. We need to bring it back.https://gitlab.kitware.com/paraview/paraview/-/issues/20019Spack: ParaView 5.8.0 with openmpi 3.1.3 fails to configure2023-03-28T12:13:58-04:00Ethan StamSpack: ParaView 5.8.0 with openmpi 3.1.3 fails to configure@utkarsh.ayachit @cory.quammen could we add this to tomorrow's discussion?
This looks like the same problem encountered here: https://discourse.paraview.org/t/building-version-5-8-0-fails/3660/16
I am trying to build 5.8.0 with Spack o...@utkarsh.ayachit @cory.quammen could we add this to tomorrow's discussion?
This looks like the same problem encountered here: https://discourse.paraview.org/t/building-version-5-8-0-fails/3660/16
I am trying to build 5.8.0 with Spack on ubuntu 18.0.4 with the spec: `spack install paraview@5.8.0 +osmesa+python3+mpi+plugins+examples ^openmpi@3.1.3`
I get this failure during CMake's configure:
```
-- Could NOT find MPI_C (missing: MPI_C_WORKS)
-- Could NOT find MPI (missing: MPI_C_FOUND C)
CMake Error at VTK/CMake/vtkModule.cmake:4111 (message):
Could not find the MPI external dependency.
Call Stack (most recent call first):
VTK/CMake/vtkModule.cmake:4634 (vtk_module_find_package)
VTK/Utilities/MPI/CMakeLists.txt:1 (vtk_module_third_party_external)
-- Configuring incomplete, errors occurred!
```
The same spec, but with 5.7.0 configures successfully: `spack install paraview@5.7.0 +osmesa+python3+mpi+plugins+examples ^openmpi@3.1.3`https://gitlab.kitware.com/paraview/paraview/-/issues/20023Extract Generators: "eyeballs" to show enable/disable state2021-11-09T16:22:30-05:00Utkarsh AyachitExtract Generators: "eyeballs" to show enable/disable stateFor extract generators, let's add an mechanism to enable/disable them using "eyeballs" (or some other icon) in the Pipeline browser.For extract generators, let's add an mechanism to enable/disable them using "eyeballs" (or some other icon) in the Pipeline browser.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20024Preview mode does not rescale text correctly2020-07-09T10:38:16-04:00Ethan StamPreview mode does not rescale text correctly@patchett2002 @utkarsh.ayachit @cory.quammen
Text scaling is mishandled in Preview mode. In this example, the Colormap text is cut off by the window size:
Using 5.8.0 and the disk_out_ref example dataset
Normal RenderView:
![Screen_S...@patchett2002 @utkarsh.ayachit @cory.quammen
Text scaling is mishandled in Preview mode. In this example, the Colormap text is cut off by the window size:
Using 5.8.0 and the disk_out_ref example dataset
Normal RenderView:
![Screen_Shot_2020-06-23_at_9.42.53_AM](/uploads/1535f63c171cd6d7b7505c184b742c90/Screen_Shot_2020-06-23_at_9.42.53_AM.png)
Preview Mode (1920x1080):
![Screen_Shot_2020-06-23_at_9.37.03_AM](/uploads/92e16749303a1fc016a6c2f12ea3a642/Screen_Shot_2020-06-23_at_9.37.03_AM.png)5.8.1https://gitlab.kitware.com/paraview/paraview/-/issues/20027Unstructured grid volume rendering: "Projected tetrahedra" does not support t...2020-08-31T14:16:26-04:00Cory Quammencory.quammen@kitware.comUnstructured grid volume rendering: "Projected tetrahedra" does not support the "Multi Components Mapping" optionThe "Projected tetrahedra" volume renderer does not support the "Multi Components Mapping" option when the color arrays contain 2 components. Steps to reproduce:
* Launch ParaView, built-in server
* Load the state file [TwoComponentStat...The "Projected tetrahedra" volume renderer does not support the "Multi Components Mapping" option when the color arrays contain 2 components. Steps to reproduce:
* Launch ParaView, built-in server
* Load the state file [TwoComponentState.pvsm](/uploads/1ba9d6da4b8c3a036ba0f603db947777/TwoComponentState.pvsm)
* In the Pipeline Browser, select the **PythonCalculator2** filter.
* Change the representation to **Volume**
* Change the color array to "TwoComponents"
* Toggle **Map Scalars** to make the **Multi Components Mapping** visible (this is a bug - it should appear when the color array is changed to "TwoComponents". Check the **Multi Components Mapping** option.
* The second component should control opacity, and opacity should go from 0 at min Z to 1 at max Z. However, no opacity mapping is being applied.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20028Text size mismatch2021-04-07T11:08:02-04:00Utkarsh AyachitText size mismatchWe want to get to point where all text in ParaView renders consistently.
**Text A:**
* Sources | Text, Change text to RTData, Apply
**Text B:**
* sources | Wavelet, Apply, Color by RTData, move scalar bar so that it's horizontal i.e. R...We want to get to point where all text in ParaView renders consistently.
**Text A:**
* Sources | Text, Change text to RTData, Apply
**Text B:**
* sources | Wavelet, Apply, Color by RTData, move scalar bar so that it's horizontal i.e. RTData oriented the same was as Text A.
* For Color Map Editor panel, edit color legend params by clicking ![image](/uploads/6551b81776cd727b4bef1593f71329e6/image.png) and change Title Font Parameters to match the Text A. i.e Arial, size = 18.
The two texts don't look the same.
![image](/uploads/eb1a99e7e85f1beef1daebaa3a8f36dc/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/20029Multiple Expressions in Find Data forgets half of the query2020-09-07T13:18:38-04:00Jean M. FavreMultiple Expressions in Find Data forgets half of the queryI wish to extract points from an unstructured grid. So, I just applied a CleantoGrid to Wavelet to make a reproducer test. The picture says it all:
Wavelet+CleantoGrid
my query should be "(RTData <= 100) & (points[:,2] > 0)" but ParaView...I wish to extract points from an unstructured grid. So, I just applied a CleantoGrid to Wavelet to make a reproducer test. The picture says it all:
Wavelet+CleantoGrid
my query should be "(RTData <= 100) & (points[:,2] > 0)" but ParaView drops the first part of it. This is v5.8.1-RC1
![FailedSelection](/uploads/24cec0462dd2c263761d4d2cd6d352c5/FailedSelection.png)5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/20030Calculator Filter Malfunctions for Dataset Names starting with a Number2021-09-21T21:43:55-04:00Joel A. KuleszaCalculator Filter Malfunctions for Dataset Names starting with a NumberThe Calculator filter malfunctions with dataset names that begin with a number.
For example, entering a calculation that should return a Result based on a dataset named `test_1` behaves correctly but a dataset named `1_test` throws an...The Calculator filter malfunctions with dataset names that begin with a number.
For example, entering a calculation that should return a Result based on a dataset named `test_1` behaves correctly but a dataset named `1_test` throws an error (see below). This behavior has been confirmed with legacy VTK (see attached) and HDF5-based XDMF files. The presence/absence of the underscore in the name has no effect.
Other filters appear to operate correctly with either dataset (e.g., Threshold).
Steps to reproduce on macOS 10.14.6:
1. Launch ParaView 5.8.0
2. File -> Open -> `block_4x4.vtk` -> Apply
3. Filters -> Calculator
4. Enter calculation formula `test_1`
5. Apply (works)
6. Change calculation formula to `1_test`
7. Apply (fails)
CC: @ethan.stam @patchett2002
![Screen_Shot_2020-06-24_at_14.24.21](/uploads/70e944b50814cce6aba12c609a2d39a6/Screen_Shot_2020-06-24_at_14.24.21.png)
[block_4x4.vtk](/uploads/6a096396a4b549d2810d82cb663b24ea/block_4x4.vtk)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/20031Show spack gitlab-ci results on Cdash2020-08-31T14:57:56-04:00Utkarsh AyachitShow spack gitlab-ci results on CdashCurrently, we have a gitlab-ci build for spack. However, the results from that are not shown in CDash which makes it hard to catch failures. We need to show spack build status (at the very least) on CDash.
One solution is as follows:
* ...Currently, we have a gitlab-ci build for spack. However, the results from that are not shown in CDash which makes it hard to catch failures. We need to show spack build status (at the very least) on CDash.
One solution is as follows:
* Under `Utilities/` add a new dir which is new CMake project for building ParaView using Spack i.e. it should merely have custom commands that runs spack using params specified to build. (see `.gitlab-ci.yml` for spack commands to use to build).
* This project can also have tests to confirm build was successful
* add CTestConfig.cmake for this project to be same as `ParaView/CTestConfig.cmake` so ctest will drop results on the same site as ParaView.
Now, one should be able to use ctest to build using spack and summit results.
Finally, update gitlab-ci.yaml to use ctest to build/test/submit instead of directly using spack.Christos TsolakisChristos Tsolakishttps://gitlab.kitware.com/paraview/paraview/-/issues/20032Extract Generators: Show progress dialog when generating extracts2020-10-29T14:39:18-04:00Utkarsh AyachitExtract Generators: Show progress dialog when generating extractsOn hitting Save Extracts, let's show the same progress (and cancel) dialog that we show when saving animations.On hitting Save Extracts, let's show the same progress (and cancel) dialog that we show when saving animations.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20033Building with OptiX2021-04-20T17:04:22-04:00Lucas GasparinoBuilding with OptiXGreetings!
It's my first time building paraview with raytracing, and I'd like to use nvidia optix for that, as it is suggested as an alternative to ospray. How would i go about configuring this in cmake? I do have Optix installed, and a...Greetings!
It's my first time building paraview with raytracing, and I'd like to use nvidia optix for that, as it is suggested as an alternative to ospray. How would i go about configuring this in cmake? I do have Optix installed, and a Quadro P4200 gpu running cuda 11.0 and latest driver. Sorry if this is a silly question, but i can't find a proper answer anywhere.
In any case, thank you very much!https://gitlab.kitware.com/paraview/paraview/-/issues/20034Nvidia Index building issue2021-06-22T19:48:02-04:00Lucas GasparinoNvidia Index building issueGreetings,
When trying to build the master version of ParaView with pvNvidiaIndex option, both the configure and compilation steps run OK. After that, the ctest fails for the plugin, and trying to use paraview with it results in the fol...Greetings,
When trying to build the master version of ParaView with pvNvidiaIndex option, both the configure and compilation steps run OK. After that, the ctest fails for the plugin, and trying to use paraview with it results in the following error:
nvindex: PVPLN init error: libnvindex.so: cannot open shared object file: No such file or directory
I did set "/path/to/paraview/lib" in my LD_LIBRARY_PATH. I had no warnings or error during compilation or "ccmake ..". Am I missing an option? I just turned to option ON, which works for all other plugins. I can't find this library anywhere, and I'm assuming it must have been built by the paraview build process. What I do find is the ../lib/paraview-5.8/plugins/pvNvidiaIndex/pvNVIDIAIndeX.so and libvtkIndeXRepresentations.so. I've tried various options in the ccmake, with the same results.
Thank you for your attention!https://gitlab.kitware.com/paraview/paraview/-/issues/20035Display changes after applying rendering, all windows re-scaled2020-06-27T14:40:30-04:00Roger RogerDisplay changes after applying rendering, all windows re-scaledI am running Paraview 5.8 on a Windows 10 system with an NVIDIA GTX1650 GPU. The program loads fine but after uploading a geometry, for example, and then selecting "Apply" to render it, everything in the Paraview environment gets re-sca...I am running Paraview 5.8 on a Windows 10 system with an NVIDIA GTX1650 GPU. The program loads fine but after uploading a geometry, for example, and then selecting "Apply" to render it, everything in the Paraview environment gets re-scaled to various sizes or magnifications. Thus, I am unable to select any menu options as they don't appear visually anymore. Some selections are in the field of view but you don't know that you are selecting them because the button is not visible.[paraview-windows10-display-issue.pdf](/uploads/a1ec98aa15c772c384c2c475cc49b576/paraview-windows10-display-issue.pdf)https://gitlab.kitware.com/paraview/paraview/-/issues/20038Build failure with external HDF5 (v1.12) and PV 5.8 build2020-07-09T16:17:34-04:00Alexander NeumannBuild failure with external HDF5 (v1.12) and PV 5.8 buildObserved error in VCPKG CI:
```
D:\buildtrees\paraview\src\4fb6e6800f-2efd43d7fc\Utilities\VisItBridge\databases\readers\M3DC1\avtM3DC1FileFormat.C(2057): error C2660: 'H5Oget_info_by_name3': function does not take 4 arguments
D:\instal...Observed error in VCPKG CI:
```
D:\buildtrees\paraview\src\4fb6e6800f-2efd43d7fc\Utilities\VisItBridge\databases\readers\M3DC1\avtM3DC1FileFormat.C(2057): error C2660: 'H5Oget_info_by_name3': function does not take 4 arguments
D:\installed\x64-windows-static\include\H5Opublic.h(188): note: see declaration of 'H5Oget_info_by_name3'
D:\buildtrees\paraview\src\4fb6e6800f-2efd43d7fc\Utilities\VisItBridge\databases\readers\M3DC1\avtM3DC1FileFormat.C(2116): error C2660: 'H5Oget_info3': function does not take 2 arguments
D:\installed\x64-windows-static\include\H5Opublic.h(187): note: see declaration of 'H5Oget_info3'
```
Either Paraview needs to set the required HDF5 preprocessor definitions to select the proper HDF5 api or VisItBridge needs updating for the new API.https://gitlab.kitware.com/paraview/paraview/-/issues/20041GhostCellsGenerator - Different behaviour in serial and parallel?2020-06-29T21:40:19-04:00Carsten UphoffGhostCellsGenerator - Different behaviour in serial and parallel?Hi,
I have a few simple **parallel** VTU files with cell-wise data, which looks as following:
![cell](/uploads/a83941cd9c67b5a0adb457d340d9fbca/cell.png)
The red and blue triangles belong to different pieces, respectively. After apply...Hi,
I have a few simple **parallel** VTU files with cell-wise data, which looks as following:
![cell](/uploads/a83941cd9c67b5a0adb457d340d9fbca/cell.png)
The red and blue triangles belong to different pieces, respectively. After applying the CellDataToPointData filter I expect to see the following:
![point](/uploads/7ce2509ec3eac2d49104758449255ccf/point.png)
Of course I need ghost cells for this to work, because the red and blue piece are not "connected" in the pvtu file. (Checking whether ghost cells work correctly is actually my intent.) Therefore, I use the GhostCellsGenerator filter, i.e. the sequence of filters
- test.pvtu
- GhostCellsGenerator
- CellDataToPointData
Doing "mpiexec -n 4 pvserver", connecting to the server, and applying the filter sequence gives the desired result. However, doing the same steps without connecting to a server, i.e. using the serial version does not give me the correct result (that is, the blue and red triangle are "disconnected").
Is this behaviour expected or am I doing something wrong? I find this highly confusing.
Note that I'm using the Paraview 5.8 (binary release) and checking the "Piece invariant" option in the CellDataToPointData filter does not change anything.
Thanks!
Carsten
Input files:
[test.pvtu](/uploads/f6619ea7c14873df9cfbbec216f090b0/test.pvtu)
[test1.vtu](/uploads/df9e5689b0cf57e0c95f2ce7ab4011e9/test1.vtu)
[test2.vtu](/uploads/38286f999a1cb327f560a3baf01fa515/test2.vtu)https://gitlab.kitware.com/paraview/paraview/-/issues/20042netCDF-CF Reader does not read all variables anymore ...2021-04-29T20:54:32-04:00Niklas RoebernetCDF-CF Reader does not read all variables anymore ...It seems that the ParaView (Master) netCDF-CF reader does not show, load or visualizes all variables anymore. It appears that only the variable that is first in the alphabet is shown as available and can be loaded and visualized. The uni...It seems that the ParaView (Master) netCDF-CF reader does not show, load or visualizes all variables anymore. It appears that only the variable that is first in the alphabet is shown as available and can be loaded and visualized. The units of the other -- not loaded -- variables are shown properly though.
How to test with ParaView Master (5.8.1):
- Load a regular or curvilinear netCDF file using the netCDF-CF reader and click on applyhttps://gitlab.kitware.com/paraview/paraview/-/issues/20043Dependency in ParaView to libmath.a from embree32020-06-30T11:22:55-04:00Alexander NeumannDependency in ParaView to libmath.a from embree3So in VCPKG CI throws the following error:
`ninja: error: '/mnt/vcpkg-ci/installed/x64-linux/lib/libmath.a', needed by 'bin/pvserver', missing and no known rule to make it`
because somehow there is a hidden dependency on embree3 which ...So in VCPKG CI throws the following error:
`ninja: error: '/mnt/vcpkg-ci/installed/x64-linux/lib/libmath.a', needed by 'bin/pvserver', missing and no known rule to make it`
because somehow there is a hidden dependency on embree3 which install libmath.a. (I mean we could simply add embree3 to ParaViews Build-Depends which solves the issue but that would probably be a hack)
Does somebody here know where this dependency might be picked up by ParaView?https://gitlab.kitware.com/paraview/paraview/-/issues/20044update loguru2020-06-30T19:21:12-04:00Utkarsh Ayachitupdate loguruv2.1.0 has several useful features like verbosity level for loguru internal messages, ability rename main thread before init, etc. that we can use.v2.1.0 has several useful features like verbosity level for loguru internal messages, ability rename main thread before init, etc. that we can use.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20045File path is not updating on macOS Paraview 5.8.02020-10-27T21:23:31-04:00lorak41File path is not updating on macOS Paraview 5.8.0File path is not updating in the file explorer when using Navigate Up.
(macOS 10.15.5, Paraview 5.8.0)
![Jun-30-2020_17-49-47](/uploads/6c105860a1ad38d5350b4dfb0f78b368/Jun-30-2020_17-49-47.gif)File path is not updating in the file explorer when using Navigate Up.
(macOS 10.15.5, Paraview 5.8.0)
![Jun-30-2020_17-49-47](/uploads/6c105860a1ad38d5350b4dfb0f78b368/Jun-30-2020_17-49-47.gif)5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20048Separate Opacity Array: can't specify custom opacity range2020-08-25T21:14:06-04:00Utkarsh AyachitSeparate Opacity Array: can't specify custom opacity rangeSteps:
* Wavelet, Apply
* Gradient, Apply
* Choose Volume representation
* From display properties, check **Use Separate Opacity Array** and make sure RTDataGradient is selected.
* Open Color Map Editor...note that the ranges for color a...Steps:
* Wavelet, Apply
* Gradient, Apply
* Choose Volume representation
* From display properties, check **Use Separate Opacity Array** and make sure RTDataGradient is selected.
* Open Color Map Editor...note that the ranges for color and opacity transfer functions are different -- as expected.
Now hit "Rescale To Custom Range" and specify a range. Issues:
1. you can only specify 1 range, not separate for color and opacity
2. range chosen is set for both color and opacity transfer functions which probably not correct.5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20051Edges visible on backface depending on the aspect ratio of the geometry2020-07-01T16:42:06-04:00Florian MaurinEdges visible on backface depending on the aspect ratio of the geometryDepending on the aspect ratio of the geometry, the edges on the backface of the geometry can be visible whereas the opacity is 1. But I don't think it is a problem of opacity, more a problem of edges vs aspect ratio.
This issue is simila...Depending on the aspect ratio of the geometry, the edges on the backface of the geometry can be visible whereas the opacity is 1. But I don't think it is a problem of opacity, more a problem of edges vs aspect ratio.
This issue is similar to https://gitlab.kitware.com/paraview/paraview/-/issues/19723, but I am running on Paraview 5.8.1 RC1 and I have already observed the benefits of this fix for the representation in general (but not the issue reported here!).
To reproduce:
* Source -> unstructured cell type -> apply
* Change the representation to surface with edges
* Select hex with a grid of 1 x 10 x 1000, apply. See the spurious edges on the blackface of the first picture
* Select hex with a grid of 1 x 10 x 10, apply. Everything looks ok, see the second picture.
![grid1x10x1000](/uploads/7da379c5ea03e134cb38ee327b78012f/grid1x10x1000.png)
![grid1x10x10](/uploads/689d4f28403164a2f0adba111e731177/grid1x10x10.png)https://gitlab.kitware.com/paraview/paraview/-/issues/20052TimeValue field data is wrong for vtkNonOverlappingAMR files written in Catalyst2020-12-14T08:20:09-05:00Boonthanome NouanesengsyTimeValue field data is wrong for vtkNonOverlappingAMR files written in CatalystThe Pagosa adaptor uses Catalyst to write vtkNonOverlappingAMR files as .vth files. TimeValue is a standard field data added by Catalyst and XML writers to store time information.
We are trying to store simulation time in TimeValue in ...The Pagosa adaptor uses Catalyst to write vtkNonOverlappingAMR files as .vth files. TimeValue is a standard field data added by Catalyst and XML writers to store time information.
We are trying to store simulation time in TimeValue in vth files. The problem is that TimeValue is correct for the first timestep, but stays the same value for each timestep afterwards. I have attached an example dataset. In the example dataset, if you open the .vth files in a text editor and see the TimeValue entry, you can check the min and max range and see that TimeValue is always the same.
Example dataset: [GridCellData.tar.gz](/uploads/9c1206d08b9a45dc495184337570139f/GridCellData.tar.gz)
```
GridCellData_1.vth, TimeValue=1.002
GridCellData_2.vth, TimeValue=1.002
GridCellData_3.vth, TimeValue=1.002
etc...
```
There are two places where TimeValue is being added: 1) in the Catalyst code (vtkCPProcessor.cxx, line 250) and 2) XML writers.
I checked the code in Catalyst, and TimeValue seems to be set to the correct time there.
It is in the XML writers where the problem seems to occur. Specifically, in vtkXMLCompositeDataWriter.cxx, function WriteData(), where the TimeValue field data is getting added. If you query the time being used there, it is the wrong time.
The strange thing is that if I query the time of the grid at any point in the adaptor or catalyst python script, it shows the correct time. Somehow by the time the code gets to the XML writer, querying the time gives the wrong answer.
Also, sometimes I see this warning when running. Seems likely to be related.
`( 13.808s) [pvbatch.9 ]vtkPVTrivialProducer.cx:95 WARN| vtkPVTrivialProducer (0xf950250): Requesting time 5.50247 but only 1.00257 is available`
The Pagosa adaptor also writes out vtm files. The vtm files do no have this issue. TimeValue has the correct time. Also, the vth files have vti files associated with them. Those vti files also have the right time. It's something specific to the .vth file.
Note: When I say "query the time", I mean something like the below code. It's exactly how the code which adds TimeValue get the time.
`double time = grid->GetInformation()->Get(vtkDataObject::DATA_TIME_STEP());`
@patchett2002 @cory.quammen
How to Reproduce
-----------------------------
Example dataset: [GridCellData.tar.gz](/uploads/9c1206d08b9a45dc495184337570139f/GridCellData.tar.gz)
Catalyst python script: [CoProcess_vth.py](/uploads/49b84d842d1066b39c2deb298001e633/CoProcess_vth.py)
Miniapp script: [filedriver_miniapp.py](/uploads/5278610bc8073da11673fb41039764a1/filedriver_miniapp.py)
I have modified `filedriver_miniapp.py` from the original so that it sets the time to be 0, 1, 2, etc., independent of what the time was in the original files that were read in. So you would expect in the resulting files to have `TimeValue` of 0, 1, 2, etc.
To run, use the command
`pvpython filedriver_miniapp.py -g "GridCellData/*.vth" -s CoProcess_vth.py`
The resulting files will be in a directory called `pv_files`. Load the .vth files in a text editor, and inspect the `TimeValue` xml entry. `TimeValue` will be 0 for all .vth files.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20053vth files not working correctly with TimeArray2020-11-25T15:19:28-05:00Boonthanome Nouanesengsyvth files not working correctly with TimeArrayWe have a set of vth files written by the Pagosa adaptor. The files have field data containing TimeValue, Cycle Number, and Simulation Time. When using the nightly build of Paraview, which has the feature of being able to choose the Time...We have a set of vth files written by the Pagosa adaptor. The files have field data containing TimeValue, Cycle Number, and Simulation Time. When using the nightly build of Paraview, which has the feature of being able to choose the Time Array, choosing Simulation Time for the Time Array creates problems, and breaks things.
Note that we also have a set of vtm files, but there doesn't seem to be any issues with the vtm files, just vth files.
Example dataset: [insitu.zip](/uploads/656d9c987a42e89c848cfaa05a94680a/insitu.zip)
How to reproduce:
1. Use a nightly build of Paraview
2. Choose the .vth files as a file series
3. The Time Array is automatically set to TimeValue, hit Apply to load
4. Note that there are 7 timesteps loaded
5. Change Time Array to Simulation Time, hit Apply
6. If you check the "Time" dropbox, the values haven't been updated
7. Step forward through a timestep
8. Change the Time Array back to TimeValue, hit Apply
9. Now Paraview says there are only two timesteps loaded
Pat has investigated this and gave an explanation of what is going on:
> XMLMultiBlockReader is a XMLCompositeDataSetReader is a XMLReader
> XMLUniformGridAMRReader is a XMLCompositeDataSetReader is a XMLReader
>
> When I change from TimeValue to CycleNumber with the .vtm, Modified() is set to true and RequestInformation is called (on MultiBlock, then Composite, and finally XMLReader). That causes the ActiveTimeArray to be set to CycleNumber and causes each of the seven .vtm files to be read. The data value corresponding to CycleNumber is pulled out of the FieldData and stored so that TIME_STEPS can be set. Then it goes back to the first file and loads the data via RequestData.
>
> When we change TimeValue to CycleNumber with the .vth, Modified() is set to true, but some extra stuff is called first. This includes RequestDataObject(), ReadVTKFile() and ReadPrimaryElement(). This last one calls XMLReader::ReadPrimaryElement which calls XMLReader::ReadXMLInformation which is where the CycleNumber is fetched.
>
> Then the regular RequestInformation sequence is called on UniformGridAMRReader, CompositeReader and XMLReader. The problem is that when XMLReader::ReadXMLInformation() was called the first time, it changed Modified() to false. So when it is called this time, and should read all the .vth and pull
> out the CycleNumber, that part does not execute, because it thinks there is no change.
>
> I was able to test this by removing the Modified() reset and was able to get it to work, but of course other stuff would be wrong.
>
> I think there is a problem in vtkXMLUniformGridAMRReader in that it should not be reading the FieldData and allowing the Modified flag to be reset prematurely.
@patchett2002 @cory.quammen5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20056Installation issue with spack: fails on cmake2022-06-23T08:16:56-04:00Navdeep RanaInstallation issue with spack: fails on cmakeI have opened the issue [#17326](https://github.com/spack/spack/issues/17326) on spack repository as well. Opening it here for visibility.
I am trying to install paraview with cuda support, which fails with the following cmake error
``...I have opened the issue [#17326](https://github.com/spack/spack/issues/17326) on spack repository as well. Opening it here for visibility.
I am trying to install paraview with cuda support, which fails with the following cmake error
```cmake
CMake Error: The inter-target dependency graph contains the following strongly connected component (cycle):
"vtkPVCatalystPython" of type STATIC_LIBRARY
depends on "ClientKit" (weak)
depends on "PythonCatalyst-objects" (weak)
depends on "PythonInitializer" (weak)
depends on "vtkPVClientWebPython" (weak)
depends on "vtkPVPythonCatalystPython" (weak)
"vtkPVPythonCatalystPython" of type STATIC_LIBRARY
depends on "PythonCatalyst-objects" (weak)
depends on "PythonInitializer" (weak)
depends on "vtkPVClientWebPython" (weak)
depends on "ClientKit" (weak)
depends on "vtkPVCatalystPython" (weak)
"ClientKit" of type STATIC_LIBRARY
depends on "PythonInitializer" (weak)
depends on "vtkPVClientWebPython" (weak)
depends on "vtkPVCatalystPython" (weak)
depends on "vtkPVPythonCatalystPython" (weak)
depends on "PythonCatalyst-objects" (strong)
"vtkPVClientWebPython" of type STATIC_LIBRARY
depends on "ClientKit" (weak)
depends on "PythonCatalyst-objects" (weak)
depends on "PythonInitializer" (weak)
depends on "vtkPVCatalystPython" (weak)
depends on "vtkPVPythonCatalystPython" (weak)
"PythonInitializer" of type STATIC_LIBRARY
depends on "vtkPVClientWebPython" (weak)
depends on "ClientKit" (weak)
depends on "PythonCatalyst-objects" (weak)
depends on "vtkPVCatalystPython" (weak)
depends on "vtkPVPythonCatalystPython" (weak)
"PythonCatalyst-objects" of type OBJECT_LIBRARY
depends on "PythonInitializer" (weak)
depends on "vtkPVClientWebPython" (weak)
depends on "ClientKit" (weak)
depends on "vtkPVCatalystPython" (weak)
depends on "vtkPVPythonCatalystPython" (weak)
At least one of these targets is not a STATIC_LIBRARY. Cyclic dependencies are allowed only among static libraries.
CMake Generate step failed. Build files cannot be regenerated correctly.
```
### Steps to reproduce the issue
```
$ spack install paraview +cuda +hdf5 +mpi +python3 -shared ^cuda@10.1.0
```
### Information on your system
```
* **Spack:** 0.15.0-2-aaf6f80d4
* **Python:** 3.6.8
* **Platform:** linux-ubuntu18.04-broadwell
```
### Additional information
I have cuda locally installed, with the following in my `.spack/packages.yaml` :
```yaml
cuda:
paths:
cuda@10.1.0: /usr/local/cuda-10.1
```
[spack-build-env.txt](https://github.com/spack/spack/files/4856724/spack-build-env.txt)
[spack-build-out.txt](https://github.com/spack/spack/files/4856725/spack-build-out.txt)
@chuckatkins @danlipsa
### General information
* [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
* [x] I have run `spack maintainers <name-of-the-package>` and @mentioned any maintainers
* [x] I have uploaded the build log and environment files
* [x] I have searched the issues of this repo and believe this is not a duplicatehttps://gitlab.kitware.com/paraview/paraview/-/issues/20057writer for vtkNonOverlappingAMR in Catalyst2020-08-19T18:56:04-04:00Boonthanome Nouanesengsywriter for vtkNonOverlappingAMR in CatalystFor the Pagosa adaptor we want to write vtkNonOverlappingAMR files to disk. The Catalyst python script currently uses the writer XMLHierarchicalBoxDataWriter to write those files. But that writer seems deprecated. I tried using a differe...For the Pagosa adaptor we want to write vtkNonOverlappingAMR files to disk. The Catalyst python script currently uses the writer XMLHierarchicalBoxDataWriter to write those files. But that writer seems deprecated. I tried using a different writer, for example XMLUniformGridAMRWriter, and got the following error when running:
`( 2.480s) [pvbatch.0 ]vtkSIProxyDefinitionMan:526 ERR| vtkSIProxyDefinitionManager (0xacb9b30): No proxy that matches: group=insitu_writer_parameters and proxy=XMLUniformGridAMRWriter were found.`
My questions:
1. What is the proper writer to use for writing vtkNonOverlappingAMR files?
2. Why can't XMLUniformGridAMRWriter be used in Catalyst?
@patchett2002 @cory.quammen5.8.1https://gitlab.kitware.com/paraview/paraview/-/issues/20060Paraview 5.8.0 compile error on RHEL 8.22021-06-22T18:08:50-04:00Orion PoplawskiParaview 5.8.0 compile error on RHEL 8.2I'm trying to build the Fedora EPEL paraview package for EPEL8 and getting:
```
[ 96%] Linking CXX executable ../../bin/pvrenderserver
cd /builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/Clients/CommandLineExecutable...I'm trying to build the Fedora EPEL paraview package for EPEL8 and getting:
```
[ 96%] Linking CXX executable ../../bin/pvrenderserver
cd /builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/Clients/CommandLineExecutables && /usr/bin/cmake -E cmake_link_script CMakeFiles/pvrenderserver.dir/link.txt --verbose=1
/usr/bin/c++ -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -DNDEBUG -Wl,-lc -Wl,-lc -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld CMakeFiles/pvrenderserver.dir/pvrenderserver.cxx.o -o ../../bin/pvrenderserver -Wl,-rpath,/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/lib/paraview:/usr/lib64/openmpi/lib: ../../lib/paraview/libvtkRemotingApplication.so.5.8 ../../lib/paraview/libvtkUtilitiesPythonInitializer.so.5.8 ../../lib/paraview/libvtkRemotingServerManager.so.5.8 /usr/lib64/libprotobuf.so ../../lib/paraview/libvtkRemotingCore.so.5.8 ../../lib/paraview/libvtkPythonInterpreter.so.5.8 /usr/lib64/libpython3.6m.so ../../lib/paraview/libvtkRemotingClientServerStream.so.5.8 ../../lib/paraview/libvtkPVVTKExtensionsCore.so.5.8 /usr/lib64/libjsoncpp.so ../../lib/paraview/libvtkIOXML.so.5.8 ../../lib/paraview/libvtkIOXMLParser.so.5.8 ../../lib/paraview/libvtkParallelCore.so.5.8 ../../lib/paraview/libvtkCommonExecutionModel.so.5.8 ../../lib/paraview/libvtkCommonDataModel.so.5.8 ../../lib/paraview/libvtkCommonMisc.so.5.8 ../../lib/paraview/libvtkCommonTransforms.so.5.8 ../../lib/paraview/libvtkCommonMath.so.5.8 ../../lib/paraview/libvtkCommonCore.so.5.8 -lpthread ../../lib/paraview/libvtksys.so.5.8 -ldl -Wl,-rpath-link,/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/lib/paraview:/usr/lib64/openmpi/lib
make[2]: Leaving directory '/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi'
/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/lib/paraview/libvtkIOParallelExodus.so.1: undefined reference to `ompi_mpi_cxx_op_intercept'
/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/lib/paraview/libvtkIOParallelExodus.so.1: undefined reference to `MPI::Win::Free()'
/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/lib/paraview/libvtkIOParallelExodus.so.1: undefined reference to `MPI::Datatype::Free()'
/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/lib/paraview/libvtkIOParallelExodus.so.1: undefined reference to `MPI::Comm::Comm()'
collect2: error: ld returned 1 exit status
```
and indeed it appears that libvtkIOParallelExodus.so.1 is not being linked to the mpi library:
```
/usr/bin/c++ -fPIC -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -DNDEBUG -Wl,-lc -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -shared -Wl,-soname,libvtkIOParallelExodus.so.1 -o ../../../lib/paraview/libvtkIOParallelExodus.so.5.8 CMakeFiles/IOParallelExodus.dir/vtkIOParallelExodusObjectFactory.cxx.o CMakeFiles/IOParallelExodus.dir/vtkPExodusIIReader.cxx.o CMakeFiles/IOParallelExodus.dir/vtkPExodusIIWriter.cxx.o -Wl,-rpath,/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/lib/paraview:/usr/lib64/openmpi/lib: ../../../lib/paraview/libvtkIOExodus.so.5.8 ../../../lib/paraview/libvtkFiltersCore.so.5.8 ../../../lib/paraview/libvtkParallelCore.so.5.8 ../../../lib/paraview/libvtkexodusII.so.5.8 /usr/lib64/openmpi/lib/libnetcdf.so ../../../lib/paraview/libvtkIOXMLParser.so.5.8 ../../../lib/paraview/libvtkIOCore.so.5.8 ../../../lib/paraview/libvtkCommonExecutionModel.so.5.8 ../../../lib/paraview/libvtkCommonDataModel.so.5.8 ../../../lib/paraview/libvtkCommonTransforms.so.5.8 ../../../lib/paraview/libvtkCommonMisc.so.5.8 ../../../lib/paraview/libvtkCommonMath.so.5.8 ../../../lib/paraview/libvtkCommonCore.so.5.8 ../../../lib/paraview/libvtksys.so.5.8 -ldl -lpthread -Wl,-rpath-link,/builddir/build/BUILD/ParaView-v5.8.0/x86_64-redhat-linux-gnu-openmpi/lib/paraview
```
There are some differences between the compile flags on Fedora 33 and EPEL 8 that seem to account for why this compiles on Fedora 33 (likely -Wl,--as-needed on F33).5.10 (Fall 2021)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20061ParaView Web Apps and Install locations2020-11-17T21:09:47-05:00Utkarsh AyachitParaView Web Apps and Install locationsCurrently all the various paraview web apps are installed under `../share` with the following structure:
```
> tree install/share/paraview/ -d 2
install/share/paraview/
└── web
├── divvy
│ ├── server
│ └── www
├── flo...Currently all the various paraview web apps are installed under `../share` with the following structure:
```
> tree install/share/paraview/ -d 2
install/share/paraview/
└── web
├── divvy
│ ├── server
│ └── www
├── flow
│ ├── server
│ │ └── flow
│ │ ├── configs
│ │ ├── plugins
│ │ └── processing
│ └── www
│ ├── css
│ ├── fonts
│ ├── img
│ └── js
├── glance
│ └── www
│ └── icons
├── lite
│ ├── server
│ └── www
│ ├── css
│ ├── fonts
│ ├── icons
│ ├── img
│ └── js
└── visualizer
├── server
└── www
```
Instead, let's create Python package for each of them with the `www` directory part of that package and install it under site-packages. Then folks can launch the server with `pvpython -m ....` easily without having to specify path to the html pages since the package should be able to figure it out.
cc: @sebastien.jourdain5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20064Catalyst connection crash2020-08-31T14:59:46-04:00Nicolas VuailleCatalyst connection crashOn paraview master:
- `Catalyst` \ `Connect`
- `OK`
crash.
backtrace:
```
�[0m�[1m�[91m
Loguru caught a signal: SIGSEGV
�[0m�[0m�[31mStack trace:
58 0x5596fa967d5e ./bin/paraview(+0x7d5e) [0x5596fa967d5e]
57 0x7fb0878c900...On paraview master:
- `Catalyst` \ `Connect`
- `OK`
crash.
backtrace:
```
�[0m�[1m�[91m
Loguru caught a signal: SIGSEGV
�[0m�[0m�[31mStack trace:
58 0x5596fa967d5e ./bin/paraview(+0x7d5e) [0x5596fa967d5e]
57 0x7fb0878c9002 __libc_start_main + 242
56 0x5596fa96e102 ./bin/paraview(+0xe102) [0x5596fa96e102]
55 0x7fb085c815c4 QCoreApplication::exec() + 148
54 0x7fb085c7913c QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 300
53 0x7fb085cd3331 QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 97
52 0x7fb07d50e221 g_main_context_iteration + 49
51 0x7fb07d55d1d9 /usr/lib/libglib-2.0.so.0(+0xa01d9) [0x7fb07d55d1d9]
50 0x7fb07d50f43c g_main_context_dispatch + 604
49 0x7fb075ac0c8c /usr/lib/libQt5XcbQpa.so.5(+0x5ec8c) [0x7fb075ac0c8c]
48 0x7fb08602ab4c QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 188
47 0x7fb086051354 QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) + 356
46 0x7fb085c7a7ba QCoreApplication::notifyInternal2(QObject*, QEvent*) + 298
45 0x7fb086fb1702 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 130
44 0x7fb08700e7ea /usr/lib/libQt5Widgets.so.5(+0x1b97ea) [0x7fb08700e7ea]
43 0x7fb085c7a7ba QCoreApplication::notifyInternal2(QObject*, QEvent*) + 298
42 0x7fb086fb8ac8 QApplication::notify(QObject*, QEvent*) + 1816
41 0x7fb086fb1702 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 130
40 0x7fb086ff3b35 QWidget::event(QEvent*) + 4229
39 0x7fb08713918b QMenu::keyPressEvent(QKeyEvent*) + 2795
38 0x7fb087136552 /usr/lib/libQt5Widgets.so.5(+0x2e1552) [0x7fb087136552]
37 0x7fb08712ef1b /usr/lib/libQt5Widgets.so.5(+0x2d9f1b) [0x7fb08712ef1b]
36 0x7fb086fad805 QAction::activate(QAction::ActionEvent) + 229
35 0x7fb086faaf23 QAction::triggered(bool) + 67
34 0x7fb085cb1a60 /usr/lib/libQt5Core.so.5(+0x2eaa60) [0x7fb085cb1a60]
33 0x7fb0875a9ff9 /home/nicolas/ParaView/paraview2/build/bin/../lib/libpqApplicationComponents-pv5.8.so.1(+0xbeff9) [0x7fb0875a9ff9]
32 0x7fb0875b1514 /home/nicolas/ParaView/paraview2/build/bin/../lib/libpqApplicationComponents-pv5.8.so.1(+0xc6514) [0x7fb0875b1514]
31 0x7fb0875e3976 pqCatalystConnectReaction::connect() + 80
30 0x7fb086b26e68 pqLiveInsituManager::connect(pqServer*, int) + 410
29 0x7fb086b2922d pqLiveInsituVisualizationManager::pqLiveInsituVisualizationManager(int, pqServer*) + 777
28 0x7fb0867eadf8 pqObjectBuilder::createServer(pqServerResource const&, int) + 1258
27 0x7fb0856f1c8a vtkSMSession::ConnectToCatalyst() + 96
26 0x7fb084bd58ac vtkProcessModule::RegisterSession(vtkSession*) + 160
25 0x7fb0819e316d vtkObject::InvokeEvent(unsigned long, void*) + 61
24 0x7fb0819e2c53 /home/nicolas/ParaView/paraview2/build/bin/../lib/libvtkCommonCore-pv5.8.so.1(+0x632c53) [0x7fb0819e2c53]
23 0x7fb0819e3ebb /home/nicolas/ParaView/paraview2/build/bin/../lib/libvtkCommonCore-pv5.8.so.1(+0x633ebb) [0x7fb0819e3ebb]
22 0x7fb0856d7122 /home/nicolas/ParaView/paraview2/build/bin/../lib/libvtkRemotingServerManager-pv5.8.so.1(+0x228122) [0x7fb0856d7122]
21 0x7fb0856d50b3 vtkSMProxyManager::ConnectionsUpdated(vtkObject*, unsigned long, void*) + 61
20 0x7fb0856d521f vtkSMProxyManager::SetActiveSession(long long) + 85
19 0x7fb0819e316d vtkObject::InvokeEvent(unsigned long, void*) + 61
18 0x7fb0819e2c53 /home/nicolas/ParaView/paraview2/build/bin/../lib/libvtkCommonCore-pv5.8.so.1(+0x632c53) [0x7fb0819e2c53]
17 0x7fb08175b661 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 71
16 0x7fb0858c2700 /home/nicolas/ParaView/paraview2/build/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x58700) [0x7fb0858c2700]
15 0x7fb0858c2773 /home/nicolas/ParaView/paraview2/build/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x58773) [0x7fb0858c2773]
14 0x7fb08589292e /home/nicolas/ParaView/paraview2/build/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x2892e) [0x7fb08589292e]
13 0x7fb085cb1a60 /usr/lib/libQt5Core.so.5(+0x2eaa60) [0x7fb085cb1a60]
12 0x7fb086a1d9db /home/nicolas/ParaView/paraview2/build/bin/../lib/libpqComponents-pv5.8.so.1(+0xdf9db) [0x7fb086a1d9db]
11 0x7fb086a47892 pqActiveObjects::onActiveServerChanged() + 102
10 0x7fb086a47c13 pqActiveObjects::setActiveServer(pqServer*) + 891
9 0x7fb086a471f8 pqActiveObjects::triggerSignals() + 592
8 0x7fb086a1e32c pqActiveObjects::viewChanged(pqView*) + 94
7 0x7fb085cb1a60 /usr/lib/libQt5Core.so.5(+0x2eaa60) [0x7fb085cb1a60]
6 0x7fb086a2d68b /home/nicolas/ParaView/paraview2/build/bin/../lib/libpqComponents-pv5.8.so.1(+0xef68b) [0x7fb086a2d68b]
5 0x7fb086b89fe9 pqPropertiesPanel::setView(pqView*) + 47
4 0x7fb086b8b73a pqPropertiesPanel::updateButtonState() + 194
3 0x7fb086b88678 /home/nicolas/ParaView/paraview2/build/bin/../lib/libpqComponents-pv5.8.so.1(+0x24a678) [0x7fb086b88678]
2 0x7fb086b26aa9 pqLiveInsituManager::isInsitu(pqProxy*) + 71
1 0x7fb0868170d6 pqProxy::getProxy() const + 16
0 0x7fb0878de3e0 /usr/lib/libc.so.6(+0x3c3e0) [0x7fb0878de3e0]�[0m
�[0m�[31m( 3.917s) [paraview ] :0 FATL| Signal: SIGSEGV�[0m
```5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachit