ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-08-28T09:39:50-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/12023Block names not save/read in/from VTM files.2018-08-28T09:39:50-04:00Kitware RobotBlock names not save/read in/from VTM files.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12023). Further discussion may take place here.**
---
Refer to thread: http://markmail.org/thread/72vc7cal3mrqclrf
**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12023). Further discussion may take place here.**
---
Refer to thread: http://markmail.org/thread/72vc7cal3mrqclrf
https://gitlab.kitware.com/paraview/paraview/-/issues/12021Xdmf dataset incorrectly loaded from state file2023-06-15T08:43:38-04:00Kitware RobotXdmf dataset incorrectly loaded from state file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12021). Further discussion may take place here.**
---
I have a dataset in an xmf+hdf5 pair that loads without problems in PV. Af...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12021). Further discussion may take place here.**
---
I have a dataset in an xmf+hdf5 pair that loads without problems in PV. After working in PV on this dataset I saved the state to a .pvsm file. When I try to load this state back in in a fresh PV session the following things happen:
1. I get a "Fix Paths in State File" dialog. The .xmf file in the edit box exists and is the correct one. The path in the .pvsm file is also correct. It's a bit of a mystery why the paths should need fixing in this case.
2. Pressing OK (or even cancel) in the fix path dialog continues loading the state. I can see from strace output that the hdf5 file gets fully loaded, the memory usage also shows this. However, when loading is completed all the memory is freed again. Even though the xmf file is present as a source in the pipeline browser and the pipeline itself is also correctly recreated the xmf dataset actually has 0 points and cells.https://gitlab.kitware.com/paraview/paraview/-/issues/12018Save screenshots and 2d windows different.2018-08-28T09:39:50-04:00Kitware RobotSave screenshots and 2d windows different.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12018). Further discussion may take place here.**
---
From a user:
The attached figs show the result of a 'Save Screenshot' i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12018). Further discussion may take place here.**
---
From a user:
The attached figs show the result of a 'Save Screenshot' in PV 3.10.0 64 bit, vs. what's actually on the screen (captured with PrtSc). In the line-plots, 'Save Screenshot' changed both the font and tick-marks from what's on the screen. I manually increased the rez for the screenshot, but would like the fonts etc to stay the same.
https://gitlab.kitware.com/paraview/paraview/-/issues/12016Line Widget has unnecessary scaling factor when reseting to X/Y/Z axis2019-03-05T10:38:10-05:00Kitware RobotLine Widget has unnecessary scaling factor when reseting to X/Y/Z axis**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12016). Further discussion may take place here.**
---
Line Widget has unnecessary scaling factor when reseting to X/Y/Z axis. Ma...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12016). Further discussion may take place here.**
---
Line Widget has unnecessary scaling factor when reseting to X/Y/Z axis. Makes it hard to plot-over-line over a plane.https://gitlab.kitware.com/paraview/paraview/-/issues/12015QtTesting playback of action2019-03-05T10:38:10-05:00Kitware RobotQtTesting playback of action**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12015). Further discussion may take place here.**
---
The playback of recorded actions, using QtTesting, doesn't work in some ap...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12015). Further discussion may take place here.**
---
The playback of recorded actions, using QtTesting, doesn't work in some applications outside of ParaView. It currently relies on a QAction being owned by the QMenu, and the implementation isn't an exact mirror of the recording.
I've attached a patch so the recording and playback are mirrors of each other.
I've not tried it against ParaView though.https://gitlab.kitware.com/paraview/paraview/-/issues/12014Xdmf dataset written from PV crashes when loading it again2023-06-15T08:46:40-04:00Kitware RobotXdmf dataset written from PV crashes when loading it again**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12014). Further discussion may take place here.**
---
Note: there doesn't seem be to a version 3.10 in the Product Version drop-...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12014). Further discussion may take place here.**
---
Note: there doesn't seem be to a version 3.10 in the Product Version drop-down, so I picked development. This is with the 64 bit binaries of 3.10.0 from paraview.org
Saving a structured points dataset from PV in xmf+hdf5 creates a file that the PV instance can't load anymore as it crashes. The steps below with the wavelet source reproduce the crash, although I encountered this on a real dataset (the attached xmf file)https://gitlab.kitware.com/paraview/paraview/-/issues/12010Visibility not handled correctly in Object Inspector2019-03-05T10:38:10-05:00Kitware RobotVisibility not handled correctly in Object Inspector**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12010). Further discussion may take place here.**
---
I'm using version 3.10.0_64
When clicking on the eye in the Pipeline br...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12010). Further discussion may take place here.**
---
I'm using version 3.10.0_64
When clicking on the eye in the Pipeline browser the tab in Object Inspector called Display does not show the appropriate form (see Screenshot).
It should only show one box where you can tick "Visible"https://gitlab.kitware.com/paraview/paraview/-/issues/12009Line Style None does not work2020-04-30T18:35:29-04:00Kitware RobotLine Style None does not work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12009). Further discussion may take place here.**
---
I'm using version 3.10.0
Line Style = None does not show correct behavi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12009). Further discussion may take place here.**
---
I'm using version 3.10.0
Line Style = None does not show correct behaviour (i.e. no line). Instead it shows a kind of dotted line that moves if mouse is moved.https://gitlab.kitware.com/paraview/paraview/-/issues/12008CTH velocities are calculated incorrectly2023-06-15T15:32:34-04:00Kitware RobotCTH velocities are calculated incorrectly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12008). Further discussion may take place here.**
---
We've found a problem with how paraview reads in velocities from CTH spypl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12008). Further discussion may take place here.**
---
We've found a problem with how paraview reads in velocities from CTH spyplot files which appears to have been a problem since at least 3.6.2. The problem is related to how CTH outputs velocities in it's spyplot files.
First of all, note that velocities are treated differently in CTH compared to all the other variables. All non-velocity values are cell-centered quantities, but velocities are face-centered quantities (x velocities on faces with an x normal, y velocities on faces with y normal, and z velocities on faces with a z normal). In order to get an appropriate cell-centered value for velocity, you have to average the velocities for opposing faces.
This is where we run into problems. Spyplot does not do this averaging before it outputs its results to an spcth file. When it outputs velocities for a cell, it is actually outputting the velocities on the bottom faces, i.e. on the x, y, and z faces that have a smaller quantity centroid than the other x, y, or z face on the cell. In order to get the cell-centered velocities, you need to take the velocities output for the cell and average them with the appropriate cells adjacent in the positive x, y, and z directions. This is elaborated in 2-D in the attached PDF file; 3-D is a simple extension.
Although this is a quirk of the CTH data, it is very much needed for this to be incorporated into paraview so that the proper velocities are output. It is an issue for all CTH visualization, but it is most evident using the material interface filter, which outputs improper averaged velocities for fragments, thus making velocity vector and momentum computations incorrect.
All of this was determined through direct debugging of routines within paraview, and has been confirmed with the CTH developers. I have a very simple, small test case which demonstrates all these issues and is unclassified. Please let me know if you would like it.
Please let me know if you have any questions about any of this.
Note from Alan - I have the dataset example. It is called CTH-velocities.
https://gitlab.kitware.com/paraview/paraview/-/issues/12007Python trace hangs during interaction with animation view2019-03-05T10:38:10-05:00Kitware RobotPython trace hangs during interaction with animation view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12007). Further discussion may take place here.**
---
Reported on the paraview mailing list under the subject: [Paraview] Error ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12007). Further discussion may take place here.**
---
Reported on the paraview mailing list under the subject: [Paraview] Error using Python Trace in PV3.10-RC1
I found a problem using the Python Trace functionality with PV3.10-RC1. I've
loaded in a dataset and started a trace. I then proceeded to take a slice
through the dataset, which worked fine. Next, in the animation view, I added
a cue based on the x-value of the slice origin. Double-clicking on the
scalar bar gives the pop up window to set the start and end values. At this
point, I can't change any of the values and ParaView just hangs. This only
appears to happen with the variables that are essentially vector components
(Normals and Origin); I can modify the scalar options without it crashing.
I did manage to get around the problem by adding one of the vector
components as a track BEFORE starting the trace and then deleting it
immediately. I can then start the trace, add the track again (or any of the
options), modify its values without ParaView crashing.
https://gitlab.kitware.com/paraview/paraview/-/issues/11998Transformation matrix2020-05-04T15:06:41-04:00Kitware RobotTransformation matrix**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11998). Further discussion may take place here.**
---
Request from one of my users:
The transformation matrix is a 3x3 matrix...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11998). Further discussion may take place here.**
---
Request from one of my users:
The transformation matrix is a 3x3 matrix of the direction cosines that is used to transform nodal fields like displacement to a rotated coordinate system. Thus, the analyst may want to have the displacement or acceleration in another frame. A common case for structural dynamics is transformation of a modal test where an accelerometer may be reporting the acceleration in the direction of it's orientation (e.g. it may by glued to a wing of a wind turbine). Element variables (such as strain gauge output) may also be so transformed.
For cartesian coordinate systems, the transformation matrix is just the 3x3 matrix of direction cosines. The coordinate frame information in the exodus file has an origin and the direction cosines of the Z and X directions. The Y direction is obtained by the right hand rule.
Curvilinear coordinates such as the cylindrical and spherical frame actually have a transformation matrix that depends on the point of evaluation. Thus, the direction cosines of a cylinder change as you evaluate points around the cylinder. I'm not sure of the best way to generate a user interface for this. Essentially the analyst needs to provide the coordinate frame and the location for evaluation. Again, the 3x3 matrix of direction cosines is the output.
Also, the customer would not mind consulting with the implementer. https://gitlab.kitware.com/paraview/paraview/-/issues/11996Disable LOD when doing stereo2021-03-24T14:49:50-04:00Kitware RobotDisable LOD when doing stereo**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11996). Further discussion may take place here.**
---
Users report that when stereo is enabled, switching LOD decimation on and ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11996). Further discussion may take place here.**
---
Users report that when stereo is enabled, switching LOD decimation on and off when interacting can be very distracting to see. Maybe by default LOD should be off when stereo is enabled.https://gitlab.kitware.com/paraview/paraview/-/issues/11995PlotOverLine plots all variables (PV 3.10)2019-03-05T10:38:10-05:00Kitware RobotPlotOverLine plots all variables (PV 3.10)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11995). Further discussion may take place here.**
---
As reported on the mailing list today (3/21/11), when I display an image a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11995). Further discussion may take place here.**
---
As reported on the mailing list today (3/21/11), when I display an image array with a single scalar field and then do a PlotOverLine filter, all variables are plotted, even though just one is selected on the Display tab. (rf. http://mypage.iu.edu/~heiland/neurons/matlab_paraview/)https://gitlab.kitware.com/paraview/paraview/-/issues/11994Find Data dialog does not show query results for multiblock datasets2019-03-05T10:38:10-05:00Kitware RobotFind Data dialog does not show query results for multiblock datasets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11994). Further discussion may take place here.**
---
Try using find data dialog on can.ex2.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11994). Further discussion may take place here.**
---
Try using find data dialog on can.ex2.https://gitlab.kitware.com/paraview/paraview/-/issues/11992Need ability to pick font etc for Legend in chart views2019-03-05T10:38:10-05:00Kitware RobotNeed ability to pick font etc for Legend in chart views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11992). Further discussion may take place here.**
---
Users at a course reported that the legend in chart views sometimes ends u...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11992). Further discussion may take place here.**
---
Users at a course reported that the legend in chart views sometimes ends up being too small. They need options to change the font for the legend.https://gitlab.kitware.com/paraview/paraview/-/issues/11989Base64 encoding of VTK output2019-03-05T10:38:10-05:00Kitware RobotBase64 encoding of VTK output**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11989). Further discussion may take place here.**
---
Maybe the Base64 - encoding/decoding is not standart-conform?
As fa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11989). Further discussion may take place here.**
---
Maybe the Base64 - encoding/decoding is not standart-conform?
As far as I understood, the decoded stream is in the format
{int n, float d[0], ... , float d[n-1]}
I exported a very simple example with Paraview;
I'm able to decode the floats, but the leading integer is just wrong;
I'm pretty sure that my decoder works correctly, because it decodes some example from wikipedia (http://de.wikipedia.org/wiki/Base64#Beispiel) correctly,
as well as it decodes the floats correctly;
https://gitlab.kitware.com/paraview/paraview/-/issues/11987Representation not showing correctly2019-03-05T10:38:10-05:00Kitware RobotRepresentation not showing correctly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11987). Further discussion may take place here.**
---
If you follow the steps in client/server mode, you will be able to hav...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11987). Further discussion may take place here.**
---
If you follow the steps in client/server mode, you will be able to have a rendering view that does not contains any representation (Clip/orientation axis)5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/11986Save Animation Error2019-03-05T10:38:10-05:00Kitware RobotSave Animation Error**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11986). Further discussion may take place here.**
---
When attempting to create an animation in the recently released 3.10.0...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11986). Further discussion may take place here.**
---
When attempting to create an animation in the recently released 3.10.0 64 the following output message is displayed
ERROR: In ..\..\..\..\source\VTK\IO\vtkAVIWriter.cxx, line 172
vtkAVIWriter (000000000B3DDF30): Unable to compress C:\Users\(me)\Documents\test.avi
This was not a problem in the previous release 3.8.1
https://gitlab.kitware.com/paraview/paraview/-/issues/11983Uncheck all in Line Chart View no longer working2019-03-05T10:38:10-05:00Kitware RobotUncheck all in Line Chart View no longer working**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11983). Further discussion may take place here.**
---
The version I use is actually 3.10.0.
In 3.8.1 if you click on the [x] ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11983). Further discussion may take place here.**
---
The version I use is actually 3.10.0.
In 3.8.1 if you click on the [x] in the "Variable" header all variables would be unchecked / checked. With the current version it is necessary to uncheck each variable manually.
It's not a really severe issue but an annoyance as I usually have quite a few variables listed.https://gitlab.kitware.com/paraview/paraview/-/issues/119823.10.0 has a fatal memory leak2019-03-05T10:38:10-05:00Kitware Robot3.10.0 has a fatal memory leak**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11982). Further discussion may take place here.**
---
Kitware knows about this and is actively researching, but I will document ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11982). Further discussion may take place here.**
---
Kitware knows about this and is actively researching, but I will document it here.
This seems to become a larger problem with clusters. However, it can be replicated on one local server.
* Release, Linux, local server.
* Open up a "top" on your linux machine. It is easier if you only show your own processes - use 'u' within top. Set refresh update to 3 seconds (use 'd').
* Open WhippleShield - 32 file version.
* All variables on. Apply.
* Notice paraview memory footprint.
* Turn all variables off. Apply.
* Notice paraview memory footprint. It has not gotten smaller.
* Turn all variables on. Apply.
* Notice paraview memory footprint. It has grown significantly.
* Memory also seems to grow if we animate.