ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:49:48-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/4739Switching to Wrapped HSV in new Color Scale Editor causes a segfault2019-03-05T10:49:48-05:00Kitware RobotSwitching to Wrapped HSV in new Color Scale Editor causes a segfault**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4739). Further discussion may take place here.**
---
If you switch to Wrapped HSV color space in the new Color Scale Editor, Par...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4739). Further discussion may take place here.**
---
If you switch to Wrapped HSV color space in the new Color Scale Editor, ParaView segfaults:
ERROR: In /home/projects/ParaView3-Trunk/ParaView3/VTK/Filtering/vtkColorTransferFunction.cxx, line 864
vtkColorTransferFunction (0xab22060): Index out of range!
ERROR: In /home/projects/ParaView3-Trunk/ParaView3/VTK/Filtering/vtkColorTransferFunction.cxx, line 864
vtkColorTransferFunction (0xab22060): Index out of range!
Segmentation faulthttps://gitlab.kitware.com/paraview/paraview/-/issues/19529Symbol Quad::Quad(void) already defined by VTK2021-03-24T06:42:41-04:00Alexander NeumannSymbol Quad::Quad(void) already defined by VTKall static build on windows with external VTK
vtkInfovisLayout-8.90d.lib(vtkIncrementalForceLayout.cxx.obj) : error LNK2005: "public: __cdecl Quad::Quad(void)" (??0Quad@@QEAA@XZ) already defined in lightweight_visit_vtk-pv5.7d.lib(vtkUn...all static build on windows with external VTK
vtkInfovisLayout-8.90d.lib(vtkIncrementalForceLayout.cxx.obj) : error LNK2005: "public: __cdecl Quad::Quad(void)" (??0Quad@@QEAA@XZ) already defined in lightweight_visit_vtk-pv5.7d.lib(vtkUnstructuredGridFacelistFilter.C.obj)
Creating library lib\paraview.lib and object lib\paraview.exphttps://gitlab.kitware.com/paraview/paraview/-/issues/22388symbols not found in some libraries in binary build2024-01-25T13:36:35-05:00Dan Lipsasymbols not found in some libraries in binary buildThis happens for ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64 and ParaView-master-5.12.0-RC1-160-g92dacc77cb-MPI-Linux-Python3.10-x86_64
```
[~/external]$ tar xzf ~/Downloads/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64.tar.gz
[~/...This happens for ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64 and ParaView-master-5.12.0-RC1-160-g92dacc77cb-MPI-Linux-Python3.10-x86_64
```
[~/external]$ tar xzf ~/Downloads/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64.tar.gz
[~/external]$ cd ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64/
~/external/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64]$ for i in `find . -name '*.so'`; do echo $i;ldd $i | grep 'not found'; done > not_found.txt
```
[not_found.txt](/uploads/d8b853d09f6fc7f9dd1d080d05279709/not_found.txt)
filtered list of libraries:
[not_found_filtered.txt](/uploads/18dda1f5901def3101bedf2e3874a252/not_found_filtered.txt)5.12 (Winter 2023)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/4403Sync interactive render on linked camera views2019-03-05T10:50:56-05:00Kitware RobotSync interactive render on linked camera views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4403). Further discussion may take place here.**
---
When the camera is linked on two views, the images are not synced during an...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4403). Further discussion may take place here.**
---
When the camera is linked on two views, the images are not synced during an interactive render. That is, when you manipulate the camera on one view, the other linked view remains static until I let go of the mouse. Both views should always update at the same time.https://gitlab.kitware.com/paraview/paraview/-/issues/21479synchronize time over multiple datasets2023-01-03T12:08:13-05:00Boonthanome Nouanesengsysynchronize time over multiple datasetsI have multiple datasets that I would like to compare at essentially the same simulation times. But each dataset has slightly different simulation times. Sometimes it’s more than slightly different. Is there some way to synchronize the d...I have multiple datasets that I would like to compare at essentially the same simulation times. But each dataset has slightly different simulation times. Sometimes it’s more than slightly different. Is there some way to synchronize the datasets together in time? I’d like to set one dataset as a “master time”, and have all the other datasets be synchronized to it.
I’m aware of the Synchronize Time filter, and that will mostly work, but sometimes the times are far enough apart that I’d like to have a new timestep be generated by interpolating between two timesteps. I do know that the Temporal Interpolator filter will interpolate between timesteps, but it doesn’t really do exactly what I want.
In summary, it would be nice to have a filter:
- accept multiple input datasets that are close together in time
- set one dataset to be the 'master' time that other datasets must sync in time to
- have a threshold
- if the time delta is smaller than the threshold, set the 'master' time as the time (like the Synchronize Time Filter)
- if the time delta is larger than the threshold, interpolate a new timestep (like the Temporal Interpolator Filter)
@patchett2002 @cory.quammen @yohann.bearzihttps://gitlab.kitware.com/paraview/paraview/-/issues/15923Syntax error when adding Python Calculator2017-11-22T15:14:20-05:00Kitware RobotSyntax error when adding Python Calculator**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15923). Further discussion may take place here.**
---
Steps:
0. This is with the official 5.0.0 Linux 64-bit binaries
1. Start...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15923). Further discussion may take place here.**
---
Steps:
0. This is with the official 5.0.0 Linux 64-bit binaries
1. Start Paraview
2. Add any source (e.g. wavelet, line, load data), press Apply
3. Add a Python Calculator, press Apply
Traceback (most recent call last):
File "<string>", line 4, in <module>
File "/home/paulm/software/ParaView-5.0.0-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages/paraview/calculator.py", line 102, in execute
retVal = compute(inputs, expression, ns=variables)
File "/home/paulm/software/ParaView-5.0.0-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/site-packages/paraview/calculator.py", line 74, in compute
retVal = eval(expression, globals(), mylocals)
File "<string>", line 0
^
SyntaxError: unexpected EOF while parsinghttps://gitlab.kitware.com/paraview/paraview/-/issues/17699sys.path ordering problem - ParaView directories are listed last2020-05-08T21:50:29-04:00Cory Quammencory.quammen@kitware.comsys.path ordering problem - ParaView directories are listed lastThere have been a couple reports on the mailing list of ParaView putting its path last in `sys.paths`:
> Paraview used the correct python executable, but the pythonpath was incorrect. vtk.__file__ showed a path to the anaconda python f...There have been a couple reports on the mailing list of ParaView putting its path last in `sys.paths`:
> Paraview used the correct python executable, but the pythonpath was incorrect. vtk.__file__ showed a path to the anaconda python folder. I had an environment variable pythonpath set for anaconda, and in paraview these paths were at the beginning of `sys.path`. I removed the environment variable and everything works fine. Could it be possible to add the paraview python paths at the beginning of `sys.path`?
and:
> I've encountered a minor, but annoying issue (for me, at least) when using Python in Paraview (installed from binaries on Windows). I noticed that since version 5.2, the Paraview-related paths are appended to the end of the system PYTHONPATH variable, instead of inserted at the beginning. For instance:
> v5.1.2
```
>>> import sys
>>> for p in sys.path:
... print p
...
D:\Program Files\ParaView 5.1.2\lib\paraview-5.1\site-packages\vtk
D:\Program Files\ParaView 5.1.2\lib\paraview-5.1\site-packages <- Paraview VTK code
D:\Program Files\ParaView 5.1.2\lib\paraview-5.1
D:\Program Files\ParaView 5.1.2\bin
...
D:\Anaconda2\Lib\site-packages <- original system PYTHONPATH paths
etc...
D:\Program Files\ParaView 5.1.2\bin\python27.zip
D:\Program Files\ParaView 5.1.2\bin\DLLs
D:\Program Files\ParaView 5.1.2\bin\lib
D:\Program Files\ParaView 5.1.2\bin\lib\plat-win
D:\Program Files\ParaView 5.1.2\bin\lib\lib-tk
D:\Program Files\ParaView 5.1.2\bin
D:\Program Files\ParaView 5.1.2\bin\lib\site-packages
```
> v5.4.0-RC2:
```
>>> import sys
>>> for p in sys.path:
... print p
...
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin
...
D:\Anaconda2\Lib\site-packages <- original system PYTHONPATH paths
etc...
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\python27.zip
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\DLLs
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\plat-win
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\lib-tk
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages <- Paraview VTK code
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\win32
D:\Program Files\ParaView 5.4.0-RC2-Qt5-OpenGL2-Windows-64bit\bin\lib\site-packages\win32\lib
```
> This is a problem for me because I like to use the Python Programmable Filter a lot, but now whenever I import VTK, it will first look for the version of VTK on my system, rather than the one used by Paraview, which leads to conflict errors.
> I know this can be fixed by running the Python Shell and manipulating the PYTHONPATH variable from there, but I'd have to do that every time I open Paraview, which is pretty cumbersome. Is there a way to change this behavior? Could it be a changed back in future versions or was there a reason for this change?https://gitlab.kitware.com/paraview/paraview/-/issues/9159system colors are ignored again2019-03-05T10:42:16-05:00Kitware Robotsystem colors are ignored again**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9159). Further discussion may take place here.**
---
Tooltips bg color is always white regardless of system settings. I use whit...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9159). Further discussion may take place here.**
---
Tooltips bg color is always white regardless of system settings. I use white for system font color (along with dark bg throughout) and the tooltips are unreadable. Ubuntu 9.04 + Gnome + Qt4.5https://gitlab.kitware.com/paraview/paraview/-/issues/17999System HANG - pvbatch is throwing bazillians of processes when loading state ...2019-07-24T18:41:47-04:00W. Alan ScottSystem HANG - pvbatch is throwing bazillians of processes when loading state fileI have a pvbatch python file that is loading a state file, and then processing over time. Each time through it creates a dozen or so new pvbatch processes. This is running until it kills the blade.
This is a show stopper for a custo...I have a pvbatch python file that is loading a state file, and then processing over time. Each time through it creates a dozen or so new pvbatch processes. This is running until it kills the blade.
This is a show stopper for a customer.
* Linux, 5.4.1 Kitware download.
* Read and implement the README file.
* Basically, copy can.ex2 into this directory.
* Edit the .py and .pvsc file, correcting the directory paths.
* Run as follows: ./pvbatch --use-offscreen-rendering --mesa-llvm save_animation.py
In a separate xterm, run htop. You will notice that there will be dozens of pvbatch processes, and every timestep, more will appear. This will continue until the Linux box dies.
Attaching the .py, .pvsc and README files.
[pvbatch-replicate-bug.tar.gz](/uploads/8f68f6e41eba263e5ae5c80decc620bc/pvbatch-replicate-bug.tar.gz)5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17549System Macro directory2021-09-01T09:16:19-04:00W. Alan ScottSystem Macro directoryPlease add a system directory that is read for system macros. That way I can give a macro to all of my users, and they can't accidentally delete it.Please add a system directory that is read for system macros. That way I can give a macro to all of my users, and they can't accidentally delete it.https://gitlab.kitware.com/paraview/paraview/-/issues/22196System TBB not found on Centos72023-06-26T10:39:39-04:00Nathan WoodsSystem TBB not found on Centos7When installing tbb-devel on CentOS 7.9, it places the libaries in /usr/lib64, rather than /usr/lib. Find_TBB does not seem to be able to find them, and it's not obvious how to give it the appropriate hints to do so.When installing tbb-devel on CentOS 7.9, it places the libaries in /usr/lib64, rather than /usr/lib. Find_TBB does not seem to be able to find them, and it's not obvious how to give it the appropriate hints to do so.https://gitlab.kitware.com/paraview/paraview/-/issues/8599System-level settings2019-03-05T10:43:09-05:00Kitware RobotSystem-level settings**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=8599). Further discussion may take place here.**
---
For organizations that install a ParaView executable on a shared file serve...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=8599). Further discussion may take place here.**
---
For organizations that install a ParaView executable on a shared file server that everyone uses, it is convenient to have a set of default settings specific to that organization. We would like a settings file located near the binary files (created/edited by the sysop) which ParaView would load before the user's settings. The user's settings could then override the system settings (just like the override the current defaults).https://gitlab.kitware.com/paraview/paraview/-/issues/17536Systematic crash when trying to open a file2023-06-15T09:13:45-04:00FlorentSystematic crash when trying to open a fileHello,
I'm a brand new user of ParaView, and tried versions 5.3 and 5.4, on a Windows 7 machine.
After launching ParaView, when I click on File>Open it crashes every time. It does not even show the file browser. I tried several things w...Hello,
I'm a brand new user of ParaView, and tried versions 5.3 and 5.4, on a Windows 7 machine.
After launching ParaView, when I click on File>Open it crashes every time. It does not even show the file browser. I tried several things with no success:
- open my *.e file with ParaView by right-clicking and "open with..."
- reboot
- reinstall
- delete all network locations, mounted drives, mapped drive
- run as admin
Below is the error report I am getting.
Any help would be appreciated...
Thanks,
F.
Problem signature:
Problem Event Name: APPCRASH
Application Name: paraview.exe
Application Version: 0.0.0.0
Application Timestamp: 58c30bdf
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915fdce
Exception Code: c0000005
Exception Offset: 000000000004f2a2
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: a210
Additional Information 2: a210f48f37319f8ddeeddc026d2b76fc
Additional Information 3: bd9e
Additional Information 4: bd9e4593e4bb98ffb9e09e13ea3ece2dhttps://gitlab.kitware.com/paraview/paraview/-/issues/15127t_index variable not available, Mode Shapes2017-12-04T12:46:54-05:00Kitware Robott_index variable not available, Mode Shapes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15127). Further discussion may take place here.**
---
My user did a good enough job explaining this bug, I will just use his ver...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15127). Further discussion may take place here.**
---
My user did a good enough job explaining this bug, I will just use his verbiage. Here it is:
Hello,
Attached is an exodus file that I'm having trouble with in ParaView 4.2.0, 64-bit, RHEL5.
The problem is that the "t_index" variable is not available when I check the "Has Mode Shapes" option. I am trying to add an annotation that say something like "Eigenvalue is : EigenFrequency[ index ]", but there I can't seem to find what variable refers to the current "Mode Index."
If I uncheck the "Has Mode Shapes" option, then the variable t_index works and I can just do "EigenFrequency[t_index]" to get the frequency to be annotated.
Steps to reproduce:
1) open "example_beam-eig.g", load all variables.
2) Create an "PythonAnnotation" filter.
3) Select "Field Data"
4) Enter "EigenFrequency[t_index]" in the "Expression" field.
5) Apply. Annotation should show up as "0.0"
6) Increase to time step 7, it should read "1985.697"
7) Go back to top of pipeline and select "Has Mode Shapes" check box.
8) ---> ERROR: name t_index is not defined
Ok, well that doesn't work. Let's try the "AnnotateGlobalData" filter.
9) Add a "AnnotateGlobalData" filter.
9a) "Select Arrays" --> EigenFrequency
9b) "Prefix" --> Value is:
9c) Apply
It will show the entire vector -- which is not useful.
10) Uncheck "Has Mode Shapes"
The AnnotateGlobalData filter will just show a single value -- which is useful.
It seems like what is missing is a "Mode Shape Index" variable. Does this exist? If so, it doesn't seem like it's being properly referenced in the annotation filters. But at least I might be able to use a Python Annotation filter to get around this if it does exist.
https://gitlab.kitware.com/paraview/paraview/-/issues/18770taanab / tylo dashboards have disappeared2019-02-12T16:49:49-05:00Utkarsh Ayachittaanab / tylo dashboards have disappearedWe seem to have lost ParaView non-gui dashboards that were running on taanab
tylo windows dashboards have disappeared too.
cc: @ben.boeckel @cory.quammenWe seem to have lost ParaView non-gui dashboards that were running on taanab
tylo windows dashboards have disappeared too.
cc: @ben.boeckel @cory.quammenBen BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19020Tab in the Probe filter is wrong2019-05-22T19:38:49-04:00W. Alan ScottTab in the Probe filter is wrongTab in the Probe filter is wrong.
* 5.6.0, Linux, builtin server.
* Open a dataset, such as can.
* Probe filter.
* Now, place the curser in the X box. Type 1.0. Tab.
The Search box will pick up focus! This is wrong. It should be ...Tab in the Probe filter is wrong.
* 5.6.0, Linux, builtin server.
* Open a dataset, such as can.
* Probe filter.
* Now, place the curser in the X box. Type 1.0. Tab.
The Search box will pick up focus! This is wrong. It should be the Y box.5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/6622Tab order for "show cube axes" is wrong.2019-03-05T10:45:48-05:00Kitware RobotTab order for "show cube axes" is wrong.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6622). Further discussion may take place here.**
---
Tab order for "show cube axes" is wrong.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=6622). Further discussion may take place here.**
---
Tab order for "show cube axes" is wrong.https://gitlab.kitware.com/paraview/paraview/-/issues/7265Tab order for Edit/ View Settings/ Lights is crazy2019-03-05T10:44:42-05:00Kitware RobotTab order for Edit/ View Settings/ Lights is crazy**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=7265). Further discussion may take place here.**
---
Please fix the tab order for the lights, under Render View Options. It jum...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=7265). Further discussion may take place here.**
---
Please fix the tab order for the lights, under Render View Options. It jumps all over the place.https://gitlab.kitware.com/paraview/paraview/-/issues/4578Tab order for text widget display corners is wrong2019-03-05T10:50:22-05:00Kitware RobotTab order for text widget display corners is wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4578). Further discussion may take place here.**
---
In text source display page, the tab order for the corner position widgets ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4578). Further discussion may take place here.**
---
In text source display page, the tab order for the corner position widgets is wrong.https://gitlab.kitware.com/paraview/paraview/-/issues/5671Tab order on Key Frame Interpolation dialog box bad2019-03-05T10:47:22-05:00Kitware RobotTab order on Key Frame Interpolation dialog box bad**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5671). Further discussion may take place here.**
---
Create a camera track using the Animation View. Use it to create some key ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=5671). Further discussion may take place here.**
---
Create a camera track using the Animation View. Use it to create some key frames and then edit one of the key frames. Hit tab in the Key Frame Interpolation dialog box and you will see that the tab order is very screwy. It should go from left to right, top to bottom.