ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-09-21T13:12:56-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19677Watney Master Issues for 5.9.02022-09-21T13:12:56-04:00W. Alan ScottWatney Master Issues for 5.9.0Here are the list of Watney issues that are targetting 5.9.0. These are generally speaking enhancing ParaView/ Catalyst's ability to do quantitative analysis. This is onging development.
Milestone 5.8.0 Watney bugs are here: https://...Here are the list of Watney issues that are targetting 5.9.0. These are generally speaking enhancing ParaView/ Catalyst's ability to do quantitative analysis. This is onging development.
Milestone 5.8.0 Watney bugs are here: https://gitlab.kitware.com/paraview/paraview/issues/19126.
At Watney's request, I am reordering them by functional group.
* Selection. This is a limiting factor in everything we are doing for getting numbers out of ParaView, and highly coupled to the next item (Internal) because selection is how we identify objects.
- [x] #19676 Extend Extract Cells by Region to include line or splice source - Important
- [x] #19406 Sources/ Ellipse misses one segment - Important
- [ ] #19649 Select cells through in parallel does not trace correctly
* Internal to ParaView. How are objects labeled and referenced? Objects are cells and points, but also objects that ParaVew and VTK define or create such as streamlines. How do I find indices, what do they mean, and how can I use them to apply selection and filters to the desired objects?
- [x] #19128 cgns reader block ids messed up - Required
- [ ] #19170 Document all of the block and id names - Required (should slip post 5.8 release)
- [x] #19661 Append Location Attributes filter crashes in Catalyst with muliblock dataset where leaves are structured - On Sandia's plate.
- [x] #19117 CGNS bad in parallel with D3 filter - Important (probable slip to 5.9)
- [ ] #19234 Clarifications and modifications to Global Ids - Important
* Reading and Writing from/to files. For now, the mechanism is writing csv files through either File/SaveData or Export on the Spreadsheet view, but a much more expansive interface should be developed.
- [x] #19073 Save data products on the client, or server, side - Nice to have
- [x] #19454 add cgns reader globbing for batch
- [x] #20664 optionally add automatic displacements in CGNS
* Scripting issues. Critical for doing anything in Catalyst, and selections are not implemented in scripting so we can’t even get started on this area.
* Other, self explanatory
- [ ] #19161 StreamTracer path length seems suspect - Important
* Build support. This includes Catalyst bugs and features, and SuperBuild support.
- [ ] Superbuild - https://gitlab.kitware.com/paraview/paraview-superbuild/issues/142 Add ability to compile LLVM static. - Important
- [x] #19669 CMAKE_INSTALL_PREFIX not propogated properly in Superbuild.
- [x] #19565 External use of hdf5 not easy to implement, and doesn't work.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19676Extend Extract Cells by Region to include a line or spline source.2022-04-27T22:36:27-04:00W. Alan ScottExtend Extract Cells by Region to include a line or spline source.Please add to Extract Cells by Region the ability to extract a line or spline source.Please add to Extract Cells by Region the ability to extract a line or spline source.5.11 (Spring 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19675Please add assemblies to the new Exodus reader2021-08-12T15:35:41-04:00W. Alan ScottPlease add assemblies to the new Exodus readerPlease add assemblies to the new Exodus reader. Here are details from a user:
--snip-customer-- have recently funded SNL (Greg Sjaardema) to add in assemblies support to the Exodus file format. Greg is about halfway through these modi...Please add assemblies to the new Exodus reader. Here are details from a user:
--snip-customer-- have recently funded SNL (Greg Sjaardema) to add in assemblies support to the Exodus file format. Greg is about halfway through these modifications which includes updating key Secas tools. I believe Greg has already documented the new features he has added to Exodus. Naturally to make use of this new important capability the pre and post processing tools which support Exodus need to have support added for this assembly capability. Please can you explore if the proposed re-write to the Exodus readers in Paraview could also include adoption of the new assemblies feature in Exodus. The point of contact at SNL for this will be Greg himself. I believe he has about 40 more hours of effort to complete his task with the IOSS before handing over to the STK team to do their bits before the assembly feature can be supported by the wider Sierra codes.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19674Python dir function is broken2020-05-19T12:51:22-04:00W. Alan ScottPython dir function is brokenParaView's python dir function is broken. Here is how to replicate:
* ParaView 5.7.0, OS X, paraview.org download
```
sphere=Sphere()
Show()
Render()
camera=GetActiveCamera()
dir(camera)
['AddObserver', 'ApplyTransform', 'A...ParaView's python dir function is broken. Here is how to replicate:
* ParaView 5.7.0, OS X, paraview.org download
```
sphere=Sphere()
Show()
Render()
camera=GetActiveCamera()
dir(camera)
['AddObserver', 'ApplyTransform', 'Azimuth', 'BreakOnError', 'ComputeViewPlaneNormal', 'DebugOff', 'DebugOn', 'DeepCopy',
--snip--
'UnRegister', 'UpdateViewport', 'UseExplicitProjectionTransformMatrixOff', 'UseExplicitProjectionTransformMatrixOn', 'UseHorizontalViewAngleOff', 'UseHorizontalViewAngleOn', 'UseOffAxisProjectionOff', 'UseOffAxisProjectionOn', 'ViewingRaysModified', 'Yaw', 'Zoom', '__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__this__', '__vtkname__']
```
* ParaView 5.8.0-RC2, OS X, paraview.org download
```
sphere=Sphere()
Show()
Render()
camera=GetActiveCamera()
dir(camera)
['__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__hash__', '__init__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__']
camera.Roll(10)
Render()
```
Does work!
dir() should show the methods for vtkCamera!5.9 (Fall 2020)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19672Bug in resample to htg with a branch factor of 3 + extrapolate data2020-06-09T13:23:59-04:00Yohann Bearzi (Kitware)Bug in resample to htg with a branch factor of 3 + extrapolate dataWhen extrapolating data with a branch factor 3 in the resample to hyper tree grid plugin, NaNs appear (in yellow in the following screenshot).
![image](/uploads/f325b826938668032fe276062761d82f/image.png)When extrapolating data with a branch factor 3 in the resample to hyper tree grid plugin, NaNs appear (in yellow in the following screenshot).
![image](/uploads/f325b826938668032fe276062761d82f/image.png)5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19671Resample to HTG - Quantile measurement2020-02-24T13:55:30-05:00Yohann Bearzi (Kitware)Resample to HTG - Quantile measurementThere is currently no Quantile measurement option in the resample to hyper tree grid plugin. It actually exists in the code but was removed due to a bug. This should be fixed, as quantile measurement is a good measurement method being qu...There is currently no Quantile measurement option in the resample to hyper tree grid plugin. It actually exists in the code but was removed due to a bug. This should be fixed, as quantile measurement is a good measurement method being quite resilient to outliers.5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19670Release ParaView 5.8.0-RC32020-02-12T11:01:02-05:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.8.0-RC3# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.8.0.pdf
- [x] Upload to www.paraview.org/files/v5.8
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.8.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.8.0.pdf
- [x] Upload to www.paraview.org/files/v5.8
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.8.0.pdf
- [x] Upload to www.paraview.org/files/v5.8
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.8.0.pdf
- [x] Upload to www.paraview.org/files/v5.8
- Assemble release notes into `Documentation/release/ParaView-5.8.0`.
- [x] Get positive review and merge.
# Update ParaView
If making a release from the `release` branch, e.g., `v5.8.0-RC2 or above`:
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.8.0-RC3
echo 5.8.0-RC3 > version.txt
git commit -m 'Update version number to 5.8.0-RC3' version.txt
git tag -a -m 'ParaView 5.8.0-RC3' v5.8.0-RC3 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] Get positive review
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.8.0-RC3:release v5.8.0-RC3`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.8.0-RC3`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.8/`
# Update ParaView-Superbuild
If making a release from the `release` branch, e.g., `v5.8.0-RC2 or above`:
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update
git checkout -b update-to-v5.8.0-RC3
```
- Update `CMakeLists.txt`
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.8.0-RC3" CACHE STRING "Force version to 5.8.0-RC3" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.8.0-RC3
- [x] ARG SUPERBUILD_TAG=v5.8.0-RC3
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/Dockerfile
git commit -m "Update the default version to 5.8.0-RC3"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [x] Build binaries (`Do: test`)
- [x] Download the binaries that have been generated in the dashboard results. They will be deleted within 24 hours.
- [x] Remove explicit version forcing added in CMakeLists.txt, amend the commit, and force push
```
git add CMakeLists.txt
git commit --amend
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.8.0-RC3' v5.8.0-RC3 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.8.0-RC3:release v5.8.0-RC3`
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.8.0-RC3.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.8.0-RC3.app/`
# Validating binaries
- For each binary, check
- [x] Getting started guide opens
- [x] Examples load and match thumbnails in dialog
- [x] Python
- [x] `import numpy`
- [x] Plugins are present and load properly
- [x] Text source LaTeX `$A^2$`
- [x] OSPRay raycasting and pathtracing runs
- [x] OptiX pathtracing runs
- [x] IndeX runs
- [x] AutoMPI
- Binary checklist
- [x] macOS
- [x] Linux
- [x] Linux osmesa
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.8/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.8
```
- [ ] Test download links on https://www.paraview.org/download
# Post-release
- [ ] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19669CMAKE_INSTALL_PREFIX not propogated properly in superbuild2021-05-17T19:42:10-04:00Jeff MauldinCMAKE_INSTALL_PREFIX not propogated properly in superbuildI am trying to build catalyst for linking against SPARC. When I set the CMAKE_INSTALL_PREFIX argument in the superbuild, that command is not propagated down to paraview (or, for that matter, python if built, osmesa, and maybe not llvm)....I am trying to build catalyst for linking against SPARC. When I set the CMAKE_INSTALL_PREFIX argument in the superbuild, that command is not propagated down to paraview (or, for that matter, python if built, osmesa, and maybe not llvm).
cmake runs find, and the build happens, but all the results are placed in the default install directory (parallel to the 'superbuild' directory) in my building directory.
When I look at the CMakeCache.txt file in .../superbuild/paraview/build I see that the CMAKE_INSTALL_PREFIX is NOT set to what I set CMAKE_INSTALL_PREFIX to in the CMakeCache.txt for the overall superbuild.
I believe I can overcome this for paraview by passing cmake arguments down into paraview, but I'm not sure I can fix it for osmesa, python, and llvm. It does look like the llvm libraries get installed into the install lib directory as desired, but no paraview directories, and there is no <install>/lib/cmake subdirectory which is supposed to contain the paraview cmake config file for SPARC to use to find paraview during it's cmake configuration.5.10 (Fall 2021)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/19667Cannot import Paraview 5.8.0 release candidate in python2020-12-16T16:28:56-05:00Yale LeeCannot import Paraview 5.8.0 release candidate in pythonI cannot import Paraview in Python, both on 5.8.0-rc1 and 5.8.0-rc2, in a Windows distribution.
When trying to import `paraview` package:
```
>>> import paraview
Traceback (most recent call last):
File "C:\Program Files (x86)\ParaVi...I cannot import Paraview in Python, both on 5.8.0-rc1 and 5.8.0-rc2, in a Windows distribution.
When trying to import `paraview` package:
```
>>> import paraview
Traceback (most recent call last):
File "C:\Program Files (x86)\ParaView-5.8.0-RC2-MPI-Windows-Python3.7-msvc2015-64bit\bin\Lib\site-packages\paraview\__init__.py", line 175, in <module>
from .modules import vtkRemotingCore
ImportError: DLL load failed: The specified module could not be found.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "C:\Program Files (x86)\ParaView-5.8.0-RC2-MPI-Windows-Python3.7-msvc2015-64bit\bin\Lib\site-packages\paraview\__init__.py", line 177, in <module>
import _paraview_modules_static
ModuleNotFoundError: No module named '_paraview_modules_static'
```
My PYTHONPATH environment variable does contain paths down to `site-packages`, `site-packages\paraview` and `site-packages\vtkmodules`. But it seems like lines 174 to 177 dedicated to static builds make the whole import fail since the exception triggers another bug.
N.B.: I cannot even import `vtk`:
```
>>> import vtk
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "C:\Program Files (x86)\ParaView-5.8.0-RC2-MPI-Windows-Python3.7-msvc2015-64bit\bin\Lib\site-packages\vtk.py", line 30, in <module>
all_m = importlib.import_module('vtkmodules.all')
File "C:\Python37\Lib\importlib\__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "C:\Program Files (x86)\ParaView-5.8.0-RC2-MPI-Windows-Python3.7-msvc2015-64bit\bin\Lib\site-packages\vtkmodules\all.py", line 8, in <module>
from .vtkWebCore import *
ImportError: DLL load failed: The specified module could not be found.
```
FYI: @pppebayhttps://gitlab.kitware.com/paraview/paraview/-/issues/19665Add optional min and max when "above range" and/or "below range" is enabled2022-08-09T12:01:11-04:00W. Alan ScottAdd optional min and max when "above range" and/or "below range" is enabledPlease add the option, default off, to add the max and min to the color legend when the user has enabled clamping the color map to the range between "above range" and "below range". Here is how to test this feature:
* Open disk_out_ref....Please add the option, default off, to add the max and min to the color legend when the user has enabled clamping the color map to the range between "above range" and "below range". Here is how to test this feature:
* Open disk_out_ref.exo. All vars on. Apply.
* Clip. Paint by Temp.
* Rescale to custom data range. 400 to 500.
* Color editor. Advanced. Select Use Above Range Color and Use Below Range Color.
I/we would like the option of actually annotating the actual min and max on the dataset. Default off.5.11 (Spring 2022)https://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/19663typographic error in colormap name2020-05-20T09:50:23-04:00Jean M. Favretypographic error in colormap namein Remoting/Views/ColorMaps.json
"Asymmtrical Earth Tones (6_21b)" should be "Asymmetrical Earth Tones (6_21b)"in Remoting/Views/ColorMaps.json
"Asymmtrical Earth Tones (6_21b)" should be "Asymmetrical Earth Tones (6_21b)"Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19662GhostCellsGenerator Filter does not propagate Global Field Information2020-02-25T10:15:18-05:00John PatchettGhostCellsGenerator Filter does not propagate Global Field InformationIf the ghost cell generator filter operates on a source/upstream filter that contains global field data, it does not propagate it to the output. Tested in ParaView 5.8.0 RC2.
[ghost-global.pvsm](/uploads/814d48d73a0d21c795981561da479d3f/...If the ghost cell generator filter operates on a source/upstream filter that contains global field data, it does not propagate it to the output. Tested in ParaView 5.8.0 RC2.
[ghost-global.pvsm](/uploads/814d48d73a0d21c795981561da479d3f/ghost-global.pvsm) Shows an example.
![Unknown](/uploads/f9c44e459e0b8184ecf7073b91d66782/Unknown.png) is a pipeline that contains global field data. The ShapedCharge.pio contains global field data, Merge Blocks output also contains the Global Field Data, but Ghost Cells Generator does not. @demarle @cory.quammen5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.com2020-02-09https://gitlab.kitware.com/paraview/paraview/-/issues/19661Append Location Attributes filter crashes in Catalyst with muliblock dataset ...2020-03-24T20:27:44-04:00Jeff MauldinAppend Location Attributes filter crashes in Catalyst with muliblock dataset where leaves are structuredWe get a crash from Append Location Attributes under the following circumstances:
* running SPARC linked to Catalyst
* incoming data is a multiblock dataset where the leaves are structured grids
* I assume some processes may have no data...We get a crash from Append Location Attributes under the following circumstances:
* running SPARC linked to Catalyst
* incoming data is a multiblock dataset where the leaves are structured grids
* I assume some processes may have no data from various blocks, and also that blocks are likely to be divided among processes
* We apply the Append Location Attributs filter
simulation crashes when it hits this filter.
If we do
* calculator
* extract subset with seed
* append location attributes,
Watney reports this succeeds; I have had to do a merge blocks after extract subset with seed to get it to work, but I may have been running an old binary.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19660SPHVolumeInterpolator and PointVolumeInterpolator have their 3D Bounding Box ...2021-08-11T12:23:00-04:00Jean M. FavreSPHVolumeInterpolator and PointVolumeInterpolator have their 3D Bounding Box widget offset from the input dataEasy to reproduce for V5.8-RC2:
Wavelet + CleanToGrid + SPHVolumeInterpolator
the 3D cuboid widget is not centered over the volume, but appears to be centered on the 0-th point of the grid
N.B. The SPHLine- and SPHPlane- interpolators...Easy to reproduce for V5.8-RC2:
Wavelet + CleanToGrid + SPHVolumeInterpolator
the 3D cuboid widget is not centered over the volume, but appears to be centered on the 0-th point of the grid
N.B. The SPHLine- and SPHPlane- interpolators are correctly centered over the volume5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19658Vtm writer failing with structured data in parallel2020-08-31T12:51:00-04:00W. Alan ScottVtm writer failing with structured data in parallelThe vtk/vtm writer appears to be failing with structured data in parallel. Here is how to replicate:
* Linux, 5.8.0-RC2, multiple rank - remote server (I'm on 8 ranks).
* Open Watney's HiFiRE CGNS dataset, sparc-volume.cgns.144.*. Only...The vtk/vtm writer appears to be failing with structured data in parallel. Here is how to replicate:
* Linux, 5.8.0-RC2, multiple rank - remote server (I'm on 8 ranks).
* Open Watney's HiFiRE CGNS dataset, sparc-volume.cgns.144.*. Only load Blk-3, Grid (only for load time reduction). I turned all vars on. Apply.
* File/ Save Data. Vtk Multi Block Files (vtm). I'm calling it deleteMeC. OK, Take defaults, OK.
* Reset session.
* Try to open this dataset. I am trying to open the file deleteMeC.vtm. This should open the directory.
Note that this error does not occur if the writer and reader is builtin server. It DOES occur if the writer is parallel, and the reader is builtin.
Error message, which is totally insufficient, is:
```
ERROR: In /projects/viz/paraview/src/ParaView/5.8.0-RC2/ParaView5/VTK/IO/XML/vtkXMLMultiBlockDataReader.cxx, line 300
vtkXMLMultiBlockDataReader (0xa997bb0): Syntax error in file.
```5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19657Plugin XML listings should support relative filepaths now2020-08-25T21:23:40-04:00Ben BoeckelPlugin XML listings should support relative filepaths nowNow that XML loading knows the path to the XML, we can support relative paths in the `filename=` attribute as well. "Escaping" the XML's directory should not be supported.
Cc: @tjcorona @mwestphal @utkarsh.ayachit @cory.quammenNow that XML loading knows the path to the XML, we can support relative paths in the `filename=` attribute as well. "Escaping" the XML's directory should not be supported.
Cc: @tjcorona @mwestphal @utkarsh.ayachit @cory.quammen5.8 (Winter 2020)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19656PV_PLUGIN_PATH should search directories for plugins2020-06-29T21:59:56-04:00Ben BoeckelPV_PLUGIN_PATH should search directories for pluginsIf a directory named `x` is found under `PV_PLUGIN_PATH`, `x/x.$ext` should be attempted to be loaded as a plugin as well.
Cc: @tjcorona @mwestphal @utkarsh.ayachit @cory.quammenIf a directory named `x` is found under `PV_PLUGIN_PATH`, `x/x.$ext` should be attempted to be loaded as a plugin as well.
Cc: @tjcorona @mwestphal @utkarsh.ayachit @cory.quammen5.8 (Winter 2020)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19655Multi-tiff broken in parallel2020-02-05T02:18:29-05:00Amin SadeghiMulti-tiff broken in parallelOpening a multi-tiff dataset in parallel using `pvserver` doesn't seem to work. I've tried 5.4.2 and 5.7 and neither worked. Here's the error that I'm getting
```
Loguru caught a signal: SIGSEGV
Loguru caught a signal: SIGSEGV
Stack tra...Opening a multi-tiff dataset in parallel using `pvserver` doesn't seem to work. I've tried 5.4.2 and 5.7 and neither worked. Here's the error that I'm getting
```
Loguru caught a signal: SIGSEGV
Loguru caught a signal: SIGSEGV
Stack trace:
36 0x401789 ./pvserver() [0x401789]
35 0x7fa10b68d1e3 __libc_start_main + 243
34 0x4016e3 ./pvserver() [0x4016e3]
33 0x7fa1099d10c5 vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) + 677
32 0x7fa106659fcc vtkMultiProcessController::ProcessRMIs(int, int) + 316
31 0x7fa106659980 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 336
30 0x7fa109c4d910 vtkPVSessionServer::OnClientServerMessageRMI(void*, int) + 272
29 0x7fa109c43685 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
28 0x7fa109c448cb vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
27 0x7fa109c44a95 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 245
26 0x7fa10927da8d vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
25 0x7fa10927d75e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1198
24 0x7fa10927cc9a vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 330
23 0x7fa10927c9a5 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 325
22 0x7fa10a7d61eb /opt/paraview/bin/../lib/libvtkPVServerManagerApplication-pv5.7.so.1(+0x36e1eb) [0x7fa10a7d61eb]
21 0x7fa10927c9a5 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 325
20 0x7fa10a7da1a3 /opt/paraview/bin/../lib/libvtkPVServerManagerApplication-pv5.7.so.1(+0x3721a3) [0x7fa10a7da1a3]
19 0x7fa109c7f2a4 vtkSISourceProxy::UpdatePipeline(int, double, bool) + 484
18 0x7fa105ccc1ef vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 255
17 0x7fa105c8d2aa vtkDemandDrivenPipeline::UpdateData(int) + 138
16 0x7fa105ccac91 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 801
15 0x7fa105c8e2d6 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 262
14 0x7fa105c87b4a vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 330
13 0x7fa105ccac91 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 801
12 0x7fa105c8e777 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1447
11 0x7fa105c88dd1 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 257
10 0x7fa105c8bbd7 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 55
9 0x7fa105c91640 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 64
8 0x7fa105c99464 vtkImageAlgorithm::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 324
7 0x7fa107c71481 vtkTIFFReader::ExecuteDataWithInformation(vtkDataObject*, vtkInformation*) + 481
6 0x7fa107c861c8 void vtkTIFFReader::Process<signed char>(signed char*, int*, long long*) + 360
5 0x7fa107c85f7c void vtkTIFFReader::ReadVolume<signed char>(signed char*) + 2012
4 0x7fa107c7eea3 void vtkTIFFReader::ReadGenericImage<signed char>(signed char*, unsigned int, unsigned int) + 3091
3 0x7fa0ec73e4c7 vtktiff_TIFFReadScanline + 215
2 0x7fa0ec716bdc /opt/paraview/bin/../lib/libvtktiff-pv5.7.so.1(+0x20bdc) [0x7fa0ec716bdc]
1 0x7fa10b724f4e /lib/x86_64-linux-gnu/libc.so.6(+0xbef4e) [0x7fa10b724f4e]
0 0x7fa10b6ac470 /lib/x86_64-linux-gnu/libc.so.6(+0x46470) [0x7fa10b6ac470]
Stack trace:
34 0x401789 ./pvserver() [0x401789]
33 0x7f86c5dfb1e3 __libc_start_main + 243
32 0x40170e ./pvserver() [0x40170e]
31 0x7f86c0dc81f5 vtkMultiProcessController::ProcessRMIs(int, int) + 869
30 0x7f86c0dc7b2b vtkMultiProcessController::BroadcastProcessRMIs(int, int) + 123
29 0x7f86c0dc7980 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 336
28 0x7f86c43b3195 vtkPVSessionCore::ExecuteStreamSatelliteCallback() + 165
27 0x7f86c43b2a95 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 245
26 0x7f86c39eba8d vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
25 0x7f86c39eb75e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1198
24 0x7f86c39eac9a vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 330
23 0x7f86c39ea9a5 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 325
22 0x7f86c4f441eb /opt/paraview/bin/../lib/libvtkPVServerManagerApplication-pv5.7.so.1(+0x36e1eb) [0x7f86c4f441eb]
21 0x7f86c39ea9a5 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 325
20 0x7f86c4f481a3 /opt/paraview/bin/../lib/libvtkPVServerManagerApplication-pv5.7.so.1(+0x3721a3) [0x7f86c4f481a3]
19 0x7f86c43ed2a4 vtkSISourceProxy::UpdatePipeline(int, double, bool) + 484
18 0x7f86c043a1ef vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 255
17 0x7f86c03fb2aa vtkDemandDrivenPipeline::UpdateData(int) + 138
16 0x7f86c0438c91 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 801
15 0x7f86c03fc2d6 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 262
14 0x7f86c03f5b4a vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 330
13 0x7f86c0438c91 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 801
12 0x7f86c03fc777 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1447
11 0x7f86c03f6dd1 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 257
10 0x7f86c03f9bd7 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 55
9 0x7f86c03ff640 vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 64
8 0x7f86c0407464 vtkImageAlgorithm::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 324
7 0x7f86c23df481 vtkTIFFReader::ExecuteDataWithInformation(vtkDataObject*, vtkInformation*) + 481
6 0x7f86c23f41c8 void vtkTIFFReader::Process<signed char>(signed char*, int*, long long*) + 360
5 0x7f86c23f3f7c void vtkTIFFReader::ReadVolume<signed char>(signed char*) + 2012
4 0x7f86c23ecea3 void vtkTIFFReader::ReadGenericImage<signed char>(signed char*, unsigned int, unsigned int) + 3091
3 0x7f86a6eac4c7 vtktiff_TIFFReadScanline + 215
2 0x7f86a6e84bdc /opt/paraview/bin/../lib/libvtktiff-pv5.7.so.1(+0x20bdc) [0x7f86a6e84bdc]
1 0x7f86c5e92f4e /lib/x86_64-linux-gnu/libc.so.6(+0xbef4e) [0x7f86c5e92f4e]
0 0x7f86c5e1a470 /lib/x86_64-linux-gnu/libc.so.6(+0x46470) [0x7f86c5e1a470]
( 53.649s) [pvserver.1 ] :0 FATL| Signal: SIGSEGV
( 53.648s) [pvserver.0 ] :0 FATL| Signal: SIGSEGV
===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 29719 RUNNING AT mcgill
= EXIT CODE: 139
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault (signal 11)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions
```