ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T10:46:42-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/14549NRRD file without end of line on last line eats all of memory2023-06-15T10:46:42-04:00Kitware RobotNRRD file without end of line on last line eats all of memory**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14549). Further discussion may take place here.**
---
Thank you for making an ASCII NRRD reader! I love it! It is a GREAT bene...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14549). Further discussion may take place here.**
---
Thank you for making an ASCII NRRD reader! I love it! It is a GREAT benefit for my vis class.
On 4.0.1, 4.1RC2 and 4.1 (on Windows and Linux), if you try to open the attached NRRD file, it will eat all of memory and die (maybe taking your machine with it).
You don't need to have the associated file; it hangs even before giving the Accept button. If you add a newline at the end of the file, it is fine.https://gitlab.kitware.com/paraview/paraview/-/issues/14541Possibly faullty data offset counting for Base64 encoded data in AppendData-s...2023-06-15T10:44:46-04:00Kitware RobotPossibly faullty data offset counting for Base64 encoded data in AppendData-section**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14541). Further discussion may take place here.**
---
Dear All,
Paraview 13.12.0 (32bit) seems to read VTK AppendedData in a
p...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14541). Further discussion may take place here.**
---
Dear All,
Paraview 13.12.0 (32bit) seems to read VTK AppendedData in a
peculiar and possibly faulty way.
According to the documentation of VTK XML format, the data
(later the raw data) of each
```
<DataArray .... format="appended" offset="N"/>
<DataArray .... format="appended" offset="N2"/>
<DataArray .... format="appended" offset="N3"/>
```
section is stored in <AppendedData> section as follows: It
starts with the total length of the data expressed as int32
(MMMM). It is followed by the data from each of the
DataArray sections in a continuous manner (AAAA,BBBB,CCCCC..):
```
<AppendedData encoding="raw">
_MMMMAAAAAAAAAAAAAAAABBBBCCCCCCCCCCCCCCCCCCCC
</DataArray>
```
The offset expresses the location of each section; N bytes
offset from the beginning of the first data section (N=0 ~
33th bit). Here N_A=0,N_B=16,N_C=20, M=40.
However, if the data is base64 encoded,
```
<AppendedData encoding="Base64">
_Base64[MMMMAAAAAAAAAAAAAAAABBBBCCCCCCCCCCCCCCCCCCCC]
</DataArray>
```
every byte (8bits) in the encoded string correspond to six
bytes of the raw data. Again the offset is based again at
the start of the actual data (N=0 is now the 45th bit).
However, the offset N correspond to N chars of encoded
array, that is 6N bit or 3N/4 bytes of raw data.
As a result the offset does not in general correspond to any
byte-boundary of the raw data and never corresponds to a
char-boundary of the encoded data.
In addition, to allow reference to the start of a data
section, previous data has to be padded to a multiple of 3
bytes; or as float32 corresponds to 4 bytes, the data has to
padded to a multiple of 12 bytes (3xfloats32).
Questions:
1) Is this true for VTK+base64 at large or only paraview
2) If not for which versions of VTK / paraview
3) Is this a stable arrangement - should I write my code to adhere?
I attach an example of the bit alignment and a vts-file for
testing (without debugger, change the alignment of rho-data
and save-data in csv). This is data is for debugging reasons
stored as UInt8, but the phenomenon is independent of the
data type.
```
Paraview 13.12.0 (32bit)
Linux 3.2.0-58-generic-pae #88-Ubuntu SMP
2013 i686 i686 i386 GNU/Linux
```
With preciation for any comments.
J.
```
EXAMPLE OF THE ALIGNMENT
========================================
|running bit
|C = byte.bit encoded data
|D = byte.bit orginal data
|comment
========================================
---- byte 0 in base64 code -------
0 0.8
1 0.7
2 0.6 0.8 data length, byte 0
3 0.5 0.7
4 0.4 0.6
5 0.3 0.5
6 0.2 0.4
7 0.1 0.3
---- byte 1 in base64 code -------
8 1.8
9 1.7
10 1.6 0.2
11 1.5 0.1
12 1.4 1.8 data length, byte 1
13 1.3 1.7
14 1.2 1.6
15 1.1 1.5
---- byte 2 in base64 code -------
16 2.8
17 2.7
18 2.6 1.4
19 2.5 1.3
20 2.4 1.2
21 2.3 1.1
22 2.2 2.8 data length, byte 2
23 2.1 2.7
---- byte 3 in base64 code -------
24 3.8
25 3.7
26 3.6 2.6
27 3.5 2.5
28 3.4 2.4
29 3.3 2.3
30 3.2 2.2
31 3.1 2.1
---- byte 4 in base64 code -------
32 4.8
33 4.7
34 4.6 3.8 data length, byte 3
35 4.5 3.7
36 4.4 3.6
37 4.3 3.5
38 4.2 3.4
39 4.1 3.3
---- byte 5 in base64 code -------
40 5.8
41 5.7
42 5.6 3.2
43 5.5 3.1
44 5.4 4.8 offset=0; data byte 0;
45 5.3 4.7
46 5.2 4.6
47 5.1 4.5
---- byte 6 in base64 code -------
48 6.8
49 6.7
50 6.6 4.4
51 6.5 4.3
52 6.4 4.2 offset=1;
53 6.3 4.1
54 6.2 5.8 data byte 1;
55 6.1 5.7
---- byte 7 in base64 code -------
56 7.8
57 7.7
58 7.6 5.6
59 7.5 5.5
60 7.4 5.4 offset=2;
61 7.3 5.3
62 7.2 5.2
63 7.1 5.1
---- byte 8 in base64 code -------
64 8.8
65 8.7
66 8.6 6.8 data byte 2;
67 8.5 6.7
68 8.4 6.6 offset=3;
69 8.3 6.5
70 8.2 6.4
71 8.1 6.3
---- byte 9 in base64 code -------
72 9.8
73 9.7
74 9.6 6.2
75 9.5 6.1
76 9.4 7.8 offset=4; data byte 3;
77 9.3 7.7
78 9.2 7.6
79 9.1 7.5
---- byte 10 in base64 code -------
80 10.8
81 10.7
82 10.6 7.4
83 10.5 7.3
84 10.4 7.2 offset=5;
85 10.3 7.1
86 10.2 8.8 data byte 4;
87 10.1 8.7
---- byte 11 in base64 code -------
88 11.8
89 11.7
90 11.6 8.6
91 11.5 8.5
92 11.4 8.4 offset=6;
93 11.3 8.3
94 11.2 8.2
95 11.1 8.1
---- byte 12 in base64 code -------
96 12.8
97 12.7
98 12.6 9.8 data byte 5;
99 12.5 9.7
100 12.4 9.6 offset=7;
101 12.3 9.5
102 12.2 9.4
103 12.1 9.3
---- byte 13 in base64 code -------
104 13.8
105 13.7
106 13.6 9.2
107 13.5 9.1
108 13.4 10.8 offset=8; data byte 6;
109 13.3 10.7
110 13.2 10.6
111 13.1 10.5
112 13.0 10.4
```https://gitlab.kitware.com/paraview/paraview/-/issues/14536Recording a test for setting a background image does not work.2020-05-07T09:38:12-04:00Kitware RobotRecording a test for setting a background image does not work.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14536). Further discussion may take place here.**
---
Record a test:
paraview -dr
Tools / Record Test...
Choose the file wher...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14536). Further discussion may take place here.**
---
Record a test:
paraview -dr
Tools / Record Test...
Choose the file where to save the test
Set Background type to 'Image'
Choose 'Load...'
In the file dialog choose ParaView/Data/NE2_ps_bath.png
Press 'Stop recording'
Press 'Disconnect'
Play the test:
Tools / Play Test...
Choose the test file you just saved.
You'll get the following error:
Couldn't find object "pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/ViewFrame/ProxyPanel/BackgroundEditor/stackedWidget/page_1/Color/0QColorDialog0"
Found up to "pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/ViewFrame/ProxyPanel/BackgroundEditor/stackedWidget/page_1/Color"
https://gitlab.kitware.com/paraview/paraview/-/issues/14472Add test for --connect-id flag2020-05-04T07:34:29-04:00Kitware RobotAdd test for --connect-id flag**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14472). Further discussion may take place here.**
---
We need to add a test to the dashboard testing if the --connect-id flag is...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14472). Further discussion may take place here.**
---
We need to add a test to the dashboard testing if the --connect-id flag is working correctly. A great test for this is found in bug number 14451.
https://gitlab.kitware.com/paraview/paraview/-/issues/14471Find Data dialog should be accessible when not built with Python2023-06-15T10:49:19-04:00Kitware RobotFind Data dialog should be accessible when not built with Python**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14471). Further discussion may take place here.**
---
Find Data dialog should be accessible when not built with Python since it'...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14471). Further discussion may take place here.**
---
Find Data dialog should be accessible when not built with Python since it's "viewer" capabilities don't depend on Pythonhttps://gitlab.kitware.com/paraview/paraview/-/issues/14469No support for Gradient Opacity in ParaView VolumeRendering2021-03-23T09:44:38-04:00Kitware RobotNo support for Gradient Opacity in ParaView VolumeRendering**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14469). Further discussion may take place here.**
---
Paraview does not expose some features that are available in the vtk Mappe...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14469). Further discussion may take place here.**
---
Paraview does not expose some features that are available in the vtk Mappers. Gradient opacity is a very useful feature for volume rendering and it should be added to paraview.https://gitlab.kitware.com/paraview/paraview/-/issues/14434Provide support for multiple baseline images and browser to pvweb testing mod...2020-05-04T07:23:35-04:00Kitware RobotProvide support for multiple baseline images and browser to pvweb testing module.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14434). Further discussion may take place here.**
---
ParaViewWeb testing needs the ability to test against multiple baseline im...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14434). Further discussion may take place here.**
---
ParaViewWeb testing needs the ability to test against multiple baseline images when do image-based comparisons. Also required is the ability to run a single test script against all known or supported browsers. In to provide this, we need to integrate python functionality explored by Roni Choudhury into the current vtk.web.testing module.https://gitlab.kitware.com/paraview/paraview/-/issues/14422Add option to label points by coordinates2020-06-09T21:53:24-04:00Kitware RobotAdd option to label points by coordinates**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14422). Further discussion may take place here.**
---
Points and cells can be labeled by the values of variables. The variable ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14422). Further discussion may take place here.**
---
Points and cells can be labeled by the values of variables. The variable to use for labeling is selected in the Selection Inspector (or Selection Display Inspector in 4.1). It would also be very helpful to have an option to label points by their x, y, z coordinates.https://gitlab.kitware.com/paraview/paraview/-/issues/14403Cannot choose "Process ID" in Find Data dialog2020-05-04T07:17:24-04:00Kitware RobotCannot choose "Process ID" in Find Data dialog**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14403). Further discussion may take place here.**
---
+ Run ParaView with parallel pvserver (> 1)
+ Create Sphere
+ Find Data,...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14403). Further discussion may take place here.**
---
+ Run ParaView with parallel pvserver (> 1)
+ Create Sphere
+ Find Data, Find all cells with ID 12. -- works correctly
+ Now try to do the same with ID 12 and Process is 1 -- no way to do that.https://gitlab.kitware.com/paraview/paraview/-/issues/14400verbose CTH AMR warnings2020-05-04T07:16:25-04:00Kitware Robotverbose CTH AMR warnings**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14400). Further discussion may take place here.**
---
When running multiple remote server with CTH AMR data, ParaView is spewing...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14400). Further discussion may take place here.**
---
When running multiple remote server with CTH AMR data, ParaView is spewing horrendously large numbers of warnings if you are running with more processes than input files. Mu current run just put out 40,000 lines of these warnings.
Please either put the warning out once, or not at all. If the developer feels that this warning should be in the code to help debug, please only print it out for debug builds.
File is vtkAMRInformation.cxx, line 314. It is as follows:
unsigned int vtkAMRInformation::GetNumberOfDataSets(unsigned int level) const
{
if( level>= this->GetNumberOfLevels())
{
cerr<<"WARNING: No data set at this level"<<endl;
return 0;
}
return this->NumBlocks[level+1]-this->NumBlocks[level];
}
https://gitlab.kitware.com/paraview/paraview/-/issues/14390Attempted null pointer dereference for Particle Tracer with grouped lines sou...2024-03-07T20:47:38-05:00Kitware RobotAttempted null pointer dereference for Particle Tracer with grouped lines sources**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14390). Further discussion may take place here.**
---
4.0.1 + git/master, Linux x86_64 debug build, builtin mode
Sources - Line...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14390). Further discussion may take place here.**
---
4.0.1 + git/master, Linux x86_64 debug build, builtin mode
Sources - Line - P1: (0,0,1), P2: (1,0,1) - Apply
Sources - Line - P2: (0,0,1), P2: (0,1,1) - Apply
Mark both line sources.
Filters - Alphabetical - Group Datasets
Sources - Time Source - Apply
Filters - Alphabetical - Random Vectors - Apply
Filters - Alphabetical - ParticleTracer - Input: RandomVectors1, Seed Source: GroupDatasets1 - Ok - Apply
=> Program received signal SIGSEGV, Segmentation fault.
0x00007ffff09daa55 in vtkPVPostFilter::RequestData (this=0x404b890, inputVector=0x404e750, outputVector=0x404d780)
at /ParaView.git/ParaViewCore/VTKExtensions/Core/vtkPVPostFilter.cxx:270
270 csOutput->CopyStructure(csInput);
(gdb) print csOutput
$1 = (vtkCompositeDataSet *) 0x0
Either the if-condition in ParaViewCore/VTKExtensions/Core/vtkPVPostFilter.cxx:263
if (!csInput && !csOutput)
or the else-condition in line 268 clearly needs some tweaking to ensure csOutput does not get dereferenced if it is a null pointer.
(To work around the bug, use filter AppendGeometry instead of GroupDatasets.)5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/14361file series reader not working properly for 5000 vtu files2021-03-23T09:41:59-04:00Kitware Robotfile series reader not working properly for 5000 vtu files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14361). Further discussion may take place here.**
---
If I create the 5000 vtu files with the following python script I have tro...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14361). Further discussion may take place here.**
---
If I create the 5000 vtu files with the following python script I have trouble reading them back in to paraview:
===============
try: paraview.simple
except: from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()
Wavelet1 = Wavelet()
Wavelet1.WholeExtent = [0, 5, 0, 5, 0, 5]
Clip1 = Clip( ClipType="Plane" )
Clip1.Scalars = ['POINTS', 'RTData']
Clip1.ClipType.Origin = [2.5, 2.5, 2.5]
Clip1.ClipType = "Plane"
Clip1.Value = 132.19195199012756
Calculator1 = Calculator()
w = XMLUnstructuredGridWriter()
for i in range(5001):
Calculator1.Function = str(i)
name = "phi0" + format(i, "05d") + "000000.vtu"
print name, Calculator1.Function
w.FileName = name
w.UpdatePipeline()
============
The problem is easily demonstrated by loading in the files and then selecting a point and using the plot selection over time. This was done with a ParaView version from the repo around 10/15/2013. The image is the result that I got but should be a straight line.https://gitlab.kitware.com/paraview/paraview/-/issues/14353Problems reading 2nd order mixed meshes in xdmf format2023-06-15T11:00:33-04:00Kitware RobotProblems reading 2nd order mixed meshes in xdmf format**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14353). Further discussion may take place here.**
---
<?xml version="1.0" ?>
<Xdmf>
<Domain Name="Unnamed">
<Grid Name="Mesh">
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14353). Further discussion may take place here.**
---
<?xml version="1.0" ?>
<Xdmf>
<Domain Name="Unnamed">
<Grid Name="Mesh">
<Geometry GeometryType="XYZ">
<DataItem Format="XML" Dimensions="10 3">
0.0 0.0 0.0
1.0 0.0 0.0
0.0 1.0 0.0
0.0 0.0 1.0
0.5 0.0 0.0
0.5 0.5 0.0
0.0 0.5 0.0
0.0 0.0 0.5
0.5 0.0 0.5
0.0 0.5 0.5
</DataItem>
</Geometry>
The following valid XDMF file causes an error when imported into ParaView 4.0.1:
<Topology TopologyType="Mixed" NumberOfElements="1" >
<DataItem Format="XML" DataType="Int" Dimensions="11">
26 0 1 2 3 4 5 6 7 8 9
</DataItem>
</Topology>
</Grid>
</Domain>
</Xdmf>https://gitlab.kitware.com/paraview/paraview/-/issues/14246Measure distance between nodes2018-08-08T22:25:01-04:00Kitware RobotMeasure distance between nodes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14246). Further discussion may take place here.**
---
We need a tool that will allow a user to measure the distance between two ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14246). Further discussion may take place here.**
---
We need a tool that will allow a user to measure the distance between two nodes. I have a ParaView user that uses EnSight when this functionality is needed.
https://gitlab.kitware.com/paraview/paraview/-/issues/14236vtkImplicitFunctionToImageStencil doesn't work in ParaView2023-06-15T08:30:17-04:00Kitware RobotvtkImplicitFunctionToImageStencil doesn't work in ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14236). Further discussion may take place here.**
---
+ Rebuild ParaView with Module_vtkImagingStencil Cmake variable ON
+ Load ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14236). Further discussion may take place here.**
---
+ Rebuild ParaView with Module_vtkImagingStencil Cmake variable ON
+ Load attached XML as a plugin.
+ Try creating the "Implicit-Function To Image-Stencil" source.
+ You'll get errors:
Generic Warning: In /home/utkarsh/Kitware/ParaView3/ParaView/VTK/Common/DataModel/vtkDataObjectTypes.cxx, line 303
NewDataObject(): You are trying to instantiate DataObjectType "vtkImageStencilData" which does not exist.
ERROR: In /home/utkarsh/Kitware/ParaView3/ParaView/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 658
vtkPVCompositeDataPipeline (0x20b9d80): Algorithm vtkImplicitFunctionToImageStencil(0x26c9770) did not create output for port 0 when asked by REQUEST_DATA_OBJECT and does not specify a concrete DATA_TYPE_NAME.
Generic Warning: In /home/utkarsh/Kitware/ParaView3/ParaView/VTK/Common/DataModel/vtkDataObjectTypes.cxx, line 303
NewDataObject(): You are trying to instantiate DataObjectType "vtkImageStencilData" which does not exist.https://gitlab.kitware.com/paraview/paraview/-/issues/14207Contour filter causes segmentation fault during insitu operation.2020-05-04T07:04:56-04:00Kitware RobotContour filter causes segmentation fault during insitu operation.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14207). Further discussion may take place here.**
---
Placing a contour filter in an in-situ python file appears to cause a segm...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14207). Further discussion may take place here.**
---
Placing a contour filter in an in-situ python file appears to cause a segmentation fault, at least when done in the manner of the python file generated by the insitu coprocessing plug in.
To replicate error do the following:
Load a dataset, presumably an exodus file.
Apply a contour filter with a single contour value at a reasonable setting (e.g. at halfway between the min and the max of a given scalar point value).
Export an insitu python file using the coprocessing plugin.
Try to run insitu using the produced python file. A segmentation violation results. In particular, it occurs when the python file tries to execute the Show() function after setting the active source to the given contour operation. For example in my python file we have:
SetActiveSource(Contour1)
DataRepresentation2 = Show()
And the segmentation violation occurs when Show() is executed. SetActiveSource() does not cause a segmentation violation, and the creation of the Contour1 filter earlier in the operation does not cause a segmentation violation.
https://gitlab.kitware.com/paraview/paraview/-/issues/14153xdmf reader crash using stride2023-08-31T04:55:06-04:00Kitware Robotxdmf reader crash using stride**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14153). Further discussion may take place here.**
---
a simple ascii xdmf file make the reader crash when playing with the strid...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14153). Further discussion may take place here.**
---
a simple ascii xdmf file make the reader crash when playing with the stride parameter.
to reproduce set Stride to 2 2 1
----- file Structured_Ascci_2D.xdmf ----
```
<?xml version="1.0" ?>
<!DOCTYPE Xdmf SYSTEM "Xdmf.dtd" []>
<Xdmf Version="2.0" xmlns:xi="http://www.w3.org/2001/XInclude" >
<Domain Name="tests/Structured_Ascii.pxdmf">
<Grid Name="PGD1" >
<Topology TopologyType="2DCORECTMESH" Dimensions="1 10 10" />
<Geometry GeometryType="ORIGIN_DXDYDZ">
<DataItem Name="Origin" Format="XML" NumberType="Float" Dimensions="3">
0 0 0
</DataItem>
<DataItem Name="Spacing" Format="XML" NumberType="Float" Dimensions="3">
1 1 1
</DataItem>
</Geometry>
<Attribute Name="dep_x_0" Center="Node" AttributeType="Scalar" >
<DataItem Format="XML" NumberType="Float" Precision="8" Dimensions="1 10 10">
10 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 6.0 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 7.0 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 8.0 8.1 8.1 8.3 8.4 8.5 8.6 8.6 8.8 8.9 9.0 9.1 9.1 9.3 9.4 9.5 9.6 9.6 9.8 9.9 0.0
</DataItem>
</Attribute>
</Grid>
</Domain>
</Xdmf>
```Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/14136Paraview aborts when launched in home directory2021-03-23T09:34:04-04:00Kitware RobotParaview aborts when launched in home directory**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14136). Further discussion may take place here.**
---
When attempting to launch paraview-4.0.1 in my home directory (~), I get t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14136). Further discussion may take place here.**
---
When attempting to launch paraview-4.0.1 in my home directory (~), I get the following error: "No current working directory \n Aborted". Any other directory (including subdirectories of ~) seem to work. The same error occurs with older versions of Paraview (tested 3.6.1, 3.8.0, 3.12 and 3.98).
Operating system is SuSE Linux Enterprise Desktop 11.2.
The home directory is networked, I believe through SAMBA (I'm just a user in a
corporate environment).https://gitlab.kitware.com/paraview/paraview/-/issues/14133Point Selection in Multi Slice View2021-03-23T09:33:27-04:00Kitware RobotPoint Selection in Multi Slice View**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14133). Further discussion may take place here.**
---
Point Selection in the multi slice view shouldn't be enabled.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14133). Further discussion may take place here.**
---
Point Selection in the multi slice view shouldn't be enabled.https://gitlab.kitware.com/paraview/paraview/-/issues/14084Inpractical rotation of 2d glyph triangle2021-03-24T16:59:20-04:00Kitware RobotInpractical rotation of 2d glyph triangle**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14084). Further discussion may take place here.**
---
Also in 4.0 RC1
The 2d glyph 'triangle' is isosceles triangle pointing up...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14084). Further discussion may take place here.**
---
Also in 4.0 RC1
The 2d glyph 'triangle' is isosceles triangle pointing upwards by its smallest angle. The glyph arrow, however, points to the right. When using these two glyphs for visualisation of an vector field, the arrows correctly points to the direction of flow, but to use triangles I have to rotate them 270 degrees.