ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-08-02T11:54:29-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19145Release ParaView 5.7-RC12019-08-02T11:54:29-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.7-RC1# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0-...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.7.0-RC1.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Assemble release notes into `Documentation/release/ParaView-5.7.0-RC1`.
- [x] Get positive review and merge.
# Update ParaView
- [x] Update `master` branch for **paraview**
```
git fetch origin
git checkout master
git merge --ff-only origin/master
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.7.0-RC1
echo 5.7.0-RC1 > version.txt
git commit -m 'Update version number to 5.7.0-RC1' version.txt
git tag -a -m 'ParaView 5.7.0-RC1' v5.7.0-RC1 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`
- Update VTK's `paraview/release` branch
- [x] `git push origin paraview-vtk-submodule-hash:paraview/release`
- [x] Update kwrobot with the new `paraview/release` branch rules
- Integrate changes to `release` branch
- [x] `git config -f .gitmodules submodule.VTK.branch paraview/release`
- [x] `git commit -m 'release: follow VTK's paraview/release branch' .gitmodules`
- [x] `git push origin update-to-v5.7.0-RC1:release v5.7.0-RC1`
- [x] Update kwrobot with the new `release` branch rules
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.7.0-RC1`)
- [ ] Catalyst (`Catalyst/generate-tarballs.sh v5.7.0-RC1`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.7/`
# Update ParaView-Superbuild
- [x] Update `master` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout master
git merge --ff-only origin/master
```
- Update `CMakeLists.txt`
- [x] `git checkout -b update-to-v5.7.0-RC1`
- [x] Update PARAVIEW_5.7.0-RC1_DEFAULT to the release version (without RC*)
- [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.7.0-RC1" CACHE STRING "Force version to 5.7.0-RC1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update `versions.cmake`
- [x] Guide selections in `versions.cmake`
- [x] `git add versions.cmake CMakeLists.txt`
- [x] `git commit -m "Update the default version to 5.7.0-RC1"`
- Update default versions in container build recipes
- Docker: update default tag strings (in `Scripts/docker/ubuntu/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.7.0-RC1
- [x] ARG SUPERBUILD_TAG=v5.7.0-RC1
- 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 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.7.0-RC1' v5.7.0-RC1 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC1:release v5.7.0-RC1`
- [x] Update kwrobot with the new `release` branch rules
# 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
- [ ] IndeX runs
- [x] AutoMPI
- Binary checklist
- [x] macOS
- [x] Linux
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.7/`)
- [x] Ask @chuck.atkins to sign macOS binary
- [x] Regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt`
```
buildListing.sh
updateMD5sum.sh v5.7
```
- [x] Test download links on https://www.paraview.org/download
# Post-release
- [ ] Write and publish blog post with release notes.
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit
/cc @demarle5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18923Scatter Plot filter should default to Plot Matrix view2019-08-06T09:20:34-04:00Kenneth MorelandScatter Plot filter should default to Plot Matrix viewWhen you add a `Scatter Plot` filter, by default a `Line Chart` view is created to show the results. Although the `Line Chart` can eventually be modified to create a desired scatter plot, the plot that comes by default is a mess.
In con...When you add a `Scatter Plot` filter, by default a `Line Chart` view is created to show the results. Although the `Line Chart` can eventually be modified to create a desired scatter plot, the plot that comes by default is a mess.
In contrast, the `Plot Matrix` view shows exactly the scatter plots that you would expect from a scatter plot filter. It additionally has much better controls to find the scatter plot for the variables desired. The `Scatter Plot` filter should be changed so that the `Plot Matrix` view comes up.
To be absolutely clear what I'm talking about, here are the steps to replicate.
1. Load `disk_out_ref`. All variables on. Apply.
2. Add the `Scatter Plot` filter. Apply.
3. You get a view that looks like this. Blech.
![ugly-line-chart](/uploads/897469af8bf6171575cbe8755ccd05cb/ugly-line-chart.png)
4. Now right-click on the bar above the line chart view and select `Convert To...` -> `Plot Matrix View`. Then click on the visibility icon for the `Scatter Plot` in the `Pipeline Browser`. The view gets converted to this, which is much, much, much better.
![nice-plot-matrix](/uploads/36f01eab4d86b44536fe4e51e754f191/nice-plot-matrix.png)
The plot matrix is what should come up first, not the line chart.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19206Plot Matrix View needs Reset and other controls2019-08-06T09:40:29-04:00W. Alan ScottPlot Matrix View needs Reset and other controlsPlot Matrix View needs Reset and other controls.
* Linux, master, remote server.
* Disk_out_ref.exo. All vars on. Apply.
* Scatter Plot. Apply.
Now, put your mouse in the upper left window. Left mouse drag around. Reset. Nothing ...Plot Matrix View needs Reset and other controls.
* Linux, master, remote server.
* Disk_out_ref.exo. All vars on. Apply.
* Scatter Plot. Apply.
Now, put your mouse in the upper left window. Left mouse drag around. Reset. Nothing happens.
Now, zoom the upper left window with the mouse wheel. Things zoom! Use the right mouse button to zoom. Nothing happens.
(Note, the mouse controls should act like a Line Chart View.)https://gitlab.kitware.com/paraview/paraview/-/issues/19085amrblock line width2019-08-06T18:58:27-04:00Carson Brownleeamrblock line widthamrblocks representations do not respect line width when rendering and render lines as tubes does nothing. Tested with git master build.amrblocks representations do not respect line width when rendering and render lines as tubes does nothing. Tested with git master build.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19152ParaView 5.7.0-RC1 linux: GenericIOReader fails to load2019-08-06T19:10:18-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 linux: GenericIOReader fails to load* Start ParaView, builtin server
* Tools -> Manage Plugins...
* Load GenericIOReader plugin
Loading fails with the error message:
```
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/bu...* Start ParaView, builtin server
* Tools -> Manage Plugins...
* Load GenericIOReader plugin
Loading fails with the error message:
```
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/ParaViewCore/ClientServerCore/Core/vtkPVPluginLoader.cxx, line 417
vtkPVPluginLoader (0x98c58e0): libvtkGenericIOReader.so: cannot open shared object file: No such file or directory
```
`ldd` shows that it is linking against libgfortran, but can't find it.
```
> ldd `find . -name libvtkGenericIOReader.so`
linux-vdso.so.1 (0x00007ffc1c1d7000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdcede08000)
libvtkParallelMPI-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkParallelMPI-pv5.7.so.1 (0x00007fdcedbf3000)
libvtkParallelCore-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkParallelCore-pv5.7.so.1 (0x00007fdced99e000)
libvtkCommonExecutionModel-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonExecutionModel-pv5.7.so.1 (0x00007fdced6c1000)
libvtkCommonDataModel-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonDataModel-pv5.7.so.1 (0x00007fdced079000)
libvtkCommonTransforms-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonTransforms-pv5.7.so.1 (0x00007fdcece4a000)
libvtkCommonMath-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonMath-pv5.7.so.1 (0x00007fdcecc2a000)
libvtkCommonCore-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonCore-pv5.7.so.1 (0x00007fdcec4c6000)
libvtksys-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtksys-pv5.7.so.1 (0x00007fdcec26a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fdcec066000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fdcebe47000)
libtbb.so.2 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libtbb.so.2 (0x00007fdcebbe9000)
libmpi.so.12 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libmpi.so.12 (0x00007fdceb6ad000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fdceb324000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fdceaf86000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fdcead6e000)
/lib64/ld-linux-x86-64.so.2 (0x00007fdcee429000)
libvtkIOLegacy-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkIOLegacy-pv5.7.so.1 (0x00007fdceaaca000)
libvtkIOCore-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkIOCore-pv5.7.so.1 (0x00007fdcea864000)
libvtkCommonSystem-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonSystem-pv5.7.so.1 (0x00007fdcea650000)
libvtkCommonMisc-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkCommonMisc-pv5.7.so.1 (0x00007fdcea435000)
libvtkloguru-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkloguru-pv5.7.so.1 (0x00007fdcea1ef000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fdce9fe7000)
libgfortran.so.3 => not found
libvtkdoubleconversion-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtkdoubleconversion-pv5.7.so.1 (0x00007fdce9dd8000)
libvtklz4-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtklz4-pv5.7.so.1 (0x00007fdce9bb2000)
libvtklzma-pv5.7.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libvtklzma-pv5.7.so.1 (0x00007fdce9982000)
libz.so.1 => /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/lib/./libz.so.1 (0x00007fdce9768000)
```
Of note: `libgfortran.so.3 => not found`. However, `libgfortran.so.3` is in the `lib` directory in the binary directory. Indeed, adding `<full/path/to>/lib` to `LD_LIBRARY_PATH` resolves the issue.5.7 (Summer 2019)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/18534Add the line controls to the Spline Source2019-08-06T19:15:41-04:00W. Alan ScottAdd the line controls to the Spline SourceTurns out the spline source is a very powerful tool to extract variable data in a dataset along a curved line. The interface sucks. Please update it to match the controls used by Plot Over Line.
* We want the starting end to be a ball...Turns out the spline source is a very powerful tool to extract variable data in a dataset along a curved line. The interface sucks. Please update it to match the controls used by Plot Over Line.
* We want the starting end to be a ball, other end to be an arrow.
* Allow "p" to place the hightlighted control point on the surface of an object. Allow "1" and "2" to place the starting point and ending point.
* Keep the spline source visible if you are clicking on other filters.
Here is a use case. Use it with disk_out_ref.exo. https://discourse.paraview.org/t/extract-data-from-a-volume-along-an-elliptical-line/7235.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19179Python LoadSate function is broken in 5.7.0-RC1 when used in combination with...2019-08-06T19:16:41-04:00Pierre CrepierPython LoadSate function is broken in 5.7.0-RC1 when used in combination with LoadStateDataFileOptions='Choose File Names'In 5.7.0-RC1, the LoadState python function is broken.
If I record the trace when loading a state and choose "Choose File Names", then I get a python code similar to this:
```
LoadState('path/to/state.pvsm',
LoadStateData...In 5.7.0-RC1, the LoadState python function is broken.
If I record the trace when loading a state and choose "Choose File Names", then I get a python code similar to this:
```
LoadState('path/to/state.pvsm',
LoadStateDataFileOptions='Choose File Names',
DataDirectory=/some/directory,
out00002880_solutioncgnsFileNames=[come/path.cgns])
```
The variable out00002880_solutioncgnsFileNames depends on the state obviously and when using multiple source files, more variables are required.
Anyway, when using those lines in pvbatch/pvpython, an error is triggered related to property out00002880_solutioncgnsFileNames which does not seem to exist.
That problem was not present in 5.65.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19151ParaView 5.7.0-RC1 linux: libxml2 warning message2019-08-06T19:17:34-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 linux: libxml2 warning messageUpon startup, we are getting the following:
```
bin/paraview: /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/bin/../lib/libxml2.so.2: no version information available (required by /home/coryquammen/Downloads/ParaView-5.7...Upon startup, we are getting the following:
```
bin/paraview: /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/bin/../lib/libxml2.so.2: no version information available (required by /home/coryquammen/Downloads/ParaView-5.7.0-RC1-MPI-Linux-64bit/bin/../lib/libvtkIOInfovis-pv5.7.so.1)
```5.7 (Summer 2019)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19168Crash on loading state file when Image Extracts in Export Inspector is enabled2019-08-06T19:20:43-04:00Feimi YuCrash on loading state file when Image Extracts in Export Inspector is enabledTo reproduce:
1. Enable `Export Inspector` in `View`
2. Enable `Image Extracts`
3. Save state.
4. Relaunch ParaView and load the state.
The cause is that enabling screenshot_writer proxy calls `vtkSMParaViewPiplineController::PostI...To reproduce:
1. Enable `Export Inspector` in `View`
2. Enable `Image Extracts`
3. Save state.
4. Relaunch ParaView and load the state.
The cause is that enabling screenshot_writer proxy calls `vtkSMParaViewPiplineController::PostInitializeProxy()` which used to have a call of `this->RegisterProxiesForProxyListDomains(proxy)` at the end before 70194459580a451e1ace9a74f746377432db7d30. After 70194459580a451e1ace9a74f746377432db7d30 this call was removed and was put in the specialized registration methods. This caused problem with creating format writer proxies needed by `SaveScreenShot` proxy.5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/18084EyeDomeLighting doesn't play with Image Reduction Factor2019-08-06T19:25:34-04:00Utkarsh AyachitEyeDomeLighting doesn't play with Image Reduction Factor* pvserver, 2 ranks or more
* connect with paraview and load the **EyeDomeLightingView** plugin on both the client and server
* In ParaView > Settings, (Render View tab), change the **Remote Render Threshold** to 0 and ensure that the *...* pvserver, 2 ranks or more
* connect with paraview and load the **EyeDomeLightingView** plugin on both the client and server
* In ParaView > Settings, (Render View tab), change the **Remote Render Threshold** to 0 and ensure that the **Image Reduction Factor** is 2 or greater
* close render view, and create **Eye Dome Lighting** view and show any geometry, say a Sphere, in it. Everything's well.
* interact, and you'll see something like the attached image.
![image](/uploads/4f6776d84f386bc606d999cf1f907ec6/image.png)5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19197ray tracing denoiser option in the GUI is counterintuitive such that it seems...2019-08-06T19:26:59-04:00David E. DeMarleray tracing denoiser option in the GUI is counterintuitive such that it seems brokenDenoising only kicks in when the number of samples or progressive passes exceeds a threshold.
However the button to enable denoising is always present, even when oidn is not configured into the build, so most new users think it doesn't...Denoising only kicks in when the number of samples or progressive passes exceeds a threshold.
However the button to enable denoising is always present, even when oidn is not configured into the build, so most new users think it doesn't work.
We need to clean up the GUI and modes to clear up the confusion. At a minimum the pop up help for the denoiser button needs to explain what else needs to be done to make it take effect.
See also: #184145.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19191paraview 5.7 on mac crashes when ospray is shutdown and reset2019-08-06T19:40:46-04:00David E. DeMarleparaview 5.7 on mac crashes when ospray is shutdown and resetRoot cause is described here https://github.com/ospray/ospray/issues/338Root cause is described here https://github.com/ospray/ospray/issues/3385.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18992Copy VTK's find_package helper code into paraview-config2019-08-06T19:43:18-04:00Ben BoeckelCopy VTK's find_package helper code into paraview-config5.7 (Summer 2019)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/1920316-bits textures does not work2019-08-06T19:50:00-04:00Michael Migliore16-bits textures does not workLoading 16-bits PNG as a texture does not work.
I think the issue is in `vtkOpenGLTexture::Load` where input ImageData is expecting an unsigned char array.
Textures loading should take into account the input image data type and corre...Loading 16-bits PNG as a texture does not work.
I think the issue is in `vtkOpenGLTexture::Load` where input ImageData is expecting an unsigned char array.
Textures loading should take into account the input image data type and correctly map the OpenGL texture format.
# Steps to reproduce:
- Create a Box
- Load the following 16-bits image as a texture:
![camera_camera_BaseColor](/uploads/7ce57d3bb1017f3d28bea96784c1fe26/camera_camera_BaseColor.png)
# Current result:
![2019-07-24-184221_856x695](/uploads/da2de169cf793b4c647ba52519f9c676/2019-07-24-184221_856x695.png)https://gitlab.kitware.com/paraview/paraview/-/issues/17800Faulty Line Styling on Log-scaled Line Chart with Hidden Values2019-08-06T19:56:06-04:00Joel A. KuleszaFaulty Line Styling on Log-scaled Line Chart with Hidden Values# Issue Summary
A data series on a log chart with a value at 0 (that is necessarily hidden) will not show line styles other than solid for the non-hidden points.
For example, series `s1_1` in the screenshot below has its left-most va...# Issue Summary
A data series on a log chart with a value at 0 (that is necessarily hidden) will not show line styles other than solid for the non-hidden points.
For example, series `s1_1` in the screenshot below has its left-most value at 0, and when a "Dot" line style is specified it is not displayed.
**Note**: When the chart is not log scaled the line style is properly applied. Marker styles are always properly applied.
# Screenshot Demonstrating Issue
![Screen_Shot_2017-10-26_at_15.15.51](/uploads/d6c34cd1a315c663e326504513b5deae/Screen_Shot_2017-10-26_at_15.15.51.png)
# Test Data File
[test_line_chart.vtk](/uploads/621f0020258283d2c822d9023968e951/test_line_chart.vtk)
----
CC: @patchett2002Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/17745Enhancement Request: Increase Line Chart Legend Swatch Width2019-08-06T19:58:28-04:00Joel A. KuleszaEnhancement Request: Increase Line Chart Legend Swatch Width# Issue Summary
When a line chart view is created with a legend, the legend swatch width demonstrating the line/marker style in the legend is small. If different line styles are used with markers, the line style can be obscured. This ...# Issue Summary
When a line chart view is created with a legend, the legend swatch width demonstrating the line/marker style in the legend is small. If different line styles are used with markers, the line style can be obscured. This is an issue if identically colored series are used. See screenshot below.
# Recommended Enhancement
Increase the swatch width so that marker and line style and color can all be clearly differentiated.
This may be increased from the current hard-coded value or set to be user defined with a larger default value (e.g., in the Legend Properties on the Properties pane).
![Screen_Shot_2017-10-02_at_08.29.44](/uploads/0132aff2ed2c818d1dc43603c18e8f30/Screen_Shot_2017-10-02_at_08.29.44.png)
# Screenshot Demonstrating Issue
In the screenshot below, it is not **clearly** apparent that the black line is also dashed.
![Screen_Shot_2017-10-02_at_08.23.30](/uploads/2530a526258268f67cac987b8613afc8/Screen_Shot_2017-10-02_at_08.23.30.png)
This is particularly problematic if identical colors are used.
![Screen_Shot_2017-10-02_at_08.23.50](/uploads/aa8ddb44d51d5fe69fe8fe8ebf8ca1cf/Screen_Shot_2017-10-02_at_08.23.50.png)
---
CC: @patchett2002Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/18237ospray expose depth of field2019-08-06T19:59:09-04:00David E. DeMarleospray expose depth of fieldOSPRay has nice support for depth of field effects in recent releases. VTK has an API for it too. We should hook them up and expose them in ParaView.OSPRay has nice support for depth of field effects in recent releases. VTK has an API for it too. We should hook them up and expose them in ParaView.https://gitlab.kitware.com/paraview/paraview/-/issues/19163External plugin are not easy to setup correctly for dynamic loading2019-08-07T04:02:48-04:00Lutz HofmannExternal plugin are not easy to setup correctly for dynamic loadingUsing ParaView 5.7.0-RC1 on Linux, built with `PARAVIEW_BUILD_SHARED_LIBS=ON`.
When building Examples/Plugins/ElevationFilter (or any plugin) externally (not within the ParaView build), only static libraries are built. This is the case ...Using ParaView 5.7.0-RC1 on Linux, built with `PARAVIEW_BUILD_SHARED_LIBS=ON`.
When building Examples/Plugins/ElevationFilter (or any plugin) externally (not within the ParaView build), only static libraries are built. This is the case for the underlying VTK module as well as the ParaView plugin.
This can be "fixed" by adding `set(BUILD_SHARED_LIBS ON)` to the top of Examples/Plugins/ElevationFilter/CMakeLists.txt.
We should add this to the cache in the CMakeLists of example plugins in order to help user avoid this error or at least fix it.
Maybe a warning when building statically would be nice as well.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19140vtkCompleteArrays/vtkXMLPRectilinearGridWriter doesn't work for rectilinear g...2019-08-07T07:47:42-04:00Andrew BauervtkCompleteArrays/vtkXMLPRectilinearGridWriter doesn't work for rectilinear grids without data on process 0vtkCompleteArrays needs to pass the X, Y and Z arrays to process 0 if process 0 has no data on it so that the vtkXMLPRectilinearGridWriter will write out the meta-data on process 0 properly. Steps to reproduce are:
1. Run ParaView and c...vtkCompleteArrays needs to pass the X, Y and Z arrays to process 0 if process 0 has no data on it so that the vtkXMLPRectilinearGridWriter will write out the meta-data on process 0 properly. Steps to reproduce are:
1. Run ParaView and connect to a pvserver with 8 MPI processes
2. Open cth.vtr which is available under ./ExternalData/Testing/Data/cth.vtr or ./ExternalData/VTK/Testing/Data/cth.vtr
3. Create an Aggregate Dataset filter with Number Of Target Processes set to 3
4. Save the output
This will fail when trying to load the saved file back into ParaView with the message "Could not find PCoordinates element with 3 arrays".5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19215Composable+recolorable export now: implied arrays are added to data.csv2019-08-07T11:49:44-04:00Ethan StamComposable+recolorable export now: implied arrays are added to data.csvFollow along with #19214 but use the sphere source instead of the wavelet
The final output has an extra scalar array, Normals_magnitude. It should not be part of the data.csv
The data.csv has:
```
timestep,producer,colorSphere1,vis,FIL...Follow along with #19214 but use the sphere source instead of the wavelet
The final output has an extra scalar array, Normals_magnitude. It should not be part of the data.csv
The data.csv has:
```
timestep,producer,colorSphere1,vis,FILE
0.0,cview_0,depth,Sphere1,RenderView1/time=0/vis=0/colorSphere1=0.im
0.0,cview_0,luminance,Sphere1,RenderView1/time=0/vis=0/colorSphere1=1.png
0.0,cview_0,Normals_0,Sphere1,RenderView1/time=0/vis=0/colorSphere1=2.png
0.0,cview_0,Normals_1,Sphere1,RenderView1/time=0/vis=0/colorSphere1=3.png
0.0,cview_0,Normals_2,Sphere1,RenderView1/time=0/vis=0/colorSphere1=4.png
0.0,cview_0,Normals_magnitude,Sphere1,RenderView1/time=0/vis=0/colorSphere1=5.png
```
The actual output is:
```
total 5600
-rw-r--r-- 1 stam staff 2.5M Jul 26 14:56 colorSphere1=0.Z
-rw-r--r-- 1 stam staff 142K Jul 26 14:56 colorSphere1=1.png
-rw-r--r-- 1 stam staff 17K Jul 26 14:56 colorSphere1=2.Z
-rw-r--r-- 1 stam staff 17K Jul 26 14:56 colorSphere1=3.Z
-rw-r--r-- 1 stam staff 17K Jul 26 14:56 colorSphere1=4.Z
```
cc @dhr5.7 (Summer 2019)David E. DeMarleDavid E. DeMarle