ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:38:37-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/11546CTH AMR clip doesn't work2019-03-05T10:38:37-05:00Kitware RobotCTH AMR clip doesn't work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11546). Further discussion may take place here.**
---
* Trunk, Remote server (4), Windows.
* Open Dave's small CTH dataset (spc...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11546). Further discussion may take place here.**
---
* Trunk, Remote server (4), Windows.
* Open Dave's small CTH dataset (spcta_a - Kitware my have this labeled as medium). All variables on, apply.
* Filters/ AMR Dual Clip. Material Volume Fraction - 1, Apply. This has shown three different behaviors - 1) this often just dies a really ugly death, 2) you see a lot of nothing, or 3) nice, beautiful wedges. I will attach a screen shot from one of the wedges.
I have seen the same nutty behavior with clip and CTH AMR data, but am hoping that fixing this will fix all...
Since this makes ParaView unusable for CTH work, I think this bug should be a showstopper for the 3.10 release.https://gitlab.kitware.com/paraview/paraview/-/issues/11545Find data Query Results reports one entry per process2019-03-05T10:38:37-05:00Kitware RobotFind data Query Results reports one entry per process**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11545). Further discussion may take place here.**
---
ParaView remote server - at least 2 pvservers (I am using 4). Windows cli...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11545). Further discussion may take place here.**
---
ParaView remote server - at least 2 pvservers (I am using 4). Windows client, Trunk.
can.exo, all vars on, apply.
Find data, GlobalElementId - is - 100. Run Selection Query.
<<Bug>> Even though there is only one element 100, 4 will show up - one per process. Since I believe it is obvious, it isn't a showstopper. I think it is very important, however - it makes the find data dialog unwieldy for large jobs.https://gitlab.kitware.com/paraview/paraview/-/issues/11544resolution does not go full when remote rendering.2019-03-05T10:38:37-05:00Kitware Robotresolution does not go full when remote rendering.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11544). Further discussion may take place here.**
---
Remote servers (4), Windows client, trunk. (Hardware rendering, but shoul...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11544). Further discussion may take place here.**
---
Remote servers (4), Windows client, trunk. (Hardware rendering, but shouldn't matter)
Edit/ Settings ... Remote Render Threshold - set to 0.
Now, set Interactive Subsample Rate to 12.
OK.
Exit ParaView.
Restart ParaView as above.
Can.exo. Apply.
Now (and I have had troubles repeating this every time, but it happens very often), grab the can with the left mouse button and move it. Release. Don't move the mouse. We stay at lower resolution, and you never see the counter at the bottom. Now, move mouse and click anywhere on the pipeline browser, or a toolbar, or even another window. Full resolution returns.
It would be really nice to be able to turn this new feature off if it becomes problematic...
This must be fixed for the 3.10 release, since it makes ParaView unusable for remote server.https://gitlab.kitware.com/paraview/paraview/-/issues/11543Crash in NetCDF reader for bad settings2018-02-15T05:44:43-05:00Kitware RobotCrash in NetCDF reader for bad settings**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11543). Further discussion may take place here.**
---
Trunk, Windows, local server.
Open sampleGenGrid3.nc. Apply.
Change Out...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11543). Further discussion may take place here.**
---
Trunk, Windows, local server.
Open sampleGenGrid3.nc. Apply.
Change Output Type to Structured. Apply.
Crash.https://gitlab.kitware.com/paraview/paraview/-/issues/11539Python Macro to "Rescale Data to Range"2019-03-05T10:38:37-05:00Kitware RobotPython Macro to "Rescale Data to Range"**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11539). Further discussion may take place here.**
---
Can I get a single Python macro that is equivalent to "Rescale to Data Ran...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11539). Further discussion may take place here.**
---
Can I get a single Python macro that is equivalent to "Rescale to Data Range"? I will provide below an example of how I want to use this macro, but I suppose this feature would be valuable for ANY python script that loads a state file where the scale of some variables changes after the state file is created.
I am doing some testing with Paraview where I'm looking at how the data is distributed across processors. So, I'm loading my data and applying the Process ID Filter. So far, so good.
I'm using PVBATCH to do some of the testing and I'm using a very simple .py file that looks like this:
rom paraview.simple import *
servermanager.LoadState("cth_390.pvsm")
WriteAnimation("./cth_390.png")
I need one more command to get things the way that I want them. The color table is not automatically scaled across the number of processors used in the current batch run - it's scaled across the number of processors I used when I created the state file. If I'm running ParaView interactively, I can simply use the "Rescale to Data Range" button. How do I find the appropriate action when running in batch? I looked at the python that was generated when I do this interactively, and the command is specific to the current run - it's not a generic solution:
a1_ProcessId_PVLookupTable = GetLookupTableForArray( "ProcessId", 1, RGBPoints=[0.0, 0.23000000000000001, 0.29899999999999999, 0.754, 5.0, 0.70599999999999996, 0.016, 0.14999999999999999] )
Render()
I suppose this feature would be valuable for ANY state file where the scale of some variables changes after the state file is created.
https://gitlab.kitware.com/paraview/paraview/-/issues/11537Saving view using "adjust camera" does not save and display the zoom factor2019-03-05T10:38:37-05:00Kitware RobotSaving view using "adjust camera" does not save and display the zoom factor**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11537). Further discussion may take place here.**
---
When saving a view in Paraview 3.8.1 with parallel projection turned on, t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11537). Further discussion may take place here.**
---
When saving a view in Paraview 3.8.1 with parallel projection turned on, the zoom factor is not stored. addtionally, there is no place to even view the zoom factor in the "adjust camera" gui. When zooming in or out a view all the displayed factors stay exactly the same.https://gitlab.kitware.com/paraview/paraview/-/issues/11535File Series Reader does not update extents2019-03-05T10:38:37-05:00Kitware RobotFile Series Reader does not update extents**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11535). Further discussion may take place here.**
---
When using a series reader, the output extent of each of the files in
the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11535). Further discussion may take place here.**
---
When using a series reader, the output extent of each of the files in
the series is the same even if all of the files in the series do not
actually have the same extent. It seems like there is an assumption
made somewhere that all of the images will have the same extent. The steps to
reproduce using the attached archive are:
// Broken
1) Open the BlankedCorrelation image in Paraview and change to a 3D view
2) Open the BestPatch_* images as a series.
3) Click "Next frame"
4) Observe that the second patch is in the same position as the first
(this is incorrect, they are supposed to be in different positions)
// Works properly
5) Delete the BestPatch_* from the pipeline
6) Open BestPatch_0000 and BestPatch_0001 separately.
7) Observe that they are in different positions (as they are supposed to be).
https://gitlab.kitware.com/paraview/paraview/-/issues/11532ParaView crashs when apply a selection to scaled point sprite on Windows.2019-03-05T10:38:37-05:00Kitware RobotParaView crashs when apply a selection to scaled point sprite on Windows.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11532). Further discussion may take place here.**
---
This problem not occured on linux.
1. Load the point sprite plugin
2....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11532). Further discussion may take place here.**
---
This problem not occured on linux.
1. Load the point sprite plugin
2. Make a Wavelet source
3. Set "Representation" to "Point Sprite"
4. Set "Scale by" to "RTData"
5. Set "Point Sprite Mode" to "Texture"
6. Use any selection from Selection Control toolbar
7. Crashhttps://gitlab.kitware.com/paraview/paraview/-/issues/11520Applying CellDataToPointData to UnstructuredGrid data set crashes ParaView 3.9.02019-03-05T10:38:37-05:00Kitware RobotApplying CellDataToPointData to UnstructuredGrid data set crashes ParaView 3.9.0**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11520). Further discussion may take place here.**
---
Load the attached data set.
Apply CellDataToPointData filter.
=> ParaV...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11520). Further discussion may take place here.**
---
Load the attached data set.
Apply CellDataToPointData filter.
=> ParaView 3.9.0 as of Aug 5, 2010 or later will segfault (tested with 32bit and 64bit Release and Debug build on Linux). ParaView 3.8.1 is not affected.
https://gitlab.kitware.com/paraview/paraview/-/issues/11519Selection requires server-side rendering2019-03-05T10:38:37-05:00Kitware RobotSelection requires server-side rendering**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11519). Further discussion may take place here.**
---
Current implementation of surface selection requires server-side rendering...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11519). Further discussion may take place here.**
---
Current implementation of surface selection requires server-side rendering. This is needed for processes ids to be rendered correctly. However, we can overcome this requirement by delivering the process ids to the client. This make it possible to use selection when server-side rendering is not available. https://gitlab.kitware.com/paraview/paraview/-/issues/11516Paraview crashes with segmentation fault when using Select Cells On with Open...2017-12-17T12:42:47-05:00Kitware RobotParaview crashes with segmentation fault when using Select Cells On with Openfoam mesh**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11516). Further discussion may take place here.**
---
Paraview always crashes with segmentation fault when selecting cells in an...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11516). Further discussion may take place here.**
---
Paraview always crashes with segmentation fault when selecting cells in an OpenFOAM mesh.
After clicking Select Cells On and selecting a cell through clicking into the mesh, processor load goes up, after few seconds paraview crashes with segmentation fault.
Using a paraview source (Cylinder) it seems to work fine.
https://gitlab.kitware.com/paraview/paraview/-/issues/11500File Groups have files missing.2019-03-05T10:38:37-05:00Kitware RobotFile Groups have files missing.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11500). Further discussion may take place here.**
---
An incorrect mapping between view and model is creating files in groups to...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11500). Further discussion may take place here.**
---
An incorrect mapping between view and model is creating files in groups to become hidden.https://gitlab.kitware.com/paraview/paraview/-/issues/11488When switching window types (2D -> 3D), all objects visibility are disabled2019-03-05T10:38:37-05:00Kitware RobotWhen switching window types (2D -> 3D), all objects visibility are disabled**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11488). Further discussion may take place here.**
---
If you have an image displayed in a 2D window and then change the window t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11488). Further discussion may take place here.**
---
If you have an image displayed in a 2D window and then change the window type to 3D, the image visibility is disabled. It should continue to display objects that were previously displayed.https://gitlab.kitware.com/paraview/paraview/-/issues/11476vtkFileSeriesWriter only checks the first input file for information (extent,...2017-12-26T14:37:18-05:00Kitware RobotvtkFileSeriesWriter only checks the first input file for information (extent, etc)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11476). Further discussion may take place here.**
---
It seems like vtkFileSeriesWriter only checks the first input file for inf...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11476). Further discussion may take place here.**
---
It seems like vtkFileSeriesWriter only checks the first input file for information (extent, etc).
To demonstrate this, if you open two image files separately, they may be in different locations (different extents). However if you open them both through a series reader, they are both in the same location.https://gitlab.kitware.com/paraview/paraview/-/issues/11454Paraview show nonsymmetrical visualizations for two rotated squares2019-03-05T10:38:37-05:00Kitware RobotParaview show nonsymmetrical visualizations for two rotated squares**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11454). Further discussion may take place here.**
---
Let us consider two vtk files (file1.vtk, file2.vtk which are attached to ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11454). Further discussion may take place here.**
---
Let us consider two vtk files (file1.vtk, file2.vtk which are attached to this message). They show two theoretically the same squares (just rotated). Unfortunately the visualizations are not similar. Why these pictures are not symmetric? (compare file1.png, file2.png which are attached to this message).
I checked that in MayaVI with similar results.
I used VTK_QUAD, VTK_PIXEL, VTK_POLYGON with similar results. It looks like each square is created with two triangle. And these triangles are clearly visible.
I think that for square (the picture should be more symmetric).
https://gitlab.kitware.com/paraview/paraview/-/issues/11453Exodus reader not reading individual files from multifile dataset correctly2019-03-05T10:38:37-05:00Kitware RobotExodus reader not reading individual files from multifile dataset correctly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11453). Further discussion may take place here.**
---
ParaView trunk, Windows, local server
File/ Open. Go to zpinch_1 direc...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11453). Further discussion may take place here.**
---
ParaView trunk, Windows, local server
File/ Open. Go to zpinch_1 directory. You will see that you can open the file set. But, we only want to open one file (for instance zpingh_1.8.2). It can't be done. This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/11438Paraview freezes on splash screen2018-04-28T07:13:52-04:00Kitware RobotParaview freezes on splash screen**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11438). Further discussion may take place here.**
---
When loading Paraview 3.8.1 on Windows 7 Ultimate x64, the program freezes...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11438). Further discussion may take place here.**
---
When loading Paraview 3.8.1 on Windows 7 Ultimate x64, the program freezes on the splash screen. I have to kill it with Task Manager. This wasn't an issue as of yesterday evening. No changes have been made in the setup of the machine; I just came in and booted this morning and Paraview is not working. I have been trying to enable the output window from the command line but I can't find the options; when i run 'paraview.exe --help' the options disappear instantly. If I put in garbage parameters to force paraview to bring up the output window with the help options ('paraview.exe --foo') it shows, but then freezes behind the splash screen and I can't scroll or read anything.https://gitlab.kitware.com/paraview/paraview/-/issues/11428Left mouse behavour on background is wrong2019-03-05T10:38:37-05:00Kitware RobotLeft mouse behavour on background is wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11428). Further discussion may take place here.**
---
When designing the left mouse behavour, try for the following:
Never be...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11428). Further discussion may take place here.**
---
When designing the left mouse behavour, try for the following:
Never be obnoxious. I.e., never do something that will often have to be changed again by the user. With that in mind,
* If a user left clicks on the background, leave the pipeline browser as was (This is a CHANGE to current behavior).
* If a user left clicks on the background, and moves the mouse, leave the pipeline browser as was (This is current behavior.)
* If a user left clicks on any object, and doesn't move mouse, select this object in the pipeline browser. (This is current behavior, after a bug fix http://www.paraview.org/Bug/view.php?id=11427).
* If a user left clicks on an object, and moves the mouse, 3d rotate occurs, objects do not change. (Current behavior).
Please feel free to push back - this is such new behavior that I haven't totally figured out what I want!
https://gitlab.kitware.com/paraview/paraview/-/issues/11427Left mouse behavour is not right2019-03-05T10:38:37-05:00Kitware RobotLeft mouse behavour is not right**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11427). Further discussion may take place here.**
---
ParaView trunk, windows, local server.
Open can.exo. Apply.
Open disk...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11427). Further discussion may take place here.**
---
ParaView trunk, windows, local server.
Open can.exo. Apply.
Open disk_out_ref.exo. Apply.
+X icon.
Now, right click on various parts of the two objects. They select incorrectly in the pipeline browser. Most of the time, even if you select on the can, you get disk_out_ref.exo highlighted. But, if you select towards the top on disk_out_ref, the can is highlighted.
Needs to be fixed for 3.10.https://gitlab.kitware.com/paraview/paraview/-/issues/11417Display/ Transform doesn't auto apply properly2019-03-05T10:38:37-05:00Kitware RobotDisplay/ Transform doesn't auto apply properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11417). Further discussion may take place here.**
---
There are cases where the Display/ Transform doesn't seem to work correctl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11417). Further discussion may take place here.**
---
There are cases where the Display/ Transform doesn't seem to work correctly.
Local server, Windows, Trunk.
Open can.exo. All vars on, apply.
Display tab, Transform.
Change Origin to X == 10. Click in the Y entry box. Nothing happens.
Change Scale to X == 2. Click in the Y entry box. We get two things - scaling, and origin movement.
Origin should change without having to change something else.