ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-23T12:22:30-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/15965using auxiliary coordinates does not working2021-03-23T12:22:30-04:00Kitware Robotusing auxiliary coordinates does not working**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15965). Further discussion may take place here.**
---
While VisIt consumes the provided input file, ParaView doesn't.
The expec...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15965). Further discussion may take place here.**
---
While VisIt consumes the provided input file, ParaView doesn't.
The expected result is also provided, the representation as boxes was chosen.
To be honest, I'm new to ParaView and trying to visualize some of my data via netCDF. I'm not sure, if VisIt is too careless about the format of my input file. But at least:
The file in the attachment converted via
ncgen -o mytest_dg.nc mytest_dg.txt
should be consumable and visualizable without any problem.https://gitlab.kitware.com/paraview/paraview/-/issues/15964ClippingRange settings2018-08-08T22:24:34-04:00Kitware RobotClippingRange settings**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15964). Further discussion may take place here.**
---
Is there a way to hide far side of 3D actors with paraview ?
In a VTK p...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15964). Further discussion may take place here.**
---
Is there a way to hide far side of 3D actors with paraview ?
In a VTK python application, you can do this with :
def MyClippingRange(obj, event):
camera=ren1.GetActiveCamera()
camera.SetFocalPoint(0,0,0)
camera_dist=camera.GetDistance()
camera.SetClippingRange(0.1,camera_dist)
...
ren.AddObserver("ResetCameraEvent",MyClippingRange)
I have not found such settings in paraview that could be really usefull.https://gitlab.kitware.com/paraview/paraview/-/issues/15959Paraview crashes often with StarCCM+-datasets2021-03-23T12:22:47-04:00Kitware RobotParaview crashes often with StarCCM+-datasets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15959). Further discussion may take place here.**
---
Hi,
I observed lots of crashes when using datasets which were exported fr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15959). Further discussion may take place here.**
---
Hi,
I observed lots of crashes when using datasets which were exported from StarCCM+ to Ensight file format.
I managed to construct a simple case where it always happens to me.
To reproduce:
- Extract zip-file
- load case-file
- generate "Slice" with origin (0 0 115) and normal (0 0 1)
- APPLY!
I think it happens because the slice intersects exactly the nodes of the mesh. I tried Paraview versions 3.10, 3.98, 4.3.1 and 5.0.0: All the same.
Best and thanks for your efforts,
Carstenhttps://gitlab.kitware.com/paraview/paraview/-/issues/15946Second view not directly updated after changing color scale2020-05-06T21:06:30-04:00Kitware RobotSecond view not directly updated after changing color scale**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15946). Further discussion may take place here.**
---
Reproductive steps:
1. Create a Wavelet source
2. Switch to slice view...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15946). Further discussion may take place here.**
---
Reproductive steps:
1. Create a Wavelet source
2. Switch to slice view
3. Split the current view and add a second Render view
4. Show wavelet in new view, switch to slice view
5. Use the Color Map Editor to pick a different color scale
6. Only one of the views updates its coloring, interacting with that view leaves the other view inconsistent
7. Only after interacting with the faulty view is its coloring updated
This is with the official ParaView 5.0 Linux 64-bit binarieshttps://gitlab.kitware.com/paraview/paraview/-/issues/15931vtkCompositeMapper not displaying correctly normals generated by the Tube Filter2021-03-23T12:24:14-04:00Kitware RobotvtkCompositeMapper not displaying correctly normals generated by the Tube Filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15931). Further discussion may take place here.**
---
When displaying a composite dataset containing normals for triangle strips...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15931). Further discussion may take place here.**
---
When displaying a composite dataset containing normals for triangle strips , the Composite Mapper seems completelly breaking normals.https://gitlab.kitware.com/paraview/paraview/-/issues/15929wavelet broken when inversing range2018-08-08T22:24:34-04:00Kitware Robotwavelet broken when inversing range**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15929). Further discussion may take place here.**
---
Wavelet does not seem to support an inversed range, but the underlying pro...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15929). Further discussion may take place here.**
---
Wavelet does not seem to support an inversed range, but the underlying problem might be biggerJean-Christophe Fillion-RobinJean-Christophe Fillion-Robinhttps://gitlab.kitware.com/paraview/paraview/-/issues/15928Resample with dataset doesn't work with cell data in multiblock datasets2021-03-23T12:24:47-04:00Kitware RobotResample with dataset doesn't work with cell data in multiblock datasets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15928). Further discussion may take place here.**
---
I've found that Resample with datasets ignores data in cells when multiblo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15928). Further discussion may take place here.**
---
I've found that Resample with datasets ignores data in cells when multiblock dataset is used as Input. Attachment demonstrates the problem
P.S. I'm not sure about multiblock datasets, this is Cory Quammen assumption:
https://cmake.org/pipermail/paraview/2016-January/035969.htmlhttps://gitlab.kitware.com/paraview/paraview/-/issues/15920Anaglyph stereo colors2018-08-08T22:24:35-04:00Kitware RobotAnaglyph stereo colors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15920). Further discussion may take place here.**
---
Allow users to choose/set colors used for Anaglyph Stereo mode. Give them...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15920). Further discussion may take place here.**
---
Allow users to choose/set colors used for Anaglyph Stereo mode. Give them suggestions/defaults. Default to current Anaglyph colors.https://gitlab.kitware.com/paraview/paraview/-/issues/15906Plot over line, selecting Use Custom Range jumps2018-08-08T22:24:35-04:00Kitware RobotPlot over line, selecting Use Custom Range jumps**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15906). Further discussion may take place here.**
---
When plotting over line, and trying to set the Use Custom Range, the Prope...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15906). Further discussion may take place here.**
---
When plotting over line, and trying to set the Use Custom Range, the Properties tab jumps. This is very obnoxious and needs to be fixed.
* ParaView 5.0.0-RC2, Linux, local server.
* Sources/ Wavelet. Apply.
* Plot over line. Apply.
* Select Advanced icon on Properties tab.
* Now, slide the Properties tab down to Left Axis use Custom Range. Select this.
The whole Properties tab jumps. I bet it is positioned as though the Properties tab advanced icon isn't enabled.https://gitlab.kitware.com/paraview/paraview/-/issues/15905Link camera doesn't work in slice view2023-06-15T13:07:16-04:00Kitware RobotLink camera doesn't work in slice view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15905). Further discussion may take place here.**
---
Link camera does not work, using right mouse clicks, on the view. For a s...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15905). Further discussion may take place here.**
---
Link camera does not work, using right mouse clicks, on the view. For a slice view and normal view, you can get around this using Tools/ Add Camera Link - but it is obnoxious. Please fix it.https://gitlab.kitware.com/paraview/paraview/-/issues/15899vtkImageSliceRepresentation using obsolete WholeExtent when caching is enabled2018-02-26T13:16:51-05:00Kitware RobotvtkImageSliceRepresentation using obsolete WholeExtent when caching is enabled**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15899). Further discussion may take place here.**
---
vtkImageSliceRepresentation doesn't pass correct "cached" image's whole ex...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15899). Further discussion may take place here.**
---
vtkImageSliceRepresentation doesn't pass correct "cached" image's whole extent or paritioned extents when cache is being used.https://gitlab.kitware.com/paraview/paraview/-/issues/15894vtkExodusIIWriter: _ (underscore) added only to 2D data arrays2023-06-15T15:44:18-04:00Kitware RobotvtkExodusIIWriter: _ (underscore) added only to 2D data arrays**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15894). Further discussion may take place here.**
---
When writing 1D or 3D data arrays, the name of the array is preserved in t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15894). Further discussion may take place here.**
---
When writing 1D or 3D data arrays, the name of the array is preserved in the output file. When writing 2D data arrays, however, an underscore (_) is added to the name.
MWE:
```
import numpy
import vtk
from vtk.util import numpy_support
points = [
[0.0, 0.0, 0.0],
[1.0, 0.0, 0.0],
[1.0, 1.0, 0.0],
]
mesh = vtk.vtkUnstructuredGrid()
# set points
vtk_points = vtk.vtkPoints()
# Not using a deep copy here results in a segfault.
vtk_array = vtk.util.numpy_support.numpy_to_vtk(points)
vtk_points.SetData(vtk_array)
mesh.SetPoints(vtk_points)
c = numpy.array([
3,
0, 1, 2,
], dtype=int)
a = vtk.util.numpy_support.numpy_to_vtkIdTypeArray(c)
cell_array = vtk.vtkCellArray()
cell_array.SetCells(1, a)
mesh.SetCells(vtk.VTK_TRIANGLE, cell_array)
# add point data
pd = mesh.GetPointData()
A = numpy.array([7, 3, -2], dtype=float)
array = vtk.util.numpy_support.numpy_to_vtk(A)
array.SetName('A')
pd.AddArray(array)
B = numpy.array([[7, 1], [3, 2], [-2, 0]], dtype=float)
array = vtk.util.numpy_support.numpy_to_vtk(B)
array.SetName('B')
pd.AddArray(array)
C = numpy.array([[7, 1, 3], [3, 2, -2], [-2, 0, 7]], dtype=float)
array = vtk.util.numpy_support.numpy_to_vtk(C)
array.SetName('C')
pd.AddArray(array)
# writer = vtk.vtkUnstructuredGridWriter()
# writer.SetFileName('test.vtk')
writer = vtk.vtkExodusIIWriter()
writer.SetFileName('test.e')
writer.SetInputData(mesh)
writer.Write()
```
Open the file in, e.g., ParaView and observe the difference between A, B_, C.
When using the `vtkUnstructuredGridWriter` to write VTK files (any other file type, in fact), no underscore is added.https://gitlab.kitware.com/paraview/paraview/-/issues/15879Xdmf data not correctly displayed2020-05-05T23:24:33-04:00Kitware RobotXdmf data not correctly displayed**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15879). Further discussion may take place here.**
---
The attached XDMF file contains three cells:
* 2 triangles and
* 1 q...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15879). Further discussion may take place here.**
---
The attached XDMF file contains three cells:
* 2 triangles and
* 1 quad.
The triangles are read and displayed alright, the quad is not.https://gitlab.kitware.com/paraview/paraview/-/issues/15878Xdmf2Reader: Unknown Attribute Type None, number of components wrong2020-05-05T23:24:50-04:00Kitware RobotXdmf2Reader: Unknown Attribute Type None, number of components wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15878). Further discussion may take place here.**
---
I've noticed some oddities with the vtkXdmfReader. The following script
`...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15878). Further discussion may take place here.**
---
I've noticed some oddities with the vtkXdmfReader. The following script
```
import vtk
reader = vtk.vtkXdmfReader()
reader.SetFileName('test.xmf')
reader.Update()
grid = reader.GetOutputDataObject(0)
point_data = grid.GetPointData()
for k in range(point_data.GetNumberOfArrays()):
array = point_data.GetArray(k)
print(array)
```
produces
```
XDMF Error in
/build/vtk6-01UJ_h/vtk6-7.1.0~20151212165543/ThirdParty/xdmf2/vtkxdmf2/libsrc/XdmfAttribute.cxx
line 183 (Unknown Attribute Type None)
```
on `GetPointData()`. This is with a simple test file, attached.
The supposed "Error" doesn't stop the execution though. However, for the point data, one gets
```
NumberOfComponents: 1
```
while it is actually 2 (as can be seen by inspecting the file).https://gitlab.kitware.com/paraview/paraview/-/issues/15876When Auto Convert Properties, expose xyz coordinates2018-08-08T22:24:35-04:00Kitware RobotWhen Auto Convert Properties, expose xyz coordinates**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15876). Further discussion may take place here.**
---
For all filters that use a variable, such as clip by scalar or threshold, ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15876). Further discussion may take place here.**
---
For all filters that use a variable, such as clip by scalar or threshold, when the Auto Convert Properties state is set, expose the X, Y and Z coordinates. This is done in the calculator, it should be done everywhere.https://gitlab.kitware.com/paraview/paraview/-/issues/15865Minor bug when compiling VisItBridge/databases/paraDIS/paraDIS_lib/paradis.C ...2021-03-23T12:11:18-04:00Kitware RobotMinor bug when compiling VisItBridge/databases/paraDIS/paraDIS_lib/paradis.C with gcc 5.2.0**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15865). Further discussion may take place here.**
---
The file VisItBridge/databases/paraDIS/paraDIS_lib/paradis.C will not comp...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15865). Further discussion may take place here.**
---
The file VisItBridge/databases/paraDIS/paraDIS_lib/paradis.C will not compile with gcc 5.2.0 on Arch Linux
A typecast is necessary at line 765.
vector<Arm*> armpair(2,(Arm*)NULL);
instead of
vector<Arm*> armpair(2,NULL);https://gitlab.kitware.com/paraview/paraview/-/issues/15850hdf5 file from PFLOTRAN Color by Material_ID doesn't work correctly.2018-02-26T13:16:51-05:00Kitware Robothdf5 file from PFLOTRAN Color by Material_ID doesn't work correctly.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15850). Further discussion may take place here.**
---
When you load an hdf5 file, ParaView fails to create and paint by a va...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15850). Further discussion may take place here.**
---
When you load an hdf5 file, ParaView fails to create and paint by a variable named Material_ID. Visit does paint this correctly (correctly defined here as what my customer wants and VisIt does). Here is how to replicate on VisIt:
* Download, install VisIt.
* Load file trial3.h5 (I will give this to Utkarsh).
* Plots/ Add/ Fill Boundary/ Material_ID.
* Draw.
Now, notice that the bar is painted by material ID. This represents where each of the materials is 1 (i.e., positive result) (as opposed to -1, negative result).
Now, run Paraview, and load trial3.h5. All variables on. Apply.
Notice that you can't paint by Material_ID.
What I want:
* To expose, or create, Material_ID. Then, we need to color by Annotated Color, KAAMS color map.https://gitlab.kitware.com/paraview/paraview/-/issues/15849Sidesets, without variable data, coloring wrong2024-03-07T20:47:40-05:00Kitware RobotSidesets, without variable data, coloring wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15849). Further discussion may take place here.**
---
We are painting by variable incorrectly on sets, when we have partial arra...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15849). Further discussion may take place here.**
---
We are painting by variable incorrectly on sets, when we have partial arrays. What we are doing (I believe) is color by the last color we had, spread across the rest of the data. Here's how to replicate, and what I think we should do.
* Open attached file. All vars on. Turn on sets Unnamed set ID: 1, Unnamed set 2 and Unnamed set 3. (Note to myself, Cal Kevin, PC)
* Unselect the one block in this dataset. The bug shows with this block set, but it isn't as obvious.
* Apply.
* Paint by Applied Pressure. Two sides of the cube will be red, one will be blue. The plane parallel with the blue plane has real data, the perpendicular one does not.
* You can see this through Find Data/ Cell Labels/ AppliedPressure, then selecting cells. The parallel plane has data (10), the perpendicular one does not.
What I want is for the side that doesn't have data to be painted in the Color Editor/ Color Mapping Parameters/ NaN Color.
Have Utkarsh ask me for this dataset.5.13 (Summer 2024)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/15846Time sequence out of order on VTK file import within ParaView2020-05-06T13:46:12-04:00Kitware RobotTime sequence out of order on VTK file import within ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15846). Further discussion may take place here.**
---
When a user imports the attached data into ParaView, the file import dialo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15846). Further discussion may take place here.**
---
When a user imports the attached data into ParaView, the file import dialogue shows an incorrect numerical order of the vtk files. This happens regardless of file name being
String_integer.vtk
string_string_integer.vtk
In the terminal, the files are in the proper order (see additional screenshot). The integer convention is tied to the real time step value for easy post processing. Screenshots and test data are attached. Also tested on Paraview 4.1https://gitlab.kitware.com/paraview/paraview/-/issues/15822OS X mouse wheel inertia / momentum makes 3D preview / ParaView become unresp...2021-03-23T12:13:09-04:00Kitware RobotOS X mouse wheel inertia / momentum makes 3D preview / ParaView become unresponsive**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15822). Further discussion may take place here.**
---
On OS X mouse wheel has inertia / momentum when scrolling / zooming. There...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15822). Further discussion may take place here.**
---
On OS X mouse wheel has inertia / momentum when scrolling / zooming. There's no typical mouse wheel, but rather touch area on Apple's Magic Mouse. Swiping with finger causes underlying view receive scroll momentum.
Currently ParaView (and probably all VTK based views) choke on such events on OS X. Where normal panning works well, using zoom via Apple's mouse swipe causes app to become unresponsive for several seconds when viewing some non-trivial data, and usually needs to be killed by the user.
This makes using ParaView on OS X really painful experience.
Please see attached video showing the random behavior of mouse wheel on some volumetric data:
1. First part using outline view, I am swiping my finger up, but rather than zooming in the outline starts to zoom then zooms out, making the behavior unpredictable
2. Using volumetric view you can see similar behavior but the zooming is far less smooth. Note this is really low zoom & low density data. Using higher zoom causes ParaView to become seriously unresponsive.
As a workaround please at least provide as soon as possible option to disable zooming by wheel, so we won't accidentally hang ParaView.