ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-08-08T22:26:16-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/14342Integrate variable fails with empty servers2018-08-08T22:26:16-04:00Kitware RobotIntegrate variable fails with empty servers**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14342). Further discussion may take place here.**
---
Sorry, not a good summary.
When you try to integrate variables, and you...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14342). Further discussion may take place here.**
---
Sorry, not a good summary.
When you try to integrate variables, and you don't have data in each remote server (each pvserver), integrate variables filter fails. Time for an example:
* Linux, master, 8 remote servers.
* Open g1s1-10fps.e.16.*. All variables on. Apply.
* Integrate variables. Apply. Go to Cell Type in the spreadsheet view. Notice that there is at TEMP summed variable, that is around 19903 degrees. This is correct.
* Close the Integrate variables filter.
* Unselect block 1 and 3, leaving only block 2 selected. Apply. Using the Process Id Scalars filter, you can see that this block only goes into one pvserver. 7 are left empty.
* Integrate variables filter. Apply. Go to Cell Type in the spreadsheet view. Notice there is no TEMP summed variable. This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/14341merge sqplugin xml updates + test system caps fix2018-08-08T22:26:16-04:00Kitware Robotmerge sqplugin xml updates + test system caps fix**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14341). Further discussion may take place here.**
---
* commit 5a5836674c9b175e907e5a4f2b08e6fd6ee9ae5a
| Author: Burlen Loring...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14341). Further discussion may take place here.**
---
* commit 5a5836674c9b175e907e5a4f2b08e6fd6ee9ae5a
| Author: Burlen Loring <bloring@lbl.gov>
| Date: Mon Oct 21 13:22:39 2013 -0700
|
| append rather than replace with cmake properties
|
| When configuring TestSystemCaps changed set_source_files_properties
| to set_property because we need to append rather than replace
| previous values. This change lets both MPI and Python report run.
|
| Change-Id: I178523a08780253c63b2e751189d6053a04cd839
|
| .../Default/Testing/Cxx/CMakeLists.txt | 8 ++++----
| 1 file changed, 4 insertions(+), 4 deletions(-)
|
* commit cd5f6bdd2b3a00fb5901c1dee204bf6244fbc1ab
Author: Burlen Loring <bloring@lbl.gov>
Date: Wed Oct 16 14:28:07 2013 -0700
SciberQuestToolKit Plugin: Don't use VTK RK45 integrator
Change-Id: Ib65f302593bedfe83a1b96e28a9ac43a97fbef44
.../SciberQuestToolKitSMFilters.xml | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
https://gitlab.kitware.com/paraview/paraview/-/issues/14339Property panel for Elevation filter is broken!2018-08-08T22:26:16-04:00Kitware RobotProperty panel for Elevation filter is broken!**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14339). Further discussion may take place here.**
---
Property panel for Elevation filter is broken!**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14339). Further discussion may take place here.**
---
Property panel for Elevation filter is broken!https://gitlab.kitware.com/paraview/paraview/-/issues/14338ParaView fails to build with External hdf52018-08-08T22:26:18-04:00Kitware RobotParaView fails to build with External hdf5**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14338). Further discussion may take place here.**
---
After recent private dependency changes, ParaView fails to build with Exte...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14338). Further discussion may take place here.**
---
After recent private dependency changes, ParaView fails to build with External hdf5.
https://gitlab.kitware.com/paraview/paraview/-/issues/14337Error deleting objects from pipeline2018-08-08T22:26:18-04:00Kitware RobotError deleting objects from pipeline**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14337). Further discussion may take place here.**
---
I am having receiving error messages with the 4.0.1 release of paraview as...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14337). Further discussion may take place here.**
---
I am having receiving error messages with the 4.0.1 release of paraview as well as a recent build of master when deleting objects that are part of a pipeline. The following code snippet gives an an error message.
from paraview import simple as smp
s = smp.Sphere()
smp.Show(s)
smp.Render()
c = smp.Contour()
smp.Show(c)
smp.Render()
smp.Delete(c)
Results in the error message
ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/ParaViewCore/ServerManager/Core/vtkSMProxyListDomain.cxx, line 189
vtkSMProxyListDomain (0x67c2aa0): Index 2 greater than max 1
https://gitlab.kitware.com/paraview/paraview/-/issues/14336ParaView examples not being built with BUILD_EXAMPLES is ON2018-08-08T22:26:18-04:00Kitware RobotParaView examples not being built with BUILD_EXAMPLES is ON**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14336). Further discussion may take place here.**
---
ParaView examples not being built with BUILD_EXAMPLES is ON. Was able to r...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14336). Further discussion may take place here.**
---
ParaView examples not being built with BUILD_EXAMPLES is ON. Was able to reproduce it with Ninja generator on Linux.https://gitlab.kitware.com/paraview/paraview/-/issues/14335Update vtkPVHardwareSelector2018-08-08T22:26:18-04:00Kitware RobotUpdate vtkPVHardwareSelector**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14335). Further discussion may take place here.**
---
Update vtkPVHardwareSelector
Update vtkPVHardwareSelector to reflect refa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14335). Further discussion may take place here.**
---
Update vtkPVHardwareSelector
Update vtkPVHardwareSelector to reflect refactor device specifc
code into the new vtkOpenGLHardwareSelector.
Fix some warnings
in vtkPVServerInformation fix int to bool performance warning
in vtkSMRepresentationProxy fix unreferenced formal paramter warning
in pqMultiBlockInspectorPanel fix signed-unsigned comparison warning
in pqScalarValueListPropertyWidget fix declaration shadow warning
in vtkTexturePainter fix int to bool performance warninghttps://gitlab.kitware.com/paraview/paraview/-/issues/14334Min/Max range not saved in state files2018-08-08T22:26:18-04:00Kitware RobotMin/Max range not saved in state files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14334). Further discussion may take place here.**
---
The min and max are not saved in state files. This is impacting climate s...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14334). Further discussion may take place here.**
---
The min and max are not saved in state files. This is impacting climate simulations of mine.
* Linux, Master, local server.
* Sources/ Wavelet. Apply. Surface. Color by RT data.
* Color Editor. Rescale to custom range. 50 to 200. Rescale, Update.
* Save state file.
* Either exit and restart ParaView, or hit the magic disconnect button.
* Open state file.
<bug> - the custom range is not restored.
<Note> - Is there anything else in the color map editor that needs to be stored?
https://gitlab.kitware.com/paraview/paraview/-/issues/14333Gradient colors don't persist between runs.2018-08-08T22:26:18-04:00Kitware RobotGradient colors don't persist between runs.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14333). Further discussion may take place here.**
---
Gradient color doesn't persist between runs. Further, Gradient color proba...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14333). Further discussion may take place here.**
---
Gradient color doesn't persist between runs. Further, Gradient color probably shouldn't be on the View Settings dialog box.
* Master, Linux, local server.
* Edit/ View Settings/ General. Click on Gradient Color.
* Change the second color to red. Apply.
* Close ParaView and reopen ParaView.
<Bug> - Gradient color background is not in effect.
<Bug> - If you turn on Gradient Color again, the second color of red is reset.
<Possible bug> - should this functionality be moved to the Settings dialog?
https://gitlab.kitware.com/paraview/paraview/-/issues/14332Document GPU-accelerated ParaViewWeb rendering using VirtualGL and TurboVNC2018-08-08T22:26:18-04:00Kitware RobotDocument GPU-accelerated ParaViewWeb rendering using VirtualGL and TurboVNC**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14332). Further discussion may take place here.**
---
We have researched a method for using VirtualGL and TurboVNC in order to p...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14332). Further discussion may take place here.**
---
We have researched a method for using VirtualGL and TurboVNC in order to provide hardware-accelerated rendering capability to ParaViewWeb, even in situations where there is not a physical display. We need some documentation of the steps required in order to reproduce this result on the ParaViewWeb documentation site.https://gitlab.kitware.com/paraview/paraview/-/issues/14328CMake 2.8.12 Now warns about mixing new and old target_link_libraries signatu...2018-08-08T22:26:18-04:00Kitware RobotCMake 2.8.12 Now warns about mixing new and old target_link_libraries signature on a target.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14328). Further discussion may take place here.**
---
The behavior of using new and old target_link_libraries signature on a tar...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14328). Further discussion may take place here.**
---
The behavior of using new and old target_link_libraries signature on a target is not what people expect.
So now CMake 2.8.12 warns about doing it.
I have pushed a change to stage that corrects all the warnings.https://gitlab.kitware.com/paraview/paraview/-/issues/14327vtkzlib is privately linked in vtk2018-08-08T22:26:18-04:00Kitware Robotvtkzlib is privately linked in vtk**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14327). Further discussion may take place here.**
---
error: http://open.cdash.org/viewBuildError.php?buildid=3060740
with vt...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14327). Further discussion may take place here.**
---
error: http://open.cdash.org/viewBuildError.php?buildid=3060740
with vtk moving vtkzlib to be a private dependency, it means that paraview has to be updated to link to vtkzlib only where required.https://gitlab.kitware.com/paraview/paraview/-/issues/14326vtkSTLReader does not read ASCII STL anymore2017-12-17T12:42:46-05:00Kitware RobotvtkSTLReader does not read ASCII STL anymore**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14326). Further discussion may take place here.**
---
Hi all,
the vtkSTLReader seems to have an old problem again. The Reader...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14326). Further discussion may take place here.**
---
Hi all,
the vtkSTLReader seems to have an old problem again. The Reader can not open an ASCII STL file anymore.
I get the following error:
ERROR: In /home/shorty/software/ParaView-3.14.1-Source/VTK/IO/vtkSTLReader.cxx, line 446
vtkSTLReader (0x2959910): STLReader error reading file: /home/shorty/OpenFOAM/shorty-2.2.x/run/schichtspeicher/cad/outlet.stl Premature EOF while reading end solid.
It is the same error like here: http://vtk.org/Bug/view.php?id=13160
The STL file is created with SALOME MECA and older STL files can not be loaded to. Additionally I tested the STL files used in the OpenFOAM tutorial for meshing. The same error.
This error occur with self-build in 3.12.0 3.14.0 3.14.1
This error occur with binaries in 3.12.0 3.14.1
With the latest version (binaries) V4 it is working.
Maybe an additional information.
I had a look at the STL files and everything is fine.
To remove the error I can change the last line in the STL file:
endsolid --> end solid
After that the vtkSTLReader can read the file but this should not be the normal way.
STL files can be loaded when converting into binary format.
If you need more information let me know.
Regard
Tobihttps://gitlab.kitware.com/paraview/paraview/-/issues/14325depth buffer with contours and alpha error2018-08-08T22:26:18-04:00Kitware Robotdepth buffer with contours and alpha error**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14325). Further discussion may take place here.**
---
There is a depth buffer bug with contours and alpha. It is replicated as ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14325). Further discussion may take place here.**
---
There is a depth buffer bug with contours and alpha. It is replicated as follows:
* Remote server, 8 servers, master, Linux. (I bet you can see it local server, although it may not be as obvious.)
* Wavelet, apply.
* Contour. Delete the contour that is there. Generate new contours (default - which makes 10 of them). Apply.
* Turn off visibility of the Wavelet.
* Change contour's coloring to Normals. Change "Magnitude" to "X".
* -X
* Now, change the opacity to 0.999. Click somewhere else, such as point size. Although there should be no change, the image will change - and look horrible. Z buffer problems will be all over - with black lines triangles bleeding through, blue bleeding through, etc.
If this is hard to replicate, ask me and I can make a screenshot.
https://gitlab.kitware.com/paraview/paraview/-/issues/14322client/server communication makes kernel's TCP buffer overflow2018-08-08T22:26:18-04:00Kitware Robotclient/server communication makes kernel's TCP buffer overflow**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14322). Further discussion may take place here.**
---
Steps to reproduce:
1. Launch pvserver in mutli-client mode
2. Launch pa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14322). Further discussion may take place here.**
---
Steps to reproduce:
1. Launch pvserver in mutli-client mode
2. Launch paraview client to connect to the above
paraview -url=cs://localhost:11111
3. Launch the attached script (shrink-sphere.py), either with "pvpython" (in which case the Ctrl-C is not caught
properly) or with python (and the correct PYTHONPATH) directly.
4. Inspecting the network status with:
netstat --inet -np
shows that the Python client script has its TCP buffer growing and growing (column "Recv-Q"). This ultimately crashes.
It seems that the client is not trying to read everything the server sends.
This is not a timing issue: increasing the "sleep" delay in the script to 1 sec shows the same behavior.
This is only with scripting: the configuration with only pvserver and paraview-client doesn't exhibit the behavior.
The behavior is seen with both the binary version (Linux 64 bits) and with a self-recompiled version (Linux 64 bits) of
ParaView 4.0.1.
-------- THE SCRIPT:
# Supposing the pvserver is already started on 'localhost'
from paraview import simple as spl
from time import sleep
# Connect to the pvserver
spl.Connect('localhost')
# Create a sphere and apply the Shrink filter to it:
ss = spl.Sphere(Radius=2, ThetaResolution=32)
shr = spl.Shrink(Input=ss)
spl.Show(shr)
spl.SetDisplayProperties(Representation = "Wireframe")
#shr.SetPropertyWithName("ShrinkFactor", 0.9)
# Loop on the shrink factor up and down for a while:
shr.ShrinkFactor = 0.5
step = 0.1
try:
while True:
if shr.ShrinkFactor >= 1.0:
step = -0.1
if shr.ShrinkFactor <= 0.0:
step = +0.1
shr.ShrinkFactor += step
sleep(0.1)
pass
except KeyboardInterrupt:
print "Ctrl-C received"
try:
while True:
pass
except KeyboardInterrupt:
print "Ctrl-C again! This time bye bye."
spl.Disconnect()
https://gitlab.kitware.com/paraview/paraview/-/issues/14321Duplicate StillRender() calls after interactive render.2018-08-08T22:26:18-04:00Kitware RobotDuplicate StillRender() calls after interactive render.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14321). Further discussion may take place here.**
---
When you create a source in ParaView (or read a file) there ONE StillRende...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14321). Further discussion may take place here.**
---
When you create a source in ParaView (or read a file) there ONE StillRender pass at the end of the process, normal. But when you interact, after the InteractiveRender passes, once you release the left button of the mouse, there is not one but TWO StillRender passes. Of course it might be nothing but it is very frustrating when visualizing very large data which requires several seconds to render...
https://gitlab.kitware.com/paraview/paraview/-/issues/14320Turn of requiring user-input on error on Windows2018-08-08T22:26:18-04:00Kitware RobotTurn of requiring user-input on error on Windows**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14320). Further discussion may take place here.**
---
From a user:
...lockup on Paraview 4.0.1 Windows pvserver
The issue ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14320). Further discussion may take place here.**
---
From a user:
...lockup on Paraview 4.0.1 Windows pvserver
The issue was that the Output Window PromptUser flag was set by default, which was causing the server processes to wait for input after the first line of output was generated. This locked up the server processes as no input could be supplied to them.
https://gitlab.kitware.com/paraview/paraview/-/issues/14318"Zoom to Box" does not behave properly2018-03-01T06:04:57-05:00Kitware Robot"Zoom to Box" does not behave properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14318). Further discussion may take place here.**
---
The attached video recording was sent to me by the customer who was experi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14318). Further discussion may take place here.**
---
The attached video recording was sent to me by the customer who was experiencing problems with the "Zoom to Box" functionality.
I was able to reproduce this with the latest master (095ac28). Here are the steps to reproduce:
(1) Open the attached GenericIO particle data
(2) Select the x,y,z variables for each respective axis
(3) Try to zoom in any of the halos (particle clusters)
The customer had also multi-core enabled, likely with 2-4 processes.https://gitlab.kitware.com/paraview/paraview/-/issues/14317Segfault in Find Data dialog2018-08-08T22:26:18-04:00Kitware RobotSegfault in Find Data dialog**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14317). Further discussion may take place here.**
---
Steps to reproduce:
1. Create Wavelet, Apply,
2. Split view to create sp...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14317). Further discussion may take place here.**
---
Steps to reproduce:
1. Create Wavelet, Apply,
2. Split view to create spreadsheet view
3. Click and drag slowly in the spreadsheet view to see that the points get selected. So far so good.
4. Open Find Data Dialog
5. Now, with Find Data dialog open, repeat 3. It will segfault quite promptly (I was doing this on Linux)https://gitlab.kitware.com/paraview/paraview/-/issues/14316Add basic tests of ParaView web services2018-08-08T22:26:18-04:00Kitware RobotAdd basic tests of ParaView web services**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14316). Further discussion may take place here.**
---
The ParaView web python based webservices (DataProber, ParallelViz, WebFil...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14316). Further discussion may take place here.**
---
The ParaView web python based webservices (DataProber, ParallelViz, WebFileViewer, WebVisualizer) need some basic tests to ensure that at least all the modules needed to run them are in place and available.