ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-05-27T17:40:32-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19434macOS Python3 binaries2020-05-27T17:40:32-04:00Utkarsh AyachitmacOS Python3 binariesWe need to add support for macOS binaries with Python3.We need to add support for macOS binaries with Python3.5.9 (Fall 2020)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19419Opacity setting changes background color with UnstructuredCellType2020-08-24T14:45:08-04:00Scott KindlOpacity setting changes background color with UnstructuredCellTypeSteps to reproduce:
* Open ParaView
* UnstructuredCellType, Apply, Volume representation
* Sphere, Apply, Opacity 0.9
* Background changes
Reference: https://discourse.paraview.org/t/opacity-setting-changes-background-color/2852Steps to reproduce:
* Open ParaView
* UnstructuredCellType, Apply, Volume representation
* Sphere, Apply, Opacity 0.9
* Background changes
Reference: https://discourse.paraview.org/t/opacity-setting-changes-background-color/28525.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19417SciPy not found (missing _main from qhull)2020-12-16T16:31:14-05:00Bane SullivanSciPy not found (missing _main from qhull)When trying `from scipy.spatial import Delaunay` the import fails. Doing the same thing on ParaView 5.6 works fine for me.
My Specs:
- MacOS Catalina 10.15 (19A602)
- ParaView 5.7.0
- Is anything else needed for this issue?
```py
>>> ...When trying `from scipy.spatial import Delaunay` the import fails. Doing the same thing on ParaView 5.6 works fine for me.
My Specs:
- MacOS Catalina 10.15 (19A602)
- ParaView 5.7.0
- Is anything else needed for this issue?
```py
>>> from scipy.spatial import Delaunay
Traceback (most recent call last):
File "<console>", line 1, in <module>
File "/Applications/ParaView-5.7.0.app/Contents/Python/scipy/spatial/__init__.py", line 100, in <module>
from .qhull import *
ImportError: dlopen(/Applications/ParaView-5.7.0.app/Contents/Python/scipy/spatial/qhull.so, 2): Symbol not found: _main
Referenced from: /Applications/ParaView-5.7.0.app/Contents/Python/scipy/spatial/qhull.so
Expected in: flat namespace
in /Applications/ParaView-5.7.0.app/Contents/Python/scipy/spatial/qhull.so
```5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19409Parallel Coordinates View crashes2019-10-30T20:57:18-04:00W. Alan ScottParallel Coordinates View crashesThe Parallel Coordinates View crashes. Here is how to replicate:
* Linux, 5.7.0, builtin server.
* Load disk_out_ref.exo. All vars on. Apply.
* Swap the view to Parallel Coordinates View.
Crashes.The Parallel Coordinates View crashes. Here is how to replicate:
* Linux, 5.7.0, builtin server.
* Load disk_out_ref.exo. All vars on. Apply.
* Swap the view to Parallel Coordinates View.
Crashes.5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19406Sources/ Ellipse misses one segment2020-06-16T12:21:04-04:00W. Alan ScottSources/ Ellipse misses one segmentSources/ Ellipse misses one segment. Here is how to replicate:
* Linux, master, builtin server.
* Sources/ Ellipse. Resolution 4. Start Angle 0. Sector Angle 90. Apply. I will call this ellipse-0.
* Sources/ Ellipse. Resolution 4...Sources/ Ellipse misses one segment. Here is how to replicate:
* Linux, master, builtin server.
* Sources/ Ellipse. Resolution 4. Start Angle 0. Sector Angle 90. Apply. I will call this ellipse-0.
* Sources/ Ellipse. Resolution 4. Start Angle 90. Sector Angle 90. Apply. I will call this ellipse-90.
These two partial ellipses should touch, but don't.
* Change ellipse-0 and ellipse-90 to be non-Closed.
This is what I would expect. Now, they touch correctly. Close and non-Close should look exactly the same, only one has a closing line.
This is a Watney bug.5.9 (Fall 2020)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19404Sidesets are rendering incorrectly2020-08-31T13:19:29-04:00W. Alan ScottSidesets are rendering incorrectlytri6 sidesets are rendering incorrectly. This works correctly with EnSight. Here is how to replicate:
* 5.7.0, Windows, builtin server.
* Open tri6sWFace2.exo. Advanced. Turn the Set on, turn the Block off. Apply.
Looks like a Pica...tri6 sidesets are rendering incorrectly. This works correctly with EnSight. Here is how to replicate:
* 5.7.0, Windows, builtin server.
* Open tri6sWFace2.exo. Advanced. Turn the Set on, turn the Block off. Apply.
Looks like a Picasso painting.
Ask me for the data. I can give it to Utkarsh or Cory.
![Capture](/uploads/e01ef857f910c4c96d4dc0826dcc1c13/Capture.PNG)5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19396No scalar values when saving a matplotlib plot of 2D image data2020-12-09T21:29:31-05:00Ethan StamNo scalar values when saving a matplotlib plot of 2D image data@terryturton @dhr
Found with ParaView 5.7.0
We are using the following programmable filter to save a matplotlib plot within a catalyst script:
```python
import matplotlib.pyplot as plt
import numpy as np
import vtk
from vtk.util.numpy...@terryturton @dhr
Found with ParaView 5.7.0
We are using the following programmable filter to save a matplotlib plot within a catalyst script:
```python
import matplotlib.pyplot as plt
import numpy as np
import vtk
from vtk.util.numpy_support import vtk_to_numpy
PNGOutputFilename = "plot.png"
indata = self.GetInput()
array = indata.GetPointData().GetArray("RTData")
if (array):
np_array = vtk_to_numpy(array)
plt.close()
plt.plot(np_array)
plt.savefig(PNGOutputFilename)
```
With 2D image data, we get the error:
```No scalar values found for texture input!```
The image of the plot does still get saved, but this error causes the in situ use case to hang.
To recreate (In the GUI):
* Sources -> Wavelet -> Apply
* Filters -> Slice -> Apply
* Filters -> Resample to Image -> set the dimensions to 1,100,100 -> Apply
* Filters -> Programmable Filter -> copy and paste the script above -> Apply5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19392Change default volume fraction value for ExtractCTHParts2020-10-27T21:35:17-04:00W. Alan ScottChange default volume fraction value for ExtractCTHPartsIn the ExtractCTHParts filter, please change the Volume Fraction Value default to be 0.45. This looks better, and was recommended by our resident experts.
Marking as 5.8 since I believe it is trivial, OK to slip to 5.9.In the ExtractCTHParts filter, please change the Volume Fraction Value default to be 0.45. This looks better, and was recommended by our resident experts.
Marking as 5.8 since I believe it is trivial, OK to slip to 5.9.5.9 (Fall 2020)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19390Volume rendering of vectors is wrong2020-08-25T17:34:11-04:00W. Alan ScottVolume rendering of vectors is wrongVolume rendering of vector data is wrong. Here is how to replicate:
* Linux, 5.7.0, builtin server.
* disk_out_ref.exo. All vars on. Apply.
* Paint by V. Volume render.
Bug. Notice that you only see one half of the disk_out_ref.ex...Volume rendering of vector data is wrong. Here is how to replicate:
* Linux, 5.7.0, builtin server.
* disk_out_ref.exo. All vars on. Apply.
* Paint by V. Volume render.
Bug. Notice that you only see one half of the disk_out_ref.exo. What you see should be symmetric.
Interesting - Change the color legend to be -22 to 22. Now, you see there are actually negative components!
To see what I would expect, do as follows:
* calculator. Formula is mag(V). Apply.
* Paint by Result. Volume Render.
![Capture](/uploads/037f280e890e67be8a0a3c8443cda407/Capture.PNG)
My guess is we have two options. Either not allow volume rendering of vectors, or calculate the magnitude of these vectors.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19387Calculator input is broken2020-03-23T22:08:33-04:00W. Alan ScottCalculator input is brokenCalculator input is broken. This is probably due to #19323.
The problem is that we want to handle edit boxes that seperate the interaction of only numbers input boxes (click on it, and it highlights, type it then replaces) from formu...Calculator input is broken. This is probably due to #19323.
The problem is that we want to handle edit boxes that seperate the interaction of only numbers input boxes (click on it, and it highlights, type it then replaces) from formula input boxes (select something, it highlights, select something else, the original gets wiped out). Here is how to replicate:
* Master (v5.7.0-537-g96ce074), local server, Linux.
* Sources/ Fast Uniform Grid. Apply.
* Calculator. Important!!!! - Click in the formula box. Scalars/ coordsX, then *. Note that the coordsX was highlighted, and is now replaced by the *.
This is a bug.
5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19386Resample to Hyper Tree Grid: cell version2020-02-24T17:14:30-05:00Yohann Bearzi (Kitware)Resample to Hyper Tree Grid: cell version`vtkResampleToHyperTreeGrid` currently only supports point data input. The way the filter is implemented really fits this kind of data. One can dump each new input in a `vtkAbstractAccumulator` either by summing a function of the input (...`vtkResampleToHyperTreeGrid` currently only supports point data input. The way the filter is implemented really fits this kind of data. One can dump each new input in a `vtkAbstractAccumulator` either by summing a function of the input (using a `vtkArithmeticAccumulator`), by sorting each point in an array to extract a quantile (using a `vtkQuantileAccumulator`), or by incrementing by one bins, for the entropy for example (using a `vtkBinsAccumulator`).
Then classes based on `vtkAbstractArrayMeasurement` can take the output of those `vtkAbstractAccumulator` and produce the desired measure.
I refactored the code a bit in https://gitlab.kitware.com/paraview/paraview/merge_requests/3625, which should be merged soon. The naming in the previous paragraph matches this new implementation.
However, obviously, cell data cannot directly fit in this framework. Let's see how we can modify the paradigm to make it happen. Let's only consider `vtkCell3D` for the moment. The challenge is to make the resampling filter a unified framework for points and volumetric cells. If one has that, generalizing to 2D cells or 1D cells should be a piece of cake.
The most straightforward way to make this filter perform the same action as with the point-wise version is to consider points as volumetric objects, which is possible using 3D Dirac distributions $`\delta_{p_i}`$, centered at point $`p_i`$, such that
```math
\left\{
\begin{array}{l}
\delta_{p_i}((x,y,z) = \not \ p_i) = 0\\
\int\int\int \delta_{p_i}(x,y,z)dxdydz = 1
\end{array}
\right.
```
If one can translate the point-wise computation to a computation dealing with volumes, it is very straightforward to feed any volumetric cell as inputs instead. Let us note $`\delta_i`$ such that if the input is formed of points, $`\delta_i=\delta_{p_i}`$, and if the input is a volumetric cell $`c_i`$, $`\delta_i(p) = 1`$ if $`p\in c_i`$, and $`\delta_i(p)=0`$ elsewhere.
Let us note $`\omega_i(C)`$ the intersection volume between a hyper tree cell $`C`$ and the point / cell $`i`$. By definition:
```math
\omega_i(C) =\int\int\int_{(x,y,z)\in C} \delta_i(x,y,z)dxdydz
```
Thus, for example, what is actually calculated for `vtkArithmeticAccumulator`, is the integral over the cells of a function $`f`$ of Dirac distributions scaled by their associated value $`\alpha_i`$, weighted by $`\omega_i(C)`$. In other words, this accumulated value $`\mathcal A(c)`$ has the expression:
```math
\mathcal A(C) = \sum_i \omega_i(C) f(\alpha_i)
```
What is incremented in the bin for $`v_i`$ of `vtkBinsAccumulator` is the intersection volume between those Diracs and the current hyper tree cell. Thus, given a regular discretization $`(b_j)_{j\in\mathbb Z}`$ of the space of values, the bin $`\mathcal B_{[b_j, b_{j+1}[}(C)`$ follows:
```math
\mathcal B_{[b_j, b_{j+1}[}(C) = \sum_{\alpha_i\in[b_j,b_{j+1}[} \omega_i(C)
```
Similarly this intersection volume is what is used in to compute the quantile as a width of each element. The quantile $`\mathcal Q_x(C)`$ is then defined as:
```math
\begin{array}{ll}
\mathcal Q_x(C) =& \text{argmin}_{\alpha_i} \left(x - \frac{\sum_{\alpha_j \le \alpha_i}\omega_j(C)}{\sum_j \omega_j(C)} \ge 0\right)
\end{array}
```
In addition to this, it should be possible to resample `vtkPolyData` with cells of different inner dimension. This can be dealt with by picturing the co-dimensions of those cells to be Diracs. One would also need to add a parameter to scale the influence of points / lines / polygons / polyhedron that could be hidden in the advanced parameters in the GUI. If one plays with such scale factors while dealing with cells of the same inner dimension, the result of the resampling would not be altered.
So basically the goal in this update is to compute the intersected volume between 3D cells / hyper tree grid cells, which would be set as the weight $`\omega_i(c)`$. The version for 2D or 1D cells will respectively be the intersected area / length of the cell and the hyper tree grid cell.
@patchett2002 @ethan.stam Are we in the same page?
@demarle FYI5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19378[Plugin] UI_FILES must be in the main directory so autouic can find them2020-05-21T20:01:34-04:00Mathieu Westphal (Kitware)[Plugin] UI_FILES must be in the main directory so autouic can find themIn the current implementation, UI_FILES must be in the directory where the paraview_add_plugin takes place.
Hence the following **does not work** :
```
set(ui_files
Ressource/myFile.ui)
paraview_add_plugin(Plugin
...
UI_FILES ...In the current implementation, UI_FILES must be in the directory where the paraview_add_plugin takes place.
Hence the following **does not work** :
```
set(ui_files
Ressource/myFile.ui)
paraview_add_plugin(Plugin
...
UI_FILES ${ui_files})
```
while this works perfectly
```
set(ui_files
myFile.ui)
paraview_add_plugin(Plugin
...
UI_FILES ${ui_files})
```
Here is a slightly modified version of the SierraPlotToolsPlugin that shows this behavior.
[SierraPlotToolsStandAlone.tgz](/uploads/f8023e2248b599c438ae93af26e15b3b/SierraPlotToolsStandAlone.tgz)
```
-- Build files have been written to: /home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/build
[ 5%] Automatic MOC and UIC for target SierraPlotTools
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqPlotVariablesDialog.cxx"
The file includes the uic file "ui_pqVariablePlot.h",
but the user interface file "pqVariablePlot.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqVariablePlot.ui"
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqPlotter.cxx"
The file includes the uic file "ui_pqSierraToolsRichTextDocs.h",
but the user interface file "pqSierraToolsRichTextDocs.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraToolsRichTextDocs.ui"
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsDataLoadManager.cxx"
The file includes the uic file "ui_pqSierraPlotToolsDataLoadManager.h",
but the user interface file "pqSierraPlotToolsDataLoadManager.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsDataLoadManager.ui"
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsManager.cxx"
The file includes the uic file "ui_pqSierraPlotToolsActionHolder.h",
but the user interface file "pqSierraPlotToolsActionHolder.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsActionHolder.ui"
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsManager.cxx"
The file includes the uic file "ui_pqVariablePlot.h",
but the user interface file "pqVariablePlot.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqVariablePlot.ui"
make[2]: *** [Plugin/CMakeFiles/SierraPlotTools_autogen.dir/build.make:58: Plugin/CMakeFiles/SierraPlotTools_autogen] Error 1
make[1]: *** [CMakeFiles/Makefile2:122: Plugin/CMakeFiles/SierraPlotTools_autogen.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
```5.9 (Fall 2020)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19376more time support for vtm files2022-06-28T13:48:23-04:00Boonthanome Nouanesengsymore time support for vtm filesRight now the Paraview in-situ adaptors at LANL are writing out vtk multiblock files (vtm). Both the simulation time and cycle time are written out as field data, which can then be shown on a Renderview using the Annotate Global Data Fil...Right now the Paraview in-situ adaptors at LANL are writing out vtk multiblock files (vtm). Both the simulation time and cycle time are written out as field data, which can then be shown on a Renderview using the Annotate Global Data Filter. Unfortunately, this does not extend to the pipeline and GUI, and this frustrates users that want to see and plot with the actual time of the data.
There seems to be time support in VTK and Paraview. The PVD format appears to have time support. But this time support is not in vtm files. We are already writing some time information to vtm files, so it would be great to add support for vtm files to properly insert time information into the pipeline and for the GUI to recognize it.
Things I'd like to be able to do with vtm files:
- have the 'Time:' box at the top reflect the simulation time or cycle number. that box updates correctly as you step through the timesteps.
- be able to query the time of a vtm file easily in scripts and code. something like data.GetTime(), so people can easily do quantitative calculations with time, or make their own graphs and charts.
- create a plot over time, and the simulation time or cycle number is used for the x-axis
- the annotate time filter works correctly
Proposed ways to do this:
A. extend the xml file formats to allow for a time tag that the pipeline and gui will recognize. this would be nice in that all vtk xml file formats can now specify time, not just vtm files.
B. add an option to the readers to choose which field data to treat as time. this is nice as the user can choose to either use cycle number or simulation time as their official 'time' when loading their data.
C. designate some field data names as keywords, and if a dataset has certain keywords, use that field data as time. for example, check if 'simulation_time' exists in the field data, and if so use that as time.
D. create a filter that applies a certain field data as time
Sample Dataset: [mg_diff.tar.gz](/uploads/a04bbc3885c813809198e0bb250b079c/mg_diff.tar.gz)
Below is a screenshot of what I'm talking about. @patchett2002 @demarle @cmbiwer
![time](/uploads/333257cb17a3426caf7358dbd1f51a10/time.png)5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19374remove deprecated Catalyst Script Generator GUI and other dead code paths2020-11-27T13:09:34-05:00David E. DeMarleremove deprecated Catalyst Script Generator GUI and other dead code pathsThe Export Inspector isn't new anymore, time to remove its predecessor and clean up some code.
- [x] remove Temporal Script Plugin
- [x] remove Catalyst Script Generator Wizard and Catalyst Writers
- [x] transition tests that use the ol...The Export Inspector isn't new anymore, time to remove its predecessor and clean up some code.
- [x] remove Temporal Script Plugin
- [x] remove Catalyst Script Generator Wizard and Catalyst Writers
- [x] transition tests that use the old GUI
https://gitlab.kitware.com/paraview/paraview/merge_requests/3627
- [x] update the documentation to describe the new GUI instead of the old plugin
https://gitlab.kitware.com/paraview/paraview-guide-ce/commit/d01f71c0d4c477bcfc358e1c46587dcfa48a49a4
https://gitlab.kitware.com/paraview/paraview-guide-ce/merge_requests/94
https://gitlab.kitware.com/paraview/paraview-tutorial/merge_requests/10
- [ ] remove Catalyst Writers XML definitions, while keeping backward compatibility
- [ ] remove original INVERTIBLE_LUT value rendering approach
https://gitlab.kitware.com/vtk/vtk/merge_requests/6062
https://gitlab.kitware.com/paraview/paraview/merge_requests/3640
- [ ] remove old python code paths in cpstate.py, cinema and others, streamline what remains. For example outward facing pose camera.
https://gitlab.kitware.com/paraview/paraview/merge_requests/36355.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19371ParaView ignores Blocks on this dataset2020-09-29T20:37:51-04:00W. Alan ScottParaView ignores Blocks on this datasetMy user gave me a dataset that ignores block selections. This dataset came from a single .g file, then was spread into numerous .g files. The block selection does not work. Here is how to replicate:
* Windows (or Linux), 5.6.0 (or 5.7...My user gave me a dataset that ignores block selections. This dataset came from a single .g file, then was spread into numerous .g files. The block selection does not work. Here is how to replicate:
* Windows (or Linux), 5.6.0 (or 5.7.0), built in server.
* Open the spread dataset, ztest.g.8.[0-7].
* Select only the second and third block (i.e., leave block 98 unselected).
* Apply.
* Compare with selecting all blocks. They are the same. This is a bug.
Dataset is paraview_block_issue.tar.bz2 on Windows. User is Mike W. I can pass this to Cory and/or Utkarsh.
@utkarsh.ayachit @cory.quammen I would appreciate this being looked at as soon as possible (and the contract allows). This may represent a bug on Sandia's code's part, and I would like to give feedback if true.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19367ParaView GUI needs is not clear about HTG array alignment.2020-03-24T16:54:54-04:00David E. DeMarleParaView GUI needs is not clear about HTG array alignment.The information panel shows the arrays as being point aligned, when they are closer to cell aligned.
The colormap array choice, shows both point and cell aligned versions of each array, but the point one is not-functional.
The spreadshee...The information panel shows the arrays as being point aligned, when they are closer to cell aligned.
The colormap array choice, shows both point and cell aligned versions of each array, but the point one is not-functional.
The spreadsheet view does not let you see any of the arrays.
Meanwhile the .htg file format labels the arrays as being point aligned and the htg reader does not give you an option to choose from the available arrays to load.5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19362Add an Export Inspector option for something like "Execute pipeline"2020-12-08T10:29:57-05:00Ethan StamAdd an Export Inspector option for something like "Execute pipeline"@dhr @patchett2002 @demarle
It would be useful to have an option somewhere in the Export Inspector -> Data Extracts -> Writers drop down that only executes the pipeline up to your selected filter and doesn't register any writers.
An e...@dhr @patchett2002 @demarle
It would be useful to have an option somewhere in the Export Inspector -> Data Extracts -> Writers drop down that only executes the pipeline up to your selected filter and doesn't register any writers.
An example is when you make a programmable filter that saves a matplotlib plot on apply, and you want to run that with a catalyst script in situ. To get that catalyst script, you still have to select a writer, either from the data extracts or image extracts, and comment it out later yourself. If you don't select an extract, you get the error:
```Nothing to export, use Export Inspector to configure what you want to write.```5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19357The ImageDataToUniformGrid filter for composite datasets should only be avail...2020-08-13T11:37:42-04:00Andrew BauerThe ImageDataToUniformGrid filter for composite datasets should only be available in the GUI if there is a vtkImageData in the composite datasetThis is nitpicking but the `ImageDataToUniformGrid` filter should not be available in the GUI (i.e. grayed out) if the composite dataset doesn't have any vtkImageDatas in it. See the discussion at https://discourse.paraview.org/t/xml-spe...This is nitpicking but the `ImageDataToUniformGrid` filter should not be available in the GUI (i.e. grayed out) if the composite dataset doesn't have any vtkImageDatas in it. See the discussion at https://discourse.paraview.org/t/xml-specification-questions-for-a-filter/2641. Steps to reproduce:
1. Create an `UnstructuredCellTypes` source
2. Create a `GroupDatasets` filter
The `ImageDataToUniformGrid` filter is now available in the GUI but shouldn't be since the composite dataset only has an unstructured grid in it. In reality nothing bad happens but nothing good happens either so we can make the GUI a bit cleaner by removing this option in this instance.
Note that if others are ok with the above behavior, I'm fine with it as well. I don't think of this as a serious flaw in the GUI.5.9 (Fall 2020)Feimi YuFeimi Yuhttps://gitlab.kitware.com/paraview/paraview/-/issues/19323Have edit boxes select all text when they grab focus2020-03-23T21:56:12-04:00W. Alan ScottHave edit boxes select all text when they grab focusPlease have edit boxes select all text when they grab focus. This is in response to a user complaint.
Here are some details on how to replicate:
* If you bring up a FastUniformGrid, then clip it, then rotate the clip around, you get e...Please have edit boxes select all text when they grab focus. This is in response to a user complaint.
Here are some details on how to replicate:
* If you bring up a FastUniformGrid, then clip it, then rotate the clip around, you get edit boxes for the normal. These are filled in with half a dozen numbers, but if you click on them, they expand to around two dozen numbers. Further, your cursor is now in the middle of the number, which is useless.
* Next, if you click in the Normal X, to change it to 1.0, you get as I describe above. Note that you now have to arrow the cursor to the right, and then delete everything – or, <ctrl>a, then delete everything.5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19306Edges of masked subtree should not be shown in hyper tree grids2020-02-24T17:28:25-05:00Yohann Bearzi (Kitware)Edges of masked subtree should not be shown in hyper tree gridsEdges of masked subtrees are still displayed even if they should not be
![htg](/uploads/28b13dcf194e6f26a94f79124a7bb822/htg.png)
To reproduce something similar:
* Sources -> Data Objects -> Hyper Tree Grid (random)
* Filters -> Hyp...Edges of masked subtrees are still displayed even if they should not be
![htg](/uploads/28b13dcf194e6f26a94f79124a7bb822/htg.png)
To reproduce something similar:
* Sources -> Data Objects -> Hyper Tree Grid (random)
* Filters -> Hyper Tree Grid -> Clip
Clip with a sphere / plane, or whatever, and then look for the edges.5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)