ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-12-16T16:41:17-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/19883Multiple warnings at built in VTK on tanaab and dres2020-12-16T16:41:17-05:00Mathieu Westphal (Kitware)Multiple warnings at built in VTK on tanaab and dresThese should be fixed in VTK.
https://open.cdash.org/viewBuildError.php?type=1&buildid=6499065
https://open.cdash.org/viewBuildError.php?type=1&buildid=6499145
eg :
```
[CTest: warning matched] /home/kitware/Dashboards/slave/paraview...These should be fixed in VTK.
https://open.cdash.org/viewBuildError.php?type=1&buildid=6499065
https://open.cdash.org/viewBuildError.php?type=1&buildid=6499145
eg :
```
[CTest: warning matched] /home/kitware/Dashboards/slave/paraview_master-taanab-linux-shared-release_adios2_icc_mpi_python2/source/VTK/Wrapping/Tools/vtkWrapPythonTemplate.c(328): warning #3656: variable "instantiations" may be used before its value is set
if (strcmp(name_with_args, instantiations[k]) == 0)
^
```https://gitlab.kitware.com/paraview/paraview/-/issues/19882Warning at configuration on tannaab, python related2020-05-04T09:24:22-04:00Mathieu Westphal (Kitware)Warning at configuration on tannaab, python relatedLots of warning on tanaab during configuration.
```
CMake Warning at VTK/CMake/vtkModuleWrapPython.cmake:426 (add_library):
Cannot generate a safe runtime search path for target
vtkRemotingViewsPythonPython because files in some dire...Lots of warning on tanaab during configuration.
```
CMake Warning at VTK/CMake/vtkModuleWrapPython.cmake:426 (add_library):
Cannot generate a safe runtime search path for target
vtkRemotingViewsPythonPython because files in some directories may conflict
with libraries in implicit directories:
runtime library [libEGL.so.1] in /usr/lib/x86_64-linux-gnu may be hidden by files in:
/usr/lib/nvidia-384
Some of these libraries may not be found correctly.
Call Stack (most recent call first):
VTK/CMake/vtkModuleWrapPython.cmake:746 (_vtk_module_wrap_python_library)
CMakeLists.txt:634 (vtk_module_wrap_python)
```
May not be worth fixing if it is related to python2.
https://open.cdash.org/viewConfigure.php?buildid=6499065
FYI : @ben.boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19881Blocks can't be unselected in Exodus reader2020-08-25T16:30:00-04:00W. Alan ScottBlocks can't be unselected in Exodus readerHere is a dataset that has blocks that can be unselected in the Exodusreader, but are read in anyway.
* 5.8.0, builtin server, Linux.
* Read in single file. Turn off reading either block. Apply.
Works!
* Read in spread file. Turn of...Here is a dataset that has blocks that can be unselected in the Exodusreader, but are read in anyway.
* 5.8.0, builtin server, Linux.
* Read in single file. Turn off reading either block. Apply.
Works!
* Read in spread file. Turn off reading either block. Apply.
Both will always be read in. This is a bug.
Needs to be tested and fixed in the Exodus reader rewrite.
@utkarsh.ayachit5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19880Glyph filter sometimes produces misplaced arrows2020-05-19T21:27:14-04:00DavidGlyph filter sometimes produces misplaced arrowsThis issue is from the discussion in [a thread on the ParaView forums.](https://discourse.paraview.org/t/misplaced-arrows-from-glyph-filter-in-5-8-0-under-linux/4160)
It's arising under Linux, 64-bit, 5.8.0 build downloaded from paravie...This issue is from the discussion in [a thread on the ParaView forums.](https://discourse.paraview.org/t/misplaced-arrows-from-glyph-filter-in-5-8-0-under-linux/4160)
It's arising under Linux, 64-bit, 5.8.0 build downloaded from paraview.org, and also occurs on a nightly build from 28th April.
Summary: After reading a VTU file with Int32 as the types for the connectivity and offset arrays, the Glyph filter when run on cell data sometimes produces arrows in incorrect places where there are no cells. It is not consistent; changing, e.g., the glyph scaling and re-applying will change the location of the arrows that are produced. If the VTU file uses Int64 for the types of connectivity and offset but is otherwise identical, then the issue does not arise.
Steps to reproduce:
1. Open the attached cleaned32.vtu and apply
2. Select current and surface with edges, reduce opacity to 0.2 so the glyphs can be seen
3. Filters->Glyph, select orientation array current_dir, no scale array, scale factor 5, all points, apply
4. If need be, switch back and forth between scale factor 4 + apply and scale factor 5 + apply a few times. At some point you’ll see the misplaced arrows.
Example picture of the problem (not always reproduced exactly):
![misplaced](/uploads/0290b0da9995140be66da28ca10cedc8/misplaced.png)
The issue does not occur if you use cleaned.vtu (which has Int64 as the offset and connectivity type).
[cleaned32.vtu](/uploads/3d56ba8a7a05414a0518d4d08b8e81d9/cleaned32.vtu)
[cleaned.vtu](/uploads/e1fbb08e9787764983b1e44322c9bdab/cleaned.vtu)5.8.1https://gitlab.kitware.com/paraview/paraview/-/issues/19879SaveData (csv) on ExtractSubset and Multithreads (pvserver)2023-06-15T09:48:34-04:00thomas theunissenSaveData (csv) on ExtractSubset and Multithreads (pvserver)When SavingData into a csv file with a client/server using 4 threads results in duplicating some points resulting in a wrong number of line in the csv file.
A simple grid of 257*257 points should provide a csv file with 66050 (+1 heade...When SavingData into a csv file with a client/server using 4 threads results in duplicating some points resulting in a wrong number of line in the csv file.
A simple grid of 257*257 points should provide a csv file with 66050 (+1 header)
If you run SaveData on 4 threads (mpiexec -np 4 pvserver -display :0.0 --force-offscreen-rendering) the csv file is 67601 (+1 header). Each direction is divided into 4 resulting in 3 duplicated points in each direction. This is annoying.
To be a bit more precise. I did this SaveData on a ExtractSubset filter applied on a cube to extract the top surface.https://gitlab.kitware.com/paraview/paraview/-/issues/19876Paraview OpenFOAM - skip zero time default: unchecked2020-04-29T06:36:12-04:00Jozsef NagyParaview OpenFOAM - skip zero time default: uncheckedDear developers,
I have been working with OpenFOAM for over 10 years and used Paraview for post-processing. First thank you for this great software!
There is one issue, which is bugging the entire OpenFOAM community, but I think no on...Dear developers,
I have been working with OpenFOAM for over 10 years and used Paraview for post-processing. First thank you for this great software!
There is one issue, which is bugging the entire OpenFOAM community, but I think no one took the time to report it to the developers and suffer silently.
At some point the feature "skip zero time" was introduced to the properties panel. This skips the initial conditions of OpenFOAM. However, this is very important to double check the case setups and especially newcomers are confused, why all of a sudden they cannot visualize and double-check their initial conditions. I have to point it our every time, that they have to uncheck the "skip zero time" box.
My request would be a simple one. Would it be possible to set the default setting of this check box to unchecked? In some cases it makes sense to use this, but in most cases it does not make sense. I hope it would be possible to disable this function as default. I hope this is only a small thing to implement in future releases. Thank you!
Best regards,
Jozsef Nagyhttps://gitlab.kitware.com/paraview/paraview/-/issues/19875XDMF reader does not support matrices of arbitrary shape2020-06-29T20:42:06-04:00Martin Diehlmartin.diehl@kuleuven.beXDMF reader does not support matrices of arbitrary shapeThe current XDMF reader does not work for arbitrarily shape matrices, this includes even vectors of a length not equals 3.
~"area:xdmf" ~"triage:hackathon"The current XDMF reader does not work for arbitrarily shape matrices, this includes even vectors of a length not equals 3.
~"area:xdmf" ~"triage:hackathon"https://gitlab.kitware.com/paraview/paraview/-/issues/19874ParaView Hackathon on Wednesday, May 62020-08-04T04:25:27-04:00Mathieu Westphal (Kitware)ParaView Hackathon on Wednesday, May 6Kitware will be holding a ParaView hackathon on Wednesday, may 6, from 8am EST (2pm GMT+2) to late.
It is open to **anyone** willing to contribute, with or without coding skills.
Here are the objectives of this hackathon :
* Cleaning ...Kitware will be holding a ParaView hackathon on Wednesday, may 6, from 8am EST (2pm GMT+2) to late.
It is open to **anyone** willing to contribute, with or without coding skills.
Here are the objectives of this hackathon :
* Cleaning up any warnings or issues on the dashboards.
* Fix simple outstanding issues.
* Implement simple life-improving features.
* Do a pass on the issues to close all the old ones that should be closed.
* Do a pass on open merge request in order to finish some up and close others.
If you or anyone you work with may be interested by contributing into ParaView, this would be a great start !
More info and updates here : https://discourse.paraview.org/t/paraview-hackathon-wednesday-may-6/4172
You have been tagged here because you are already a ParaView developper and are not a kitwareean.
@ryan.krattiger1234 @todoooo @cobo @EvgenyVRN @eolivares @ethan.stam @allisonvacanti @yufeimi @williamfgc @kvankooten @jschueller @dalcinl @quantumsteve @MicK7 @boonth @gvilanovac @demarle @mrasquin @yasushi.saito @MartinDiehl @florian360Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19873ExtractSubsetWithSeed missing blocks with pvbatch2020-09-30T19:05:35-04:00W. Alan ScottExtractSubsetWithSeed missing blocks with pvbatchJeff wrapped this one up really well in a directory that I can give Kitware. Lets call it ExtractSubsetWithSeed missing blocks with pvbatch.
Here is what Jeff wrote in the README:
The contents of this directory demonstrate an error wi...Jeff wrapped this one up really well in a directory that I can give Kitware. Lets call it ExtractSubsetWithSeed missing blocks with pvbatch.
Here is what Jeff wrote in the README:
The contents of this directory demonstrate an error with the
ExtractSubsetWithSeed filter in pvbatch/catalyst. In the gui operation,
ExtractSubsetWithSeed successfully follows a path from block to block.
In the pvbatch operation, we only get data from one block. This error occurs
even on single process operation. To see this bug in operation (or for
debugging):
In the gui, open the cgns data set, including cell data. Make an
ExtractSubsetWithSeed filter with seed point [1.0, 0.08685, 0.08685] and
direction 'JK'. Render by surface, color by block and examine.
On the command line, execute the following line (make sure you have access to
pvbatch for paraview 5.8):
pvbatch --symmetric cgns2catalyst.py sparc-volume-1process.cgns -ps do_essws_script_from_gui.py
or
pvbatch cgns2catalyst.py sparc-volume-1process.cgns -ps do_essws_script_from_gui.py
And look at the output image.
(Snip second bug that has not been replicated)
Sending the tarball to Kitware.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19871Axes Grid not visible with Ray Tracing / Path Tracing enabled2020-12-08T10:51:22-05:00Nick LeafAxes Grid not visible with Ray Tracing / Path Tracing enabledEnabling any ray tracing back-end causes the axes grid to disappear in ParaView 5.8.0.
Steps to reproduce:
1. Create a wavelet source: Source > Alphabetical > Wavelet & Apply
1. Add a contour filter: Filters > Alphabetical > Contour & A...Enabling any ray tracing back-end causes the axes grid to disappear in ParaView 5.8.0.
Steps to reproduce:
1. Create a wavelet source: Source > Alphabetical > Wavelet & Apply
1. Add a contour filter: Filters > Alphabetical > Contour & Apply
1. Enable the axes grid: under Properties > View (Render View), check "Axes Grid"; Axes Grid should appear
1. Enable ray tracing: under Properties > View (Render View), check "Enable Ray Tracing"; Axes Grid disappearshttps://gitlab.kitware.com/paraview/paraview/-/issues/19870Update IndeX support on master2021-01-14T21:41:00-05:00Ben BoeckelUpdate IndeX support on masterThe following discussion from !4066 should be addressed:
- [ ] @utkarsh.ayachit started a [discussion](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4066#note_743756): (+2 comments)
> @eolivares, you may want to re...The following discussion from !4066 should be addressed:
- [ ] @utkarsh.ayachit started a [discussion](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4066#note_743756): (+2 comments)
> @eolivares, you may want to reconsider this change. ParaView `master` no longer uses `vtkKdTree` etc. We can have this change target the `release` branch for 5.8.1, but you'll need to rework it for `master` and 5.9.0.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19868RedistributeDataset filter has issues with partitioned datasets2020-05-24T06:46:06-04:00Utkarsh AyachitRedistributeDataset filter has issues with partitioned datasets* open `can.e.4.*` using the IOSS reader, load just the `block_1`, apply
* create RedistributeDataSet filter (the D3 replacement), number of paritions = 2, and check "preserve partitions in output".
* you;ll see somethign like this:
![i...* open `can.e.4.*` using the IOSS reader, load just the `block_1`, apply
* create RedistributeDataSet filter (the D3 replacement), number of paritions = 2, and check "preserve partitions in output".
* you;ll see somethign like this:
![image](/uploads/f8fc07416d2319af589b44fb90685d42/image.png)
that's incorrect.
If you apply RedistributeDataSet after MergeBlocks the issue goes away.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19867H5Part.c:2095:11: error: too few arguments to function ‘H5Oget_info_by_name3’2020-04-24T09:30:28-04:00Julien SchuellerH5Part.c:2095:11: error: too few arguments to function ‘H5Oget_info_by_name3’current paraview master fails to build with hdf5 1.12.0 in vtkh5part
after setting VTK_MODULE_ENABLE_VTK_h5part=NO and VTK_MODULE_ENABLE_VTK_IOH5part=NO
it still tells "The VTK::IOH5part module requires the disabled module VTK::h5part"
...current paraview master fails to build with hdf5 1.12.0 in vtkh5part
after setting VTK_MODULE_ENABLE_VTK_h5part=NO and VTK_MODULE_ENABLE_VTK_IOH5part=NO
it still tells "The VTK::IOH5part module requires the disabled module VTK::h5part"
otherwise vtk master succeeds
probably related: https://gitlab.kitware.com/paraview/paraview/-/issues/15186https://gitlab.kitware.com/paraview/paraview/-/issues/19866Legend rescaling after Transform filter applied2020-04-23T11:27:18-04:00Cailen SnikerLegend rescaling after Transform filter appliedHello,
Up front, this is in 5.8.0, and I'm using it in GUI mode. Unfortunately, I cannot share screenshots of the problem, but it should be easy enough to describe step-by-step.
1. I open an Exodus data set and load a nodal property (...Hello,
Up front, this is in 5.8.0, and I'm using it in GUI mode. Unfortunately, I cannot share screenshots of the problem, but it should be easy enough to describe step-by-step.
1. I open an Exodus data set and load a nodal property (Velocity) and plot it. The legend shows values in the range of approx. 1.0e+03 (expected)
2. I apply a Transform filter to the data, uniformly scaling by 100 in x, y, and z directions. The legend now shows values in the range of approx. 1.0e+05 (expected)
3. Keeping the same Transform filter, I now reduce the scale factors back to 1. The legend remains at approx. 1.0e+05 (should be at approx. 1.0e+03)
4. In Step 3, if I instead increase the scale factors (such as to 1000), the legend automatically rescales and is now at approx. 1.0e+06
5. As an alternative, if my initial scaling (Step 2) is a decrease (such as to 0.1), the legend does not rescale at all
6. Manually applying the legend rescale (clicking the button) does correctly update the legend, but the problem is that it isn't consistent in its automatic behavior
So a summary of the issue: The legend automatically rescales when a Transform filter is applied as long as the scaling is an increase. But it does not rescale if the scaling is a decrease.
Some other noted behaviors:
* I did not see any legend updating (increase or decrease) on another nodal property in the dataset (displacements)
* Cell/Element properties such as density do not appear to be affected, either (stayed in native unit scaling)
* I have not tried this using other readers yet. But I have the ability to try an XDMF format if that would be helpful.https://gitlab.kitware.com/paraview/paraview/-/issues/19864SaveAnimation as .avi without compression invert the frame2020-10-27T15:36:09-04:00Mathieu Westphal (Kitware)SaveAnimation as .avi without compression invert the frame * Run ParaView
* Open can.ex2, Apply
* File -> SaveAnimation
* movie.avi, uncheck "Compression" checkbox
* Save
![2020-04-22-035730_1608x436_scrot](/uploads/6ac8e3b75ab97b058b8c9885d23daa2d/2020-04-22-035730_1608x436_scrot.png) * Run ParaView
* Open can.ex2, Apply
* File -> SaveAnimation
* movie.avi, uncheck "Compression" checkbox
* Save
![2020-04-22-035730_1608x436_scrot](/uploads/6ac8e3b75ab97b058b8c9885d23daa2d/2020-04-22-035730_1608x436_scrot.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19863Segfault calling VisRTX_GetContext() at startup2020-06-09T18:39:15-04:00W. Alan ScottSegfault calling VisRTX_GetContext() at startupParaView 5.8.0 has a segfault at startup. It is in the following section of code.
```
42 0x408939 /snip/bin/paraview() [0x408939]
41 0x7fac7b0094d1 pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) + 1041
40 ...ParaView 5.8.0 has a segfault at startup. It is in the following section of code.
```
42 0x408939 /snip/bin/paraview() [0x408939]
41 0x7fac7b0094d1 pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) + 1041
40 0x7fac7af7fea5 pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) + 293
39 0x7fac7af7fd14 pqAlwaysConnectedBehavior::serverCheck() + 132
38 0x7fac79b998a7 pqObjectBuilder::createServer(pqServerResource const&, int) + 199
37 0x7fac782c5749 vtkSMSession::ConnectToSelf(int) + 105
36 0x7fac779c5a3e vtkProcessModule::RegisterSession(vtkSession*) + 142
35 0x7fac725616c6 /snip/bin/../lib/libvtkCommonCore-pv5.8.so.1(+0x4936c6) [0x7fac725616c6]
34 0x7fac723f4c99 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
33 0x7fac787c4c7c /snip/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x3ac7c) [0x7fac787c4c7c]
32 0x7fac787b0947 /snip/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x26947) [0x7fac787b0947]
31 0x7fac78f18c47 QMetaObject::activate(QObject*, int, int, void**) + 1511
30 0x7fac79b39d09 /snip/bin/../lib/libpqCore-pv5.8.so.1(+0x77d09) [0x7fac79b39d09]
29 0x7fac79b35452 pqServerManagerObserver::connectionCreated(long long) + 50
28 0x7fac78f18c47 QMetaObject::activate(QObject*, int, int, void**) + 1511
27 0x7fac79be69a2 pqServerManagerModel::onConnectionCreated(long long) + 770
26 0x7fac79b342c2 pqServerManagerModel::serverAdded(pqServer*) + 50
25 0x7fac78f18c47 QMetaObject::activate(QObject*, int, int, void**) + 1511
24 0x7fac7afcc379 pqDefaultViewBehavior::onServerCreation(pqServer*) + 585
23 0x7fac79b94b3e pqObjectBuilder::createView(QString const&, pqServer*) + 158
22 0x7fac782d145b vtkSMSessionProxyManager::NewProxy(char const*, char const*, char const*) + 203
21 0x7fac782d11a4 vtkSMSessionProxyManager::NewProxy(vtkPVXMLElement*, char const*, char const*, char const*) + 324
20 0x7fac6e0432f5 vtkSMViewProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 21
19 0x7fac7829c6cb vtkSMProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 683
18 0x7fac7829e2fb vtkSMProxy::CreateSubProxiesAndProperties(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 699
17 0x7fac7829be46 vtkSMProxy::NewProperty(char const*, vtkPVXMLElement*) + 422
16 0x7fac78302a9c vtkSMStringVectorProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 28
15 0x7fac7830cba7 vtkSMVectorProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 23
14 0x7fac78287def vtkSMProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 11871
13 0x7fac6dffffce vtkSMRendererDomain::ReadXMLAttributes(vtkSMProperty*, vtkPVXMLElement*) + 30
12 0x7fac6dfffb46 vtkSMRendererDomain::Update(vtkSMProperty*) + 54
11 0x7fac6c471bd4 vtkOSPRayPass::IsBackendAvailable(char const*) + 20
10 0x7fac6c446656 /snip/bin/../lib/libvtkRenderingRayTracing-pv5.8.so.1(+0x1d656) [0x7fac6c446656]
9 0x7fac6c44653f /snip/bin/../lib/libvtkRenderingRayTracing-pv5.8.so.1(+0x1d53f) [0x7fac6c44653f]
8 0x7fac6c446f77 /snip/bin/../lib/libvtkRenderingRayTracing-pv5.8.so.1(+0x1df77) [0x7fac6c446f77]
7 0x7fac39e492b9 VisRTX_GetContext + 5081
6 0x7fac70ff1993 /lib64/libstdc++.so.6(+0x5e993) [0x7fac70ff1993]
5 0x7fac70ff1773 /lib64/libstdc++.so.6(+0x5e773) [0x7fac70ff1773]
4 0x7fac70ff1746 /lib64/libstdc++.so.6(+0x5e746) [0x7fac70ff1746]
3 0x7fac70ff37d5 __gnu_cxx::__verbose_terminate_handler() + 357
2 0x7fac7b3a59b8 abort + 328
1 0x7fac7b3a42c7 gsignal + 55
0 0x7fac7b3a4340 /lib64/libc.so.6(+0x36340) [0x7fac7b3a4340]
( 2.988s) [paraview ] :0 FATL| Signal: SIGABRT5.8.1Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19862"Extract Block" filter can be applied to HyperTreeGrid data set2020-06-05T15:25:49-04:00Utkarsh Ayachit"Extract Block" filter can be applied to HyperTreeGrid data set"Extract Block" filter can is enabled when HyperTreeGrid is active. This is incorrect. The filter cannot really be applied to hypertree grids.
Steps:
1. Sources | 'Hyper Tree Grid (random)', Apply
2. Filters | Extract Block
You get err..."Extract Block" filter can is enabled when HyperTreeGrid is active. This is incorrect. The filter cannot really be applied to hypertree grids.
Steps:
1. Sources | 'Hyper Tree Grid (random)', Apply
2. Filters | Extract Block
You get errors:
```
vtkPVCompositeDataPipeline (0x5570c463d580): Input for connection index 0 on input port index 0 for algorithm vtkExtractBlock(0x5570c4652c70) is of type vtkHyperTreeGrid, but a vtkMultiBlockDataSet is required.
```Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19860Rename Mesh Quality Filter Lin. Tet. Aspect Ratio Beta -> Radius Ratio2022-03-31T11:49:05-04:00Joel A. KuleszaRename Mesh Quality Filter Lin. Tet. Aspect Ratio Beta -> Radius RatioParaView's Mesh Quality Filter provides the option of "Aspect Ratio Beta" for linear tetrahedral elements.
This is (apparently) dated terminology from an older version/implementation of the Verdict library. The (apparently) [most-rec...ParaView's Mesh Quality Filter provides the option of "Aspect Ratio Beta" for linear tetrahedral elements.
This is (apparently) dated terminology from an older version/implementation of the Verdict library. The (apparently) [most-recent Verdict publication (SAND2007-1751)](https://www.osti.gov/biblio/901967-verdict-geometric-quality-library) refers to this metric as "Radius Ratio" and makes the tie to the old term (see Section 6.11) and notes its deprecation.
For consistency, it is recommended that ParaView update this filter setting.
@patchett2002 @ethan.stam5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/19859DataAssembly in Information Tab2021-08-24T17:05:50-04:00Utkarsh AyachitDataAssembly in Information TabOpen an exodus file using the Ioss reader. The information tab shows this:
![image](/uploads/51a9eb8716fdefd7e8c2deb25116d32e/image.png)
While this is useful, it doesn't show the logical groupping of blocks/sets etc which is provided a...Open an exodus file using the Ioss reader. The information tab shows this:
![image](/uploads/51a9eb8716fdefd7e8c2deb25116d32e/image.png)
While this is useful, it doesn't show the logical groupping of blocks/sets etc which is provided as a `vtkDataAssembly`.
Solution:
* Make this top part on the information tab a tabbed widget which shows the assembly in one tab and the raw hierarchy in another.
* If the data doesn't have an assembly, only the hierarchy tab should be visible.
* clicking on items in the assembly tree should correctly update to show array information for the selected subset (similar to how it does in the hierarchy view)5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19858Build instructions include deprecated PARAVIEW_ENABLE_PYTHON option2020-06-11T18:51:25-04:00Ryan KrattigerBuild instructions include deprecated PARAVIEW_ENABLE_PYTHON optionThe new name, according to the CMake error, is PARAVIEW_USE_PYTHON. It would be nice if the build.md used this instead to avoid the warning when building Paraview from source.The new name, according to the CMake error, is PARAVIEW_USE_PYTHON. It would be nice if the build.md used this instead to avoid the warning when building Paraview from source.