ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-12T22:33:46-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22526update example visualizations to incude new palette and fast color map2024-03-12T22:33:46-04:00W. Alan Scottupdate example visualizations to incude new palette and fast color mapupdate example visualizations to include new palette and fast color map. Test on all 3 OSs.update example visualizations to include new palette and fast color map. Test on all 3 OSs.5.13 (Summer 2024)W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/22525New example visualizations2024-03-12T22:31:58-04:00W. Alan ScottNew example visualizationsAdd 3 new examples to the Example Visualizations. Have them be: 1) One or more of the examples found in the Examples/ vtk folder. 2) a vtkhdf example. 3) A data analysis example, possibly with a python calculator, histogram, plot and ...Add 3 new examples to the Example Visualizations. Have them be: 1) One or more of the examples found in the Examples/ vtk folder. 2) a vtkhdf example. 3) A data analysis example, possibly with a python calculator, histogram, plot and spreadsheet.5.14 (Fall 2024)W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/22524Add VTKHDF examples to ParaView Examples directory2024-03-13T08:41:22-04:00W. Alan ScottAdd VTKHDF examples to ParaView Examples directoryPlease add some VTKHDF examples to the ParaView Examples directory. A good idea would be to add all of the examples at the bottom of the document here: https://www.paraview.org/Wiki/ParaView/Data_formats. Make sure they can be loaded a...Please add some VTKHDF examples to the ParaView Examples directory. A good idea would be to add all of the examples at the bottom of the document here: https://www.paraview.org/Wiki/ParaView/Data_formats. Make sure they can be loaded and run.5.14 (Fall 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22523Help menu - Moving data into and out of ParaView2024-03-12T22:24:32-04:00W. Alan ScottHelp menu - Moving data into and out of ParaViewPlease add a new Help menu line. Please bounce this name by Cory Q (who is better at names than I am). Possibly name the help menu "Moving data into and out of ParaView". Have this menu point at a paraview.org webpage, much as the Onl...Please add a new Help menu line. Please bounce this name by Cory Q (who is better at names than I am). Possibly name the help menu "Moving data into and out of ParaView". Have this menu point at a paraview.org webpage, much as the Online Tutorials line does (i.e., https://www.paraview.org/tutorials/).
In this new webpage, include at least the following links:
* VTK File formats: https://docs.vtk.org/en/latest/design_documents/VTKFileFormats.html
* PVD file format: This needs a new page. The best I can find is something I created maybe 10 years ago. https://www.paraview.org/Wiki/ParaView/Data_formats.
* ParaView supported file formats for read: https://docs.vtk.org/en/latest/supported_data_formats.html
* ParaView supported file formats for write: Page probably needs to be created. Note, have two sections on this page - Save Data and Export scene. Explain both.5.14 (Fall 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22499Expose Grow and Shrink selection operations in paraview.selection2024-02-28T15:19:32-05:00Cory Quammencory.quammen@kitware.comExpose Grow and Shrink selection operations in paraview.selection5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22489Release ParaView 5.12.02024-03-08T20:38:39-05:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.12.0<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.12.0` - replace with base version, e.g., 5.7.0
- `` - for release candidates, replace with "-RC?". For f...<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.12.0` - replace with base version, e.g., 5.7.0
- `` - for release candidates, replace with "-RC?". For final, replace with "".
- `5` - replace with major version number
- `12` - replace with minor version number
- `0` - replace with patch version number
- `release`: The branch to create the release on (for `x.y.0-RC1`,
`master`, otherwise `release`)
- `release`: The ParaView commit where the release should be started
Please remove this comment.
-->
# Preparatory steps
- macOS signing machine
- [x] Check that the macOS signing machine is reachable. If not, request it to be switched on.
# Update ParaView
- Update the local copy of `release`.
- If `0` is `0-RC1`, update `master`
- Otherwise, update `release`
```
git fetch origin
git checkout release
git merge --ff-only origin/release # if this fails, there are local commits that need to be removed
git submodule update --recursive --init
```
- If `release` is not `master`, ensure merge requests which should be
in the release have been merged. The [`backport-mrs.py`][backport-mrs]
script can be used to find and ensure that merge requests assigned to the
associated milestone are available on the `release` branch.
- Integrate changes.
- Make a commit for each of these `release` changes on a single topic
(suggested branch name: `update-to-v5.12.0`):
- [x] Assemble release notes into `Documentation/release/ParaView-5.12.0.md`.
- [x] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.12.0 release
echo 5.12.0 > version.txt
git commit -m 'Update version number to 5.12.0' version.txt
```
- Make a commit for each of these `release`-only changes
- [x] Merge the VTK `paraview/release` update MR
- [x] Update kwrobot with the new `paraview/release` branch rules (@ben.boeckel)
- [x] `.gitmodules` to track the `paraview/release` branch of VTK
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [x] Pull the script for each release; it may have been updated since it
was last used
- [x] Add your development fork as a remote named `gitlab`
- [x] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m release`
- [x] The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Run the test with `Do: test` and get a green dashboard.
- [x] Get positive review
- [x] `Do: merge`
- [ ] Create tag: `git tag -a -m '5.12.0' v5.12.0 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.12.0`)
- Upload tarballs to `paraview.org`
- [x] Setup your `~/.ssh/config` and add the web host (@vbolea).
- [x] `rsync -rptv $tarballs web:ParaView_Release/v5.12/`
- Software process updates (these can all be done independently)
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [ ] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `release` is `release`) version selection entry
in paraview-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Update ParaView-Superbuild
- [x] Update release branch for **paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Create new branch `git checkout -b update-to-v5.12.0 release`
- Integrate changes.
- Update versions
- [x] Guide selections in `versions.cmake`.
- [x] `paraview_SOURCE_SELECTION` version in `README.md`
- [x] `PARAVIEW_VERSION_DEFAULT` in CMakeLists.txt
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/development/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.12.0
- [x] ARG SUPERBUILD_TAG=v5.12.0
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.12
- [x] Commit changes
- [x] `git add README.md versions.cmake CMakeLists.txt Scripts/docker/ubuntu/development/Dockerfile`
- [x] `git commit -m "Update the default version to 5.12.0"`
- Make a commit for each of these `release`-only changes
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups (if `release` is `master`)
- [x] Create a commit which will be tagged:
- [x] `git commit --allow-empty -m "paraview: add release 5.12.0"`
- [x] Create tag: `git tag -a -m 'ParaView superbuild 5.12.0' v5.12.0 HEAD`
- [x] Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.paraview` user
(ask @ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.paraview` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- [x] Pull the script for each release; it may have been updated since it
was last used
- [x] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m release`
- [x] Make sure that the backporting directive in the merge-request
description skips the last commit such as: `Backport: master:HEAD~`
- Build binaries
- [x] Build binaries (start all pipelines)
- [x] Download the binaries that have been generated from the Pipeline
build products. They will be deleted within 24 hours.
- [ ] Remove fixup commit: `git reset --hard @^`
- [ ] Get positive review
- [ ] Force push `git push -f gitlab`
- [ ] `Do: merge`
- Software process updates (these can all be done independently)
- [ ] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [ ] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `release` is `release`) version selection entry
in paraview-superbuild
# Sign Windows binaries
- [x] Request Windows binary signings (only .exe archives) on the Package
Signing repo. Example request [here][win-sign-example].
# 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.12.0.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.12.0.app/`
# Validating binaries
For each binary, open the Python shell and run the following:
```python
import numpy
s = Show(Sphere())
ColorBy(s, ('POINTS', 'Normals', 'X'))
Show(Text(Text="$A^2$"))
```
Check that
- Getting started guide opens
- Help lists Readers, Writers, Filters, and Sources properly
- Examples load and match thumbnails in dialog
- Plugins are present and load properly
- OSPRay raycasting and pathtracing runs ("Enable Ray Tracing" property in View panel)
- OptiX pathtracing runs (not macOS)
- ref. !22372 for current expected results
- IndeX runs (load pvNVIDIAIndeX plugin, add a Wavelet dataset, change representaiton to NVIDIA IndeX)
Binary checklist
- [x] macOS arm64
- [x] macOS x86\_64
- [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.12/`)
- [x] Ask @cory.quammen to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website from within the directory corresponding to www.paraview.org/files/
```
buildListing.sh
updateMD5sum.sh v5.12
```
- [x] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.12.0`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.12.0`.
# Spack
- [x] Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/paraview/package.py
If making a non-RC release:
# Update documentation
- [x] Submit a Merge Request for release that updates the version to 5.12.0 in https://gitlab.kitware.com/paraview/paraview-docs/-/blob/master/doc/source/conf.py` for `paraview-docs`
- [x] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [x] Tag the HEAD of release in [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.12.0.
- [x] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [x] Go to readthedocs.org and activate
- [x] Write and publish blog post with release notes.
- [x] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [ ] Request DoD vulnerability scan
- [ ] Request an XRInterface plugin validation using [TESTING.md](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/XRInterface/TESTING.md) protocol from KEU
If making a non-RC release:
- [x] Request from comm@kitware.com an update of version number in "Download Latest Release" text on www.paraview.org
- [x] Move unclosed issues in GitLab to the next release milestone in GitLab
/cc @ben.boeckel
/cc @cory.quammen
/cc @charles.gueunet
/cc @mwestphal
[win-sign-example]: https://kwgitlab.kitware.com/software-process/package-signing/-/issues/125.12 (Winter 2023)Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.com2024-03-01https://gitlab.kitware.com/paraview/paraview/-/issues/22455ParaView date based versioning is incomplete2024-01-18T03:12:38-05:00Mathieu Westphal (Kitware)ParaView date based versioning is incompleteParaView recently switched to date based versionning, however it seems incomplete.
The date appears in `version.txt` as well as in the package names generated by ParaView-superbuild.
But it seems to be incorrect in many other places.
...ParaView recently switched to date based versionning, however it seems incomplete.
The date appears in `version.txt` as well as in the package names generated by ParaView-superbuild.
But it seems to be incorrect in many other places.
- `paraview --version` reports `paraview version 5.12.0-RC2-330-g0cf0dc5a12`
- About dialog reports `5.12.0-RC2-330-g0cf0dc5a12`
- ParaView dialog is `5.12.0-RC2-330-g0cf0dc5a12`
- find_package(ParaView) report a ParaView_VERSION `5.12.0-RC2-330-g0cf0dc5a12`
It would be nice if the versionning was coherent. Using VTK has an example would be fine imo.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22452Screenshots are incorrect size on Mac2024-01-17T10:31:31-05:00W. Alan ScottScreenshots are incorrect size on MacScreenshots are incorrect size on Mac. Here is how to replicate. Note that I am on a monitor that is 2560X1440
* 5.12.0-RC1, builtin server, Mac M1
* Sources/ Wavelet. Apply. Surface.
* File/ Save Screenshot. deleteMe (take default ...Screenshots are incorrect size on Mac. Here is how to replicate. Note that I am on a monitor that is 2560X1440
* 5.12.0-RC1, builtin server, Mac M1
* Sources/ Wavelet. Apply. Surface.
* File/ Save Screenshot. deleteMe (take default of .png). OK.
Notice that the chosen resolution is 3514X1956. This is totally, totally bogus and is a bug.
@phismith25 - Be sure to check on all three platforms.5.12.1 (Spring 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22436Aggregate Dataset Filter crashes in Catalyst2024-01-04T19:35:22-05:00W. Alan ScottAggregate Dataset Filter crashes in CatalystThe Aggregate dataset filter (I incorrectly reported as Redistribute Data Set Filter) is crashing in Catalyst API 1. Here is how to replicate.
* Run ParaView 5.11.0, remote server (16 ranks), Linux.
* Open g1s1. Apply.
* Merge Blocks. ...The Aggregate dataset filter (I incorrectly reported as Redistribute Data Set Filter) is crashing in Catalyst API 1. Here is how to replicate.
* Run ParaView 5.11.0, remote server (16 ranks), Linux.
* Open g1s1. Apply.
* Merge Blocks. (Aggregate dataset filter does not take multiblock data.)
* Aggregate dataset Filter. Number of target processes: 4. Apply.
* Extracts/ png.
* File/ Save State. Save as junkState.py file.
* pvbatch - I believe 16 ranks. junkState.py file.
* There will be a movie output of .png images.
* Going back to ParaView,
* File/ Save Catalyst State File
* Use this as the controlling script for a Catalyst run. This is primarily on Sparc, but has also been seen on Sierra.
* This will crash with an MPI error.
Note we don't think this is an MPI version issue, as other MPI areas of Catalyst work correctly.
I can't find a trace from Jeff, ask if needed.
As LANL has not seen this issue, this may need to be debugged at Sandia.
Contact is Jeff Mauldin.5.12.1 (Spring 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22416Time Manager - Animation - Follow Path is not editable2024-01-15T08:42:15-05:00W. Alan ScottTime Manager - Animation - Follow Path is not editableThe Time Manager, Animation, Follow Path is not editable. Here is how to replicate:
* 5.12.0-RC1, Linux, builtin server
* File/ open/ examples/ can.exo. Apply.
* View/ Time Manager.
* Animations/ Camera/ Follow Path. Blue +.
* Click the...The Time Manager, Animation, Follow Path is not editable. Here is how to replicate:
* 5.12.0-RC1, Linux, builtin server
* File/ open/ examples/ can.exo. Apply.
* View/ Time Manager.
* Animations/ Camera/ Follow Path. Blue +.
* Click the track. Click the "path". (Side issue, this is not obvious that you need to do this. A comment somewhere would be nice.). Camera Position.
Issue 1) I have no mouse control whatsoever of the control points. This is a feature loss. Please add it back. Next, please add the normal - enhanced mouse controls - X, Y, Z.
Issue 2) The control points are set for the can in it's intial position. It should be for the camera when the Follow Path is created. You can see this by using the steps above, but:
* After reading in the can, move the camera.
* After creating the path, click "play".5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22415Time Manager Animations needs to be clarified2023-12-07T20:48:07-05:00W. Alan ScottTime Manager Animations needs to be clarifiedThe Time Manager Animations needs clarification. Do the following:
* 5.12.0-RC1, Linux, builtin server.
* File/ Open/ Examples/ can.exo. Apply
* View/ Time Manager.
Now, we want to create an animation track.
* Animations/ Camera/ Fo...The Time Manager Animations needs clarification. Do the following:
* 5.12.0-RC1, Linux, builtin server.
* File/ Open/ Examples/ can.exo. Apply
* View/ Time Manager.
Now, we want to create an animation track.
* Animations/ Camera/ Follow Path. Click the magic blue +.
I now don't know what type of Camera control I have made. My first suggestion would be to add the words right on the track - "Follow Path Animation. Click here to customize". If that doesn't work, add another line below Camera - Renderview1.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22401Superbuild is failing using system python2024-02-07T07:46:44-05:00W. Alan ScottSuperbuild is failing using system pythonSuperbuild is failing using system python. The issue is pythonwheel is trying to be built and installed, and the install is trying to update the system. We don't have permission to write into system Python. Thus, the build breaks.
I ...Superbuild is failing using system python. The issue is pythonwheel is trying to be built and installed, and the install is trying to update the system. We don't have permission to write into system Python. Thus, the build breaks.
I have given detailed information to Ben offline.
This doesn't impact ParaView itself, but rather memory footprint for Catalyst.
@ben.boeckel5.12.1 (Spring 2024)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22379Allow midpoints of color maps to be adjusted with adjacent points being moved2023-11-27T13:41:28-05:00W. Alan ScottAllow midpoints of color maps to be adjusted with adjacent points being movedHere is a proposal from Ken Moreland. Great idea, and it is needed as we add a new default color map. In essence, allow adjustment of control points in the color map editor to proportionally scale all other control points. Keep the ori...Here is a proposal from Ken Moreland. Great idea, and it is needed as we add a new default color map. In essence, allow adjustment of control points in the color map editor to proportionally scale all other control points. Keep the original behavior as an option. Make the new behavior the default.
From Ken:
To follow up on Francesca’s description of moving the midpoint of the colormap, I suggested a slightly more general feature. The idea would be that you would be able to adjust a control point such that the remaining control points would be proportionally scaled with respect to that point. The main use case would be to change the center point as Francesca suggests, but it would work with any control point.
To make the idea clearer, here is an example. Let’s say you have a colormap with 7 evenly spaced control points. Now let’s say you grab the middle control point (the 4th one) and move it to the left. The rest of the control points stay exactly where they are, and the movement of the middle point is constrained to be between the 3rd and 5th point. To really adjust the color map to move the “middle point” from the center of the range, you must independently adjust all the control points, which is problematic even with only 7. What we would like is an alternate move mode where when I move the 4th control point to the left, the 2nd and 3rd control points move closer together and left so that points 1, 2, 3, and 4 remain evenly spaced. Likewise, the 5th and 6th control points move further apart and left so that points 4, 5, 6, and 7 remain evenly spaced.
@kmorel5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22314Selection labels of partial arrays is broken2023-09-25T22:03:52-04:00W. Alan ScottSelection labels of partial arrays is brokenSelection labels of partial arrays are broken.
First, I made a dataset. This dataset replicates a user's dataset, so I don't think the issue is with my voodoo'd dataset. Load can.exo. Load only the first block. Turn ACCL off. Save ...Selection labels of partial arrays are broken.
First, I made a dataset. This dataset replicates a user's dataset, so I don't think the issue is with my voodoo'd dataset. Load can.exo. Load only the first block. Turn ACCL off. Save with the IOSS writer. Load the second block only. Turn only VEL off. Save with the IOSS writer. Change files to be can3.e.2.\[0,1\]. Now, we should have two blocks with partial arrays.
* Linux, master, builtin server.
* Load can3.e.2.\[0,1\]. Apply.
* Find Data. Selection labels. Display ACCL.
* Multiblock inspector. Select first block. Select last block. Select all blocks.
What should happen is that if the data is missing, nothing shows without an error. If the data is present, it should show. Finally, if the data is only one one of the two blocks, that block should have annotations, but not both. This fails.
Attaching can3.e.2.\[0,1\]5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22313Allow "selection labels" without selection2023-09-25T21:11:08-04:00W. Alan ScottAllow "selection labels" without selectionThe Selection Labels functionality is extremely powerful. Currently it shows variable data on cells/points that are selected. However, it should also be available for all of the cells and points being shown, without selection. Selecti...The Selection Labels functionality is extremely powerful. Currently it shows variable data on cells/points that are selected. However, it should also be available for all of the cells and points being shown, without selection. Selection adds a pink highlight around selected cells or on points, and users may want to show their mesh, with some variable labeled, without this pink highlight.
Please add a checkbox on the Find Data dialog/ Selection Labels section named "label without selection" or somesuch.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22274New defaut colormap2024-03-23T23:51:52-04:00W. Alan ScottNew defaut colormapPlease make the colormap named Fast on the Presets dialog the new default map.
Issue # 22271 created the Fast color map.
Showstopper for 5.13.0.Please make the colormap named Fast on the Presets dialog the new default map.
Issue # 22271 created the Fast color map.
Showstopper for 5.13.0.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22273New default palette2024-03-23T23:51:57-04:00W. Alan ScottNew default palettePlease make the palette background color named Warm Gray Background (98,93,90) the new default.
#22270 created the palette.
Showstopper for 5.13.0.Please make the palette background color named Warm Gray Background (98,93,90) the new default.
#22270 created the palette.
Showstopper for 5.13.0.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22260Speed up sideset reads in the IOSS reader/library reading Exodus2023-08-10T13:08:57-04:00W. Alan ScottSpeed up sideset reads in the IOSS reader/library reading ExodusWe found a major performance degredation in the IOSS reader/library. This was mostly solved in #22227, by changing
`dbase->set_surface_split_type(Ioss::SPLIT_BY_TOPOLOGIES);` to `dbase->set_surface_split_type(Ioss::SPLIT_BY_ELEMENT_BLO...We found a major performance degredation in the IOSS reader/library. This was mostly solved in #22227, by changing
`dbase->set_surface_split_type(Ioss::SPLIT_BY_TOPOLOGIES);` to `dbase->set_surface_split_type(Ioss::SPLIT_BY_ELEMENT_BLOCKS);` This changed the performance degredation from about 2 orders of magnitude slower to 4x slower. We still want to discuss, research and possibly implement speeding current code up to the speeds of the Exodus reader/library.
Here is a comment from Greg Sjaardema from #22227:
OK, I think the issue is that the caching that IOSS does is to check whether the current side's parent element is from the same element block as the previous side's parent element. The sidesets in this model somewhat follow that assumption, but do switch back and forth a few/many times which results in a new query of the element block connectivity.
So, we aren't seeing 199,427 exodus calls, but we aren't seeing 2 either...
There are a few ways to fix this. I need to see what would be the least intrusive and behavior changing...
1. Can sort the elements (based on internal id, not global id) in the SideBlock lists which would guarantee an orderly progression through the element blocks.
1. Could process the sideblock element lists multiple times -- once per block. Fairly easy, but need to calculate some offsets based on the face node counts to know where to store the connectivity when skpping over elements that are not in the current element block. Not too difficult, but some added bookkeeping.
1. Cache element connectivity for multiple element blocks instead of just the "current" block. Uses more memory.
1. If sidesets use the SPLIT_BY_ELEMEMT_BLOCK method for generating homogenous sideblocks, then process in element block order by default.
@spiros.tsalikis @gsjaardema5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22254When creating two Box sources, with the Boxes not centered on the origin, sel...2023-08-16T08:23:38-04:00Phil SmithWhen creating two Box sources, with the Boxes not centered on the origin, selecting the Outline representation is incorrect.Steps to reproduce:
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
* Representation to outline
* Select Box from the sources menu
* For illu...Steps to reproduce:
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
* Representation to outline
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
This appears to work correctly on either builtin or when connected to the server of your choice. I think it is working correctly when builtin is being used, because the dementions of both boxes are the same, but I could be incorrect. This only happens when there is an offset to the center of the box.
I also noticed that when connected to a server and outline is selected as the representation for Box1, the bottom of the box gets elongated. This may be the expected behavior, because the center is off, but then the builtin would be incorrect, because it dose not elongate the outline under the same circumstances.
Thanks,
\-Phil5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22231Programmable Annotation fails for field data2023-07-25T04:18:19-04:00W. Alan ScottProgrammable Annotation fails for field dataThe Programmable Annotation filter fails with field data. Here is what I am looking for.
* We need to be able to annotate different datasets and types of field data. Please use can.ex2 and mb.vtm (dataset from Mathieu - a vtm file of c...The Programmable Annotation filter fails with field data. Here is what I am looking for.
* We need to be able to annotate different datasets and types of field data. Please use can.ex2 and mb.vtm (dataset from Mathieu - a vtm file of can.exo).
* Please add a section to ParaView Reference Manual, section 5.4, showing how to annotate the following. We will use this section for testing.
* A point from point data. For instance, point 100.
* A cell from cell data. For instance, cell 100.
* Field data. For instance title, or QA Records, or NSTEPS.
* Add an example of writing two lines of field data. (Can it be done with one Programmable Annotation, or does it take two? Two is acceptable.)
* There is a known issue accessing field data, documented for the Programmable Filter in #21104. This will need to be fixed.5.13 (Summer 2024)