ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-02-15T05:44:43-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/14283Color editor doesn't update - CAM data2018-02-15T05:44:43-05:00Kitware RobotColor editor doesn't update - CAM data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14283). Further discussion may take place here.**
---
Haven't been able to replicate this with any other data. Sorry. Utkarsh ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14283). Further discussion may take place here.**
---
Haven't been able to replicate this with any other data. Sorry. Utkarsh has all of the data for this bug.
Linux, master, remote server (8 servers).
Read in Sandia-CAM-Data-Alan1-Do-Not-Release.nc. CAM NetCDF (Unstructured) reader.
Use "Connectivity File Name" Sandia-CAM-latlon-Alan1-Do-Not-Release.nc.
Unclick Cell Layer Right. Click Single Level.
Apply.
Color by TMQ.
Open the Color Editor.
Make sure auto apply is OFF.
Select Enable opacity mapping for surfaces.
Update.
Now, drag the right control button for red vertically down, so the opacity control is basically horizontal, and zero.
Update.
Nothing happens. This is a bad bug.
Marking high since this is impacting me.
https://gitlab.kitware.com/paraview/paraview/-/issues/14282CAM reader - Connectivity file name is too wide2018-02-15T05:44:43-05:00Kitware RobotCAM reader - Connectivity file name is too wide**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14282). Further discussion may take place here.**
---
With the CAM reader, the entry for the Connectivity file is too large, and...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14282). Further discussion may take place here.**
---
With the CAM reader, the entry for the Connectivity file is too large, and doesn't scale to fit the Properties tab. You always have to miss with the left dialog box widths.
Master, Linux, remote server (local server will do).
Open Sandia-CAM-Data-Alan1-Do-Not-Release.nc (given to Utkarsh).
Choose the CAM NetCDF (Unstructured) reader. OK.
Now, browse to the Connectivity File. Note that the browse window is hidden. Either widen the properties tab dialog, or pull the horizontal ruler at the bottom of the dialog to the right.
Please make the width of the Connectivity File Name entry narrow enough to fit the default Properties panel width.
https://gitlab.kitware.com/paraview/paraview/-/issues/14281Turn off (optionallly) tick mark number labels on each axis on cube axes2018-02-14T09:56:19-05:00Kitware RobotTurn off (optionallly) tick mark number labels on each axis on cube axes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14281). Further discussion may take place here.**
---
Sometimes, particularly when you have a data volume which is narrow in one...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14281). Further discussion may take place here.**
---
Sometimes, particularly when you have a data volume which is narrow in one of the three x/y/z dimensions, the tick mark labels on the short axis(es) lie on top of each other, and the result is a detraction from the image. It should be possible to optionally turn off the tic mark labels on each axis, similar to how you can now turn on and off the tick marks and minor tick marks on each axis.
Also handy would be an intelligent mode where the number of tick labels reduced to avoid overwrite, and went invisible altogether when the axis took a sufficiently small angle of the view. https://gitlab.kitware.com/paraview/paraview/-/issues/14280Multiple view rendering issues in batch/symmetric batch2018-08-08T22:26:20-04:00Kitware RobotMultiple view rendering issues in batch/symmetric batch**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14280). Further discussion may take place here.**
---
The attached script produces causes following issues:
-----------------...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14280). Further discussion may take place here.**
---
The attached script produces causes following issues:
-----------------------------------------------------------------
> ./pvpython two_view.py
This works as expected and produces 3 images of 2 views
-----------------------------------------------------------------
> ./pvbatch two_view.py
This doesn't render correctly. The chart view images are incorrect. They seem to simply show the result from the 3D render view.
-----------------------------------------------------------------
> mpirun -np 2 ./pvbatch two_view.py
OR
> mpirun -np 2 ./pvbatch -sym two_view.py
This dead locks on the first attempt to render the chart view.https://gitlab.kitware.com/paraview/paraview/-/issues/14279Glyph filter producing different results on OsX and Windows.2018-08-08T22:26:20-04:00Kitware RobotGlyph filter producing different results on OsX and Windows.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14279). Further discussion may take place here.**
---
Check the attached images produces on OsX and Windows using data in Archiv...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14279). Further discussion may take place here.**
---
Check the attached images produces on OsX and Windows using data in Archive.zip (check with Utkarsh for the dataset).https://gitlab.kitware.com/paraview/paraview/-/issues/14278SelectionLabels test failing2018-08-08T22:26:20-04:00Kitware RobotSelectionLabels test failing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14278). Further discussion may take place here.**
---
See http://open.cdash.org/viewTest.php?onlyfailed&buildid=3030353**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14278). Further discussion may take place here.**
---
See http://open.cdash.org/viewTest.php?onlyfailed&buildid=3030353https://gitlab.kitware.com/paraview/paraview/-/issues/14277StreamTracer streamlines not terminating reliably at exterior boundary2021-03-24T18:02:10-04:00Kitware RobotStreamTracer streamlines not terminating reliably at exterior boundary**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14277). Further discussion may take place here.**
---
Some of the streamlines continue past the exterior boundary of the input d...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14277). Further discussion may take place here.**
---
Some of the streamlines continue past the exterior boundary of the input dataset (see attached screenshot). This happens with all integrator types and is independent of the initial and minimum step lengths.
VTK file for reproducing the problem:
# vtk DataFile Version 3.0
Unstructured Grid Example
ASCII
DATASET UNSTRUCTURED_GRID
POINTS 72 float
0.0000 0.0000 0.0000
2.0000 0.0000 0.0000
4.0000 0.0000 0.0000
6.0000 0.0000 0.0000
8.0000 0.0000 0.0000
10.0000 0.0000 0.0000
10.0000 2.0000 0.0000
10.0000 4.0000 0.0000
10.0000 6.0000 0.0000
10.0000 8.0000 0.0000
10.0000 10.0000 0.0000
8.0000 10.0000 0.0000
6.0000 13.0000 0.0000
4.0000 10.0000 0.0000
2.0000 10.0000 0.0000
0.0000 10.0000 0.0000
0.0000 8.0000 0.0000
0.0000 6.0000 0.0000
0.0000 4.0000 0.0000
0.0000 2.0000 0.0000
5.1098 1.9166 0.0000
8.3291 6.6185 0.0000
3.3142 8.4218 0.0000
1.8685 5.2462 0.0000
5.0691 8.1893 0.0000
8.2395 4.9328 0.0000
8.4232 3.2829 0.0000
1.7293 3.4518 0.0000
7.2577 8.1381 0.0000
7.3442 1.8115 0.0000
1.8120 7.3696 0.0000
2.8024 1.9116 0.0000
6.5401 3.6777 0.0000
3.6979 6.5582 0.0000
6.1567 6.0293 0.0000
3.9835 4.1100 0.0000
0.0000 0.0000 1.0000
2.0000 0.0000 1.0000
4.0000 0.0000 1.0000
6.0000 0.0000 1.0000
8.0000 0.0000 1.0000
10.0000 0.0000 1.0000
10.0000 2.0000 1.0000
10.0000 4.0000 1.0000
10.0000 6.0000 1.0000
10.0000 8.0000 1.0000
10.0000 10.0000 1.0000
8.0000 13.0000 1.0000
6.0000 10.0000 1.0000
4.0000 10.0000 1.0000
2.0000 10.0000 1.0000
0.0000 10.0000 1.0000
0.0000 8.0000 1.0000
0.0000 6.0000 1.0000
0.0000 4.0000 1.0000
0.0000 2.0000 1.0000
5.1098 1.9166 1.0000
8.3291 6.6185 1.0000
3.3142 8.4218 1.0000
1.8685 5.2462 1.0000
5.0691 8.1893 1.0000
8.2395 4.9328 1.0000
8.4232 3.2829 1.0000
1.7293 3.4518 1.0000
7.2577 8.1381 1.0000
7.3442 1.8115 1.0000
1.8120 7.3696 1.0000
2.8024 1.9116 1.0000
6.5401 3.6777 1.0000
3.6979 6.5582 1.0000
6.1567 6.0293 1.0000
3.9835 4.1100 1.0000
CELLS 50 350
6 19 0 1 55 36 37
6 19 31 27 55 67 63
6 20 2 3 56 38 39
6 32 20 29 68 56 65
6 6 4 5 42 40 41
6 29 3 4 65 39 40
6 32 29 26 68 65 62
6 32 26 25 68 62 61
6 21 8 9 57 44 45
6 11 9 10 47 45 46
6 9 28 21 45 64 57
6 21 34 25 57 70 61
6 24 12 13 60 48 49
6 22 13 14 58 49 50
6 16 14 15 52 50 51
6 14 30 22 50 66 58
6 33 22 30 69 58 66
6 18 27 23 54 63 59
6 9 11 28 45 47 64
6 19 1 31 55 37 67
6 34 24 33 70 60 69
6 25 7 8 61 43 44
6 14 16 30 50 52 66
6 31 2 20 67 38 56
6 22 33 24 58 69 60
6 17 18 23 53 54 59
6 11 12 28 47 48 64
6 24 13 22 60 49 58
6 26 6 7 62 42 43
6 25 8 21 61 44 57
6 29 4 6 65 40 42
6 26 7 25 62 43 61
6 23 35 33 59 71 69
6 18 19 27 54 55 63
6 28 12 24 64 48 60
6 34 21 28 70 57 64
6 29 20 3 65 56 39
6 29 6 26 65 42 62
6 16 17 30 52 53 66
6 30 17 23 66 53 59
6 31 35 27 67 71 63
6 1 2 31 37 38 67
6 34 28 24 70 64 60
6 31 20 35 67 56 71
6 33 30 23 69 66 59
6 35 20 32 71 56 68
6 35 32 34 71 68 70
6 34 32 25 70 68 61
6 35 34 33 71 70 69
6 23 27 35 59 63 71
CELL_TYPES 50
13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13 13
POINT_DATA 72
SCALARS Velocity FLOAT 3
LOOKUP_TABLE default
1.000 0.000 0.000
1.000 0.200 0.000
1.000 0.400 0.000
1.000 0.600 0.000
1.000 0.800 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 0.800 0.000
1.000 0.600 0.000
1.000 0.400 0.000
1.000 0.200 0.000
1.000 0.000 0.000
1.000 0.000 0.000
1.000 0.000 0.000
1.000 0.000 0.000
1.000 0.000 0.000
1.000 0.511 0.000
1.000 0.833 0.000
1.000 0.331 0.000
1.000 0.187 0.000
1.000 0.507 0.000
1.000 0.824 0.000
1.000 0.842 0.000
1.000 0.173 0.000
1.000 0.726 0.000
1.000 0.734 0.000
1.000 0.181 0.000
1.000 0.280 0.000
1.000 0.654 0.000
1.000 0.370 0.000
1.000 0.616 0.000
1.000 0.398 0.000
1.000 0.000 0.000
1.000 0.200 0.000
1.000 0.400 0.000
1.000 0.600 0.000
1.000 0.800 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 1.000 0.000
1.000 0.800 0.000
1.000 0.600 0.000
1.000 0.400 0.000
1.000 0.200 0.000
1.000 0.000 0.000
1.000 0.000 0.000
1.000 0.000 0.000
1.000 0.000 0.000
1.000 0.000 0.000
1.000 0.511 0.000
1.000 0.833 0.000
1.000 0.331 0.000
1.000 0.187 0.000
1.000 0.507 0.000
1.000 0.824 0.000
1.000 0.842 0.000
1.000 0.173 0.000
1.000 0.726 0.000
1.000 0.734 0.000
1.000 0.181 0.000
1.000 0.280 0.000
1.000 0.654 0.000
1.000 0.370 0.000
1.000 0.616 0.000
1.000 0.398 0.000https://gitlab.kitware.com/paraview/paraview/-/issues/14276"Cell Label Visibility" and "Point Label Visibility" are showing up on the Di...2018-08-08T22:26:20-04:00Kitware Robot"Cell Label Visibility" and "Point Label Visibility" are showing up on the Display properties section**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14276). Further discussion may take place here.**
---
+ Create Sphere, hit apply.
You'll see that "Cell Label Visibility" and...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14276). Further discussion may take place here.**
---
+ Create Sphere, hit apply.
You'll see that "Cell Label Visibility" and "Point Label Visibility" are shown on the Properties panel's "Display" section. That's a bug. We don't want to see these here.https://gitlab.kitware.com/paraview/paraview/-/issues/14275Warning messages when using comparative view2018-08-08T22:26:22-04:00Kitware RobotWarning messages when using comparative view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14275). Further discussion may take place here.**
---
Try the following:
1. Open can.ex2 or disk_out_ref.ex2
2. Add a ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14275). Further discussion may take place here.**
---
Try the following:
1. Open can.ex2 or disk_out_ref.ex2
2. Add a Slice
3. Open a 3D View (Comparative)
You'll get error messages as follows:
Generic Warning: In /home/utkarsh/Kitware/ParaView3/ParaView/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 484
Failed to locate property: HiddenRepresentations
Generic Warning: In /home/utkarsh/Kitware/ParaView3/ParaView/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 805
Call not supported for the current property type.
Generic Warning: In /home/utkarsh/Kitware/ParaView3/ParaView/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 484
Failed to locate property: HiddenRepresentations
Generic Warning: In /home/utkarsh/Kitware/ParaView3/ParaView/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx, line 825
Call not supported for the current property type.
https://gitlab.kitware.com/paraview/paraview/-/issues/14274Fix up Catalyst Base edition patch2018-08-08T22:26:22-04:00Kitware RobotFix up Catalyst Base edition patch**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14274). Further discussion may take place here.**
---
Code has changed a patch no longer applies**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14274). Further discussion may take place here.**
---
Code has changed a patch no longer applieshttps://gitlab.kitware.com/paraview/paraview/-/issues/14273Segfault on loading state with missing data2018-08-08T22:26:22-04:00Kitware RobotSegfault on loading state with missing data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14273). Further discussion may take place here.**
---
Try loading the attached state. ParaView segfaults due to missing data. It...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14273). Further discussion may take place here.**
---
Try loading the attached state. ParaView segfaults due to missing data. It should not segfault.https://gitlab.kitware.com/paraview/paraview/-/issues/14270Build errors with building external plugins that add new vtk modules.2018-08-08T22:26:22-04:00Kitware RobotBuild errors with building external plugins that add new vtk modules.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14270). Further discussion may take place here.**
---
Building plugins with new VTK modules outside of ParaView's source dir cau...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14270). Further discussion may take place here.**
---
Building plugins with new VTK modules outside of ParaView's source dir causes errors.
e.g. try building this plugin:
https://github.com/utkarshayachit/PythonWrappedPluginExamplehttps://gitlab.kitware.com/paraview/paraview/-/issues/14269Add ability to save dataset for a subset of time range.2020-06-09T20:49:59-04:00Kitware RobotAdd ability to save dataset for a subset of time range.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14269). Further discussion may take place here.**
---
When saving datasets out, some writers provide an ability to save all time...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14269). Further discussion may take place here.**
---
When saving datasets out, some writers provide an ability to save all timesteps. One cannot choose what range of timesteps to save, however. We need to add an ability to do the same.
https://gitlab.kitware.com/paraview/paraview/-/issues/14268Center appears/disappears strangly2018-08-08T22:26:22-04:00Kitware RobotCenter appears/disappears strangly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14268). Further discussion may take place here.**
---
Master, Linux, local server. Either delete your .config/ParaView files, o...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14268). Further discussion may take place here.**
---
Master, Linux, local server. Either delete your .config/ParaView files, or run
-dr.
Box.
X length 0.1
Y length 0.1
Z length 0.018
Center 1, 0.05, 0.01.
Apply.
Now, rotate the slab. You will see the center cross appear and disappear.
Pretty sure this is not a driver bug - it shows up with RGS (hardware rendered) and NX (software rendered.)https://gitlab.kitware.com/paraview/paraview/-/issues/14267behavior of views when displaying vector fields2018-08-08T22:26:22-04:00Kitware Robotbehavior of views when displaying vector fields**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14267). Further discussion may take place here.**
---
Hello,
Some of my users complain about a behavior of the views when dis...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14267). Further discussion may take place here.**
---
Hello,
Some of my users complain about a behavior of the views when displaying vector fields. I am trying to explain this behavior by a simple example :
1) Create a PacMan using the menu "Sources"
2) Open a second "3D View" and display also the PacMan inside
3) In the first view chose to visualize the field "Normals" and its component "X"
4) Go to the second view and display also "Normals" but choosing "Y" as a component
5) If you now click in the first view this view changes its selection to the "Y" component !
I would like to know if this is just a bug or the behavior is there to respect some visualization philosophy.
Cheers,
Alejandro.https://gitlab.kitware.com/paraview/paraview/-/issues/14265Exodus writer fails with polyhedral data2023-06-15T14:07:22-04:00Kitware RobotExodus writer fails with polyhedral data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14265). Further discussion may take place here.**
---
Local server, master, Linux.
Open dataset fmaego.mesh.case, found in bug r...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14265). Further discussion may take place here.**
---
Local server, master, Linux.
Open dataset fmaego.mesh.case, found in bug report http://paraview.org/Bug/view.php?id=13338. Apply.
File/ Save Data, and write this out as an exodus dataset. ParaView/VTK will output lots of error verbiage, and then write out an empty file.
```
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 42
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 110
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 178
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 382
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 450
```W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/14264Show Frustrum fails2017-04-20T16:16:41-04:00Kitware RobotShow Frustrum fails**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14264). Further discussion may take place here.**
---
Linux, master, local server.
* disk_out_ref.exo, all vars on, Apply.
*...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14264). Further discussion may take place here.**
---
Linux, master, local server.
* disk_out_ref.exo, all vars on, Apply.
* Select cells through. Select something.
* View/ Selection Inspector/ Show Frustrum.
I don't think it is a crash, but Show Frustrum is useless and doesn't work.
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 389
vtkPVSessionCore (0x18d21e0): Object type: vtkPVRenderView, could not find requested method: "AddPropToRenderer"
or the method was called with incorrect arguments.
while processing
Message 0 = Invoke
Argument 0 = vtk_object_pointer {vtkPVRenderView (0x258b830)}
Argument 1 = string_value {AddPropToRenderer}
Argument 2 = vtk_object_pointer {vtkPVFrustumActor (0x39b1ac0)}
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/ParaViewCore/ServerImplementation/Core/vtkPVSessionCore.cxx, line 390
vtkPVSessionCore (0x18d21e0): Aborting execution for debugging purposes.
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 131
vtkSIProxy (0x25859f0): Error pushing property state: HiddenPropshttps://gitlab.kitware.com/paraview/paraview/-/issues/14263Trace recorder is broken2018-08-08T22:26:22-04:00Kitware RobotTrace recorder is broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14263). Further discussion may take place here.**
---
Master, Linux, local server.
Start ParaView.
Tools/ Start Trace. Erro...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14263). Further discussion may take place here.**
---
Master, Linux, local server.
Start ParaView.
Tools/ Start Trace. Error.
This needs to be fixed ASAP.
Error: Could not import vtkCommonComputationalGeometryPython
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/projects/viz/paraview/ParaView/4.1.0-alan2/Linux-eng-sci-rhel6-x86_64/lib/paraview-4.0/site-packages/paraview/smtrace.py", line 2, in <module>
import simple
File "/projects/viz/paraview/ParaView/4.1.0-alan2/Linux-eng-sci-rhel6-x86_64/lib/paraview-4.0/site-packages/paraview/simple.py", line 41, in <module>
import servermanager
File "/projects/viz/paraview/ParaView/4.1.0-alan2/Linux-eng-sci-rhel6-x86_64/lib/paraview-4.0/site-packages/paraview/servermanager.py", line 48, in <module>
import paraview, re, os, os.path, new, sys, atexit, vtk
File "/projects/viz/paraview/ParaView/4.1.0-alan2/Linux-eng-sci-rhel6-x86_64/lib/paraview-4.0/site-packages/paraview/vtk/__init__.py", line 7, in <module>
from vtkCommonCorePython import *
ImportError: No module named vtkCommonCorePythonhttps://gitlab.kitware.com/paraview/paraview/-/issues/14262Fix clang warnings2018-08-08T22:26:22-04:00Kitware RobotFix clang warnings**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14262). Further discussion may take place here.**
---
See http://open.cdash.org/viewBuildError.php?type=1&buildid=3019881**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14262). Further discussion may take place here.**
---
See http://open.cdash.org/viewBuildError.php?type=1&buildid=3019881https://gitlab.kitware.com/paraview/paraview/-/issues/14261Forward VTK to gerrit/master2018-08-08T22:26:22-04:00Kitware RobotForward VTK to gerrit/master**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14261). Further discussion may take place here.**
---
Forward VTK to gerrit/master**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14261). Further discussion may take place here.**
---
Forward VTK to gerrit/master