ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-11-24T10:22:39-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/20338v5.9-RC1 crash when raytracing molecular data2020-11-24T10:22:39-05:00Jean M. Favrev5.9-RC1 crash when raytracing molecular dataI downloaded and installed ParaView-5.9.0-RC1-MPI-Linux-Python3.8-64bit from www.paraview.org
paraview /local/apps/VTK/VTKBuild/ExternalData/Testing/Data/nanowireTB23K298.xyz
switch raytracing on
OSPRay ERROR: OSPData: all numItems mu...I downloaded and installed ParaView-5.9.0-RC1-MPI-Linux-Python3.8-64bit from www.paraview.org
paraview /local/apps/VTK/VTKBuild/ExternalData/Testing/Data/nanowireTB23K298.xyz
switch raytracing on
OSPRay ERROR: OSPData: all numItems must be positive
OSPRay ERROR: null handle provided to void ospCommit(OSPObject)
OSPRay ERROR: OSPData: shared buffer is NULL
OSPRay ERROR: null handle provided to void ospCommit(OSPObject)
Loguru caught a signal: SIGSEGV5.9 (Fall 2020)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/203363D Glyphs representation: restrict orientation vectors to 3- or 4-component a...2020-12-09T21:57:53-05:00Cory Quammencory.quammen@kitware.com3D Glyphs representation: restrict orientation vectors to 3- or 4-component arraysAll arrays appear as options for the **Orientation Vectors** array, but only 3- or 4- component vector arrays should be presented as options.
Steps to reproduce:
* Launch ParaView, builtin server
* Sources -> **Fast Uniform Grid**
* Ch...All arrays appear as options for the **Orientation Vectors** array, but only 3- or 4- component vector arrays should be presented as options.
Steps to reproduce:
* Launch ParaView, builtin server
* Sources -> **Fast Uniform Grid**
* Change representation to "3D Glyphs"
* Check the **Orient** checkbox
* Click on the **Orientation Vectors** combo box. You'll see options "DistanceSquared", "None", "Swirl", "X". Only the 3-component array "Swirl" and the "None" options should be present.
* If you select "DistanceSquared", you'll get an error message
```
ERROR: In /opt/glr/paraview/paraview-ci/source-paraview/VTK/Rendering/OpenGL2/vtkOpenGLGlyph3DMapper.cxx, line 637
vtkOpenGLGlyph3DMapper (0x7fb7c999e9a0): expecting an orientation array with 3 components, getting 1 components.
```https://gitlab.kitware.com/paraview/paraview/-/issues/20335macOS: pvbatch/pvpython raise PYTHONHOME errors2022-10-18T12:03:02-04:00Utkarsh AyachitmacOS: pvbatch/pvpython raise PYTHONHOME errors```
> ./pvpython
Could not find platform dependent libraries <exec_prefix
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
```
this happens only on macOS```
> ./pvpython
Could not find platform dependent libraries <exec_prefix
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
```
this happens only on macOS5.11 (Spring 2022)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20333Paraview 5.8.1 icons are back to tiny2020-11-17T12:09:16-05:00Amin SadeghiParaview 5.8.1 icons are back to tinyThe icons in the RenderView window used to be tiny, then they got fixed, and in 5.8.1 they're back to tiny. I wonder if that was intended.
![image](/uploads/a5234ac2fe73edb209e17668f86b5c29/image.png)The icons in the RenderView window used to be tiny, then they got fixed, and in 5.8.1 they're back to tiny. I wonder if that was intended.
![image](/uploads/a5234ac2fe73edb209e17668f86b5c29/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/20332ParaView freezes on Mac OS Big Sur2021-09-24T09:52:30-04:00Elliott MacneilParaView freezes on Mac OS Big SurI am running Paraview 5.8.0 on my machine with Mac OS Big Sur (Version 11.0.1) installed. When I open the Paraview application and click anything, the application freezes and my machine claims that the "application is not responding".I am running Paraview 5.8.0 on my machine with Mac OS Big Sur (Version 11.0.1) installed. When I open the Paraview application and click anything, the application freezes and my machine claims that the "application is not responding".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/20325Tolerance related rendering issue2020-11-13T12:48:34-05:00Ethan HerethTolerance related rendering issueGood afternoon ParaView team, this is the first time I've ever submitted a bug/issue report here so forgive me if I leave out anything obvious.
I have a CGNS grid file wherein the smallest elements are very small compared to the largest...Good afternoon ParaView team, this is the first time I've ever submitted a bug/issue report here so forgive me if I leave out anything obvious.
I have a CGNS grid file wherein the smallest elements are very small compared to the largest as well as the overall size of the mesh. The smallest elements (which are on a boundary) appear improperly rendered; they seem jagged and perhaps crossed. This happens in release versions 5.6.2 and 5.8.1 on Linux at least; I have not tested any other versions/OSes. I have a colleague who has verified that this mesh renders as expected in both VisIt and TecPlot.
If the extents of the mesh are clipped sufficiently, the poorly rendered elements are properly rendered. The steps to reproduce this clipping are as follows:
- Clip
- Clip Type: Sphere
- Center: approximate center of interior circle
- Radius: 1
- Crinkle Clip: checked
See screenshots below:
| before clip | after clip |
| ------ | ------ |
| ![Paraview_render_issue-before](/uploads/89e20fa1b701e19696d6d136ff2b7252/Paraview_render_issue-before.png) | ![Paraview_render_issue-after](/uploads/99b38c5a011b7558e50bf698d6eaed60/Paraview_render_issue-after.png) |
Lastly perhaps one more thing that is relevant is that the mesh points seem to be rendered properly, just not mesh edges/elements; see screenshot below
![Parview_render_issue_cells_vs_points](/uploads/963dca2b316f21efa6b02d51ac17c791/Parview_render_issue_cells_vs_points.png)
I have attached the CGNS file here in this issue that I use to reproduce this issue. Please feel free to follow up with any questions or for any details I may have left out. Thanks for you help!
[Paraview_render_issue.cgns](/uploads/75400817f37f2231ffdc5bcd98f6335a/Paraview_render_issue.cgns)https://gitlab.kitware.com/paraview/paraview/-/issues/20324v5.9-RC1 cannot compile external plugins2021-05-18T09:27:22-04:00Jean M. Favrev5.9-RC1 cannot compile external pluginsI have v5.8.1 and v5.9-RC1 both compiled successfully with PARAVIEW_USE_MPI:BOOL=ON. All my external reader plugins compile flawlessly under v5.8. I cannot configure any of them under v5.9.
Going back to to a plugin distributed with the...I have v5.8.1 and v5.9-RC1 both compiled successfully with PARAVIEW_USE_MPI:BOOL=ON. All my external reader plugins compile flawlessly under v5.8. I cannot configure any of them under v5.9.
Going back to to a plugin distributed with the source, I can compile Examples/Plugins/MyPNGReader flawlessly under v5.8, but I cannot configure the same plugin under v5.9
```
CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
Could NOT find MPI (missing: MPI_C_FOUND C)
Call Stack (most recent call first):
/usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE)
/local/apps/ParaView/5.9/lib/cmake/paraview-5.9/vtk/patches/3.17/FindMPI.cmake:1730 (find_package_handle_standard_args)
/local/apps/ParaView/5.9/lib/cmake/paraview-5.9/vtk/VTK-vtk-module-find-packages.cmake:433 (find_package)
/local/apps/ParaView/5.9/lib/cmake/paraview-5.9/vtk/vtk-config.cmake:138 (include)
/local/apps/ParaView/5.9/lib/cmake/paraview-5.9/paraview-config.cmake:53 (find_package)
CMakeLists.txt:4 (find_package)
```
Do I need a version of cmake greater than 3.16.3?5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20321Paraview Download not working2020-11-11T09:01:32-05:00chrisj-epccParaview Download not workingToday when I visit
https://www.paraview.org/download/
I get
Error establishing a database connection
This seems to have been happening for a few hours now. Thanks.Today when I visit
https://www.paraview.org/download/
I get
Error establishing a database connection
This seems to have been happening for a few hours now. Thanks.https://gitlab.kitware.com/paraview/paraview/-/issues/20319paraview.simple.GetAllSettings() error2020-12-16T15:53:02-05:00Cory Quammencory.quammen@kitware.comparaview.simple.GetAllSettings() errorThe implementation of `GetAllSettings()` calls `simple.servermanager.ProxyManager()`. This should call `servermanager.ProxyManager()` instead.The implementation of `GetAllSettings()` calls `simple.servermanager.ProxyManager()`. This should call `servermanager.ProxyManager()` instead.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/20318Rotations seems to be inverted in pqCameraToolbar2020-11-18T13:28:28-05:00MelanieCarriereRotations seems to be inverted in pqCameraToolbarThe `CW` and the `CCW`rotations seems to be inverted https://gitlab.kitware.com/paraview/paraview/-/blob/master/Qt/ApplicationComponents/pqCameraToolbar.cxx#L52The `CW` and the `CCW`rotations seems to be inverted https://gitlab.kitware.com/paraview/paraview/-/blob/master/Qt/ApplicationComponents/pqCameraToolbar.cxx#L52Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20316Compilation with NVIDIA EGL fails on ppc64le2020-11-10T17:11:22-05:00Robert Manson-SawkoCompilation with NVIDIA EGL fails on ppc64leHello,
I am trying to compile ParaView v5.8.1 with EGL using NVIDIA stack. They changed slightly how they package OpenGL and friends `ppc64le` RHEL and now all libraries sit in `/usr/lib64/*_nvidia.so*` rather than in the separate direc...Hello,
I am trying to compile ParaView v5.8.1 with EGL using NVIDIA stack. They changed slightly how they package OpenGL and friends `ppc64le` RHEL and now all libraries sit in `/usr/lib64/*_nvidia.so*` rather than in the separate directory.
I use the following:
```bash
cmake \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DBUILD_TESTING=OFF \
-DPARAVIEW_USE_PYTHON=OFF \
-DPARAVIEW_INSTALL_DEVELOPMENT_FILES=ON \
-DPARAVIEW_USE_MPI=ON \
-DVTK_USE_X=OFF \
-DOPENGL_egl_LIBRARY=/usr/lib64/libEGL_nvidia.so.0 \
-DOPENGL_gles2_LIBRARY=/usr/lib64/libGLESv2_nvidia.so.2 \
-DOPENGL_gles3_LIBRARY=/usr/lib64/libGLESv2_nvidia.so.2 \
-DOPENGL_glx_LIBRARY=/usr/lib64/libGLX_nvidia.so.0 \
-DPARAVIEW_USE_QT=OFF \
-DCMAKE_INSTALL_PREFIX=${INSTALL_DIR} \
../ParaView-v${VERSION} \
&& make -j20 \
&& rm -rf $INSTALL_DIR \
&& make install
```
This is the error I am encountering:
```
/gpfs/users/shared/apps/core/gcc/9.2.0/bin/g++ -O2 -g -DNDEBUG -Wl,-lc -Wl,-lc -Wl,-rpath=/gpfs/users/shared/apps/compiler/gcc/9.2/openmpi/3.1.4/lib CMakeFiles/vtkProbeOpenGLVersion.dir/vtkProbeOpenGLVersion.cxx.o -o ../../../bin/vtkProbeOpenGLVersion-pv5.8 -Wl,-rpath,/gpfs/users/rrs59-sxa03/sources/paraview/build-paraview-5.8.1-gcc-ompi/lib64: ../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8 ../../../lib64/libvtkRenderingCore-pv5.8.so.5.8 ../../../lib64/libvtkFiltersCore-pv5.8.so.5.8 ../../../lib64/libvtkglew-pv5.8.so.5.8 /usr/lib64/libEGL_nvidia.so.0 /usr/lib64/libOpenGL.so ../../../lib64/libvtkCommonExecutionModel-pv5.8.so.5.8 ../../../lib64/libvtkCommonDataModel-pv5.8.so.5.8 ../../../lib64/libvtkCommonTransforms-pv5.8.so.5.8 ../../../lib64/libvtkCommonMisc-pv5.8.so.5.8 ../../../lib64/libvtkCommonMath-pv5.8.so.5.8 ../../../lib64/libvtkCommonCore-pv5.8.so.5.8 -lpthread ../../../lib64/libvtksys-pv5.8.so.5.8 -ldl -Wl,-rpath-link,/gpfs/users/rrs59-sxa03/sources/paraview/build-paraview-5.8.1-gcc-ompi/lib64
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglQueryString'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglCreateContext'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetCurrentDisplay'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetDisplay'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetProcAddress'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglQuerySurface'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglMakeCurrent'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglDestroyContext'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetError'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglChooseConfig'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglSwapBuffers'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglCreatePbufferSurface'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetCurrentContext'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglTerminate'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglDestroySurface'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglGetCurrentSurface'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglBindAPI'
../../../lib64/libvtkRenderingOpenGL2-pv5.8.so.5.8: undefined reference to `eglInitialize'
collect2: error: ld returned 1 exit status
```
Please advise.https://gitlab.kitware.com/paraview/paraview/-/issues/20315CGNSSeriesReader Blocks.Available is broken in PV 5.8.0?2021-02-12T05:45:48-05:00Serge ToxopeusCGNSSeriesReader Blocks.Available is broken in PV 5.8.0?In PV 5.6, I could use the CGNSSeriesReader's Blocks.Available property to see which "blocks" are available in my CGNS file. However, doing the same in PV 5.8.0 shows an empty list. Am I doing something wrong, or is this option broken?
...In PV 5.6, I could use the CGNSSeriesReader's Blocks.Available property to see which "blocks" are available in my CGNS file. However, doing the same in PV 5.8.0 shows an empty list. Am I doing something wrong, or is this option broken?
Consider the following python script (mwe.py) together with the attached cgns file:
```
from paraview.simple import *
reader = CGNSSeriesReader(FileNames=["example_grid.cgns"],guiName="reader")
AvailableBlocks = reader.Blocks.Available
print AvailableBlocks
```
If I run this in PV 5.6, I get:
```
['/Families', '/Hierarchy/Base_Surface_elements/Zone_XMAX/Grid', '/Hierarchy/Base_Surface_elements/Zone_XMIN/Grid', '/Hierarchy/Base_Surface_elements/Zone_YMAX/Grid', '/Hierarchy/Base_Surface_elements/Zone_YMIN/Grid', '/Hierarchy/Base_Surface_elements/Zone_ZSYM/Grid', '/Hierarchy/Base_Volume_elements/Zone_Interior/Grid', '/Patches/Base_Surface_elements/Zone_XMAX', '/Patches/Base_Surface_elements/Zone_XMIN', '/Patches/Base_Surface_elements/Zone_YMAX', '/Patches/Base_Surface_elements/Zone_YMIN', '/Patches/Base_Surface_elements/Zone_ZSYM', '/Patches/Base_Volume_elements/Zone_Interior']
```
In PV 5.8.0, apart from display information, only an empty list is returned:
```
VisRTX 0.1.6, using devices:
0: Quadro P4000 (Total: 8.5 GB, Available: 7.6 GB)
[]
```
Any help is very much appreciated.
[mwe.py](/uploads/6f325b758ba58415d89d6c2a315c9539/mwe.py)
[example_grid.cgns](/uploads/be9f6cd934d37934791205cdbccb61ec/example_grid.cgns)https://gitlab.kitware.com/paraview/paraview/-/issues/20314v5.9-RC1 file is constantly re-opened and read when playing camera keyframes ...2020-11-20T08:43:47-05:00Jean M. Favrev5.9-RC1 file is constantly re-opened and read when playing camera keyframes animationThe issue raised https://discourse.paraview.org/t/xmlimagedatareader-keeps-re-executing-with-a-static-dataset-when-playing-keyframes-animation/5692 appears in v5.9-RC1. A reproducer is included on the discourse pageThe issue raised https://discourse.paraview.org/t/xmlimagedatareader-keeps-re-executing-with-a-static-dataset-when-playing-keyframes-animation/5692 appears in v5.9-RC1. A reproducer is included on the discourse page5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20313Custom Filenamesuffix (from list) in SaveData using pvbatch2021-04-20T17:12:04-04:00NiazCustom Filenamesuffix (from list) in SaveData using pvbatchPlease add TimestepValues (from a python list) as an option for Filenamesuffix in SavaData.
Original Discussion: https://discourse.paraview.org/t/custom-filenamesuffix-from-list-in-savedata-using-pvbatch/5707Please add TimestepValues (from a python list) as an option for Filenamesuffix in SavaData.
Original Discussion: https://discourse.paraview.org/t/custom-filenamesuffix-from-list-in-savedata-using-pvbatch/5707https://gitlab.kitware.com/paraview/paraview/-/issues/20311Support plugins knowing where they live2021-01-19T15:23:10-05:00Ben BoeckelSupport plugins knowing where they liveSome plugins would like to know where they were loaded from so that they can access their own resources beside themselves. This is known to the `vtkPVPlugin` instance via its `GetFileName()` method (`nullptr` in static plugins). There sh...Some plugins would like to know where they were loaded from so that they can access their own resources beside themselves. This is known to the `vtkPVPlugin` instance via its `GetFileName()` method (`nullptr` in static plugins). There should be a new plugin interface type to call code with this location so that a plugin can know where it lives to access other resources beside itself.
`paraview_plugin_add_self_awareness(CLASS_NAME <classname> INTERFACES <var> SOURCES <var>)` (feel free to bikeshed the name)
This would basically just call `<classname>::SetPluginFileName(plugin->GetFileName())` (a static method). The plugin can then do whatever it wants with this information.
Cc: @john.tourtellott @utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20309Paraview 5.7.0 opacity problem2020-11-05T21:25:49-05:00Joaquin GonzalezParaview 5.7.0 opacity problemHello, I just entered here, this is my first post. I recently incorporated ubuntu 20.04 to windows 10 on my laptop because I am using liggghts in ubuntu, to visualize the simulations for my pregrade in Santiago,Chile. I use paraview 5.7....Hello, I just entered here, this is my first post. I recently incorporated ubuntu 20.04 to windows 10 on my laptop because I am using liggghts in ubuntu, to visualize the simulations for my pregrade in Santiago,Chile. I use paraview 5.7.0 and I have the same problem as #17553 and #18030.
When I change the opacity to less than 1 the object disappears, I have tried to use the command "VTK_USE_LEGACY_DEPTH_PEELING = 1 paraview" in terminal but apparently no results.
This is my output for
```bash
> glxinfo | grep OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.8
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.8
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.8
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
```
I also have a nvidia GTX1650 video card (In windows I have downloaded the updated drivers and in Ubuntu select the one that said tested), which I don't know if it can generate this error when the object disappears. Finally I apologize for my English which is not my native language and I would really appreciate it if you could help me with this.
![Captura_de_pantalla_de_2020-11-04_13-50-11](/uploads/622f9933ff408e367a29567d845f9768/Captura_de_pantalla_de_2020-11-04_13-50-11.png)https://gitlab.kitware.com/paraview/paraview/-/issues/20308__file__ is not defined when ParaView python state file is loaded through ``F...2020-11-17T22:29:50-05:00Nima Tofighi__file__ is not defined when ParaView python state file is loaded through ``File->Load State...''When loading a python state file through ``File->Load State...'' the __file__ variable is not defined. This makes it impossible to use relative paths inside python state files when loaded in this manner. Loading the state file through Py...When loading a python state file through ``File->Load State...'' the __file__ variable is not defined. This makes it impossible to use relative paths inside python state files when loaded in this manner. Loading the state file through Python Shell via Run Script works as expected and __file__ points to the location of the state file.
Example file:
[placeholder.py](/uploads/67fb103c0b3a10dea251dc39b3f79b61/placeholder.py)
Error message:
Traceback (most recent call last):
File "<string>", line 14, in <module>
NameError: name '__file__' is not defined5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20305Mac/Python 3 issue with -m option2020-11-18T16:16:15-05:00Sebastien JourdainMac/Python 3 issue with -m optionRunning the following command should give you the following
```
$ pvbatch -m paraview.apps -l
Available applications:
divvy
flow
lite
visualizer
```
On Mac with ParaView-5.8.1-1539-ge438006c96.app we get
```
./pvbatch -m parav...Running the following command should give you the following
```
$ pvbatch -m paraview.apps -l
Available applications:
divvy
flow
lite
visualizer
```
On Mac with ParaView-5.8.1-1539-ge438006c96.app we get
```
./pvbatch -m paraview.apps -l
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Available applications:
```Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20304gitlab-ci: move vall to gitlab-ci2021-02-12T11:56:31-05:00Utkarsh Ayachitgitlab-ci: move vall to gitlab-ci* [ ] move linux-shared-debug+adios2+extdeps+gui+mpi+python3 on `vall` to gitlab-ci
* [ ] reinstall vall to become a standard gitlab-ci linux runner
cc: @ben.boeckel @cory.quammen* [ ] move linux-shared-debug+adios2+extdeps+gui+mpi+python3 on `vall` to gitlab-ci
* [ ] reinstall vall to become a standard gitlab-ci linux runner
cc: @ben.boeckel @cory.quammenVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.com