ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-11-08T10:05:52-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22366Ensight Reader fails due to quotation marks around file names2023-11-08T10:05:52-05:00njwallaEnsight Reader fails due to quotation marks around file namesThe Ensight case reader fails to identify file names of referenced files (e.g. the *.geo and scalar files) when those filenames are within quotes in the *.case file. This can occur for files exported from ANSYS Fluent at least since 202...The Ensight case reader fails to identify file names of referenced files (e.g. the *.geo and scalar files) when those filenames are within quotes in the *.case file. This can occur for files exported from ANSYS Fluent at least since 2022, when ANSYS decided to put the internally-referenced filenames in quotes. Manually editing the .case file to remove the quotes (e.g. `"simulation-case.geo"` becomes `simulation-case.geo`) allows the file to be loaded without issue. A suggested fix would be to simply remove outer quotes when reading in a filename.https://gitlab.kitware.com/paraview/paraview/-/issues/21069Pipeline source gets stuck in broken state when REQUEST_DATA_OBJECT fails (v5...2021-12-22T19:11:08-05:00Lutz HofmannPipeline source gets stuck in broken state when REQUEST_DATA_OBJECT fails (v5.10.0-RC1)When the REQUEST_DATA_OBJECT request fails once for a filter in the pipeline, the pipeline source seems to get stuck in some invalid state where it is never updated again, even if its input is changed.
This does not seem happen for any ...When the REQUEST_DATA_OBJECT request fails once for a filter in the pipeline, the pipeline source seems to get stuck in some invalid state where it is never updated again, even if its input is changed.
This does not seem happen for any other request (REQUEST_INFORMATION, REQUEST_UPDATE_EXTENT, etc), where the pipeline source keeps working as expected even if such a request fails.
I originally discovered this bug when using "Extract Subset" on a filter that can change its output data object (e.g. Programmable Source), where the output data type changed from vtkImageData to vtkTable and back.
A "constructed" example is attached below.
Tested with v5.10.0-RC1. The issue is not present in v5.9.1.
### To Reproduce
(see screen capture below)
1. Load the following Python plugin: [MyFilter.py](/uploads/ff7418c97e0f3de866bbe96e63aaa0be/MyFilter.py)
<details><summary>My Filter</summary>
```python
from vtkmodules.vtkCommonDataModel import vtkDataObject, vtkDataSet
from vtkmodules.util.vtkAlgorithm import VTKPythonAlgorithmBase
from paraview.util.vtkAlgorithm import smproxy, smproperty, smdomain
from datetime import datetime
@smproxy.filter(label="My Filter")
@smproperty.input(name="Input")
class MyFilter(VTKPythonAlgorithmBase):
def __init__(self):
self._request_data_object_fail = False
self._dummy = False
VTKPythonAlgorithmBase.__init__(self)
@smproperty.intvector(label='RequestDataObject Fail', default_values=0)
@smdomain.xml('<BooleanDomain name="bool"/>')
def SetRequestDataObjectFail(self, b):
self._request_data_object_fail = b
self.Modified()
@smproperty.intvector(label='Dummy', default_values=0)
@smdomain.xml('<BooleanDomain name="bool"/>')
def SetDummy(self, b):
self._dummy = b
self.Modified()
def RequestDataObject(self, request, inInfo, outInfo):
if self._request_data_object_fail:
return 0
inp = vtkDataSet.GetData(inInfo[0], 0)
if not inp:
return 0
for i in range(self.GetNumberOfOutputPorts()):
output = vtkDataSet.GetData(outInfo, i)
if not output or not output.IsA(inp.GetClassName()):
outInfo.GetInformationObject(i).Set(
vtkDataObject.DATA_OBJECT(), inp.NewInstance())
return 1
def RequestData(self, request, inInfo, outInfo):
input0 = vtkDataSet.GetData(inInfo[0])
output = vtkDataSet.GetData(outInfo)
output.ShallowCopy(input0)
print('RequestData', datetime.now())
return 1
```
</details>
2. Create a few sources, attach "My Filter" to one of them
3. Checking/unchecking the "Dummy" property updates the filter as expected
4. Checking "RequestDataObject Fail" causes REQUEST_DATA_OBJECT to fail
5. Unchecking "RequestDataObject Fail" does not execute the filter anymore; changing the "Dummy" property also does not update it
6. Changing the filter's input does not recover its state (so far I have found no method that returns to a valid state)
![Peek_2021-10-29_10-49](/uploads/e4ee65f2cb046a627b00c5df0442c871/Peek_2021-10-29_10-49.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/21044Error reading large VTK files in the Windows version2023-06-28T03:03:03-04:00vmajorError reading large VTK files in the Windows versionI have large (3.5 Gb+) VTK files generated by our CFD software running on Ubuntu (WSL2 in Windows 11 in fact).
Paraview 5.10.0-RC1 running on Ubuntu WSL2 opens the file correctly, albeit the Nvidia virtualised driver tends to crash so I...I have large (3.5 Gb+) VTK files generated by our CFD software running on Ubuntu (WSL2 in Windows 11 in fact).
Paraview 5.10.0-RC1 running on Ubuntu WSL2 opens the file correctly, albeit the Nvidia virtualised driver tends to crash so I cannot actually use this method. Previously using previous versions of Paraview I successfully worked with the results files in native Ubuntu. The point is that our results files are not corrupted or faulty.
Paraview 5.10.0-RC1 running on Windows 11 while opening the same files reports the errors previously reported by others in other threads on the Paraview support forum and seems related to the issue #16019:
```
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
```
Summary of the issue:
- Linux ParaView is on ext4.
- Our native Linux CFD solver is on ext4 and the results directory is on ext4.
- Linux software and partitions are running and mounted under WSL2 on Windows 11.
- Windows ParaView is on an ntfs partition on the same Windows 11 machine that is running WSL2
- Linux ParaView can read and visualize the results data. Windows ParaView cannot read and visualize the results data.
Windows ParaView throws up errors with the large domain file (the 3.5 Gb one) when I try to read it from the ext4, or when I copy this file to an ntfs partition. Both files show the same error reading the file and the result cannot be visualized.
Windows ParaView can read the smaller 162 Mb file both from ext4 and the ntfs partitions.
Here is the download link for the 3.5 Gb file (zipped to 2.48Gb): https://velocite-public.s3.fr-par.scw.cloud/domain_00010000.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=SCW4RPBSRG82A0JQQSTB%2F20211019%2Ffr-par%2Fs3%2Faws4_request&X-Amz-Date=20211019T054859Z&X-Amz-Expires=3596&X-Amz-Signature=f9ed586080046ca85380cfe70218dc5c1df575efba945601c56462b31814dd4d&X-Amz-SignedHeaders=hosthttps://gitlab.kitware.com/paraview/paraview/-/issues/20851Error in Gradient Of Unstructured Grid Data Set when using fields with differ...2023-10-24T07:48:09-04:00Gonzalo SáezError in Gradient Of Unstructured Grid Data Set when using fields with different number of components**Tested in Paraview 5.9.1 + Windows**
## Steps to reproduce
1. `Unstructured Cell Types`
2. `Calculator` -> Expression -> `DistanceToCenter*iHat` (this field is stored in `Result` and has 3 components)
3. `Gradient Of Unstructured Gri...**Tested in Paraview 5.9.1 + Windows**
## Steps to reproduce
1. `Unstructured Cell Types`
2. `Calculator` -> Expression -> `DistanceToCenter*iHat` (this field is stored in `Result` and has 3 components)
3. `Gradient Of Unstructured Grid Data Set`
4. The `Gradients` field (computed by default from the `DistanceToCenter` field) will have three components as expected
5. Change the `Scalar Array` of the `Gradient Of Unstructured Grid Data Set` filter to `Result`
6. The resulting **`Gradients` field only has 3 components while 9 are expected** since `Result` is a vector
Besides, it seems that ParaView enters a strange after state after 6. probably due to some UB or out of bounds issue?
Similar behavior can be observed when using first `Result` to compute the `Gradients` field and then changing `DistanceToCenter` in `ScalarArray`.https://gitlab.kitware.com/paraview/paraview/-/issues/20832Pink lines in AVI animations on Linux2023-07-07T14:22:29-04:00Patrick AveryPink lines in AVI animations on LinuxUsing the latest Linux nightly (that was built today, July 7, 2021), I am running into an issue exporting AVI animations via FFMPEG. There are horizontal pink lines being drawn across the frames.
![Screenshot_from_2021-07-07_15-58-00](/...Using the latest Linux nightly (that was built today, July 7, 2021), I am running into an issue exporting AVI animations via FFMPEG. There are horizontal pink lines being drawn across the frames.
![Screenshot_from_2021-07-07_15-58-00](/uploads/9943c6d94dc473a7ce5eb7b4da35d901/Screenshot_from_2021-07-07_15-58-00.png)
[example.avi](/uploads/bd8caeae8861ba1d7a1a9d2392acc016/example.avi)
To reproduce:
1. Create a cone and show it
2. Click "File"->"Save Animation..."
3. Select FFMPEG AVI files for the filter, and choose "example.avi" for the file name.
4. Use the default animation options (I'm pasting mine below).
5. Open up the video, and you can see pink lines.
![settings](/uploads/a862ca8c36109cd642cd48d180620253/settings.png)
I did not test other platforms for this issue.
I am also running into this same issue exporting AVI files via the Looking Glass plugin.https://gitlab.kitware.com/paraview/paraview/-/issues/20329EnSight reader can't open quoted files names2023-03-27T11:27:09-04:00Denis TelnovEnSight reader can't open quoted files namesIf in the `.case` file the data files names quoted with `"`, like
```
FORMAT
type: ensight gold
GEOMETRY
model: "CD1-case2b-CO2src-1-34000.geo"
VARIABLE
scalar per node: cff_co2_mmhg "CD1-case2b-CO2src-1-34000.scl1"
scala...If in the `.case` file the data files names quoted with `"`, like
```
FORMAT
type: ensight gold
GEOMETRY
model: "CD1-case2b-CO2src-1-34000.geo"
VARIABLE
scalar per node: cff_co2_mmhg "CD1-case2b-CO2src-1-34000.scl1"
scalar per node: cff_velmag_ftpm "CD1-case2b-CO2src-1-34000.scl2"
vector per node: velocity "CD1-case2b-CO2src-1-34000.vel"
```
then the paraview yelds error:
```
ERROR: In /home/buildslave/dashboards/buildbot/paraview_release-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/IO/EnSight/vtkGenericEnSightReader.cxx, line 437
vtkPGenericEnSightReader (0xc181aa0): Unable to open file: /home/denis/tmp/test/"CD1-case2b-CO2src-1-34000.geo"
Warning: In /home/buildslave/dashboards/buildbot/paraview_release-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/IO/EnSight/vtkGenericEnSightReader.cxx, line 438
vtkPGenericEnSightReader (0xc181aa0): Assuming binary file.
```
because of symbol `"` inside the resulted file name.https://gitlab.kitware.com/paraview/paraview/-/issues/20219pqAnimationModel assert failure and stackoverflow while moving the timebar in...2023-12-20T12:37:58-05:00Guillaume GindrepqAnimationModel assert failure and stackoverflow while moving the timebar in "SnapToTimeSteps" in debug mode.pqAnimationModel assert failure and stackoverflow while moving the timebar in "SnapToTimeSteps" in debug mode.
It happens when no temporal dataset is loaded.
Steps to reproduce:
* Launch Paraview in Debug mode
* View -> Animation View...pqAnimationModel assert failure and stackoverflow while moving the timebar in "SnapToTimeSteps" in debug mode.
It happens when no temporal dataset is loaded.
Steps to reproduce:
* Launch Paraview in Debug mode
* View -> Animation View
* Switch to "Snap To TimeSteps" mode
* Click and drag the time bar
* Assert failure and stackoverflow
```sh
Debug Error!
Program: C:\Qt\5.15.0\msvc2019_64\bin\Qt5Cored.dll
Module: 5.15.0
File: C:\Qt\5.15.0\msvc2019_64\include\QtCore/qlist.h
Line: 579
ASSERT failure in QList<T>::operator[]: "index out of range", file C:\Qt\5.15.0\msvc2019_64\include\QtCore/qlist.h, line 579
```
The callstack points to this call > pqAnimationModel::timeFromTick(int tick) Line 281 C++https://gitlab.kitware.com/paraview/paraview/-/issues/19668VTK issue fixed 5 months ago seems to persist in Paraview 5.72020-05-05T02:59:38-04:00Yale LeeVTK issue fixed 5 months ago seems to persist in Paraview 5.7An issue has been created on VTK repository concerning a [bug](https://gitlab.kitware.com/vtk/vtk/issues/17682) in the histogram functionality. This has been fixed **within** VTK and supposedly included in VTK 8.
Yet, Paraview 5.7.0 st...An issue has been created on VTK repository concerning a [bug](https://gitlab.kitware.com/vtk/vtk/issues/17682) in the histogram functionality. This has been fixed **within** VTK and supposedly included in VTK 8.
Yet, Paraview 5.7.0 still contains that bug.
FYI: @pppebayhttps://gitlab.kitware.com/paraview/paraview/-/issues/19664PV5.8-RC2: Plane Widgets showing when Raytracing is enabled2023-02-22T05:41:35-05:00Jean M. FavrePV5.8-RC2: Plane Widgets showing when Raytracing is enabledThe attached Python script demonstrates how 3D widgets such as a Plane widget are always drawn when Raytracing is turned on, when using a layout with more than one RenderView [3Dwidgets.py](/uploads/5247f22248413cdbd442c5da6f0de8ff/3Dwid...The attached Python script demonstrates how 3D widgets such as a Plane widget are always drawn when Raytracing is turned on, when using a layout with more than one RenderView [3Dwidgets.py](/uploads/5247f22248413cdbd442c5da6f0de8ff/3Dwidgets.py)https://gitlab.kitware.com/paraview/paraview/-/issues/19487MPIEXEC PRe and POSTFLAGS ignored2020-12-16T16:36:24-05:00Jean M. FavreMPIEXEC PRe and POSTFLAGS ignoredI have set
`MPIEXEC_POSTFLAGS:STRING=--oversubscribe
MPIEXEC_PREFLAGS:STRING=--oversubscribe`
but they seem completely ignored in AutoMPI load.I have set
`MPIEXEC_POSTFLAGS:STRING=--oversubscribe
MPIEXEC_PREFLAGS:STRING=--oversubscribe`
but they seem completely ignored in AutoMPI load.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/18552OpenVR Plugin issues2022-12-21T08:18:28-05:00Mathieu Westphal (Kitware)OpenVR Plugin issuesA few issues in the OpenVR plugin :
"Edit Fields" :
* Unclear what it is doing
"Select Scalar to view" :
* Once a scene has been set, only the sclar from this scene will ever be available, even if some are added or removed before s...A few issues in the OpenVR plugin :
"Edit Fields" :
* Unclear what it is doing
"Select Scalar to view" :
* Once a scene has been set, only the sclar from this scene will ever be available, even if some are added or removed before sending to OpenVR again
* When showing a scalar that has not been shown in ParaView, the color map is incorrect
"Taking a measurement" :
* Once taking a measurement has been used, there is no way to get out of this mode
* When a measurement is shown, other mode (like cropping) applies to the measurement, not the dataset
"Probe Mode" :
* It is the default for some reason, instead of grabbing the geometry
* Does not work well with wolume rendering
* the label ends up hidden in the geometry
ParaView :
Once the scene is sent to OpenVR, the render view in ParaView does not update itself.
@ken\-martin
tested with ParaView-5.6.0-RC2-312-gd2c37aeef2-Qt5-Windows-msvc2015-64bithttps://gitlab.kitware.com/paraview/paraview/-/issues/18278Loading Python Module Results in Error2020-09-22T14:04:46-04:00chart3388Loading Python Module Results in ErrorFollowing the Tutorial found on the Paraview - Embedding Python Source as Modules (https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Embedding_Python_Source_as_Modules) it was discovered that this throws an error upon loading the plugi...Following the Tutorial found on the Paraview - Embedding Python Source as Modules (https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Embedding_Python_Source_as_Modules) it was discovered that this throws an error upon loading the plugin with paraview:
`exec(code in module.__dict__)
TypeError: exec: arg 1 must be a string, file, or code object`
Looking into the issue looks like it is coming from Wrapping/Python/paraview/servermanager.py , class _ModuleLoader(object)
```
if moduleInfo.GetIsPackage:
module.__path__ = moduleInfo.GetFullName()
code = compile(moduleInfo.GetSource(), module.__file__, 'exec')
exec (code in module.__dict__)
return module
```
removing the parenthesis around from the exec resolves the issue:
```
if moduleInfo.GetIsPackage:
module.__path__ = moduleInfo.GetFullName()
code = compile(moduleInfo.GetSource(), module.__file__, 'exec')
exec code in module.__dict__
return module
```https://gitlab.kitware.com/paraview/paraview/-/issues/17721Paraview 5.4 crashes X on Ubuntu Gnome 16.04 with Point Gaussian2022-04-11T10:57:36-04:00Arno MayrhoferParaview 5.4 crashes X on Ubuntu Gnome 16.04 with Point GaussianSteps to reproduce:
Open the file: [parts.tar.gz](/uploads/72b9de64334640d0080bd95e55fe05f6/parts.tar.gz)
Set display to "Point Gaussian"
In the Point Gaussian options set radius to 1, preset to sphere, array to radius and then tick "...Steps to reproduce:
Open the file: [parts.tar.gz](/uploads/72b9de64334640d0080bd95e55fe05f6/parts.tar.gz)
Set display to "Point Gaussian"
In the Point Gaussian options set radius to 1, preset to sphere, array to radius and then tick "use scale array". (Another bug for me: I have to also click on "Edit" (Scale transfer function) and close the dialogue to get a proper display.)
Next switch the array to type (or id)
Watch the world burn, i.e. for me: all screens go black and X locks up (seen when sshing into the machine).
Some colleagues of mine using Mir (default Ubuntu) report freezing without black screens or in the best case ParaView crashes.https://gitlab.kitware.com/paraview/paraview/-/issues/17589Crinkle Slice with Value Range does not work2020-05-06T08:18:07-04:00Emanuele LeggioCrinkle Slice with Value Range does not workWith Value Range you can get more than one slice with one command but if you want to get all the cells intersected by the set of planes with the "Crinkle Slice" option does not work.
Is this behavior normal?With Value Range you can get more than one slice with one command but if you want to get all the cells intersected by the set of planes with the "Crinkle Slice" option does not work.
Is this behavior normal?https://gitlab.kitware.com/paraview/paraview/-/issues/17483ParaView is passing truncated time values to filters2022-04-12T15:45:15-04:00Shawn WaldonParaView is passing truncated time values to filtersTo reproduce:
1. open the can.ex2 data file
2. create an annotate time source and set its time format to `%10.20f` to see the full time value being passed to filters
3. Go to timestep 5
The annotate time filter shows `0.0004999190000000...To reproduce:
1. open the can.ex2 data file
2. create an annotate time source and set its time format to `%10.20f` to see the full time value being passed to filters
3. Go to timestep 5
The annotate time filter shows `0.00049991900000000004` (and all filters are requested to get this time), but the timestep value in the file is `0.00049991923151537776`. This difference can mess up filters that are comparing the time requested to the timesteps in the input.https://gitlab.kitware.com/paraview/paraview/-/issues/16872Cleanup ParaView installations on Windows2021-03-19T09:06:26-04:00Utkarsh AyachitCleanup ParaView installations on Windows- [ ] remove `<prefix>/lib/paraview-$version/site-packages`. That should just move to `<prefix>/bin/Lib/site-packages`.
- [ ] `data`, `doc`, etc. stay under `<prefix>`.
- [ ] plugins are currently under `<prefix>/bin/`. (investigate movi...- [ ] remove `<prefix>/lib/paraview-$version/site-packages`. That should just move to `<prefix>/bin/Lib/site-packages`.
- [ ] `data`, `doc`, etc. stay under `<prefix>`.
- [ ] plugins are currently under `<prefix>/bin/`. (investigate moving them to a subdir under `bin`)
- [ ] add documentation for what goes where so that we can refer developer to it when adding any new install rules.
SDK notes:
- [ ] need to figure out SDK installs.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/16795Python syntax highlighter can crash when Script has syntax errors2020-05-06T09:02:26-04:00Kitware RobotPython syntax highlighter can crash when Script has syntax errors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16795). Further discussion may take place here.**
---
Launch ParaView
Add Python View
Enter some text in the Script text entry...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16795). Further discussion may take place here.**
---
Launch ParaView
Add Python View
Enter some text in the Script text entry
Click outside the text entry
Click back inside the text entry and modify the text
ParaView will crash
Partial stack track is:
frame #0: 0x0000000107fb3f5f Python`PyUnicodeUCS2_AsUTF8String + 4
frame #1: 0x0000000100b4ce85 libvtkpqPython-pv5.1.1.dylib`pqPythonSyntaxHighlighter::rehighlightSyntax(this=0x00000001168210a0) + 1637 at pqPythonSyntaxHighlighter.cxx:193
frame #2: 0x0000000100b4f5e2 libvtkpqPython-pv5.1.1.dylib`pqPythonSyntaxHighlighter::qt_static_metacall(_o=0x00000001168210a0, _c=InvokeMetaMethod, _id=0, _a=0x00007fff5fbfdd80) + 130 at moc_pqPythonSyntaxHighlighter.cxx:49
frame #3: 0x00000001072e3c2e QtCore`QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1566
https://gitlab.kitware.com/paraview/paraview/-/issues/16746Cell centers calculation error2020-05-06T08:39:56-04:00Kitware RobotCell centers calculation error**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16746). Further discussion may take place here.**
---
Cell centers are sometimes placed on a vertex, or on an edge, instead of a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16746). Further discussion may take place here.**
---
Cell centers are sometimes placed on a vertex, or on an edge, instead of at the cell center.
See the attached file for an example.Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/15393can't create writers in PV GUI Python shell2020-05-06T09:04:39-04:00Kitware Robotcan't create writers in PV GUI Python shell**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15393). Further discussion may take place here.**
---
Steps to reproduce:
1) run paraview
2) open up the Python Shell
3) crea...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15393). Further discussion may take place here.**
---
Steps to reproduce:
1) run paraview
2) open up the Python Shell
3) create a Line source
4) create a XMLPolyDataWriter
->crash
https://gitlab.kitware.com/paraview/paraview/-/issues/14965Changes to solid color are not recorded in Python trace2020-05-06T09:09:23-04:00Kitware RobotChanges to solid color are not recorded in Python trace**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14965). Further discussion may take place here.**
---
If you change the solid color of an object while Python trace recording is...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14965). Further discussion may take place here.**
---
If you change the solid color of an object while Python trace recording is on, that coloring is not recored even if the trace was started with the "Fully trace supplement objects, such as color maps,..." checkbox is checked. To replicate, do the following.
1. Create a Sphere source. Apply.
2. Tools -> Start Trace
3. In the Trace Options dialog, check the "Fully trace supplemental objects..." checkbox.
4. Click "OK"
5. Click the Edit Colors button and change the color of the sphere.
6. Tools -> Stop Trace
Note that the change in the sphere color is not captured in the Python trace.