ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-23T19:24:18-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17366Representation settings not being saved in custom default settings2021-03-23T19:24:18-04:00Cory Quammencory.quammen@kitware.comRepresentation settings not being saved in custom default settingsCustom default settings do not seem to be either saved or respected when creating new representations. Steps to reproduce:
* Run ParaView, built-in server
* Load **can.ex2**, all variables on
* Select some points on the surface
* Add **...Custom default settings do not seem to be either saved or respected when creating new representations. Steps to reproduce:
* Run ParaView, built-in server
* Load **can.ex2**, all variables on
* Select some points on the surface
* Add **Plot Selection Over Time** filter
* Uncheck the **Show Median** checkbox.
* Click the disk icon in the **Display** section of the Properties panel
* Quit ParaView
* Repeat the first 4 steps. Notice the **Show Median** checkbox is checked, even though we saved the setting default to not be checked.
Now, manually add the following to `/.config/ParaView/ParaView-UserSettings.json`:
```
{
"views" : {
"QuartileChartView" : {
"ShowMedian" : false
}
}
}
```
Repeat the first 4 steps above again. Notice **Show Median** is checked.https://gitlab.kitware.com/paraview/paraview/-/issues/17365PythonQt plugin fails to build2021-11-15T04:46:57-05:00Orion PoplawskiPythonQt plugin fails to buildIt's looking for PythonQt_QtBindings.h which is not present in the Fedora build of PythonQt either versions 2.1 or 3.1.It's looking for PythonQt_QtBindings.h which is not present in the Fedora build of PythonQt either versions 2.1 or 3.1.https://gitlab.kitware.com/paraview/paraview/-/issues/17360Selection actions should warn when selection is not enabled2020-05-06T05:34:42-04:00Shawn WaldonSelection actions should warn when selection is not enabledFor dataserver-renderserver mode, the selection actions in the view frame don't do anything, the user should be warned about this.For dataserver-renderserver mode, the selection actions in the view frame don't do anything, the user should be warned about this.https://gitlab.kitware.com/paraview/paraview/-/issues/17341Menu scroll bars too narrow2018-02-26T13:16:35-05:00W. Alan ScottMenu scroll bars too narrowWith PV version 5.3, menu scroll bars are too narrow. I am having issues finding them, and on a Mac they actually hide! I just watched a user have issues finding them also. Please make them wider and/or a different color so users can ...With PV version 5.3, menu scroll bars are too narrow. I am having issues finding them, and on a Mac they actually hide! I just watched a user have issues finding them also. Please make them wider and/or a different color so users can find them!
The most obvious example is the Properties tab, after reading in can.exo.https://gitlab.kitware.com/paraview/paraview/-/issues/17333Ensight reader cannot advance to second time step in parallel2021-03-23T13:23:05-04:00Andrew BauerEnsight reader cannot advance to second time step in parallelSteps to reproduce:
1. Run pvserver with 2 mpi processes and connect the PV GUI
2. Load the LB.case in [data_pv_error.tar.gz](/uploads/0b655e3db2cc51a5a1de6c28543c1b4d/data_pv_error.tar.gz)
3. Advance to the second time step
ParaVie...Steps to reproduce:
1. Run pvserver with 2 mpi processes and connect the PV GUI
2. Load the LB.case in [data_pv_error.tar.gz](/uploads/0b655e3db2cc51a5a1de6c28543c1b4d/data_pv_error.tar.gz)
3. Advance to the second time step
ParaView will freeze. Note that this works with a serial pvserver processhttps://gitlab.kitware.com/paraview/paraview/-/issues/17329simple.SaveAnimation doesn't work in pvbatch with symmetric mode.2023-06-15T10:16:56-04:00Utkarsh Ayachitsimple.SaveAnimation doesn't work in pvbatch with symmetric mode.The `SaveAnimation` tests fails in symmetric batch mode. I believe this is due to all the data information being invalid.The `SaveAnimation` tests fails in symmetric batch mode. I believe this is due to all the data information being invalid.https://gitlab.kitware.com/paraview/paraview/-/issues/17327Change "Save Screenshot" scale factor to 1.5X instead of 2X2021-03-23T13:08:22-04:00Utkarsh AyachitChange "Save Screenshot" scale factor to 1.5X instead of 2XSee discussion on paraview/paraview!1478See discussion on paraview/paraview!1478https://gitlab.kitware.com/paraview/paraview/-/issues/17325pqProxyWidgetDialog ends up being too wide2021-03-23T13:08:30-04:00Utkarsh AyachitpqProxyWidgetDialog ends up being too wideSee paraview/paraview!1478, we get the following by default:
![image](/uploads/0e38aaec35d32d9f1afb793296896732/image.png)
When, ideally it should look like this:
![image](/uploads/08ea917995413c15af7006c78b2a60bd/image.png)See paraview/paraview!1478, we get the following by default:
![image](/uploads/0e38aaec35d32d9f1afb793296896732/image.png)
When, ideally it should look like this:
![image](/uploads/08ea917995413c15af7006c78b2a60bd/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/17321Link Editor Selection does not update correctly2021-03-23T13:08:47-04:00Mathieu Westphal (Kitware)Link Editor Selection does not update correctlyWhen using Link Editor to edit a Selection Link, the object tree is not selected correctly :
How to reproduce :
* Open ParaView
* Create Wavelet
* Create a second Wavelet
* Select point on second wavelet
* Right lick on first wavel...When using Link Editor to edit a Selection Link, the object tree is not selected correctly :
How to reproduce :
* Open ParaView
* Create Wavelet
* Create a second Wavelet
* Select point on second wavelet
* Right lick on first wavelet to create a selection link
* Tools->LinkManager
* Click on selection link
* Edit
* Objects Trees are not correctly selected - both sources are not selected
the same manipulation with a camera link works without problems.https://gitlab.kitware.com/paraview/paraview/-/issues/17301Paraview Tecplot reader doesn't map variables onto X,Y,Z coordinates2021-03-23T13:08:56-04:00Christopher NealParaview Tecplot reader doesn't map variables onto X,Y,Z coordinatesHi,
I noticed that if I have a tecplot formatted file that has actual physical coordinates(x,y,z), and the first three variable names are "X", "Y", and "Z", then Paraview can read the file just fine. If the variable name list doesn't co...Hi,
I noticed that if I have a tecplot formatted file that has actual physical coordinates(x,y,z), and the first three variable names are "X", "Y", and "Z", then Paraview can read the file just fine. If the variable name list doesn't contain "X","Y", or "Z" though, Paraview completely fails are loading in the data. Nothing gets displayed on the screen because no variables appear to be mapped to Paraview's X,Y,Z axes. Tecplot doesn't seem to have this issue, and the Tecplot data format guide makes so such mention of any requirement to include "X", "Y", or "Z" in the variable names list.
Loads in just fine:
[test_tecplot_file.dat](/uploads/b56fd61404487ad7b640e193476501d2/test_tecplot_file.dat)
Fails to recognize that the first three variables are the axes
[test_tecplot_file2.dat](/uploads/35788bb5bb0c0243119e6c15a4b40a96/test_tecplot_file2.dat)https://gitlab.kitware.com/paraview/paraview/-/issues/172962d plots axis grid is too light2018-02-26T13:16:53-05:00W. Alan Scott2d plots axis grid is too lightThe Axis Grid Color is too light for 2d. Replicate as follows:
* 5.3.0, Windows.
* Wavelet. Apply.
* Plot over line. Apply.
Notice how faint the axis grid is. Click Advanced on the Properties tab. Left Axis Grid Color. Please chan...The Axis Grid Color is too light for 2d. Replicate as follows:
* 5.3.0, Windows.
* Wavelet. Apply.
* Plot over line. Apply.
Notice how faint the axis grid is. Click Advanced on the Properties tab. Left Axis Grid Color. Please change this default to something like 220 to 230. Change for all four Axis - Left, Right, Top, Bottom.https://gitlab.kitware.com/paraview/paraview/-/issues/17295XDMF3 reader fails to read large file in parallel2021-03-23T13:09:53-04:00Jean M. FavreXDMF3 reader fails to read large file in parallelI have a 1.8Tb file in HDF5 format, with a single variable per file (uniform grid of size 7680*7680*7680). The XDMF reader version 2 reads it without problem, using 256 tasks (64 nodes of 64Gb each).
the XDMF reader version 3 crashes wi...I have a 1.8Tb file in HDF5 format, with a single variable per file (uniform grid of size 7680*7680*7680). The XDMF reader version 2 reads it without problem, using 256 tasks (64 nodes of 64Gb each).
the XDMF reader version 3 crashes with the error:
terminate called after throwing an instance of 'XdmfError'
what(): Number of values in hdf5 dataset (452984832000)
does not match allocated size in XdmfArray (2013265920).
Am not sure if it is a problem of syntax, or something worse. My XDMF file is:
>>>
<?xml version="1.0" ?>
<!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
<Xdmf xmlns:xi="http://www.w3.org/2003/XInclude" Version="2.2">
<Domain>
<Grid GridType="Uniform">
<Topology TopologyType="3DCORECTMesh" Dimensions=" 7680 7680 7680"/>
<Geometry GeometryType="ORIGIN_DXDYDZ">
<DataItem Name="Origin" Dimensions="3" NumberType="Float" Precision="4" Format="XML">
0.0 0.0 0.0
</DataItem>
<DataItem Name="Spacing" Dimensions="3" NumberType="Float" Precision="4" Format="XML">
1.0E-00 1.0E-00 1.0E-00
</DataItem>
</Geometry>
<Attribute Name="phi0" Active="1" AttributeType="Scalar" Center="Node">
<DataItem Dimensions=" 7680 7680 7680" NumberType="Float" Precision="4" Format="HDF">lc_9600box_7680_lightcone_phi_0.h5:/data</DataItem>
</Attribute>
</Grid>
</Domain>
</Xdmf>
>>>https://gitlab.kitware.com/paraview/paraview/-/issues/17277Recorded Python scripts do not handle certain proxy parameters correctly2021-03-23T13:11:48-04:00Liang WangRecorded Python scripts do not handle certain proxy parameters correctlyWhen recording macros, parameters setting are often (or always?) recorded like, for example
```python
proxy.Foo = VALUE
```
However, this fails for certain derived proxies with error like
```sh
File "$PARAVIEWPATH/lib/python2.7/site...When recording macros, parameters setting are often (or always?) recorded like, for example
```python
proxy.Foo = VALUE
```
However, this fails for certain derived proxies with error like
```sh
File "$PARAVIEWPATH/lib/python2.7/site-packages/paraview/servermanager.py", line 308, in __setattr__
"to add this attribute.")
AttributeError: Attribute Foo does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute.
```
I did a naive research on this. From the online documentation of [Proxy](http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/_modules/paraview/servermanager.html#Proxy),
```
Instead of::
proxy.GetProperty("Foo").SetElement(0, 1)
proxy.GetProperty("Foo").SetElement(0, 2)
you can do::
proxy.Foo = (1,2)
or
proxy.Foo.SetData((1,2))
or
proxy.Foo[0:2] = (1,2)
```
This feature is really implemented by updating the class dictionary. It appears to me that this can be manually done by c the `_createSetProperty` function. For certain derived proxies , their dictionary might not be updated with the extra parameters, thus calls like `proxy.Foo = value` fails.
My solution:
The extra parameters have to be accessed like `proxy.SetPropertyWithName('parameter_name', value)`. Or, a better choice might be to populate the dictionary with the extra parameters.
Please note that my understanding of pypython is very preliminary (a few days), thus I might not be understanding the features/solutions correctly. However, this is still a bug, in my opinion.https://gitlab.kitware.com/paraview/paraview/-/issues/17270error paraview.smtrace.Untraceable2023-06-15T11:20:45-04:00Ufuk Turuncogluerror paraview.smtrace.UntraceableTo create issue, please download simple dataset from [here](https://www.dropbox.com/s/eqe7jj1nsct04kc/dataset.tar.gz?dl=0) and follow these steps,
* Load sample dataset atm_input3d_100 using atm_input3d_100.vtm file. It is multi block d...To create issue, please download simple dataset from [here](https://www.dropbox.com/s/eqe7jj1nsct04kc/dataset.tar.gz?dl=0) and follow these steps,
* Load sample dataset atm_input3d_100 using atm_input3d_100.vtm file. It is multi block dataset.
* Add Transform filter and set Scale in z axis as 0.0005
* Add Calculator filter and calculate **wspd** variable using formula **sqrt(ulev*ulev+vlev*vlev)**
* Add Threshold filter and set range for **wspd** as 15-50 and change representation as Points
* Use **Select Points Through (g)** button and select circular shape in the middle of the domain
* Add Extract Selection filter from menu and push apply
* Try to create Python script with CoProcessing menu
It will generates following error,
`Traceback (most recent call last):
File "<string>", line 10, in <module>
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpexport.py", line 97, in DumpCoProcessingScript
export_rendering, simulation_input_map, screenshot_info, cinema_tracks, array_selection)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 351, in DumpPipeline
state = smstate.get_state(filter=filter, raw=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smstate.py", line 170, in get_state
traceitem.finalize()
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 766, in finalize
trace.append(accessor.trace_ctor(ctor, filter_type))
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 177, in trace_ctor
self, ctor, filter, ctor_args, skip_assignment)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 444, in trace_ctor
ctor_props_trace = self.trace_properties(ctor_props, in_ctor=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 437, in trace_properties
return joiner.join([x.get_property_trace(in_ctor) for x in props])
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 547, in get_property_trace
if in_ctor: return "%s=%s" % (varname, self.get_value())
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 567, in get_value
data = [str(Trace.get_accessor(x)) for x in self.get_object()[:]]
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 167, in get_accessor
"it. Skipping this action." % repr(obj))
paraview.smtrace.Untraceable: "<paraview.servermanager.FrustumSelectionSource object at 0x1376d54d0> is not 'known' at this point. Hence, we cannot trace it. Skipping this action."`
and if you try to generate Python script again with CoProcessing menu, now it gives different one
`Traceback (most recent call last):
File "<string>", line 10, in <module>
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpexport.py", line 97, in DumpCoProcessingScript
export_rendering, simulation_input_map, screenshot_info, cinema_tracks, array_selection)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 351, in DumpPipeline
state = smstate.get_state(filter=filter, raw=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smstate.py", line 105, in get_state
raise RuntimeError ("Cannot generate Python state when tracing is active.")
RuntimeError: Cannot generate Python state when tracing is active.`
I think that the second one is related with first one because in the first case the tracing (to create Python script for co-processing) is not fully completed and somehow it triggers the second error. So, the main error can be tracked down from the first error message. The error is probably related with the Extract Selection filter but i am not sure. BTW, I am getting same error under Linux and MacOS using PV version 5.3.0RC2.https://gitlab.kitware.com/paraview/paraview/-/issues/17248Axes Grid Unexpected Behaviour2021-03-23T13:15:27-04:00RustemAxes Grid Unexpected BehaviourUnder certain angles Axes Grid just disappears or labels overlay each other.
Steps to reproduce:
1. Create a cone with radius 1500 and height 800.
2. Enable Axes Grid in properties.
3. Turn camera around and zoom in until you see this:...Under certain angles Axes Grid just disappears or labels overlay each other.
Steps to reproduce:
1. Create a cone with radius 1500 and height 800.
2. Enable Axes Grid in properties.
3. Turn camera around and zoom in until you see this:****
![image](/uploads/93dfd86bb49667c35023ee28d61dae6e/image.png)
![image](/uploads/ab448540874eec98cafaeeab0710a9d8/image.png)
![image](/uploads/976f7ae2c7565dd61f96a78a5f488996/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/17246Empty result on large rectilinear grid2021-03-23T13:15:44-04:00Paul MelisEmpty result on large rectilinear grid#17245 might be related to this.
On the same dataset (rectilinear grid of 1297x1536x1536 points read from an Xdmf file) filters applied to the loaded dataset have empty output (0 points, 0 cells). I tried Clip (plane and box) and Slice...#17245 might be related to this.
On the same dataset (rectilinear grid of 1297x1536x1536 points read from an Xdmf file) filters applied to the loaded dataset have empty output (0 points, 0 cells). I tried Clip (plane and box) and Slice, both give empty result. ExtractSubset does seem to work, though.https://gitlab.kitware.com/paraview/paraview/-/issues/17245Overflow in information panel2021-03-23T13:02:32-04:00Paul MelisOverflow in information panelOne of our users has a rectilinear grid of 1297x1536x1536 points, defined in an Xdmf file. When loaded in PV5.3.0RC2 (official binaries) the Information tab shows the number of Cells correctly as 3053667600, but the number of Points as -...One of our users has a rectilinear grid of 1297x1536x1536 points, defined in an Xdmf file. When loaded in PV5.3.0RC2 (official binaries) the Information tab shows the number of Cells correctly as 3053667600, but the number of Points as -1234960384.https://gitlab.kitware.com/paraview/paraview/-/issues/17244CellCenters filter produces non-deterministic result on data with blanking2021-03-23T13:03:06-04:00David DoriaCellCenters filter produces non-deterministic result on data with blankingWith the attached file [grid_demo.vts](/uploads/15e48e2412fec3cabcd1af227424cc5d/grid_demo.vts) file, when I apply a Cell Centers filter sometimes it works ![working](/uploads/de67ef3cc314db4144940763615634a5/working.jpg) and sometimes i...With the attached file [grid_demo.vts](/uploads/15e48e2412fec3cabcd1af227424cc5d/grid_demo.vts) file, when I apply a Cell Centers filter sometimes it works ![working](/uploads/de67ef3cc314db4144940763615634a5/working.jpg) and sometimes it produces garbage output (note the Y-range) ![broken](/uploads/6451ebe6e65f4eb3465e042b626d908e/broken.jpg)https://gitlab.kitware.com/paraview/paraview/-/issues/17238Color table symmetric around 02023-06-15T10:59:20-04:00W. Alan ScottColor table symmetric around 0From a user:
I'd like to add a feature request for ParaView sometime down the road.. symmetric colormap range option.
I've found myself manually setting the colormap range to be symmetric about 0 (e.g., [-10, 10] and not [-3.29, 10])....From a user:
I'd like to add a feature request for ParaView sometime down the road.. symmetric colormap range option.
I've found myself manually setting the colormap range to be symmetric about 0 (e.g., [-10, 10] and not [-3.29, 10]). The auto-range feature is helpful, but a GUI checkbox that says "Force symmetric auto-range" would be great. In a lot of cases, the value 0 has some meaning (such as zero stress), and using the Red/Blue colormap or something similar helps quickly visualize areas of postive v.s negative value (e.g., compressive vs tensile stress).https://gitlab.kitware.com/paraview/paraview/-/issues/17237State file is bad if selection is on2023-06-15T10:57:51-04:00W. Alan ScottState file is bad if selection is onIf a user saves a state file when selection is on, that state file is broken. Replicate as follows:
* Master, Linux, local server.
* Sources/ Wavelet. Apply. Surface. RTData.
* Select Cells On. DON'T DO THE SELECTION. Just proceed ...If a user saves a state file when selection is on, that state file is broken. Replicate as follows:
* Master, Linux, local server.
* Sources/ Wavelet. Apply. Surface. RTData.
* Select Cells On. DON'T DO THE SELECTION. Just proceed to next step.
* File/ Save State.
* Reset Session.
* File/ Load State.
Your mouse controls are bad.