ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-08-15T21:37:31-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19246ParaView 5.7.0-RC2: mac icon missing2019-08-15T21:37:31-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC2: mac icon missingThe .app bundle does not have the ParaView icon but rather the default application icon.The .app bundle does not have the ParaView icon but rather the default application icon.5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19245The cell data to point data and point data to cell data filters should pass f...2019-08-15T22:30:28-04:00Andrew BauerThe cell data to point data and point data to cell data filters should pass field dataThe cell data to point data and point data to cell data filters should pass field data
Steps to reproduce:
1. Load [pointdatawithfielddata.vti](/uploads/f0473e3dd7a9d4d02d9d28aa37097d6d/pointdatawithfielddata.vti)
2. Use the `Point Data...The cell data to point data and point data to cell data filters should pass field data
Steps to reproduce:
1. Load [pointdatawithfielddata.vti](/uploads/f0473e3dd7a9d4d02d9d28aa37097d6d/pointdatawithfielddata.vti)
2. Use the `Point Data to Cell Data` filter
3. The `dog` field data array is no longer available to the output of the `Point Data to Cell Data` filter
A VTK fix is at https://gitlab.kitware.com/vtk/vtk/merge_requests/5844
@cory.quammen @utkarsh.ayachit could we get this into ParaView 5.7? I consider this a bug.5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19242External plugin do not support testing with baseline2019-11-19T19:55:30-05:00Mathieu Westphal (Kitware)External plugin do not support testing with baselineIt looks like external plugin cannot have baseline XML tests.
The following testing CMakeLists.txt :
```
enable_testing()
ExternalData_Add_Target(TestPluginData)
ExternalData_Expand_Arguments(TestPluginData
"DATA{Data/Bas...It looks like external plugin cannot have baseline XML tests.
The following testing CMakeLists.txt :
```
enable_testing()
ExternalData_Add_Target(TestPluginData)
ExternalData_Expand_Arguments(TestPluginData
"DATA{Data/Baseline/Test.png}"
)
paraview_add_client_tests(
LOAD_PLUGIN "OverrideXMLOnly"
BASELINE_DIR "/home/glow/tmp/OverrideXMLOnly/Plugin/Testing/Data/Baseline"
TEST_DATA_TARGET TestPluginData
TEST_SCRIPTS Test.xml)
```
Result to the following smTestDriver command :
`/home/glow/work/paraview/paraviewSecondary/paraview_build/bin/smTestDriver-pv5.7 "--enable-bt" "--client" "/home/glow/work/paraview/paraviewSecondary/paraview_build/bin/paraview" "--enable-bt" "--test-plugin=OverrideXMLOnly" "--test-script=/home/glow/tmp/OverrideXMLOnly/Plugin/Testing/Test.xml" "--test-directory=/home/glow/tmp/OverrideXMLOnly/build/Testing/Temporary" "--test-baseline=/home/glow/tmp/OverrideXMLOnly/build/ExternalData/Plugin/Testing/Data/Baseline/Test.png" "-dr" "--exit"`
The incorrect part is
`--test-baseline=/home/glow/tmp/OverrideXMLOnly/build/ExternalData/Plugin/Testing/Data/Baseline/PanoramicProjectionEquirectangular.png`
When it would be expected to be
`--test-baseline="/home/glow/tmp/OverrideXMLOnly/Plugin/Testing/Data/Baseline/PanoramicProjectionEquirectangular.png"`
Notes :
* Here is the full plugin if needed, A lightly modified [OverrideXMLOnly.tgz](/uploads/fc43eac761d0f932f4d783c054ebd232/OverrideXMLOnly.tgz).
* Tests must be run from build/Plugin/Testing, unexpected and not really practical
* I'm not sure about the ExternalData part. is it needed ? Is it done correctly ?
* The build directory contains an ExternalData directory, with only an empty Object directory inside.
* During configuration, I see this :
`-- Linked Plugin/Testing/Data/Baseline/Test.png.sha512 to ExternalData SHA512/22efa16a9a46ccf58de47a36c568521b6dd3737533ded2bfee979a3da11936fbe923a6a9dae25cfb14a135223ecc1a7e4a45fa0ce4b926d43bc112b55f115c71`
Which results to a sha512 and object file in src/Plugin/Testing/Data/Baseline/, I do **not** want that.
@ben.boeckelMathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19240Help/ Example Visualizations/ Can fails on nightly2019-09-11T21:37:02-04:00W. Alan ScottHelp/ Example Visualizations/ Can fails on nightlyHelp/ Example Visualizations/ Exodus II File with timesteps. Clip filter. When run, the Layout stays white. I have to actually click on a clip, then turn on visibility. Then, I see two views, and data from the selected clip, but not ...Help/ Example Visualizations/ Exodus II File with timesteps. Clip filter. When run, the Layout stays white. I have to actually click on a clip, then turn on visibility. Then, I see two views, and data from the selected clip, but not the other one.
Showstopper bug for 5.7.0.
Nightly (5.7.0-RC1-231-g72ff4fc), Linux, local server.5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19238Web: Pushing proxy property change doesn't trigger render in Python32021-11-04T11:21:35-04:00Scott WittenburgWeb: Pushing proxy property change doesn't trigger render in Python3With the latest 5.7 release candidate binaries, and only under Python3, ParaViewWeb visualizer can get into a state where changing proxy properties and applying them is not reflected in the 3D view until you interact with it in some way....With the latest 5.7 release candidate binaries, and only under Python3, ParaViewWeb visualizer can get into a state where changing proxy properties and applying them is not reflected in the 3D view until you interact with it in some way. To reproduce:
1. Create a cone
2. Change resolution and apply (you should see change reflected w/out needing to interact)
3. Delete the cone
4. Create a sphere
5. Change resolution phi or theta resolution and apply (change is not reflected until you interact)
After this point, it seems no more property changes applied to any pipeline elements are reflected in the view until you interact, or else kill the server and start fresh.5.10 (Fall 2021)Scott WittenburgScott Wittenburghttps://gitlab.kitware.com/paraview/paraview/-/issues/19237Release ParaView 5.7.0-RC22019-08-09T15:02:43-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.7.0-RC2# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Assemble release notes into `Documentation/release/ParaView-5.7.0`.
- [x] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.7.0-RC2
echo 5.7.0-RC2 > version.txt
git commit -m 'Update version number to 5.7.0-RC2' version.txt
git tag -a -m 'ParaView 5.7.0-RC2' v5.7.0-RC2 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.7.0-RC2:release v5.7.0-RC2`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.7.0-RC2`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.7/`
# Update ParaView-Superbuild
- Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
```
- 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.7.0-RC2" CACHE STRING "Force version to 5.7.0-RC2" 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-RC2"`
- 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.7.0-RC2' v5.7.0-RC2 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC2:release v5.7.0-RC2`
# 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
- [x] 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.ayachitCory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19236Line source: add multiple ways of generating sample points2020-01-16T18:47:56-05:00Utkarsh AyachitLine source: add multiple ways of generating sample pointsCurrently line source only supports sampling with equal spacing between sample points along the line. Add support for other modes including: geometric distribution, hyperbolic tangent distribution (one-sided and two-sided), a gaussian di...Currently line source only supports sampling with equal spacing between sample points along the line. Add support for other modes including: geometric distribution, hyperbolic tangent distribution (one-sided and two-sided), a gaussian distribution.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19235Catalyst script generator creates inconsistent variable names with plotOverLine2020-06-03T13:14:56-04:00Kyle SchauCatalyst script generator creates inconsistent variable names with plotOverLineI am using the prebuild Paraview 5.6.1 binary found [here](https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.6&type=binary&os=Linux&downloadFile=ParaView-5.6.1-MPI-Linux-64bit.tar.gz) to generate Catalys...I am using the prebuild Paraview 5.6.1 binary found [here](https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.6&type=binary&os=Linux&downloadFile=ParaView-5.6.1-MPI-Linux-64bit.tar.gz) to generate Catalyst scripts. If I use the plot over line filter as a desired PolyData export on a Multiblock Data Set the python script generated initialized the plot over line as
```
xmf = coprocessor.CreateProducer(datadescription, 'input')
# create a new 'Plot Over Line'
plotOverLine1 = PlotOverLine(Input=xmf, Source='High Resolution Line Source')
```
But when the XMLPolyDataWriter is created, its input variables has incorrect capitalization on the plotOverLine variables
```# Now any catalyst writers
xMLPPolyDataWriter1 = servermanager.writers.XMLPPolyDataWriter(Input=plotoverline1)
```
The input to the writer should be `plotOverLine1` not `plotoverline1`5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19233Add circle source2019-08-15T21:44:43-04:00W. Alan ScottAdd circle sourcePlease add a 3d circle source. This is needed as a seed for other filters (such as stream tracer with custom source with curvilinear data). Please add the same controls as Cylinder - i.e., Resolution, center and Radius.Please add a 3d circle source. This is needed as a seed for other filters (such as stream tracer with custom source with curvilinear data). Please add the same controls as Cylinder - i.e., Resolution, center and Radius.5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19232ospray target was not found when compiling a ParaView plugin2019-08-27T13:20:02-04:00Charles Gueunetospray target was not found when compiling a ParaView pluginWe are building a collection of filters in a Paraview plugin and have encoutered an error when ParaView is compiled with the option: `PARAVIEW_USE_RAYTRACING`.
During the generate phase of our project we have the following error:
```
CM...We are building a collection of filters in a Paraview plugin and have encoutered an error when ParaView is compiled with the option: `PARAVIEW_USE_RAYTRACING`.
During the generate phase of our project we have the following error:
```
CMake Error at /home/charles/Software/compil/ParaView/build/lib64/cmake/paraview-5.7/ParaViewPlugin.cmake:935 (add_library):
Target "TopologyToolKit" links to target "ospray::ospray" but the target
was not found. Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
Call Stack (most recent call first):
paraview/singlePlugin/CMakeLists.txt:1 (paraview_add_plugin)
CMake Error at /home/charles/Software/compil/ParaView/build/lib64/cmake/paraview-5.7/vtkModuleWrapClientServer.cmake:179 (add_library):
Target "ttkUncertainDataEstimatorCS" links to target "ospray::ospray" but
the target was not found. Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
Call Stack (most recent call first):
/home/charles/Software/compil/ParaView/build/lib64/cmake/paraview-5.7/vtkModuleWrapClientServer.cmake:305 (_vtk_module_wrap_client_server_library)
/home/charles/Software/compil/ParaView/build/lib64/cmake/paraview-5.7/ParaViewPlugin.cmake:655 (vtk_module_wrap_client_server)
paraview/singlePlugin/CMakeLists.txt:1 (paraview_add_plugin)
...
```
Maybe a `fing_dependency` is missing in a ParaView cmake file somewhere?
Charleshttps://gitlab.kitware.com/paraview/paraview/-/issues/19231We need frozen python2019-11-19T19:00:08-05:00W. Alan ScottWe need frozen pythonWe need the ability to make Python frozen. This needs to be an option in the Superbuild, and if possible, should default on.
This is needed for performance reasons on pvserver (and Catalyst) loads on HPC clusters for large viz runs.We need the ability to make Python frozen. This needs to be an option in the Superbuild, and if possible, should default on.
This is needed for performance reasons on pvserver (and Catalyst) loads on HPC clusters for large viz runs.5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19228Please add a Global [node,element] Id generator filter2019-08-26T20:45:39-04:00W. Alan ScottPlease add a Global [node,element] Id generator filterPlease add a filter to ParaView that will generate GlobalNodeIds and GlobalElementIds. After running this filter, these new ids must be unique for the whole dataset.
Needs to work for Exodus datasets as well as CGNS datasets.
This is ...Please add a filter to ParaView that will generate GlobalNodeIds and GlobalElementIds. After running this filter, these new ids must be unique for the whole dataset.
Needs to work for Exodus datasets as well as CGNS datasets.
This is a Watney bug.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/192275.6.1 builds with python 3.4.x import error2019-08-01T14:24:13-04:00Ethan Stam5.6.1 builds with python 3.4.x import error@ben.boeckel @demarle
Tested with superbuild tag v5.6.1-python3 using v5.6.1 paraview tag.
Python 3.4.9 was used in this build.
```
pvpython
>>> import vtk
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
Fi...@ben.boeckel @demarle
Tested with superbuild tag v5.6.1-python3 using v5.6.1 paraview tag.
Python 3.4.9 was used in this build.
```
pvpython
>>> import vtk
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/projects/paraview/stam/07-26-19/paraview-sdk/5.6.1-py3-osmesa_intel-18.0.2_openmpi-2.1.2_python-system3/lib/python3.4/site-packages/vtk.py", line 31, in <module>
all_m = importlib.util.module_from_spec(all_spec)
AttributeError: 'module' object has no attribute 'module_from_spec'
```
A superbuild patch is in for this at my branch: https://gitlab.kitware.com/ethan.stam/paraview-superbuild/commit/f966590da76eaf9c5c6df08fc9fb3d3dccc145ac
This patch needs to go in the v5.6.1-python3 tag if that's possible.5.6.1Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19226Point IDs are misnamed with CGNS.2019-08-01T15:10:55-04:00W. Alan ScottPoint IDs are misnamed with CGNS.Point (and possibly cell) Ids are misnamed with CGNS. Here is how to replicate.
* Linux, remote server (I have 16 ranks), 5.7.0-RC1.
* Load the Watney CGNS dataset.
* Split View Vertical. Spreadsheet view.
* Sort on PointID.
Th...Point (and possibly cell) Ids are misnamed with CGNS. Here is how to replicate.
* Linux, remote server (I have 16 ranks), 5.7.0-RC1.
* Load the Watney CGNS dataset.
* Split View Vertical. Spreadsheet view.
* Sort on PointID.
There are hundreds of point id 0! This is actually written up as #19225. Notice that we have a Point ID column.
We need a unique handle to find points and cells for data analysis. This isn't it.
* Next, run filter Generate IDs.
* Have the Generate Ids filter show in the spreadsheet.
There are two Point IDs (well, Pointids and Point ID). Which is which? Please change label to say what this is!!
* Find Data. Points. GenerateIds1.
Now, open the pulldown to chose variable. Options are ID (what is this?), PointIds (I assume from GenerateIds, but can't tell), Point and Query.
Please have Point Id's be consistent between all tools!
* View/ Selection Inspector. Cell Labels.
We now have ID. Again, what is this?
Obviously, go through the same process for Cells.
Watney bug.5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19225Point Ids and Cell Ids are broken with CGNS2019-08-01T14:15:37-04:00W. Alan ScottPoint Ids and Cell Ids are broken with CGNSPoint Ids and Cell IDs are broken with CGNS. Here is how to replicate.
* Linux, remote server (I have 16 ranks), 5.7.0-RC1.
* Load the Watney CGNS dataset.
* Split View Vertical. Spreadsheet view.
* Sort on PointID.
There are hu...Point Ids and Cell IDs are broken with CGNS. Here is how to replicate.
* Linux, remote server (I have 16 ranks), 5.7.0-RC1.
* Load the Watney CGNS dataset.
* Split View Vertical. Spreadsheet view.
* Sort on PointID.
There are hundreds of point id 0! What is point id, where does it come from, and why is it all zero?
We need a unique handle to find points and cells for data analysis. This isn't it.
Cell IDs have the same issue.
Watney bug.5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19224Save Data, csv file, from streamtracer is bad2019-08-16T15:32:57-04:00W. Alan ScottSave Data, csv file, from streamtracer is badSave data, to a csv file, from a streamtracer is bad.
I don't know how to simplify this bug. If desired, ask me and I can try to simplify.
* 5.7.0-RC1, remote server (16 ranks), Linux.
* Load the Watney CGNS dataset. Load density, ...Save data, to a csv file, from a streamtracer is bad.
I don't know how to simplify this bug. If desired, ask me and I can try to simplify.
* 5.7.0-RC1, remote server (16 ranks), Linux.
* Load the Watney CGNS dataset. Load density, T, velocity_1, velocity_2 and velocity_3. Apply.
* Cell Data to Point Data filter. Apply.
* Calculator filter. `velocity_1*iHat+velocity_2*jHat+velocity_3*kHat` . Result name velvec
* (Not required) Surface. (Not required) Paint by velvec.
* Sources/ Point Source. 0.67, 0.03, 0.12. Apply.
* Click on Calculator in the pipeline browser.
* Stream Tracer with Custom Source. Seed Source == PointSource. OK. Apply.
* Turn visibility of Calculator off.
* Paint by Velocity_1. Notice Velocity_1 goes from about 1000 to 2000. (Note, I rounded the numbers to the nearest thousand.)
* In the information tab, look at velocity_1.
* If interested, you can look at this data with the spreadsheet. Notice column Velocity_1. All looks correct.
* File/ Save Data. OK, OK.
* Move this data somewhere you can open it in a spreadsheet.
* Look at column velocity_1. It starts reasonably well, in the 2000's, then goes to around 0.01 at point 21, then moves back to expected at point 92.
Ask me if you want the .csv file that I just wrote out with actual data.
This is a Watney bug.
Showstopper for the 5.7.0 release.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19221intermittent cinema test failures on tylo from vtkThreadedImageWriter2020-04-07T03:42:07-04:00David E. DeMarleintermittent cinema test failures on tylo from vtkThreadedImageWriterThe CoProcessingFullWorkflowCinema* tests intermittently hang and timeout on tylo, our windows python 3 tester. Debugging on the machine indicates that the hang occurs inside this line:
https://gitlab.kitware.com/paraview/paraview/blob/m...The CoProcessingFullWorkflowCinema* tests intermittently hang and timeout on tylo, our windows python 3 tester. Debugging on the machine indicates that the hang occurs inside this line:
https://gitlab.kitware.com/paraview/paraview/blob/master/ThirdParty/cinema/paraview/tpl/cinema_python/adaptors/paraview/pv_introspect.py#L487 when we construct a cinema store to work with and in particular when we initialize the VTK threaded image writer https://gitlab.kitware.com/paraview/paraview/blob/master/ThirdParty/cinema/paraview/tpl/cinema_python/database/raster_wrangler.py#L80
Be warned, there are Heisenbug aspects here, inserting prints before the code in question makes it pass more often, and perhaps every time.https://gitlab.kitware.com/paraview/paraview/-/issues/19220View menu entries should be sorted2019-08-15T22:16:02-04:00Joachim PouderouxView menu entries should be sortedEntries in the View menu are not sorted (including the panels/views and the Control bar submenu) which is not very practical.
They should be sorted so the user can more quickly access the entries she is looking for.
![Screenshot_2019072...Entries in the View menu are not sorted (including the panels/views and the Control bar submenu) which is not very practical.
They should be sorted so the user can more quickly access the entries she is looking for.
![Screenshot_20190729_133349](/uploads/aeb862ece93e79ed7fdd53bee1fcd8d5/Screenshot_20190729_133349.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19217Cinema 'Export Now' exports incorrect float (recolorable) images2019-09-09T14:35:17-04:00DavidCinema 'Export Now' exports incorrect float (recolorable) imagesFloat images exported contain only ```Nan``` values.
Attached is a folder containing files to run the following test, which shows the bug:
[float_bug.zip](/uploads/6d8bf3eb690eda591e0d0b2a6083a4c0/float_bug.zip)
- open ParaView
- load...Float images exported contain only ```Nan``` values.
Attached is a folder containing files to run the following test, which shows the bug:
[float_bug.zip](/uploads/6d8bf3eb690eda591e0d0b2a6083a4c0/float_bug.zip)
- open ParaView
- load small.csv
- close the table view window that is created
- add TableToStructuredGrid filter, setting the following:
- Whole extents to 0,1 0,1 0,0
- 'X column' to x
- 'Y column' to y
- 'Z column' to z
- Coloring to 'scalar'
- Zoom so that the data fills the entire view (there is no background showing)
- run the ```test.xml``` script
- Change the 'Root Directory' field to export ```test.cdb``` to this test directory
- File->Export Now
- run ```uncompress``` script
- this will produce one ```raw``` files:
- ```uncompressed_scalar.raw```
- ```uncompressed_depth.raw```
- run ```od -f uncompressed_scalar.raw```
- this shows that the resulting uncompressed image contains only ```NaN``` values5.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19216Composable+Recolorable specD export of mandelbrot crashes2019-08-13T09:22:25-04:00Ethan StamComposable+Recolorable specD export of mandelbrot crashesTested on MacOS 10.13.6 with the 5.7.0-RC1 nightly binary
Follow along with #19215, but use the Mandelbrot source
* Enable and pick iterations in export inspector->advanced->data extracts->cinema image options
* Export a static cinem...Tested on MacOS 10.13.6 with the 5.7.0-RC1 nightly binary
Follow along with #19215, but use the Mandelbrot source
* Enable and pick iterations in export inspector->advanced->data extracts->cinema image options
* Export a static cinema image database with composable+recolorable selected
* Check "Save the cinema D table" as well
* File -> Export Now crashes my client
This seems too specific to worry about getting a fix in 5.7.0, as it is the only case we've found to cause the crash.
cc: @demarle @dhr5.7 (Summer 2019)