ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:23:47-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21130Axis scale factor2024-03-07T20:23:47-05:00W. Alan ScottAxis scale factorAs written up on Discourse, we need to add the ability to independently scale axes. Users will generally scale the Z axis, but lets make it more generic. This is different than the transform filter scale, where the data in some axis is...As written up on Discourse, we need to add the ability to independently scale axes. Users will generally scale the Z axis, but lets make it more generic. This is different than the transform filter scale, where the data in some axis is changed. An example of this feature would be an oil field that has X and Y of 20 miles and Z of .5 miles. Visualizing this would make it look like a 2d slice, where you want to see a 3d cube. Transform filter doesn't work, as a cube axis would then lie about the depth of the oil field. Please add this control to the Properties tab, somewhere around Cube Axis. Make this feature sticky (as users will probably be using it over and over on similar data). Optionally print "Z Axis: 10X" for the example of the Z axis being expanded 10X, lower right below the Orientation Axis, default on.
https://discourse.paraview.org/t/axis-scale-factor-or-vertical-exaggeration-of-z-axis/48085.13 (Summer 2024)Aron HelserAron Helserhttps://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/22153Axis grid is SLOW when zoomed in2023-05-25T10:49:06-04:00W. Alan ScottAxis grid is SLOW when zoomed inThe axis grid is slow when zoomed in. It can be bad enough that it appears to hang. Here is how to replicate.
* 5.11.1, Linux, builtin server.
* Open can.exo. Don't touch it. Apply.
* Axis grid.
* On the left side you will see a coor...The axis grid is slow when zoomed in. It can be bad enough that it appears to hang. Here is how to replicate.
* 5.11.1, Linux, builtin server.
* Open can.exo. Don't touch it. Apply.
* Axis grid.
* On the left side you will see a coordinate of 4 on the y axis. Place your mouse on the edge of the can just to the right of the 4.
* <CTRL>, and now Right mouse button, and pull down. Do down (zoom in) until the axis grid goes away, and then reverse until the axis grid reappears. Let go of the mouse.
ParaView will tend to freeze as a bazillion axis grid labels are calculated. This is very, very bad behavior. We need to fix it.5.13 (Summer 2024)https://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/21692color blocks in a multiblock by different variables2023-12-12T12:20:07-05:00Boonthanome Nouanesengsycolor blocks in a multiblock by different variablesWe would like the ability to color blocks in the same multiblock by different variables. For example, let's say there's a multiblock with two blocks. We would like to be able to color the first block by density, and then the second block...We would like the ability to color blocks in the same multiblock by different variables. For example, let's say there's a multiblock with two blocks. We would like to be able to color the first block by density, and then the second block by velocity. This is achievable with the `Extract Blocks` filter, but we would like an easier way to do this. Maybe in the Multi-block Inspector.
It is important to be able to turn on/off visibility of certain blocks while they are being colored by different variables. We can turn on/off visibility with the Multi-block inspector, but just keep in mind we need to keep that functionality.
@patchett2002 @cory.quammen5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21181Python Editor not closing tabs correctly2024-03-07T20:23:48-05:00W. Alan ScottPython Editor not closing tabs correctlyThe Python Editor is not closing tabs correctly. If a user creates a trace (i.e., Tools/ Start Trace, Tools/ Stop Trace), and goes File/ Close, upon creating another trace, the old tab still exists and is populated. This is a bug.
Lin...The Python Editor is not closing tabs correctly. If a user creates a trace (i.e., Tools/ Start Trace, Tools/ Stop Trace), and goes File/ Close, upon creating another trace, the old tab still exists and is populated. This is a bug.
Linux, 5.10.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21015Enable opacity mapping using a different array than the color table2024-03-07T20:23:46-05:00W. Alan ScottEnable opacity mapping using a different array than the color tablePlease enable opacity mapping using a different array than the color table. Also, clean up opacity mapping of volume rendering.
* Volume rendering evidentially allows a different color map than opacity map, but I can't find it. It is ...Please enable opacity mapping using a different array than the color table. Also, clean up opacity mapping of volume rendering.
* Volume rendering evidentially allows a different color map than opacity map, but I can't find it. It is evidentially on the Properties tab. Please move this to the Color Editor.
* Opacity mapping needs to also optionally, default off, have an independent opacity map added, seperate from the color map.
Discourse discussion and request written up here: https://discourse.paraview.org/t/enable-opacity-mapping-for-surfaces-using-a-different-array-than-for-color-mapping/76465.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20330v5.9-RC1 going full screen (F11) in C/S mode crashes2024-03-07T20:23:44-05:00Jean M. Favrev5.9-RC1 going full screen (F11) in C/S mode crasheswhen connecting my desktop client to a remote ParaView server (1 node, 1 task, with EGL or with osmesa), with an empty pipeline, going to full screen (F11) crashes ParaView immediately.
the same does not happen with 5.8 compiled with th...when connecting my desktop client to a remote ParaView server (1 node, 1 task, with EGL or with osmesa), with an empty pipeline, going to full screen (F11) crashes ParaView immediately.
the same does not happen with 5.8 compiled with the same options/compilers on client and server by myself. server-side, I see:
```
( 13.978s) [pvserver ]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x7d5ba0): Could not receive tag. 1
( 13.978s) [pvserver ]vtkTCPNetworkAccessMana:297 ERR| vtkTCPNetworkAccessManager (0x6e7b40): Some error in socket processing.
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20227Labels are overlapping in the Color Legend2024-03-27T12:19:16-04:00W. Alan ScottLabels are overlapping in the Color LegendLabels are overlapping in the Color Legend. Here is how to replicate:
* ParaView 5.8.0, and master, Linux, local server.
* Load vessel_out.e (Attached). All vars on. Apply.
* Last timestep.
* Paint by _disp.
* Drag the color legend...Labels are overlapping in the Color Legend. Here is how to replicate:
* ParaView 5.8.0, and master, Linux, local server.
* Load vessel_out.e (Attached). All vars on. Apply.
* Last timestep.
* Paint by _disp.
* Drag the color legend to be horizontal, under the dataset.
* Now, drag the color legend to be wider and narrower. The labels will overlap.
Attaching a screenshot.
Workaround is in the Color Legend Editor. You can turn off Automatic Label Format, and then change the format.
![Screen_Shot_2020-09-24_at_3.55.28_PM](/uploads/6f172402f63908242133a6a6ba176a3f/Screen_Shot_2020-09-24_at_3.55.28_PM.png)5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/18125Camera animation2023-07-17T17:50:20-04:00Utkarsh AyachitCamera animationWe need to revisit camera animation in ParaView. The current UI is quite clumsy and cumbersome to use. Here are some of the limitations of the current one:
1. "follow path" uses a fixed up direction for the whole path. To overcome this ...We need to revisit camera animation in ParaView. The current UI is quite clumsy and cumbersome to use. Here are some of the limitations of the current one:
1. "follow path" uses a fixed up direction for the whole path. To overcome this issue, folks split the path, but then change in the view up direction is abrupt between paths.
2. "follow path" doesnt offer mechanism to use current camera parameters like "interpolate camera locations"
3. setting up parameters for multiple paths for "follow path" is insanely complex esp when trying to keep end points consistent.
5. "Interpolate camera locations" mode doesn't offer linear interpolation mode. The current interpolation has tendency to overshoot.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18002Glyph filter GUI for 2D Glyphs is terrible2024-03-07T20:47:47-05:00Kenneth MorelandGlyph filter GUI for 2D Glyphs is terribleThe interface for the Glyph filter is fine for "3D Glyphs," but it also supports what it calls "2D Glyphs" (like flat polygonal glyphs or vertex cells), and the interface for those is stupid. I'll go over the steps to create vertex cells...The interface for the Glyph filter is fine for "3D Glyphs," but it also supports what it calls "2D Glyphs" (like flat polygonal glyphs or vertex cells), and the interface for those is stupid. I'll go over the steps to create vertex cells (which is something I use the Glyph filter frequently for to convert a set of points with no cell data to something that you can see).
1. Under `Glyph Type` you cannot select `Vertex`. Instead you select `2D Glyph`. (Never mind that a vertex is not 2D).
2. Now there is a second combo box also labeled `Glyph Type`. Yes, that's right. There are two combo boxes with _the exact same name_. Yeah, that makes no sense.
3. In this second `Glyph Type` combo box, you can select `Vertex`.
4. But wait, you probably already got confused in step 2 because you didn't see the second `Glyph Type` combo box. That's because it is an "advanced" property. That's right, to select any 2D Glyph you have to have the advanced properties on.
This does not make any sense. Instead, the 2D glyphs should just be listed in the `Glyph Type` combo box. So instead of selecting `2D Glyph` in the combo box, you should just be able to select `Vertex` right there.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17643Add the ability to auto set 2d plots over all time2024-03-07T20:47:45-05:00W. Alan ScottAdd the ability to auto set 2d plots over all timeWe need the ability to automatically set the left, right, top and bottom axes for 2d plots. For instance, I want to be able to do the following;
* Open can.exo. All variables on. Apply.
* Plot over line. Apply. Turn on display of o...We need the ability to automatically set the left, right, top and bottom axes for 2d plots. For instance, I want to be able to do the following;
* Open can.exo. All variables on. Apply.
* Plot over line. Apply. Turn on display of only DISPL and ACCL. Place ACCL on the Right axis.
* Lock the bottom, right and left axis with Use Custom Range for each axis.
Now, I want the ability to set these over all timesteps, same as Rescale to Data Range over All Timesteps does for color.5.13 (Summer 2024)https://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/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)