ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-05-29T21:00:33-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18193VTKm in VTK has changed and ParaView needs to change accordingly2018-05-29T21:00:33-04:00Mathieu Westphal (Kitware)VTKm in VTK has changed and ParaView needs to change accordinglyWhen updating VTK in ParaView, this [issue](https://open.cdash.org/index.php?compare1=61&filtercount=1&field1=revision&project=ParaView&showfilters=0&limit=100&value1=04842e1d7781ae742dea0141617493b44b032aeb&showfeed=0) appears :
```
No...When updating VTK in ParaView, this [issue](https://open.cdash.org/index.php?compare1=61&filtercount=1&field1=revision&project=ParaView&showfilters=0&limit=100&value1=04842e1d7781ae742dea0141617493b44b032aeb&showfeed=0) appears :
```
Not searching for unused variables given on the command line.
Internal cmake changing into directory: /home/kitware/Dashboards/slave/paraview-taanab-linux-static-release_mpi_offscreen_osmesa_python/build/CoProcessing/Adaptors/NPICAdaptor
Error: cmake execution failed
CMake Error at CMakeLists.txt:4 (find_package):
Found package configuration file:
/home/kitware/Dashboards/slave/paraview-taanab-linux-static-release_mpi_offscreen_osmesa_python/build/ParaViewConfig.cmake
but it set ParaView_FOUND to FALSE so package "ParaView" is considered to
be NOT FOUND. Reason given by package:
The following imported targets are referenced, but are missing: vtkm_cont
```
To reproduce, update VTK to last master and activate the following options :
```
PARAVIEW_ENABLE_CATALYST = ON
PARAVIEW_BUILD_CATALYST_ADAPTOR = ON
VTK_LINKER_FATAL_WARNINGS = ON
```5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18191Cell connectivity is bogus2018-07-30T19:37:16-04:00W. Alan ScottCell connectivity is bogusCell connectivity in the spreadsheet view is bugus, and lies. Lets get it fixed. Here is how to replicate:
* Open the attached file file-0.vtk. Apply.
* Surface with edges.
* Select 6 cells around a point. Easiest way is with the I...Cell connectivity in the spreadsheet view is bugus, and lies. Lets get it fixed. Here is how to replicate:
* Open the attached file file-0.vtk. Apply.
* Surface with edges.
* Select 6 cells around a point. Easiest way is with the Interactive Select Cells On.
* View/ Selection Display Inspector. Turn Cell Labels: ID on, Turn Point Labels: ID on.
* Split View Vertical. Spreadsheet View. Toggle cell connectivity visibility on.
Now, look at the spreadsheet view. Point Indexes on the main 3d view and on the spreadsheet show as their real point IDs.
* Select Show only selected elements.
Now, look at the spreadsheet view. Point Indexes have changed to go from 0 through 6. This may be the index in the spreadsheet, but is useless.
Please change this to show the Point ID. Further, please change the label to be Point Id, not Point Index.
![CaptureA](/uploads/a590260dfa7d7032c76421951a1c8a05/CaptureA.JPG)
Dataset is:
[file-0.vtk](/uploads/e644d0d18902d59471c8fc0460073558/file-0.vtk)5.6 (Fall 2018)Shreeraj JadhavShreeraj Jadhavhttps://gitlab.kitware.com/paraview/paraview/-/issues/18190Add LANL Pagosa In Situ Adaptor to ParaView Adaptors2018-07-18T16:23:24-04:00John PatchettAdd LANL Pagosa In Situ Adaptor to ParaView Adaptors[pagosaadaptor.tgz](/uploads/374d2963fd4835360f83221c3b9bf58c/pagosaadaptor.tgz)
@demarle @acbauer @sebastien.jourdain @chuck.atkins @ka5855
We would like this Catalyst adaptor added to the ParaView source and the library made availabl...[pagosaadaptor.tgz](/uploads/374d2963fd4835360f83221c3b9bf58c/pagosaadaptor.tgz)
@demarle @acbauer @sebastien.jourdain @chuck.atkins @ka5855
We would like this Catalyst adaptor added to the ParaView source and the library made available in LANL builds.5.6 (Fall 2018)Andrew BauerAndrew Bauer2018-07-31https://gitlab.kitware.com/paraview/paraview/-/issues/18189Crash reading vtm dataset2018-09-04T20:50:27-04:00W. Alan ScottCrash reading vtm datasetWe are going to create a vtm dataset, and read it into ParaView. This will crash. Here is how to replicate:
* Master (v5.5.0-340-ga3633e), Linux, build-in server. NOTE - this is a debug build.
* Load can.exo. All vars on. Turn off EQ...We are going to create a vtm dataset, and read it into ParaView. This will crash. Here is how to replicate:
* Master (v5.5.0-340-ga3633e), Linux, build-in server. NOTE - this is a debug build.
* Load can.exo. All vars on. Turn off EQPS and ACCL. Only load Unnamed block ID: 1. Apply.
* File/ Save Data. Save as canA, as an exodus file. Save all timesteps.
* Back to can in the pipeline browser. All vars on. Only load Unnamed block ID: 2. Apply.
* File/ Save Data. Save as canB, as an exodus file. Save all timesteps.
* Reset Session.
* Load canA. Apply. Load canB. Apply.
* Select both cans. Group Datasets. Apply.
* Save as VTM dataset. Save all timesteps.
* Reset Session.
* Load this new vtm dataset. We will crash, with the following:
paraview: /projects/viz/paraview/src/ParaView/5.6.0-junk/ParaView5/VTK/IO/XML/vtkXMLDataReader.cxx:297: virtual void vtkXMLDataReader::SetupOutputData(): Assertion `this->NumberOfPointArrays == this->PointDataArraySelection->GetNumberOfArraysEnabled()' failed.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18188When loading state files, the "path" fixing logic doesn't work for paths to t...2018-08-20T20:56:57-04:00Utkarsh AyachitWhen loading state files, the "path" fixing logic doesn't work for paths to textures in the state fileWhen loading state files, the "path" fixing logic doesn't work for paths to textures in the state file.When loading state files, the "path" fixing logic doesn't work for paths to textures in the state file.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18187Disappearing block2018-08-16T10:30:29-04:00W. Alan ScottDisappearing blockWe have a case where a clip will make a block disappear. This was found on a very complex model, and caused us a lot of confusion and work. It needs to be fixed. Here is how to replicate:
* Built-in server, 5.5.0, Linux.
* Load datase...We have a case where a clip will make a block disappear. This was found on a very complex model, and caused us a lot of confusion and work. It needs to be fixed. Here is how to replicate:
* Built-in server, 5.5.0, Linux.
* Load dataset multiple_element_types_with_spiders-DoNotRelease.g. Apply. (I will give dataset to Cory and Utkarsh).
* Clip. Z Normal. Apply.
The lower left block disappears! This is a bug and needs to get fixed.5.6 (Fall 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/18186Spredsheet doesn't show "Structured Coordinates"2018-08-20T20:59:20-04:00Utkarsh AyachitSpredsheet doesn't show "Structured Coordinates"* wavelet, appy
* spreadsheet view.
you'll see an empty "Structructured Coordinates" column.* wavelet, appy
* spreadsheet view.
you'll see an empty "Structructured Coordinates" column.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18182Unstructured grid ghost cells generator doesn't work with non-mpi build of Pa...2018-07-31T21:23:02-04:00Andrew BauerUnstructured grid ghost cells generator doesn't work with non-mpi build of ParaViewBuild PV without MPI enabled but the CS wrapping is still done for the unstructured grid ghost cells generator filter even though that filter isn't built because it's on FiltersParallelGeometry module which depends on the ParallelMPI mod...Build PV without MPI enabled but the CS wrapping is still done for the unstructured grid ghost cells generator filter even though that filter isn't built because it's on FiltersParallelGeometry module which depends on the ParallelMPI module which isn't built.5.6 (Fall 2018)Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/18179EGL client-server breaks with Json::RuntimeError2018-10-30T02:52:29-04:00Robert Manson-SawkoEGL client-server breaks with Json::RuntimeErrorUsing instructions from this #18176 I have compiled `pvserver` on a ppc64le machine and I am using ArchLinux on my client machine with 1.
I need to go through some port-forwarding and reverse port skullduggery, but the bottomline is tha...Using instructions from this #18176 I have compiled `pvserver` on a ppc64le machine and I am using ArchLinux on my client machine with 1.
I need to go through some port-forwarding and reverse port skullduggery, but the bottomline is that the setup works for 5.4.1 version but doesn't work for version with 5.5.0. On the client side, I am getting the following error:
```
Generic Warning: In /build/paraview/src/ParaView-v5.5.0/ParaViewCore/ClientServerCore/Core/vtkPVServerInformation.cxx, line 784
vtkPVServerInformation::GetOGVSupport was deprecated for ParaView 5.5 and will be removed in a future version.
Generic Warning: In /build/paraview/src/ParaView-v5.5.0/ParaViewCore/ClientServerCore/Core/vtkPVServerInformation.cxx, line 797
vtkPVServerInformation::GetAVISupport was deprecated for ParaView 5.5 and will be removed in a future version.
Generic Warning: In /build/paraview/src/ParaView-v5.5.0/ParaViewCore/ClientServerCore/Core/vtkPVServerInformation.cxx, line 784
vtkPVServerInformation::GetOGVSupport was deprecated for ParaView 5.5 and will be removed in a future version.
Generic Warning: In /build/paraview/src/ParaView-v5.5.0/ParaViewCore/ClientServerCore/Core/vtkPVServerInformation.cxx, line 797
vtkPVServerInformation::GetAVISupport was deprecated for ParaView 5.5 and will be removed in a future version.
terminate called after throwing an instance of 'Json::RuntimeError'
what(): * Line 1, Column 1
Syntax error: value, object or array expected.
[avignon:17635] *** Process received signal ***
[avignon:17635] Signal: Aborted (6)
[avignon:17635] Signal code: (-6)
[avignon:17635] [ 0] /usr/lib/libc.so.6(+0x368f0)[0x7f6de19648f0]
[avignon:17635] [ 1] /usr/lib/libc.so.6(gsignal+0x10b)[0x7f6de196486b]
[avignon:17635] [ 2] /usr/lib/libc.so.6(abort+0x129)[0x7f6de194f40e]
[avignon:17635] [ 3] /usr/lib/libstdc++.so.6(+0x8944a)[0x7f6de1f8b44a]
[avignon:17635] [ 4] /usr/lib/libstdc++.so.6(+0x8f9d6)[0x7f6de1f919d6]
[avignon:17635] [ 5] /usr/lib/libstdc++.so.6(+0x8fa13)[0x7f6de1f91a13]
[avignon:17635] [ 6] /usr/lib/libstdc++.so.6(+0x8fc48)[0x7f6de1f91c48]
[avignon:17635] [ 7] /usr/lib/libjsoncpp.so.20(_ZN4Json17throwRuntimeErrorERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x3a)[0x7f6de171089a]
[avignon:17635] [ 8] /usr/lib/libjsoncpp.so.20(_ZN4JsonrsERSiRNS_5ValueE+0xa2)[0x7f6de171bf62]
[avignon:17635] [ 9] /usr/lib/libvtkRenderingOSPRay-pv5.5.so.1(_ZN24vtkOSPRayMaterialLibrary17InternalParseJSONEPKcbPSi+0x52)[0x7f6dcbfaa122]
[avignon:17635] [10] /usr/lib/libvtkRenderingOSPRay-pv5.5.so.1(_ZN24vtkOSPRayMaterialLibrary13InternalParseEPKcb+0x456)[0x7f6dcbfabf26]
[avignon:17635] [11] /usr/lib/libvtkPVServerManagerApplication-pv5.5.so.1(_Z27vtkPVMaterialLibraryCommandP26vtkClientServerInterpreterP13vtkObjectBasePKcRK21vtkClientServerStreamRS5_Pv+0x6a8)[0x7f6de0cd0f78]
[avignon:17635] [12] /usr/lib/libvtkClientServer-pv5.5.so.1(_ZN26vtkClientServerInterpreter19CallCommandFunctionEPKcP13vtkObjectBaseS1_RK21vtkClientServerStreamRS4_+0x1e1)[0x7f6dd9daa651]
[avignon:17635] [13] /usr/lib/libvtkClientServer-pv5.5.so.1(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServerStreami+0x670)[0x7f6dd9daaed0]
[avignon:17635] [14] /usr/lib/libvtkClientServer-pv5.5.so.1(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerStreami+0x5cf)[0x7f6dd9dab6ef]
[avignon:17635] [15] /usr/lib/libvtkClientServer-pv5.5.so.1(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStream+0x1e)[0x7f6dd9daba4e]
[avignon:17635] [16] /usr/lib/libvtkPVServerImplementationCore-pv5.5.so.1(_ZN16vtkPVSessionCore21ExecuteStreamInternalERK21vtkClientServerStreamb+0xff)[0x7f6ddf0af4af]
[avignon:17635] [17] /usr/lib/libvtkPVServerImplementationCore-pv5.5.so.1(_ZN16vtkPVSessionCore13ExecuteStreamEjRK21vtkClientServerStreamb+0x4c)[0x7f6ddf0af2cc]
[avignon:17635] [18] /usr/lib/libvtkPVServerImplementationCore-pv5.5.so.1(_ZN16vtkPVSessionBase13ExecuteStreamEjRK21vtkClientServerStreamb+0x35)[0x7f6ddf0addc5]
[avignon:17635] [19] /usr/lib/libvtkPVServerManagerCore-pv5.5.so.1(_ZN18vtkSMSessionClient13ExecuteStreamEjRK21vtkClientServerStreamb+0x19f)[0x7f6de40442df]
[avignon:17635] [20] /usr/lib/libvtkPVServerManagerRendering-pv5.5.so.1(_ZN25vtkSMMaterialLibraryProxy11SynchronizeEv+0x297)[0x7f6ddf39c187]
[avignon:17635] [21] /usr/lib/libvtkPVServerManagerCore-pv5.5.so.1(_ZN31vtkSMParaViewPipelineController17InitializeSessionEP12vtkSMSession+0x768)[0x7f6de3fe6468]
[avignon:17635] [22] /usr/lib/libvtkpqCore-pv5.5.so.1(_ZN20pqServerManagerModel19onConnectionCreatedEx+0x31b)[0x7f6de48c681b]
[avignon:17635] [23] /usr/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x886)[0x7f6de27a6606]
[avignon:17635] [24] /usr/lib/libvtkpqCore-pv5.5.so.1(_ZN23pqServerManagerObserver17connectionCreatedEx+0x43)[0x7f6de4906503]
[avignon:17635] [25] /usr/lib/libvtkpqCore-pv5.5.so.1(+0x14c962)[0x7f6de4906962]
[avignon:17635] [26] /usr/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x886)[0x7f6de27a6606]
[avignon:17635] [27] /usr/lib/libvtkGUISupportQt-pv5.5.so.1(+0x37e2c)[0x7f6ddfb36e2c]
[avignon:17635] [28] /usr/lib/libvtkGUISupportQt-pv5.5.so.1(+0x24e89)[0x7f6ddfb23e89]
[avignon:17635] [29] /usr/lib/libvtkCommonCore-pv5.5.so.1(_ZN18vtkCallbackCommand7ExecuteEP9vtkObjectmPv+0x19)[0x7f6ddd99d1c9]
[avignon:17635] *** End of error message ***
```
The client complains with:
```
Client connected.
ERROR: In /gpfs/paragon/local/HCRI016/dre03/shared/build/paraview/ParaView-v5.5.0/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 808
vtkSocketCommunicator (0x10008b368f0): Could not receive tag. 1
ERROR: In /gpfs/paragon/local/HCRI016/dre03/shared/build/paraview/ParaView-v5.5.0/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 301
vtkTCPNetworkAccessManager (0x10007cf7f20): Some error in socket processing.
```
I wasn't able to test alternative clients yet, so I am not sure which side id really failing. At the moment I am leaning towards my client side PV.
If you have any thoughts, please advise.5.6 (Fall 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/18174Programmable filter acting weird2018-08-20T21:02:45-04:00W. Alan ScottProgrammable filter acting weirdI have a user that has created two datasets, one with one simulation process, and one with 10 simulation processes. The second dataset has been appended back into one file. Files are attached (and are UUR). The files should be exactly...I have a user that has created two datasets, one with one simulation process, and one with 10 simulation processes. The second dataset has been appended back into one file. Files are attached (and are UUR). The files should be exactly the same.
When my user loads these two files, and selects both of them, and runs the Programmable Filter, with the following, he gets weird results. If you paint by difference, this should be 0. It is ending up going from -30 to 30.
ParaView 5.5.0, Linux, local server.
* Open both datasets. Be sure to turn all variables on.
* If you look at these datasets, they do not have unique Global Node Ids and Global Element Ids. There are two blocks, and each block has a unique Global Id, but not when you combine two blocks. Is this a bug in the dataset?
* Apply the Programmable filter. Use the following code. Paint by difference.
Code for the Programmable filter is:
```
phi1=inputs[0].PointData['potential']
phi2=inputs[1].PointData['potential']
output.PointData.append(phi2-phi1, 'difference')
```
The difference should be 0. It is -30 to 30. Why?
@utkarsh.ayachit @cory.quammen Have any ideas? Is this even a bug? Any idea what the "right thing to do" is?5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18170Pipeline Browser: eyeball icons not aligned correctly on high DPI displays2018-05-17T22:49:06-04:00Lutz HofmannPipeline Browser: eyeball icons not aligned correctly on high DPI displaysWith a DPI scaling factor of 2, the eyeball icons are not vertically centered:
![image](/uploads/60a7201a88e41dc3952d1e503025eb8b/image.png)With a DPI scaling factor of 2, the eyeball icons are not vertically centered:
![image](/uploads/60a7201a88e41dc3952d1e503025eb8b/image.png)5.6 (Fall 2018)Lutz HofmannLutz Hofmannhttps://gitlab.kitware.com/paraview/paraview/-/issues/18163Windows/dialogs can sometimes get stuck off screen2018-09-10T22:01:06-04:00Cory Quammencory.quammen@kitware.comWindows/dialogs can sometimes get stuck off screenIf a window or dialog is placed on a screen in a multimonitor setup and then that monitor is removed, the window may get stuck in an offscreen position, never to be retrieved. Add a function to bring all windows to the current screen.
S...If a window or dialog is placed on a screen in a multimonitor setup and then that monitor is removed, the window may get stuck in an offscreen position, never to be retrieved. Add a function to bring all windows to the current screen.
See the motivation for this feature originally discussed in #17916.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18162color map editor has incorrect behavior for large ranges2018-10-16T15:25:52-04:00Andrew Bauercolor map editor has incorrect behavior for large rangesSteps to reproduce:
1. Create a Wavelet source
2. Create an Elevation filter with Scalar Range of -1e10 to 1e10
3. Change pseudo-color variable to Elevation
4. Click on the Color Map Editor
Mapping Data window is flashing garbage. Th...Steps to reproduce:
1. Create a Wavelet source
2. Create an Elevation filter with Scalar Range of -1e10 to 1e10
3. Change pseudo-color variable to Elevation
4. Click on the Color Map Editor
Mapping Data window is flashing garbage. This is not occurring in PV 5.5 but is occurring in 5edcdd16598893942bf3515d03592e51bc2ac089.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18159Multiblock Inspector: allow changing properties for all selected items2018-07-16T21:40:24-04:00Utkarsh AyachitMultiblock Inspector: allow changing properties for all selected itemsIn the same spirit as paraview/paraview#18157, if user selects a bunch of rows and then double clicks on the color or opacity swatch to change it, the change should apply to all the selected items and not just the item that was clicked.In the same spirit as paraview/paraview#18157, if user selects a bunch of rows and then double clicks on the color or opacity swatch to change it, the change should apply to all the selected items and not just the item that was clicked.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18157Support toggling check state for all selected items in a tree view2018-07-16T21:44:10-04:00Utkarsh AyachitSupport toggling check state for all selected items in a tree view* open can.ex2, apply
* open Multiblock Inspector, and select a bunch of rows.
* Now, if you click on the checkbox in any of the selected rows to toggle it, the selection gets cleared.
What we want instead, is following:
* leave selecti...* open can.ex2, apply
* open Multiblock Inspector, and select a bunch of rows.
* Now, if you click on the checkbox in any of the selected rows to toggle it, the selection gets cleared.
What we want instead, is following:
* leave selection state unchanged
* change check-state for all selected items to match the item that was clicked on.
The same behavior is expected of all checkable tree/table widgets including the variables, blocks, side sets, etc. selection widgets for readers like Exodus, CTH.
See discussion paraview/paraview#181505.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18155Drop *click-row-to-toggle-check* support in tree/table widgets2018-07-16T21:37:06-04:00Utkarsh AyachitDrop *click-row-to-toggle-check* support in tree/table widgetsSee discussion here: paraview/paraview#18150
We're dropping support in widget like the variable selection widget on Exodus reader where the user can click on a row to toggle the checkstate for it. Now, the user has the click on the chec...See discussion here: paraview/paraview#18150
We're dropping support in widget like the variable selection widget on Exodus reader where the user can click on a row to toggle the checkstate for it. Now, the user has the click on the checkbox -- which is the norm.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18150Block selection in Exodus reader and multiblock inspector broken2018-09-10T19:06:44-04:00W. Alan ScottBlock selection in Exodus reader and multiblock inspector brokenThe block selection in the Exodus reader and the Multi-block inspector is broken. This is important functionality, and needs to get fixed. This selection worked correctly with 5.4.1, and can be used to see what should happen. Here is ...The block selection in the Exodus reader and the Multi-block inspector is broken. This is important functionality, and needs to get fixed. This selection worked correctly with 5.4.1, and can be used to see what should happen. Here is how to replicate:
* Linux, builtin server, 5.5.0.
* Open bake.e. (UUR dataset, ask me for it if you don't have it.) Apply (not necessary, but then you see the model.)
Now, our goal is to only select blocks 20 through 40.
* On the Blocks section of the Properties tab, turn off all blocks
* Highlight block 20.
* SHIFT and select row block 40.
Now, all of the blocks between 20 and 40 are highlighted.
* Left select one of the check-boxes for the blocks. All 21 of the blocks should now be selected. But, the highlights are lost, and only one is selected.
We need the same functionality in the multi-block inspector (although this tab never worked correctly.)5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18146Create faster wavelet type source2018-09-19T16:56:46-04:00W. Alan ScottCreate faster wavelet type sourcePlease add a source that makes 3d cells, such as wavelet, without the complex (and time expensive) math. This does not need to be complex at all - it can be as simple as wavelet, but color by distance from the center, or corner. Maybe...Please add a source that makes 3d cells, such as wavelet, without the complex (and time expensive) math. This does not need to be complex at all - it can be as simple as wavelet, but color by distance from the center, or corner. Maybe make numerous variables, some trivial to calculate, such as distance in the X axis.
This filter needs to create it's data correctly in parallel, as Wavelet currently does.5.6 (Fall 2018)John TourtellottJohn Tourtellotthttps://gitlab.kitware.com/paraview/paraview/-/issues/18140Add feature to allow users to specify a window title for the GUI2018-05-18T20:53:17-04:00Andrew BauerAdd feature to allow users to specify a window title for the GUIWhen using multiple PV GUIs simultaneously, especially with similar datasets and analyses, it can be confusing to quickly determine which GUI is doing what. It would be good to allow the user to specify a window title to allow them to ea...When using multiple PV GUIs simultaneously, especially with similar datasets and analyses, it can be confusing to quickly determine which GUI is doing what. It would be good to allow the user to specify a window title to allow them to easily identify what each PV GUI is doing.
This should probably be allowed to be done 2 ways:
1. Through an environment variable like `> PARAVIEW_WINDOW_TITLE="Some Name" ./bin/paraview`
2. Through the PV Edit menu with an entry called something like `Set Window Title`5.6 (Fall 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/18137Find Data spreadsheet numbers are trash2018-05-18T20:20:48-04:00W. Alan ScottFind Data spreadsheet numbers are trashFind data is producing numbers in the spreadsheet that are total trash. They look like numerous numbers are writing on top of each other! Here is how to fix:
* OSX, 5.5.0, built in server.
* can.exo. All vars on. Apply.
* Merge Block...Find data is producing numbers in the spreadsheet that are total trash. They look like numerous numbers are writing on top of each other! Here is how to fix:
* OSX, 5.5.0, built in server.
* can.exo. All vars on. Apply.
* Merge Blocks. Apply.
* Move forward one timestep.
* Find Data. Points. Merge Blocks. Displ(2). Is Min. Run Selection query.
The X component of the Displ variable will be trash. I wonder if it a problem mixing normal floats (0.123) with very small numbers 1.23e-6 or negative small numbers -1.23e-6. Please fix it.
Ask if we need a screenshot, I can make one when home.5.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachit