ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2017-12-04T12:46:55-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/15062Change Time toolbar verbiage2017-12-04T12:46:55-05:00Kitware RobotChange Time toolbar verbiage**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15062). Further discussion may take place here.**
---
I have had a customer state that the new time format on the Current Time C...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15062). Further discussion may take place here.**
---
I have had a customer state that the new time format on the Current Time Controls is misleading. I agree. The problem with "of" is that it is one based (i.e., number of time steps in the data), comparing against the current time step that is zero based. We are comparing apples and cantaloupe. Please change the "of" to be "Max".https://gitlab.kitware.com/paraview/paraview/-/issues/15064(Venus) plot over line doesn't correctly reset2017-12-04T12:46:55-05:00Kitware Robot(Venus) plot over line doesn't correctly reset**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15064). Further discussion may take place here.**
---
When re-targeting inputs to plot over line, it doesn't correctly reset. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15064). Further discussion may take place here.**
---
When re-targeting inputs to plot over line, it doesn't correctly reset. Although this sequence sounds strange, it is used all the time by my user. He is setting up a complex set of 2d plots, and trying to reuse the same setup for multiple files. Save/restore state is failing for him.
Linux, 4.2.0, local server, auto apply on (although I bet it doesn't matter.)
* Sources/ line.
* Calculator. (Correct, no input formula.)
* Plot over line. Notice the X and Y extents. Both are 0-1.
* Sources line. Change the X coordinate of point 1 to be -5, point 2 to be 5. We now have a line that is 1
* Right click on the Calculator in the pipeline browser, and "change input". Change it to line 2.
<<Bug>> Notice that the line will shift, as it should, but the X axis doesn't change. Further, the green line appears to go into negative line space. This is probably misrepresenting data.
If you run plot over line from line2, you can see what should be happening - the X axis goes from 0 to 10.
https://gitlab.kitware.com/paraview/paraview/-/issues/15069Color legend marks are crazy.2017-12-04T12:46:55-05:00Kitware RobotColor legend marks are crazy.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15069). Further discussion may take place here.**
---
The color legend marks calculator is crazy. I realize that this is a hard...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15069). Further discussion may take place here.**
---
The color legend marks calculator is crazy. I realize that this is a hard problem, but what we have isn't correct. Here is an example, with two screenshots.
Linux, 4.2.0, local server.
* Load can.exo. Apply.
* Last time step. Color by ACCL.
* The next part is dependent on the size of ParaView - thus, varies. I manually change the color range to be 4000 to 2e8th, and get a minimum and maximum tick mark, and one in the middle. Changing the range to be 4100 to 2e8, I see a minimum and maximum, and 4 in the middle. There is a huge jump here, with font rescaling and everything. It is very disruptive. Please make it transition better.
https://gitlab.kitware.com/paraview/paraview/-/issues/15071Python trace does not record solid color changes2017-12-04T12:46:55-05:00Kitware RobotPython trace does not record solid color changes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15071). Further discussion may take place here.**
---
Steps to reproduce:
- Run ParaView, built-in server
- Tools -> Start T...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15071). Further discussion may take place here.**
---
Steps to reproduce:
- Run ParaView, built-in server
- Tools -> Start Trace
- "any *modified* properties", "Fully trace supplemental objects..." on, "Show trace as it is being generated." on
- Sources -> Sphere
- Change color
- Tools -> Stop Trace
No change in color is recorded.
No color change is recorded.https://gitlab.kitware.com/paraview/paraview/-/issues/15073Python trace: ResetCamera() method generated from Zoom to Data produces calle...2017-12-04T12:46:55-05:00Kitware RobotPython trace: ResetCamera() method generated from Zoom to Data produces called with too many arguments**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15073). Further discussion may take place here.**
---
Steps to reproduce:
- Paraview, built-in server
- Tools -> Start Trace...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15073). Further discussion may take place here.**
---
Steps to reproduce:
- Paraview, built-in server
- Tools -> Start Trace, default options
- Sources -> Sphere
- Click 'Zoom to Data' button
- Tools -> Stop Trace
- Save generated script
- Tools -> Python Shell
- Click Run Script, select saved generated script
An error occurs:
Traceback (most recent call last):
File "<string>", line 26, in <module>
TypeError: __call__() takes exactly 1 argument (7 given)
The offending call is
renderView1.ResetCamera(-0.999689161777, 0.999689161777, -0.999689161777, 0.999689161777, -1.0, 1.0)https://gitlab.kitware.com/paraview/paraview/-/issues/15076Color editor color mapping data opacity control goes crazy2017-12-04T12:46:55-05:00Kitware RobotColor editor color mapping data opacity control goes crazy**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15076). Further discussion may take place here.**
---
The color editor Mapping Data opacity control goes crazy upon update. Thi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15076). Further discussion may take place here.**
---
The color editor Mapping Data opacity control goes crazy upon update. This needs to be fixed.
* Linux, 4.2.0, local server (I found it originally on master, Windows, so I believe it is still broken)
* Open can.exo, all vars on, Apply.
* Settings/ General/ Color/Opacity Map Range Options/ select Clamp and Update Every Timestep.
* Color by ACCL.
* Open the color editor.
* Go forward one timestep.
<<bug>> The Mapping Data Opacity control will have gone crazy. If you rescale to data range it goes back to normal, but then move forward another time step, and the control goes crazy once again.
https://gitlab.kitware.com/paraview/paraview/-/issues/15078Point sprite mode has not effect on OsX2017-12-04T12:46:55-05:00Kitware RobotPoint sprite mode has not effect on OsX**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15078). Further discussion may take place here.**
---
For the Point Sprite plugin, changing the "Point Sprite Mode" value on OsX...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15078). Further discussion may take place here.**
---
For the Point Sprite plugin, changing the "Point Sprite Mode" value on OsX has no effect in 4.2, while it works in 4.1.https://gitlab.kitware.com/paraview/paraview/-/issues/15085vtkPVPythonCatalystPython.so isn't getting installed2017-12-04T12:46:55-05:00Kitware RobotvtkPVPythonCatalystPython.so isn't getting installed**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15085). Further discussion may take place here.**
---
When Catalyst is installed to a specific directory, vtkPVPythonCatalystPyt...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15085). Further discussion may take place here.**
---
When Catalyst is installed to a specific directory, vtkPVPythonCatalystPython.so isn't installed. This is needed when running Catalyst Python code.https://gitlab.kitware.com/paraview/paraview/-/issues/15087Build ParaView on Xeon Phi2017-12-04T12:46:55-05:00Kitware RobotBuild ParaView on Xeon Phi**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15087). Further discussion may take place here.**
---
As per Ken, Build ParaView on Xeon Phi**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15087). Further discussion may take place here.**
---
As per Ken, Build ParaView on Xeon Phihttps://gitlab.kitware.com/paraview/paraview/-/issues/15088Issues Berk found with python syntax highlighting2017-12-04T12:46:55-05:00Kitware RobotIssues Berk found with python syntax highlighting**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15088). Further discussion may take place here.**
---
*Typing a unicode character in a python syntax highlighted field causes a ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15088). Further discussion may take place here.**
---
*Typing a unicode character in a python syntax highlighted field causes a crash.
*Code is not syntax-highlighted until user types in the field.https://gitlab.kitware.com/paraview/paraview/-/issues/15089Add file name and path at bottom of ParaView2017-12-04T12:46:55-05:00Kitware RobotAdd file name and path at bottom of ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15089). Further discussion may take place here.**
---
Please add the dataset name (first dataset name if more than one) and path...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15089). Further discussion may take place here.**
---
Please add the dataset name (first dataset name if more than one) and path to the space to the left of the status bar, i.e., bottom left of the ParaView window. We have users that work on multiple datasets, sometimes at the same time, that superficially look the same. These users need the dataset displayed.https://gitlab.kitware.com/paraview/paraview/-/issues/15090State files load time incorrectly, leading to a crash.2017-12-04T12:46:55-05:00Kitware RobotState files load time incorrectly, leading to a crash.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15090). Further discussion may take place here.**
---
ParaView has an incorrect load of time when loading from state. This lead...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15090). Further discussion may take place here.**
---
ParaView has an incorrect load of time when loading from state. This leads to a crash when a user tries to make any movies. This needs to be fixed ASAP.
* Linux, 4.2.0, local server.
* Start ParaView.
* Open can.exo. Apply.
* File/ Save State. Save as a .pvsm file.
* Quit ParaView. (Reset Session does not show the same issues)
* Start ParaView.
* File/ Load State. Load the file you saved above.
* Notice that the number of timesteps has gone to TBD. Further, if you step forward one step, the counter never goes off of 0.
* File/ Save Animation. Save as .avi.
Crash.https://gitlab.kitware.com/paraview/paraview/-/issues/15091XML Reader causes unnecessary error messages2017-12-04T12:46:55-05:00Kitware RobotXML Reader causes unnecessary error messages**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15091). Further discussion may take place here.**
---
Caused by a VTK update to vtkXMLReader**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15091). Further discussion may take place here.**
---
Caused by a VTK update to vtkXMLReaderhttps://gitlab.kitware.com/paraview/paraview/-/issues/15092Change Point Label Font color to Yellow2017-12-04T12:46:55-05:00Kitware RobotChange Point Label Font color to Yellow**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15092). Further discussion may take place here.**
---
Please change the Point Label Font color to yellow. Currently, it is gray...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15092). Further discussion may take place here.**
---
Please change the Point Label Font color to yellow. Currently, it is gray, which often looks like a shaded white - which is our Solid Color default, or the mid range of our default color table.https://gitlab.kitware.com/paraview/paraview/-/issues/15093Stereo interlace problem2017-12-04T12:46:55-05:00Kitware RobotStereo interlace problem**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15093). Further discussion may take place here.**
---
I have not been able to get PV 4.2.0 to work in stereo interlace mode on m...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15093). Further discussion may take place here.**
---
I have not been able to get PV 4.2.0 to work in stereo interlace mode on my Windows 7 64 bit system. Default mode seems to be red-blue, and that works fine, but I get this error on startup when I specify –stereo-type=Interlaced
ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLCamera.cxx, line 167
vtkOpenGLCamera (000000000B119790): failed after Render 1 OpenGL errors detected
0 : (1282) Invalid operation
It continues to run despite this error, but the view generated is mono, not stereo. Alan Scott verified this on his system.
On my Windows 8 64bit laptop, PV 4.2.0 will not even start with the -stereo option.
PV 4.0.1 starts in interlace mode with no problem on the same system.
https://gitlab.kitware.com/paraview/paraview/-/issues/15094Color editor dialog won't go off screen2017-12-04T12:46:55-05:00Kitware RobotColor editor dialog won't go off screen**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15094). Further discussion may take place here.**
---
We want the Color Map Editor to be dragged mostly off screen. Users do th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15094). Further discussion may take place here.**
---
We want the Color Map Editor to be dragged mostly off screen. Users do this to move dialog boxes out of the way. Here is an example. Weird.
* Linux, 4.2.0, local server.
* Full screen the ParaView program (i.e., don't go to View/ Full Screen).
* can.exo. All vars on. Apply.
* Color by EQPS.
* Open Color Editor.
* Now, grab the Color Map Editor by the top bar (i.e., where it says Color Map Editor), and slide it DOWN. Without releasing it, notice that you can move most of the color editor off the screen. This is good. (Make sure you can't "loose" any dialogs, in an unrecoverable way). Now, set the Color Map Editor dialog down in the middle of ParaView (without docking). Now, try to move the editor off screen. It won't go! This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/15100ColorMapEditor panel is too small by default2017-12-04T12:46:55-05:00Kitware RobotColorMapEditor panel is too small by default**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15100). Further discussion may take place here.**
---
> paraview -dr
> Wavelet, Apply, Color By->RTData and then edit the color...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15100). Further discussion may take place here.**
---
> paraview -dr
> Wavelet, Apply, Color By->RTData and then edit the color map.
The Color Map editor pops up with scroll bar on the bottom hiding part of the transfer function editor, confusing the users.https://gitlab.kitware.com/paraview/paraview/-/issues/15101improve vtkParticlePat h filter2017-12-04T12:46:55-05:00Kitware Robotimprove vtkParticlePat h filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15101). Further discussion may take place here.**
---
particle path filter needs to be updated to support outputting simulation ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15101). Further discussion may take place here.**
---
particle path filter needs to be updated to support outputting simulation time and proper injection time step information.https://gitlab.kitware.com/paraview/paraview/-/issues/15102Something's wrong with Partial array indicators2017-12-04T12:46:55-05:00Kitware RobotSomething's wrong with Partial array indicators**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15102). Further discussion may take place here.**
---
Load the attached vtm file and then inspect the Information panel paying a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15102). Further discussion may take place here.**
---
Load the attached vtm file and then inspect the Information panel paying attention to arrays marked as "partial". When the "Node Sets" tree node is selected, SourceElement* arrays are marked partial when both the array are present on both the child node set blocks!
Something's awry!https://gitlab.kitware.com/paraview/paraview/-/issues/15104catalyst scripts is adding in WriteFrequency output for writers2017-12-04T12:46:55-05:00Kitware Robotcatalyst scripts is adding in WriteFrequency output for writers**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15104). Further discussion may take place here.**
---
A potential fix is at http://review.source.kitware.com/#/c/17864/1
S...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15104). Further discussion may take place here.**
---
A potential fix is at http://review.source.kitware.com/#/c/17864/1
Steps to reproduce:
load the catalyst script generator plugin
load a file
create a catalyst writer for that file and change File Name and Write Frequency
export the script
The writer in the generated script will try to set both FileName and WriteFrequency, e.g.:
parallelImageDataWriter1.FileName = 'filena33me_%t.pvti'
parallelImageDataWriter1.WriteFrequency = 133