ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2017-12-04T12:46:52-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/15211TechPlot VTK ParaView Problems2017-12-04T12:46:52-05:00Kitware RobotTechPlot VTK ParaView Problems**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15211). Further discussion may take place here.**
---
I've attempted to modify these ASCII files that my brain is just mush now....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15211). Further discussion may take place here.**
---
I've attempted to modify these ASCII files that my brain is just mush now. Either ParaView doesn't work well with Mac OS X or Paraview has some serious issues.
TechPlot doesn't read in. Then VTK crashes. I would appreciate a second pair of eyes to tell me what is wrong with my files. It's a simple, single element example. I'll have more of course but it doesn't seem to like even a single element FEA ASCII file.
I've attached several modified ASCII .dat files and .vtkhttps://gitlab.kitware.com/paraview/paraview/-/issues/15207Bug: Wrong selection of nodes on quadratic mesh2017-12-04T12:46:52-05:00Kitware RobotBug: Wrong selection of nodes on quadratic mesh**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15207). Further discussion may take place here.**
---
Attached test_selection_on_nodes_0_0.vtu file contains quaratic mesh, sele...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15207). Further discussion may take place here.**
---
Attached test_selection_on_nodes_0_0.vtu file contains quaratic mesh, selection of the nodes on this mesh is wrong.
To test it click on "select points on" and draw a rectangle around some nodes on a cylindrical face..
The selected nodes are not those wanted, but are scattered in the mesh.https://gitlab.kitware.com/paraview/paraview/-/issues/15199EnSightReader: Change input file2017-12-04T12:46:52-05:00Kitware RobotEnSightReader: Change input file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15199). Further discussion may take place here.**
---
Subject: [Paraview] EnSightReader: Change input file
--------------------...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15199). Further discussion may take place here.**
---
Subject: [Paraview] EnSightReader: Change input file
------------------------
From: Ian Krukow <i.krukow@tu-braunschweig.de>
Date: Tue, Nov 11, 2014 at 8:39 AM
To: ParaView <paraview@paraview.org>
Hi all,
I want to apply the same pipeline to a series of Ensight data files in order to save extractions in a different format. For the first file, this works fine. For the second file, I thought I could change the input file by changing the CaseFileName attribute:
reader.CaseFileName = nextfile
But when I run
reader.UpdatePipeline()
I get a segmentation fault. This depends neither on the file, nor on the pipeline following.
I tried a workaround by building up a new pipeline for each file. It works, and as I have only two files by now, it is ok to do that, but for more files, memory usage would explode. Therefore, my question is: Is it possible only to change the input file of the EnSightReader, while keeping the pipeline?
Kind regards
Ian
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
----------
From: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Date: Fri, Nov 14, 2014 at 10:39 PM
To: Ian Krukow <i.krukow@tu-braunschweig.de>
Cc: ParaView <paraview@paraview.org>
Ability to change filenames depends on specific reader
implementations. I am not entire familiar with the internal
implementation, but if you have a couple of sample datasets/script to
reproduce the segfault, I can check if its a minor fix to the reader
to enable this or if it just can't support it.
Either case, you should be able to call Delete(reader) to delete old
reader once you're done with it to avoid memory bloat.
Utkarsh
----------
From: Ian Krukow <i.krukow@tu-braunschweig.de>
Date: Tue, Nov 18, 2014 at 5:20 AM
To: Utkarsh Ayachit <utkarsh.ayachit@kitware.com>
Ok, the problem obviously does depend on the input files to a certain degree. I use TAU as a flow solver (from the DLR, Germany), and it gives me two solution files, one for the fluid solution, one for the surface data. The problem with the EnSightReader occurs, when I try to switch from one category to the other (no matter, which direction). However, there is no problem loading another file of the same category, even with another geometry.
I attach two solution file sets, fluid and surface, with a short pvpython script to reproduce the error (sorry, that they are not smaller, but I do not create any grids of my own).
The behaviour is the same with ParaView versions 3.14.1 and 4.2.0.
Kind regards
Ianhttps://gitlab.kitware.com/paraview/paraview/-/issues/15198Allow (legacy) Xdmf writer to write all time steps.2017-12-04T12:46:53-05:00Kitware RobotAllow (legacy) Xdmf writer to write all time steps.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15198). Further discussion may take place here.**
---
The current vtkXmdfWriter proxy does not expose the "WriteAllTimeSteps" pr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15198). Further discussion may take place here.**
---
The current vtkXmdfWriter proxy does not expose the "WriteAllTimeSteps" property that would optionally allow to export all the time steps of the input data to the Xdmf file.https://gitlab.kitware.com/paraview/paraview/-/issues/15197Cannot record tests rrom ParaView after updates to QtTesting2017-12-04T12:46:53-05:00Kitware RobotCannot record tests rrom ParaView after updates to QtTesting**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15197). Further discussion may take place here.**
---
Trying to record a test from Tools menu, raises the following error:
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15197). Further discussion may take place here.**
---
Trying to record a test from Tools menu, raises the following error:
No acive windows has been found
https://gitlab.kitware.com/paraview/paraview/-/issues/15193Surface representation doesn't respect blanked cells in a vtkStructuredGrid2017-12-04T12:46:53-05:00Kitware RobotSurface representation doesn't respect blanked cells in a vtkStructuredGrid**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15193). Further discussion may take place here.**
---
Surface representation doesn't respect blanked cells in a vtkStructuredGri...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15193). Further discussion may take place here.**
---
Surface representation doesn't respect blanked cells in a vtkStructuredGrid. It simply shows the outer faces, rather than the outer faces for non-blanked cells.https://gitlab.kitware.com/paraview/paraview/-/issues/15192Tear away sections in Properties Panel2017-12-04T12:46:53-05:00Kitware RobotTear away sections in Properties Panel**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15192). Further discussion may take place here.**
---
Please allow a user to tear off sub sections of the Properties Panel. Not ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15192). Further discussion may take place here.**
---
Please allow a user to tear off sub sections of the Properties Panel. Not sure how, but allow the user to restore the setup of the Properties Panel.https://gitlab.kitware.com/paraview/paraview/-/issues/15190Add a deselect button2017-12-04T12:46:53-05:00Kitware RobotAdd a deselect button**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15190). Further discussion may take place here.**
---
When a user is zoomed in close, and selects a cell or point, there is no w...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15190). Further discussion may take place here.**
---
When a user is zoomed in close, and selects a cell or point, there is no way to unselect without zooming out. This is obnoxious. Please add an icon on the toolbar, looking like Select Cells On, without the green triangle.https://gitlab.kitware.com/paraview/paraview/-/issues/15189Drag and drop in the pipeline browser.2017-12-04T12:46:53-05:00Kitware RobotDrag and drop in the pipeline browser.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15189). Further discussion may take place here.**
---
I had a user suggest/request that drag and drop be implemented in the pipe...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15189). Further discussion may take place here.**
---
I had a user suggest/request that drag and drop be implemented in the pipeline browser. This would allow inputs to filters to be reorganized with the mouse.
Low priority.https://gitlab.kitware.com/paraview/paraview/-/issues/15188Add a cylinder as a clip type2017-12-04T12:46:53-05:00Kitware RobotAdd a cylinder as a clip type**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15188). Further discussion may take place here.**
---
Please add a cylinder as a clip type. This would be applicable to the cli...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15188). Further discussion may take place here.**
---
Please add a cylinder as a clip type. This would be applicable to the clip filter.https://gitlab.kitware.com/paraview/paraview/-/issues/15184Crash when using Rescale to Visible Data Range2017-12-04T12:46:53-05:00Kitware RobotCrash when using Rescale to Visible Data Range**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15184). Further discussion may take place here.**
---
Steps to reproduce:
- run paraview/local server
- Sources -> Sphere
-...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15184). Further discussion may take place here.**
---
Steps to reproduce:
- run paraview/local server
- Sources -> Sphere
- Color by Normals
- Click "Rescale to Visible Data Range"
- Crashhttps://gitlab.kitware.com/paraview/paraview/-/issues/15183Imp: Add "Use Cell Centers" option in the Glyph filter2017-12-04T12:46:53-05:00Kitware RobotImp: Add "Use Cell Centers" option in the Glyph filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15183). Further discussion may take place here.**
---
“Auto convert properties” allows to apply filters which requires node fiel...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15183). Further discussion may take place here.**
---
“Auto convert properties” allows to apply filters which requires node field on a cell field, auto applying the filter “cell data to point data”. However, this filter computes mean values on the nodes. The resulting field data is an approximation of the initial field, with different min and max values. In order to keep the initial values, we must use the filter “cell centers”. This can be done for the filter glyph, but not for the filter contour for which the result of “cell centers” cannot be used as an input. That’s why we need to be able to set to use “cell centers” when the result can be used for a filter but still use “cell data to point data” otherwise, at least for the Glyph filter.https://gitlab.kitware.com/paraview/paraview/-/issues/15181ExtractBlock filter is broken in ParaViewWeb2017-12-04T12:46:53-05:00Kitware RobotExtractBlock filter is broken in ParaViewWeb**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15181). Further discussion may take place here.**
---
You have to guess the block ids in order to add blocks to extract. We nee...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15181). Further discussion may take place here.**
---
You have to guess the block ids in order to add blocks to extract. We need better ui which allows to select the blocks from a list, like in the ParaView desktop ui.https://gitlab.kitware.com/paraview/paraview/-/issues/15180Default proxy list for paraviewweb includes typo in filter name.2017-12-04T12:46:53-05:00Kitware RobotDefault proxy list for paraviewweb includes typo in filter name.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15180). Further discussion may take place here.**
---
This bug causes the Cell Data To Point Data filter not to work properly in...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15180). Further discussion may take place here.**
---
This bug causes the Cell Data To Point Data filter not to work properly in ParaViewWeb.https://gitlab.kitware.com/paraview/paraview/-/issues/15173Imp: Add UI control to activate/deactivate 3D stereo and to select the stereo...2017-12-04T12:46:53-05:00Kitware RobotImp: Add UI control to activate/deactivate 3D stereo and to select the stereo mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15173). Further discussion may take place here.**
---
Currently, 3D view can be changed to stereo mode only at ParaView start-up...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15173). Further discussion may take place here.**
---
Currently, 3D view can be changed to stereo mode only at ParaView start-up with the following options:
--stereo:--stereo-type=SplitViewportHorizontal
or by some python code:
GetRenderView().StereoRender=1
GetRenderView().StereoType="SplitViewportHorizontal"
To be more user friendly, we need an icon in the top of 3D views to be able to activate/deactivate 3D stereo and to select which stereo mode to use in a drop-down list.https://gitlab.kitware.com/paraview/paraview/-/issues/15172Imp: Generating annotations corresponding to discrete colours2017-12-04T12:46:53-05:00Kitware RobotImp: Generating annotations corresponding to discrete colours**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15172). Further discussion may take place here.**
---
When we plot with discrete colours (5 or 6 colours in order to see the dis...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15172). Further discussion may take place here.**
---
When we plot with discrete colours (5 or 6 colours in order to see the distribution of values better), we want to know the range corresponding to each colour.
In Paraview, what is displayed are rounded values and not the bounds corresponding to each colour. Therefore, it is impossible to interpret the visualization.
For instance:
- Load the attached file TempField_4_0.vtu
- Display the scalar bar
- Edit the bar in order to display 6 discrete colours
=> The labels are : 0, 20, 40, 60, 75
Furthermore, if we change the number of labels to 7, we still have only 5 labels displayed. We should have labels: 0, 12.5, 25, 37.5, 50, 62.5, 75.https://gitlab.kitware.com/paraview/paraview/-/issues/15170Imp: Be able to drag and drop the legend of plot charts2017-12-04T12:46:53-05:00Kitware RobotImp: Be able to drag and drop the legend of plot charts**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15170). Further discussion may take place here.**
---
In a 3D view, we can drag and drop the colour legend to change its positio...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15170). Further discussion may take place here.**
---
In a 3D view, we can drag and drop the colour legend to change its position.
We want to be able to do the same for the legend of plot charts. https://gitlab.kitware.com/paraview/paraview/-/issues/15168Add ability to save/ restore ParaView window and tool size and placement2017-12-04T12:46:53-05:00Kitware RobotAdd ability to save/ restore ParaView window and tool size and placement**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15168). Further discussion may take place here.**
---
Please add the ability for a user to save his/her current window size and ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15168). Further discussion may take place here.**
---
Please add the ability for a user to save his/her current window size and visibility, position and size of toolbars. This is needed for users that want to restore the size of the 3d window between sessions, so that they can make the same size screenshots.https://gitlab.kitware.com/paraview/paraview/-/issues/15167Spreadsheet view and multiple blocks2017-12-04T12:46:53-05:00Kitware RobotSpreadsheet view and multiple blocks**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15167). Further discussion may take place here.**
---
Please change Spreadsheet View to include all blocks, not just the first b...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15167). Further discussion may take place here.**
---
Please change Spreadsheet View to include all blocks, not just the first block. This is confusing, and awkward. Here is a writeup from a user:
I guess I don't understand why showing more than 1 block at a time is a problem.
Suppose I am looking at shear strain in the Belt end region. I probably want to look at multiple components (blocks). I don't know why I shouldn't be allowed to select 2 or 3 or 4 blocks to be visible in the spreadsheet. I want to pick on elements and see their property values in the spreadsheet.
Yes, I can merge blocks beforehand but that is very limiting - once I merge blocks, I lose the ability to conveniently turn components on and off using the Multi-block inspector. I might have to extract 3 blocks to make a merged set, then examine that, then decide I want to look at adjoining elements in an adjoining block and have to repeat the whole thing over again.
As far as partial arrays, what is the difference between merging blocks and displaying in the spreadsheet and displaying all the individual blocks in the spreadsheet? I can't count the times I've had to merge all blocks, sort spreadsheet to get some max/min values, then delete the merged blocks to do some selection by blocks and proceed with other operations. It seems like an inefficiency to constantly have to merge blocks to see stuff in the spreadsheet. What advantage is there to only showing 1 block at a time?
Dennis
https://gitlab.kitware.com/paraview/paraview/-/issues/15166QtTesting switch to master2017-12-04T12:46:53-05:00Kitware RobotQtTesting switch to master**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15166). Further discussion may take place here.**
---
Paraview QtTesting submodule has been on a separate branch from master for...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15166). Further discussion may take place here.**
---
Paraview QtTesting submodule has been on a separate branch from master for a while because some changes in QtTesting master broke many paraview's UI tests. This needs to be resolved the sooner the better.https://gitlab.kitware.com/paraview/paraview/-/issues/15165rename the vtkADIOSReader in readers.xml to be consistent with vtkADIOSWriter2017-12-04T12:46:53-05:00Kitware Robotrename the vtkADIOSReader in readers.xml to be consistent with vtkADIOSWriter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15165). Further discussion may take place here.**
---
In Python the instantiation method for the vtkADIOSWriter is ADIOSWriter()...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15165). Further discussion may take place here.**
---
In Python the instantiation method for the vtkADIOSWriter is ADIOSWriter() but for the vtkADIOSReader it is VTKADIOSReader. Change it to ADIOSReader() to be consistent.https://gitlab.kitware.com/paraview/paraview/-/issues/15161"Default Time Step" setting not working.2017-12-04T12:46:53-05:00Kitware Robot"Default Time Step" setting not working.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15161). Further discussion may take place here.**
---
* From Settings | General page, change the "Default Time Step" to "Go to l...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15161). Further discussion may take place here.**
---
* From Settings | General page, change the "Default Time Step" to "Go to last timestep". Hit Ok.
* Open can.ex2
* The current timestep should have been the last one, it's not. That's a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/15159Save Data doesn't have option to follow selection2017-12-04T12:46:53-05:00Kitware RobotSave Data doesn't have option to follow selection**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15159). Further discussion may take place here.**
---
We should add the ability to only put out what shows in the spreadsheet vi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15159). Further discussion may take place here.**
---
We should add the ability to only put out what shows in the spreadsheet view.
* Linux, master, local server.
* Open can.exo. Apply.
* Split horizontal, spreadsheet view.
* In the 3d window, select a cell.
* In the spreadsheet view, only show selected cells.
Feature - there should be a way, somehow, to only Save Data that which is in the spreadsheet view. Maybe make it optional in the Save Data dialog? After all, users may not be aware that this is just the output of the filter - some (including me just a few minutes ago) may think that they want to save what is in the spreadsheet view, not everything.https://gitlab.kitware.com/paraview/paraview/-/issues/15157Some Qt event player classes are missing Q_Object declaration2017-12-04T12:46:53-05:00Kitware RobotSome Qt event player classes are missing Q_Object declaration**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15157). Further discussion may take place here.**
---
A few of the Qt event players are missing Q_Object macro so that they did ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15157). Further discussion may take place here.**
---
A few of the Qt event players are missing Q_Object macro so that they did not have qt meta_object (moc_<class> objects) created. This breaks some Qt UI testing scripts with the changes in QtTesting repo because those changes use the class name of the event_player meta_objects when registering them with testing utility. The end result of this mis-match is that these paraview event players won't register with the testing utility, which leads to some scripts fail due to unhandled events.https://gitlab.kitware.com/paraview/paraview/-/issues/15156Save/restore color map is crazy2017-12-04T12:46:54-05:00Kitware RobotSave/restore color map is crazy**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15156). Further discussion may take place here.**
---
Save/ restore color map is crazy/nuts/broken. Replicate as follows:
* ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15156). Further discussion may take place here.**
---
Save/ restore color map is crazy/nuts/broken. Replicate as follows:
* Master, Linux, local server.
* disk_out_ref.exo. All vars on. Apply. Color by Temp.
* Edit Color Map.
* Change the middle point of the current color map to be yellow (double click on the point).
* Save to Preset. Highlight this preset (it may already be highlighted), and Export. Name this color map Fred. Now, remove this preset (in the Preset Color Scalars dialog).
* Now, import.
Bug - Two new presets will be read into the table of presets! Further, the first will be called Fred (correctly), and the second will be named Diverging. These are bugs.
https://gitlab.kitware.com/paraview/paraview/-/issues/15155Temporal interpolator misses first time step.2017-12-04T12:46:54-05:00Kitware RobotTemporal interpolator misses first time step.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15155). Further discussion may take place here.**
---
Linux, master, local server.
can.exo, all vars on, apply.
View/ Annimati...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15155). Further discussion may take place here.**
---
Linux, master, local server.
can.exo, all vars on, apply.
View/ Annimation view.
Change Mode to Sequence. No. Frames == 100.
Temporal Interpolator. Apply.
Now, move forward one frame. Can disappears! This is a bug.
https://gitlab.kitware.com/paraview/paraview/-/issues/15150vtkKdTree::GenerateRepresentationWholeSpace does 1 << -12017-12-04T12:46:54-05:00Kitware RobotvtkKdTree::GenerateRepresentationWholeSpace does 1 << -1**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15150). Further discussion may take place here.**
---
From: Sean McBride
Date: Fri, Nov 21, 2014 at 11:46 AM
Subject: [vtk-dev...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15150). Further discussion may take place here.**
---
From: Sean McBride
Date: Fri, Nov 21, 2014 at 11:46 AM
Subject: [vtk-developers] Need help with a few clang analyzer warnings
To: vtk-developers@vtk.org
Occasionally, I try to fix some of the hundreds of clang static
analyzer warnings in VTK. Some are easy, some are false positives,
and some are real problems that I don't know how to fix.
file: Common/DataModel/vtkKdTree.cxx
line: 3188
method: vtkKdTree::GenerateRepresentationWholeSpace
problem: the first time through the 'for' loop always does "1 << -1".
You can't left shift by a negative count.
https://gitlab.kitware.com/paraview/paraview/-/issues/15148update writer factory to ignore writers that don't work without MPI for vtkAD...2017-12-04T12:46:54-05:00Kitware Robotupdate writer factory to ignore writers that don't work without MPI for vtkADIOSWriter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15148). Further discussion may take place here.**
---
The vtkADIOS{Reader,Writer} require MPI so adding in mpi_required to their...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15148). Further discussion may take place here.**
---
The vtkADIOS{Reader,Writer} require MPI so adding in mpi_required to their XML proxy definitions. Also, adding in a check in vtkSMWriterFactory if the writer requires MPI and it's not initialized on the session that is doing the writing.https://gitlab.kitware.com/paraview/paraview/-/issues/15146Imp: Be able to select points in python: in simple.py, create SelectPoints li...2017-12-04T12:46:54-05:00Kitware RobotImp: Be able to select points in python: in simple.py, create SelectPoints like SelectCells and refactor the code**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15146). Further discussion may take place here.**
---
To be able to make some selections in Python, there is already a SelectCel...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15146). Further discussion may take place here.**
---
To be able to make some selections in Python, there is already a SelectCells() function defined in simple.py.
It would be useful to have the same function for points. https://gitlab.kitware.com/paraview/paraview/-/issues/15145Settings/Load Last TimeStep ignored for EXODUS multi-block set2017-12-04T12:46:54-05:00Kitware RobotSettings/Load Last TimeStep ignored for EXODUS multi-block set**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15145). Further discussion may take place here.**
---
Settings saved as Goto Last Timestep on Load
Load bake.e example EXODUS...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15145). Further discussion may take place here.**
---
Settings saved as Goto Last Timestep on Load
Load bake.e example EXODUS file
File stays at initial timestep.
Later timesteps are available and can manually step to last timestephttps://gitlab.kitware.com/paraview/paraview/-/issues/15144Imp: In the color bar, be able to deactivate sub-tick marks2017-12-04T12:46:54-05:00Kitware RobotImp: In the color bar, be able to deactivate sub-tick marks**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15144). Further discussion may take place here.**
---
In the colour bar properties, one can deactivate all ticks, but it would b...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15144). Further discussion may take place here.**
---
In the colour bar properties, one can deactivate all ticks, but it would be useful to deactivate only the sub-tick marks.https://gitlab.kitware.com/paraview/paraview/-/issues/15143Color legend disappears2017-12-04T12:46:54-05:00Kitware RobotColor legend disappears**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15143). Further discussion may take place here.**
---
The color legend disappears. Here is how to repeatably replicate this bug...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15143). Further discussion may take place here.**
---
The color legend disappears. Here is how to repeatably replicate this bug.
Linux, 4.2.0, remote server (8 pvservers).
Sources/ Cylinder. Apply.
Color by Normals. Color legend appears (as it should)
Color by TCoord. Color legend remains visible (as it should).
Color by Normals. Color legend disappears. This is a bug.
This must be fixed for 4.3https://gitlab.kitware.com/paraview/paraview/-/issues/15141Imp: Improve the 3D view manipulation for long objects2017-12-04T12:46:54-05:00Kitware RobotImp: Improve the 3D view manipulation for long objects**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15141). Further discussion may take place here.**
---
For objects which have a dimension much bigger than the others, the view m...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15141). Further discussion may take place here.**
---
For objects which have a dimension much bigger than the others, the view manipulation is not easy, because the rotation is too fast.
As an example, create a cylinder source with the properties:
- Resolution: 36
- Height: 200
- Radius: 0.5
and make several zooms and rotations to see the problems.https://gitlab.kitware.com/paraview/paraview/-/issues/15137Cell ID displays are junk in vtu files2017-12-04T12:46:54-05:00Kitware RobotCell ID displays are junk in vtu files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15137). Further discussion may take place here.**
---
Windows, 4.2, local server.
* Open attached .vtu file. All vars on. A...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15137). Further discussion may take place here.**
---
Windows, 4.2, local server.
* Open attached .vtu file. All vars on. Apply.
* Z-
* Select a cell.
* Find data. Cell Labels. Id.
Bug - the cell labels are crazy size numbers, such as 1e-323. This is an important bug, and needs to be fixed.https://gitlab.kitware.com/paraview/paraview/-/issues/15132OGG/Theora movie writer not working2017-12-04T12:46:54-05:00Kitware RobotOGG/Theora movie writer not working**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15132). Further discussion may take place here.**
---
This was tried on a linux build of ParaView: when saving an animation as ....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15132). Further discussion may take place here.**
---
This was tried on a linux build of ParaView: when saving an animation as .ogv, we get the following error:
ERROR: In /home/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/ParaViewCore/Animation/vtkSMAnimationSceneImageWriter.cxx, line 385
pqAnimationSceneImageWriter (0x89c4ab0): Unknown extension .ogv
https://gitlab.kitware.com/paraview/paraview/-/issues/15130Fix sorting logic in vtkPVDataSetAttributesInformation2017-12-04T12:46:54-05:00Kitware RobotFix sorting logic in vtkPVDataSetAttributesInformation**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15130). Further discussion may take place here.**
---
vtkPVDataSetAttributesInformation is using case-insenstive sorting. Not en...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15130). Further discussion may take place here.**
---
vtkPVDataSetAttributesInformation is using case-insenstive sorting. Not entirely sure why. We should not ignore case.
https://gitlab.kitware.com/paraview/paraview/-/issues/15129Slow ADIOS write performance2017-12-04T12:46:54-05:00Kitware RobotSlow ADIOS write performance**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15129). Further discussion may take place here.**
---
ADIOS write performance doe snot scale as expected.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15129). Further discussion may take place here.**
---
ADIOS write performance doe snot scale as expected.https://gitlab.kitware.com/paraview/paraview/-/issues/15128Avoid creating vtkWin32OutputWindow on ParaView server processes2017-12-04T12:46:54-05:00Kitware RobotAvoid creating vtkWin32OutputWindow on ParaView server processes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15128). Further discussion may take place here.**
---
vtkWin32OutputWindow on Windows on the server processes is fairly useless ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15128). Further discussion may take place here.**
---
vtkWin32OutputWindow on Windows on the server processes is fairly useless since it's not intractable. It also deteriorates the user experience. https://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/15126Misc separated properties panel issues.2017-12-04T12:46:54-05:00Kitware RobotMisc separated properties panel issues.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15126). Further discussion may take place here.**
---
When using separate panels for Display properties (as described here [1]),...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15126). Further discussion may take place here.**
---
When using separate panels for Display properties (as described here [1]), we had a few issues:
* Save/Restore properties buttons don't show up properly.
* The Display properties are not updated when switching between multiple sources.
[1] http://www.kitware.com/blog/home/post/673https://gitlab.kitware.com/paraview/paraview/-/issues/15125Python Calculator is missing a lot of information2017-12-04T12:46:54-05:00Kitware RobotPython Calculator is missing a lot of information**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15125). Further discussion may take place here.**
---
With the changes of moving some of the functionality from ParaView to VTK ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15125). Further discussion may take place here.**
---
With the changes of moving some of the functionality from ParaView to VTK for the Python calculator filter, some of the functionality was lost. An incomplete list of the functions at http://www.itk.org/Wiki/ParaView/Users_Guide/Python_Calculator that are no longer available are divide() and reciprocal(). From what I can tell there is no way to divide an array with more than one component by an array with just one component. Additionally, single quotes can't be in the expression e.g. "inputs[0].PointData['RTData']" doesn't work. Attached is a ParaView Python script that demonstrates some of the problems. I think this needs to be fixed before PV 4.3 is released.
https://gitlab.kitware.com/paraview/paraview/-/issues/15124Gaussian cube warning and volume rendering not working2017-12-04T12:46:54-05:00Kitware RobotGaussian cube warning and volume rendering not working**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15124). Further discussion may take place here.**
---
I have a set of Gaussian cube files that each produce the following wa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15124). Further discussion may take place here.**
---
I have a set of Gaussian cube files that each produce the following warning after loading the file and pressing apply in the properties window.
After selecting "Volume" I get the warning again and no data is rendered. These cube files were generated with the qube CLI tool in Avogadro2. The source is a available in the current head of the avoagdrolibs project on github.
https://github.com/OpenChemistry/avogadrolibs/commits/master
I have uploaded two cube files that produce the warning.
-----------------------------------------------------
Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Rendering/Core/vtkRenderer.cxx, line 1030
vtkOpenGLRenderer (0x7fa4843b3b20): Resetting view-up since view plane normal is parallel
Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release-Python27/paraview/src/paraview/VTK/Rendering/Core/vtkRenderer.cxx, line 1030
vtkOpenGLRenderer (0x7fa4843b3b20): Resetting view-up since view plane normal is parallel
--------------------------------------------
5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15122Python View is not updated in the PythonView test in nightly binaries2017-12-04T12:46:54-05:00Kitware RobotPython View is not updated in the PythonView test in nightly binaries**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15122). Further discussion may take place here.**
---
CDash test:
http://open.cdash.org/testDetails.php?test=293546215&build=...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15122). Further discussion may take place here.**
---
CDash test:
http://open.cdash.org/testDetails.php?test=293546215&build=3568153
Doing the steps manually works, but when running the XML, the view doesn't redraw until something causes a rerender (but not just an expose event, but changing the Python script, closing another view).https://gitlab.kitware.com/paraview/paraview/-/issues/15117Warn when volume rendering2017-12-04T12:46:54-05:00Kitware RobotWarn when volume rendering**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15117). Further discussion may take place here.**
---
Volume rendering can take a very long time to render, and it is easy to mi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15117). Further discussion may take place here.**
---
Volume rendering can take a very long time to render, and it is easy to mis-select volume rendering when changing representation. Please add an optional (settings selectable), default on, warning that you are going to volume render when volume is selected.https://gitlab.kitware.com/paraview/paraview/-/issues/15116Trace recorder misses changing color presets2017-12-04T12:46:54-05:00Kitware RobotTrace recorder misses changing color presets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15116). Further discussion may take place here.**
---
The trace recorder misses changing color presets. Here is how to replicat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15116). Further discussion may take place here.**
---
The trace recorder misses changing color presets. Here is how to replicate:
* Linux, local server, Master.
* Start trace. Fully trace supplemental proxies on. OK.
* can.exo. All vars on. Apply.
* Color by ACCL.
* Color Editor. Select preset. Select Cold and Hot. Close.
* Stop trace. Save as macro (I used the name test). Close the script editor.
* Reset session.
* Run your macro.
<<bug>> Color table (i.e., Preset) will be wrong.
This is impacting one of my users.
https://gitlab.kitware.com/paraview/paraview/-/issues/15114Color table export fails Opacity2017-12-04T12:46:54-05:00Kitware RobotColor table export fails Opacity**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15114). Further discussion may take place here.**
---
The color table export/import code fails with regards to opacity.
* M...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15114). Further discussion may take place here.**
---
The color table export/import code fails with regards to opacity.
* Master, Linux, local server.
* can.exo. All vars on. Apply.
* Color by Accl.
* Color map editor. (default color map, by the way).
* Click on the middle of the three buttons on the horizontal Mapping Data section. Change the color to yellow. Then, click in the middle of the ramp above, creating another point. Drag this point down, near opacity 0. Congratulations - you have created a unique, ugly color map.
* Save to Preset. (This is right below Choose Preset). Change new preset to deleteMe.
* Export this to a file, I chose the name fileDeleteMe.
* Now, remove preset deleteMe.
* Reset Session.
* can.exo. All vars on. Apply.
* Color by Accl.
* Choose Preset. Import. Import fileDeleteMe. Select preset deleteMe.
<<Bug - the Opacity point you created above is not present.>>
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/15109vtkCompleteArrays not handling situation with only points and not cells2017-12-04T12:46:55-05:00Kitware RobotvtkCompleteArrays not handling situation with only points and not cells**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15109). Further discussion may take place here.**
---
If there are points but no cells and points are only on process 0 then vtk...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15109). Further discussion may take place here.**
---
If there are points but no cells and points are only on process 0 then vtkCompleteArrays gets rid of all point data arrays.
I'm also making it more efficient where process 0 only has to get the point data and cell data arrays information from one other process.https://gitlab.kitware.com/paraview/paraview/-/issues/15107catalyst rendering edition busted2017-12-04T12:46:55-05:00Kitware Robotcatalyst rendering edition busted**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15107). Further discussion may take place here.**
---
rendering edition became broken due to changes to VTK/Rendering/{Core,OpenGL}**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15107). Further discussion may take place here.**
---
rendering edition became broken due to changes to VTK/Rendering/{Core,OpenGL}https://gitlab.kitware.com/paraview/paraview/-/issues/15106Update HDF5 version in ParaView superbuild2017-12-04T12:46:55-05:00Kitware RobotUpdate HDF5 version in ParaView superbuild**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15106). Further discussion may take place here.**
---
Update HDF5 version in ParaView superbuild. Current version is too old.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15106). Further discussion may take place here.**
---
Update HDF5 version in ParaView superbuild. Current version is too old.https://gitlab.kitware.com/paraview/paraview/-/issues/15105vtkCPAdaptorAPI::CoProcessorInitialize hardcodes input name to 'input'2017-12-04T12:46:55-05:00Kitware RobotvtkCPAdaptorAPI::CoProcessorInitialize hardcodes input name to 'input'**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15105). Further discussion may take place here.**
---
vtkCPAdaptorAPI::CoProcessorInitialize which is called from
vtkCPPythonAd...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15105). Further discussion may take place here.**
---
vtkCPAdaptorAPI::CoProcessorInitialize which is called from
vtkCPPythonAdaptorAPI::CoProcessorInitialize
hardcodes the input name to 'input' instead of using what is defined in the Python coprocessing script.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 = 133https://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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/15060(Venus) TemporalShiftScale doesn't update 2d correctly2017-12-04T12:46:55-05:00Kitware Robot(Venus) TemporalShiftScale doesn't update 2d correctly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15060). Further discussion may take place here.**
---
Not sure where the fault is here, I can only give you the end bug.
* Li...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15060). Further discussion may take place here.**
---
Not sure where the fault is here, I can only give you the end bug.
* Linux, 4.2.0, local server.
The goal here is to be able to change time units in a 2d plot to something reasonable. User has time that is in 1e-13 seconds, wants to change to 1e-4 nanoseconds.
* Open can.exo. All variables on. Apply.
* Last time step.
* Temporal Shift Scale filter. Apply.
* Plot over line filter. Change Chart Title to "Time = ${TIME} Milliseconds"
* Now, click on Temporal Shift Scale filter. Change scale to 1000. Apply.
<<Bug>> - the time in the title of the 2d plot didn't change! You can make it change by moving forward/ back in time.https://gitlab.kitware.com/paraview/paraview/-/issues/15059Time in 2d plots comments missing2017-12-04T12:46:56-05:00Kitware RobotTime in 2d plots comments missing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15059). Further discussion may take place here.**
---
There use to be a comment in the View Settings, saying how to place time i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15059). Further discussion may take place here.**
---
There use to be a comment in the View Settings, saying how to place time in the chart title. It has gone missing in the Chart Title's new location on the Properties tab. Please restore it.
It use to say: "Use ${TIME} to display current time."
https://gitlab.kitware.com/paraview/paraview/-/issues/15058(Venus) Log 2d plots go too high2017-12-04T12:46:56-05:00Kitware Robot(Venus) Log 2d plots go too high**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15058). Further discussion may take place here.**
---
PV 4.2.0, Linux, local server.
I bet that this can be replicated easier...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15058). Further discussion may take place here.**
---
PV 4.2.0, Linux, local server.
I bet that this can be replicated easier than this, but this is what I have. Also, the effect is worse as you stretch ParaView wider in the horizontal direction, while leaving it fairly short in the vertical direction. Furthermore, if you make the lower 2d window smaller vertically, the effect gets even more pronounced.
* Open can.exo. Al vars on. Apply.
* Go to the last time step.
* Plot over line. Apply.
* Split the 2d viewport vertically, and turn on visibility for the Plot Over Line.
* Left Axis Range - check Left Axis Use Custom Range. Use [1, 4000000] (one to four million). Check Left Axis Log Scale.
<<bug>> Notice that the horizontal lines from the left axis grid go off the top of the plot. This needs to be fixed.
Attaching a screenshot.
https://gitlab.kitware.com/paraview/paraview/-/issues/15053Color legend visibility broken2017-12-04T12:46:56-05:00Kitware RobotColor legend visibility broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15053). Further discussion may take place here.**
---
The color legend automatic visibility is broken when dealing with sets. H...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15053). Further discussion may take place here.**
---
The color legend automatic visibility is broken when dealing with sets. Here is a trivial way to replicate it.
* ParaView 4.2.0. Windows. Local server.
* Open can.exo, all vars on, apply.
* Color by EQPS. Notice that the color legend opens in the lower right corner.
* On the properties panel, turn off all blocks. Turn on Unnamed Sideset 4.
<<Bug>> The sideset is now being painted by Solid Color, but the color legend for EQPS still shows.
https://gitlab.kitware.com/paraview/paraview/-/issues/15052vtkPVServerManagerCorePython-Settings test failing2017-12-04T12:46:56-05:00Kitware RobotvtkPVServerManagerCorePython-Settings test failing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15052). Further discussion may take place here.**
---
This was caused by the update to jsoncpp in VTK.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15052). Further discussion may take place here.**
---
This was caused by the update to jsoncpp in VTK.https://gitlab.kitware.com/paraview/paraview/-/issues/15049Logarithmic color legend tick marks in wrong position2017-12-04T12:46:56-05:00Kitware RobotLogarithmic color legend tick marks in wrong position**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15049). Further discussion may take place here.**
---
Suppose I set up a logarithmic color legend that spans, for example, from ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15049). Further discussion may take place here.**
---
Suppose I set up a logarithmic color legend that spans, for example, from 10 to 100.
One would expect to have default tick marks at 10, 20, 30 ... 100. The total amount of tick marks would thus be 10.
Please, check this: you have 11 tick marks. Thus, ticks are not intuitive to read, as one does not know which values they represent.
I also noticed that the manual annotations do not account for logarithmic scaling, so that if I want to add a manual annotation I have to calculate the non-logarithmic position of the annotation with the following formula:
xmin=minimum value of legend
xmax=maximum value of legend
x=desired annotation value
x' = xmin + (xmax-xmin)*(log10(x)-log10(xmin))/(log10(xmax)-log10(xmin))
For example, in the above example, if I add an annotation at x=30, it will appear at the position of x=30 of the nonlogarithmic color legend. When I apply the above formula, I get x'=52.9409. That is the position I have to assign the annotation of x=30 when using logarithmic scale, if I want it to be correctly located.
Thank you very much.5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/15048Find data, Max, fails for Windows2017-12-04T12:46:56-05:00Kitware RobotFind data, Max, fails for Windows**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15048). Further discussion may take place here.**
---
Find data, Max, fails for windows. To replicate:
* Download 64 bit Win...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15048). Further discussion may take place here.**
---
Find data, Max, fails for windows. To replicate:
* Download 64 bit Windows .exe 4.2.0 install from Kitware website.
* Load can.exo. All vars on. Apply.
* Find Data dialog. Find Cells From can.ex2. Variable: EQPS. "is max"
* Run Selection Query.
Fails. My guess is numpy isn't installed.
Traceback (most recent call last):
File "<string>", line 8, in <module>
File "<string>", line 5, in vtkPythonExtractSelection_RequestData
File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\extract_selection.py", line 111, in execute
output.FieldData.append(nonzero_indices, "vtkSelectedIds");
File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\vtk\numpy_interface\dataset_adapter.py", line 596, in append
ds.GetAttributes(self.Association).append(array, name)
File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\vtk\numpy_interface\dataset_adapter.py", line 535, in append
arr = numpyTovtkDataArray(copy, name)
File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\paraview\vtk\numpy_interface\dataset_adapter.py", line 119, in numpyTovtkDataArray
vtkarray = numpy_support.numpy_to_vtk(array)
File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\vtk\util\numpy_support.py", line 141, in numpy_to_vtk
result_array = create_vtk_array(vtk_typecode)
File "C:\Program Files (x86)\ParaView 4.2.0\lib\paraview-4.2\site-packages\vtk\util\numpy_support.py", line 97, in create_vtk_array
return vtk.vtkDataArray.CreateDataArray(vtk_arr_type)
TypeError: CreateDataArray argument 1: an integer is required
https://gitlab.kitware.com/paraview/paraview/-/issues/15047Buttons duplication in "Separate panels for each type of properties" mode2017-12-04T12:46:56-05:00Kitware RobotButtons duplication in "Separate panels for each type of properties" mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15047). Further discussion may take place here.**
---
After activating the "Separate panels for each type of properties" option ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15047). Further discussion may take place here.**
---
After activating the "Separate panels for each type of properties" option in the global Settings and restarting ParaView, the "Restore defaults" and "Save as default" buttons appears 3 times instead of one in each panel. Only 1 is enabled while the other 2 are disabled.
See attached screenshot. https://gitlab.kitware.com/paraview/paraview/-/issues/15046Windows volume rendering appears broken2017-12-04T12:46:56-05:00Kitware RobotWindows volume rendering appears broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15046). Further discussion may take place here.**
---
(This bug is possibly due to my remote desktop'ing into my desktop. If so...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15046). Further discussion may take place here.**
---
(This bug is possibly due to my remote desktop'ing into my desktop. If so, less important of a bug.)
Windows, 4.2.0, local server.
* disk_our_ref.exo. All vars on. Apply.
* Volume render. It errors out, with the following:
ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLExtensionManager.cxx, line 757
vtkOpenGLExtensionManager (0000000010686D60): Extension GL_VERSION_1_3 could not be loaded.
https://gitlab.kitware.com/paraview/paraview/-/issues/15045Color legend bad for ranges of zero2017-12-04T12:46:56-05:00Kitware RobotColor legend bad for ranges of zero**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15045). Further discussion may take place here.**
---
Windows, 4.2.0, local server.
* Load disk_out_ref.exo. All vars on. A...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15045). Further discussion may take place here.**
---
Windows, 4.2.0, local server.
* Load disk_out_ref.exo. All vars on. Apply.
* Contour filter. Temp. 400. Apply.
* Now, color by temp. The object will look gray, with blue and red trianges. Further, the color legend will have three colors only - red at top, white (grey) in the middle, and blue at bottom. No numerical annotation shows up.
* Clicking on the map editor is nuts also, but I am not sure what we want... https://gitlab.kitware.com/paraview/paraview/-/issues/15044Representation and HiddenLinesRemoval plugin examples do not work2017-12-04T12:46:56-05:00Kitware RobotRepresentation and HiddenLinesRemoval plugin examples do not work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15044). Further discussion may take place here.**
---
Email from paraview email list from B.W.H. van Beest <bwvb@xs4all.nl>:
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15044). Further discussion may take place here.**
---
Email from paraview email list from B.W.H. van Beest <bwvb@xs4all.nl>:
I think there is a bug in the plugin example in
../ParaView/Examples/Plugin/Representation (Paraview 4.2)
As given, loading the plugin manually, and then creating a new source
(e.g. Box) causes Paraview to crash with the error message:
> ERROR: In
> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx,
> line 565
> vtkSIProxyDefinitionManager (0x265ebb0): No proxy that matches:
> group=representations and proxy=SurfaceRepresentationBase were found.
>
>
> ERROR: In
> /usr/local/git/ParaView/ParaViewCore/ServerImplementation/Core/vtkSIProxyDefinitionManager.cxx,
> line 989
> vtkSIProxyDefinitionManager (0x265ebb0): Failed to locate base proxy
> definition (representations, SurfaceRepresentationBase). Aborting for
> debugging purposes.
>
>
> Abort
The error seems to be in the file Representation.xml, where the attribute
base_proxyname is set to "SurfaceRepresentationBase", which should be
"SurfaceRepresentation" according to the documentation in
http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_new_Representations_for_3D_View_using_Plugins_.2A_new_in_version_3.7
When I make the change, recompile the plugin and load in into Paraview,
there is no longer the above crash when I create a new Box, and the
representation "Special Mapper" feautures in the Representationnn combobox.
> [243] Representation> diff Representation.xml.org Representation.xml
> 7c7
> < base_proxyname="SurfaceRepresentationBase">
> ---
> > base_proxyname="SurfaceRepresentation">https://gitlab.kitware.com/paraview/paraview/-/issues/15043QMake executable is not being set in ParaView/CMake/UseParaView.cmake2017-12-04T12:46:56-05:00Kitware RobotQMake executable is not being set in ParaView/CMake/UseParaView.cmake**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15043). Further discussion may take place here.**
---
Reported by Jim.Eliot@awe.co.uk on the paraview mailing list:
I am tryi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15043). Further discussion may take place here.**
---
Reported by Jim.Eliot@awe.co.uk on the paraview mailing list:
I am trying to build a file reader plugin against ParaView 4.2.0 and have been experiencing some difficulties. Qt is not found by cmake during the build process causing it to fail.
To illustrate the issue, I created the following simplified CMakeLists.txt file:
CMAKE_MINIMUM_REQUIRED
FIND_PACKAGE(ParaView REQUIRED)
INCLUDE(${PARAVIEW_USE_FILE})
When I call cmake with ParaView_DIR pointing at my 4.1.0 build Qt is found, but with 4.2.0 Qt is NOT found.
ParaView was built using Superbuild and Qt was built as part of that process. Should Qt be detected from ParaViewConfig.cmake?
Is this a change in behaviour between 4.1.0 and 4.2.0? Do I somehow need to specify the location of Qt manually?https://gitlab.kitware.com/paraview/paraview/-/issues/15032Duplicated entries in Settings/Render View window2017-12-04T12:46:56-05:00Kitware RobotDuplicated entries in Settings/Render View window**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15032). Further discussion may take place here.**
---
The "Set the compression method used blah blah..." text entry is duplicate...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15032). Further discussion may take place here.**
---
The "Set the compression method used blah blah..." text entry is duplicated in the panel. See the attached image.
Moreover, the difference between the sections "Remote/Parallel Rendering Options" and "Client/Server Rendering Options" is unclear.https://gitlab.kitware.com/paraview/paraview/-/issues/15031Multicore mode does not work with PV >= 4.2 and <= 4.3.12017-12-04T12:46:56-05:00Kitware RobotMulticore mode does not work with PV >= 4.2 and <= 4.3.1**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15031). Further discussion may take place here.**
---
Tested with official build of ParaView 4.3.1 under Win64.
Start ParaVie...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15031). Further discussion may take place here.**
---
Tested with official build of ParaView 4.3.1 under Win64.
Start ParaView. Go in the Settings window. In General table, enable the "Enable multicore support for data processing." Set 4 or 8 as maximum number of cores. Apply. OK. Restart ParaView.
Create a Wavelet source, choose Surface representation. You cannot choose the vtkProcessId array. In About panel, the Connection information says that there is no Remote Connection. Indeed at loading ParaView, no mpirun seems to be done in background.https://gitlab.kitware.com/paraview/paraview/-/issues/15029Crash on "Save current color map settings values as default"2017-12-04T12:46:56-05:00Kitware RobotCrash on "Save current color map settings values as default"**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15029). Further discussion may take place here.**
---
Start a fresh official ParaView 4.2 (downloaded in Win64 version) - do not...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15029). Further discussion may take place here.**
---
Start a fresh official ParaView 4.2 (downloaded in Win64 version) - do not load any file nor create any source.
Show the color map editor.
Click on the button "Save current color map settings values as default". ParaView just crashes.https://gitlab.kitware.com/paraview/paraview/-/issues/15023point IDs show up as reals instead of ints2017-12-14T16:59:39-05:00Kitware Robotpoint IDs show up as reals instead of ints**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15023). Further discussion may take place here.**
---
when showing point ids of a selection, the values are displayed as meaning...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15023). Further discussion may take place here.**
---
when showing point ids of a selection, the values are displayed as meaningless reals instead of ints.
this used to work in previous versions.
the spreadsheet view is unaffected.https://gitlab.kitware.com/paraview/paraview/-/issues/15022ExtractSubset broken in parallel2017-12-04T12:46:56-05:00Kitware RobotExtractSubset broken in parallel**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15022). Further discussion may take place here.**
---
read a partitioned structured grid with 2 pvserver processes:
ExtractSu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15022). Further discussion may take place here.**
---
read a partitioned structured grid with 2 pvserver processes:
ExtractSubset will return some bogus (infinite numbers) coordinates and the data is not visible.
brickpvtr = XMLPartitionedRectilinearGridReader(FileName=['/tmp/brick.pvtr'])
brickpvtrDisplay = Show(brickpvtr)
extractSubset1 = ExtractSubset(Input=brickpvtr)
extractSubset1.VOI = [0, 13, 0, 7, 0, 3]
extractSubset1Display = Show(extractSubset1)
https://gitlab.kitware.com/paraview/paraview/-/issues/15020Mesa3d volume rendering incorrectly forces use of floating point frame buffer2017-12-04T12:46:56-05:00Kitware RobotMesa3d volume rendering incorrectly forces use of floating point frame buffer**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15020). Further discussion may take place here.**
---
There is a mistake in the way ParaView incorrectly forces Mesa3d to use fl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15020). Further discussion may take place here.**
---
There is a mistake in the way ParaView incorrectly forces Mesa3d to use floating point buffer when volume rendering. I can trivially test this, if anyone wants. The problem is in the following code:
../VTK/Rendering/VolumeOpenGL/vtkOpenGLProjectedTetrahedraMapper.cxx.
Around line 145 is the following code:
if (!this->CanDoFloatingPointFrameBuffer)
{
vtkWarningMacro(
"Missing FBO support. The algorithm may produce visual artifacts.");
}
This forces ParaView to issue a warning, that is not needed, whenever we are rendering with an old version of Mesa3d (i.e., version 7.10.3).
The way I worked around the issue, at Utkarsh's suggestion, was to changed line
98,
this->UseFloatingPointFrameBuffer = true;
to be
this->UseFloatingPointFrameBuffer = false;
Please either change the this->UseFloatingPointFrameBuffer to be false in the constructor, or rework the logic of this if() test at line 147.
Alan - tested with Linux, local server, NX, disk_out_ref.exo. Just volume render. Error pops up.https://gitlab.kitware.com/paraview/paraview/-/issues/15014Add Dax plugin2017-12-04T12:46:56-05:00Kitware RobotAdd Dax plugin**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15014). Further discussion may take place here.**
---
Make the Dax filters in VTK/Accelerators available through a plugin.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15014). Further discussion may take place here.**
---
Make the Dax filters in VTK/Accelerators available through a plugin.https://gitlab.kitware.com/paraview/paraview/-/issues/15009Naming conflict with gtk package2017-12-04T12:46:56-05:00Kitware RobotNaming conflict with gtk package**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15009). Further discussion may take place here.**
---
In Paraview 4.1, there is a python module called gtk:
[PARAVIEW_INSTALL...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15009). Further discussion may take place here.**
---
In Paraview 4.1, there is a python module called gtk:
[PARAVIEW_INSTALL_DIR]/lib/paraview-4.1/site-packages/vtk/gtk
Problem is that this is also the name of standard python package.
Thus, any software using the gtk module may find the ParaView module instead of the standard one.
Is it possible to rename the gtk package in the Paraview to avoid naming conflict?https://gitlab.kitware.com/paraview/paraview/-/issues/15007Problem with the Magnitude calculation for a low values2017-12-04T12:46:56-05:00Kitware RobotProblem with the Magnitude calculation for a low values**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15007). Further discussion may take place here.**
---
Open attached file RES_DEPL_0_0.vtu
For the field RES_DEPL, the 3 compone...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15007). Further discussion may take place here.**
---
Open attached file RES_DEPL_0_0.vtu
For the field RES_DEPL, the 3 components DX, DY and DZ are well filled with values but the magnitude is not computed correctly for all the cells.
This can be seen by coloring the mesh according to each of these components (DX, DY, DZ, Magnitude).
The RES_DEPL_Magnituge.png picture demostrates the problem.
Note that the values are particularly low for DX and DY ~ 1e-17 in average, up to 1e-39 in some cases.https://gitlab.kitware.com/paraview/paraview/-/issues/15006proper formatting of 2D data2017-12-04T12:46:57-05:00Kitware Robotproper formatting of 2D data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15006). Further discussion may take place here.**
---
I tried to visualize 2D structured point data when I observed a strang...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15006). Further discussion may take place here.**
---
I tried to visualize 2D structured point data when I observed a strange behavior. If the spacing in Y direction is negative, the data is flipped upside-down in 'Slice' representation mode but shown properly as a 'Surface' representation. Tried in v. 4.0.1 and 4.2rc1 on Linux 64 bit. I attach a small VTK file to test it.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/14998Catalyst scripts can't import other python scripts in the run directory2017-12-04T12:46:57-05:00Kitware RobotCatalyst scripts can't import other python scripts in the run directory**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14998). Further discussion may take place here.**
---
Catalyst scripts can't import other python scripts in the run directory. C...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14998). Further discussion may take place here.**
---
Catalyst scripts can't import other python scripts in the run directory. Can be fixed by adding the run directory to PYTHONPATH but this shouldn't be necessary.https://gitlab.kitware.com/paraview/paraview/-/issues/14995Labels format string not working properly for IDs2017-12-14T17:01:01-05:00Kitware RobotLabels format string not working properly for IDs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14995). Further discussion may take place here.**
---
+ Sphere, APply
+ Select a cell
+ Show cell label and label by cell ID
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14995). Further discussion may take place here.**
---
+ Sphere, APply
+ Select a cell
+ Show cell label and label by cell ID
You'll see some weird number.
Now do go "advanced" settings on the "Selection Display Inspector" and change the format to %d. The number will show up properly.https://gitlab.kitware.com/paraview/paraview/-/issues/14993Fix Catalyst so that it can use LoadDistributedPlugin()2017-12-04T12:46:57-05:00Kitware RobotFix Catalyst so that it can use LoadDistributedPlugin()**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14993). Further discussion may take place here.**
---
Fix Catalyst so that it can use LoadDistributedPlugin()**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14993). Further discussion may take place here.**
---
Fix Catalyst so that it can use LoadDistributedPlugin()https://gitlab.kitware.com/paraview/paraview/-/issues/14990need to finalize catalyst scripts2017-12-04T12:46:57-05:00Kitware Robotneed to finalize catalyst scripts**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14990). Further discussion may take place here.**
---
vtkCPProcessor needs to finalize the vtkCPPipeline objects before deleting...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14990). Further discussion may take place here.**
---
vtkCPProcessor needs to finalize the vtkCPPipeline objects before deleting them.https://gitlab.kitware.com/paraview/paraview/-/issues/14989Extend Catalyst Live: pause simulation, set breakpoints, edit data writer par...2017-12-04T12:46:57-05:00Kitware RobotExtend Catalyst Live: pause simulation, set breakpoints, edit data writer parameters**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14989). Further discussion may take place here.**
---
Catalyst Live is extended to enable pausing a remote simulation linked wit...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14989). Further discussion may take place here.**
---
Catalyst Live is extended to enable pausing a remote simulation linked with Catalyst, setting a breakpoint (pausing the simulation at a certain time step in the future) as well as setting data writer parameters through Catalyst Live.
commit c01bfef0b802c37df45bd7b03680ea14cc8ab534
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Tue Aug 26 09:25:39 2014 -0400
Baseline for CatalystLiveBreakpoint test.
Change-Id: I1f0864618ac1977eb80aaac42c0ffafc4bbc7cb9
commit 7ed2b1485d730e5bd5badd150a7b49073388cc85
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Aug 25 14:34:18 2014 -0400
Disable Delete for Catalyst PipelineSource objects.
This commit also includes some renames for consistency.
Change-Id: I1f7ef5cb37aa8146cab3bcd761732e6114e768bf
commit 4e43dbbe50ff82e9efca1525c99248c6df13262b
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Aug 25 14:29:10 2014 -0400
Try to fix CatalystLive test.
Catalyst runs independently from CatalystLive. CatalystLive waits for certain
time steps from Catalyst, however Catalyst can run first and finish before
CatalystLive. We fix this by setting a very long Catalyst run and
killing it when CatalystLive finishes.
Change-Id: I08a36911b6357eae997356c42d94095f93b96c7e
commit b9b5eeb9f9e4d75cf98a458dc1fe60c09e574ba1
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Aug 25 08:11:10 2014 -0400
Use a 'file save' icon for writer parameters proxies.
Change-Id: I3525075f23a0ff6d334e4092b1d43110f9fc27b5
commit 2357270266564077f14353ba86607da4a8a2c538
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Wed Aug 20 15:29:35 2014 -0400
Catalyst writer parameters proxies cannot have extracts.
So, there is not icon and you cannot click on these proxies.
Change-Id: I721f92b7d50ed4915abe160364a9d4a4f47d82a4
commit 89b6e507bf85dfe216d46a2513139fbb8ac34947
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Wed Aug 20 14:45:10 2014 -0400
Move Catalyst writers parameters proxies into insitu_writer_parameters
Change-Id: I3a714d9a2ac323e172448386d9d9472dd2187afc
commit e6bab00e2387466868f6f56a2280c83c8be1de98
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Wed Aug 20 11:15:06 2014 -0400
FIX: ParaView does not crash on Disconnect.
Paraview was crashing if showing data through Live and disconnected.
Change-Id: I58744a36209b86d1d4c4124273b17cc22c87aa16
commit c87f9d4d2d2bc8c01f8b2964f1f778e98f863759
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Sun Aug 17 23:07:30 2014 -0400
Revert commit 'reduce catalystlive running time'.
This did not work on Mac.
Change-Id: I1e43c9a3598762478dbfffd466f283e35cf381b1
commit ca06b26856cdd9390bf92fb5ff6d754d0f5c513d
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Fri Aug 15 14:52:28 2014 -0400
Allow more time for Catalyst to send data (try to fix a test failure on Mac)
Change-Id: Iab4928d67dacff63bdb43f0901e7c4d582997cbf
commit ca0009c45b3511c036a51d4c33e4ce9b03e3bd97
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Thu Aug 14 11:14:12 2014 -0400
Undo extra panel added by leprechauns
Change-Id: Ie42baa2b7e15789d9147ab457c3471df30c777d4
commit 2fa86ab864e6962ddd6851bf7343a02fd72c95de
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Wed Aug 13 11:08:30 2014 -0400
Reduce CatalystLiveSetBreakpoint running time.
Change-Id: I8ce462fcc51017dd0671e586e719c5a38513fe8a
commit 24968b939c1c1ec2c5d79d4b19b1d684fe5725f7
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Wed Aug 13 10:49:03 2014 -0400
Fix clang warning.
Change-Id: If942dd6e6382d15c4839591f4f0860cb3cd19d31
commit 5656b777dbb70ff7aae0039bd82de964c09a21a5
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Aug 11 15:05:12 2014 -0400
Comment for cleanup to be done.
Change-Id: I3505ee5dc0b2bbc3a78fa7e37091d8fbae529974
commit cb55fc2d0f3a83e3a623bbf72b554c0d16570fbe
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Aug 11 13:35:33 2014 -0400
Remove CatalystLive test for Windows.
Change-Id: I54cfb4f44d78295049d1e5efd464c1898b9edde3
commit ba62e7ab18ec12e7c207fa22c5dd4708f5e2d4ba
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Fri Aug 8 17:35:05 2014 -0400
Enable editing of filename, frequency for Catalyst writers through Live.
Change-Id: Ib98a5412dc7b0a0d5f4ceff1e23bd6073288ac5e
commit bb0fc3f0d37b9d0ae608b5a64aee2034c092ab83
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Fri Aug 8 12:07:10 2014 -0400
Add a --script-ignore-output-errors option to vtkSMTestDriver.
Change-Id: Ia687424639bcbae3271955d34d143a02aa2eebed
commit 92c95860c402ef5a220fa96ad72e676a596653d4
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Thu Aug 7 12:18:10 2014 -0400
We wait a longer time for a script (catalyst server) to finish.
Change-Id: I01c6da138bd222c64cbab5bd409f492b0b94814a
commit 5e67a76838bf06232825733322cb9154a2ce170b
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Thu Aug 7 10:30:24 2014 -0400
Run an extra time step in Catalyst so that the client finishes.
Change-Id: I2b1b1c69ed8507dd0cb3246376730d1651c81823
commit b4dc3e392d04d9ebbe347c9374d61b3bfbfbb9f7
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Tue Aug 5 12:36:09 2014 -0400
Add ParaView version number to the coprocessing script.
Change-Id: If614b4ff9ff0e471e01dd3dfef697c207a01ec2f
commit 26d0de45eb051fe41c7c141e742b100a906143b5
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Tue Aug 5 09:26:40 2014 -0400
Fix warnings and baseline tests.
Change-Id: Ide92e770bd6884c3b905e56868877c9d07526cf7
commit 62e81c747da46df2613808b465fcbf9b02afec0a
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Aug 4 17:19:41 2014 -0400
Updated baseline for CatalystLiveSetBreakpoint test.
Change-Id: I193a488645dbeb62b3d497d9b5f93fe9d7b0ed29
commit 5c1ea7143fe20d005af946019ca3ae2372af24b5
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Jul 28 13:36:16 2014 -0400
Create a new doxygen module LiveInsitu.
Add relevant classes to the new module.
Change-Id: I432999ebdebb99f6dde3ce955ddbe26f9bc021ce
commit bccc0fa6af264bc20c93d824c509cb4b3fcdee26
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Wed Jul 23 17:43:30 2014 -0400
Add Catalyst - Live test.
Change-Id: I44d46de149bfe1b39786e62f9ac8e1a17322ff93
commit ef916df5ef42f61ea4309269ab6ac3d8f7c21aee
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Wed Jul 2 09:28:04 2014 -0400
Add the simulation timeStep as a choice when setting a breakpoint.
Change-Id: I84ad2fe37b6c6edbf273c806162b9c3f732291ca
commit b0906e82b04c6c71f9723b25fb62ac5e6ab90406
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Jun 30 11:22:00 2014 -0400
Push the state to the server when simulation is paused.
Also, move comunication between server and client in separate functions.
Change-Id: Iac94886138e2e2e3d030f924665e319f28b3e67a
commit f46c057abfbbb1e00dc6ab9f37e63e38437ba7ad
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Jun 16 09:17:36 2014 -0400
Add a breakpoint (pause simulation in the future) to Catalyst Live.
Change-Id: I0839517f20947a63c175ace4fb27071afdd0916e
commit d567064e156a7c256aa25b07cee733dbea2dedac
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Tue May 13 11:55:12 2014 -0400
Pause simulation and continue for ParaView Live Catalyst.
Implementation includes user feedback (menus and catalyst icon).
commit 8b6975930d4fa20ef4fd000bb97ec84973038949
Author: Dan Lipsa <dan.lipsa@kitware.com>
Date: Mon Mar 17 15:29:17 2014 -0400
Add default of 1 to the frequency of Catalyst to Live View communication.
Change-Id: I6a419c8319fc558d03aec787394095bf345101d9
https://gitlab.kitware.com/paraview/paraview/-/issues/14983programmable filter doesn't work with Catalyst2017-12-04T12:46:57-05:00Kitware Robotprogrammable filter doesn't work with Catalyst**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14983). Further discussion may take place here.**
---
The attached Catalyst Python script causes problems due to the programmabl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14983). Further discussion may take place here.**
---
The attached Catalyst Python script causes problems due to the programmable filter. If I replace the \n with \\n in programmableFilter1.Script everything works fine.
See me if you need an example to show this. Note that this issue exists in serial as well as parallel.
Also, it's weird that the following has been added to the script:
parallelUnstructuredGridWriter1.FileName = 'cppf_%t.pvtu'
parallelUnstructuredGridWriter1.WriteFrequency = 10
https://gitlab.kitware.com/paraview/paraview/-/issues/14981Build with VTK_USE_SYSTEM_PUGIXML=ON fails2017-12-04T12:46:57-05:00Kitware RobotBuild with VTK_USE_SYSTEM_PUGIXML=ON fails**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14981). Further discussion may take place here.**
---
Trying to build ParaView 4.2RC1 for Fedora using the system PUGIXML librar...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14981). Further discussion may take place here.**
---
Trying to build ParaView 4.2RC1 for Fedora using the system PUGIXML library. Linking libvtkPVServerManagerCore.so.1 fails because libpugixml.so is not added to the link line, or not added to the linking of libvtkpugixml.so.https://gitlab.kitware.com/paraview/paraview/-/issues/14980Scalar bar legend labels have not reliable behaviour for display2017-12-04T12:46:57-05:00Kitware RobotScalar bar legend labels have not reliable behaviour for display**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14980). Further discussion may take place here.**
---
In the "Color map editor", there is a dialog box "Edit color legend parame...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14980). Further discussion may take place here.**
---
In the "Color map editor", there is a dialog box "Edit color legend parameters".
It allows to choose the number of labels that you want to show along the scalar bar legend by filling the field "Number Of Labels".
But the number of the labels asked for the displaying doesn't correspond to the real number of the displayed labels.
The behaviour is similar to the following:
Number Of Labels = 1 --> 0 label is displayed
Number Of Labels = 2 --> 1 label is displayed
Number Of Labels = 3 to 5 --> 2 labels are displayed
Number Of Labels = 6 to 14 --> 5 labels are displayed
Number Of Labels = 15 to 23 --> 14 labels are displayed
Number Of Labels = 24 to 29 --> 23 labels are displayed
Number Of Labels = 30 to 59 --> 29 labels are displayed
Number Of Labels => 60 OR = 0 --> 59 labels are displayed
Could it be possible that the number of labels asked is exactly the number of labels displayed ?5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.com