ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-03-13T08:24:12-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21817ParaView fails to find ExprTk due to changed type in the version variable2023-03-13T08:24:12-04:00yurivictParaView fails to find ExprTk due to changed type in the version variableSince exprtk-0.0.2 the type of the 'version' variable changed. FindExprTk.cmake parses the header and fails to find ExprTk version >=2.7
Patch that resolves this problem:
```
--- VTK/CMake/FindExprTk.cmake.orig 2023-03-11 22:27:31 U...Since exprtk-0.0.2 the type of the 'version' variable changed. FindExprTk.cmake parses the header and fails to find ExprTk version >=2.7
Patch that resolves this problem:
```
--- VTK/CMake/FindExprTk.cmake.orig 2023-03-11 22:27:31 UTC
+++ VTK/CMake/FindExprTk.cmake
@@ -21,8 +21,8 @@ mark_as_advanced(ExprTk_INCLUDE_DIR)
if (ExprTk_INCLUDE_DIR)
file(STRINGS "${ExprTk_INCLUDE_DIR}/exprtk.hpp" _exprtk_version_header
- REGEX "static const char\\* version")
- string(REGEX MATCH "static const char\\* version = \"([0-9.]+)\"" _exprtk_version_match "${_exprtk_version_header}")
+ REGEX "static char_cptr *version")
+ string(REGEX MATCH "static char_cptr *version = \"([0-9.]+)\"" _exprtk_version_match "${_exprtk_version_header}")
set(ExprTk_VERSION "${CMAKE_MATCH_1}")
unset(_exprtk_version_header)
unset(_exprtk_version_match)
```
But it would be better if you would compile and run a program that prints this value in cmake, instead of parsing the header file.https://gitlab.kitware.com/paraview/paraview/-/issues/21799Release ParaView 5.11.1-RC12023-03-29T17:05:39-04:00Ryan Krattigerryan.krattiger@kitware.comRelease ParaView 5.11.1-RC1<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.11.1` - replace with base version, e.g., 5.7.0
- `-RC1` - for release candidates, replace with "-RC?". F...<!--
This template is for tracking a release of ParaView. Please replace the
following strings with the associated values:
- `5.11.1` - replace with base version, e.g., 5.7.0
- `-RC1` - for release candidates, replace with "-RC?". For final, replace with "".
- `5` - replace with major version number
- `11` - replace with minor version number
- `1` - replace with patch version number
- `release`: The branch to create the release on (for `x.y.0-RC1`,
`master`, otherwise `release`)
- `e39c9fe7beebc506fc3640b9ec579ba61dba65db`: The ParaView commit where the release should be started
Please remove this comment.
-->
# Preparatory steps
- Update ParaView guides
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.11.1.pdf
- [x] Upload to www.paraview.org/files/v5.11
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.11.1.pdf
- [x] Upload to www.paraview.org/files/v5.11
- 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 `1-RC1` 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`-only changes on a single topic
(suggested branch name: `update-to-v5.11.1`):
- Assemble release notes into `Documentation/release/ParaView-5.11.1.md`.
- [x] Update `version.txt` and tag the commit (tag this commit below)
```
git checkout -b update-to-v5.11.1-RC1 e39c9fe7beebc506fc3640b9ec579ba61dba65db
echo 5.11.1-RC1 > version.txt
git commit -m 'Update version number to 5.11.1-RC1' version.txt
```
- [ ] Update VTK's `paraview/release` branch. The
[`release-mr`][release-mr] script should be used to do this. Pass
`-c .kitware-release-paraview.json` to use the appropriate
configuration file.
- [ ] Merge the VTK `paraview/release` update MR
- [ ] Update kwrobot with the new `paraview/release` branch rules (@ben.boeckel)
- [ ] `.gitmodules` to track the `paraview/release` branch of VTK
- [ ] 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] `release-mr.py -t TOKEN_STRING -c .kitware-release.json -m e39c9fe7beebc506fc3640b9ec579ba61dba65db`
- [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] Get positive review
- [x] `Do: merge`
- [x] Create tag: `git tag -a -m '5.11.1-RC1' v5.11.1-RC1 commit-that-updated-version.txt`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.11.1-RC1`)
- Upload tarballs to `paraview.org`
- [x] Setup your `~/.ssh/config` and add the web host (@vbolea).
- [x] `rsync -rptv $tarballs web:ParaView_Release/v5.11/`
- 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.11.1-RC1 release`
- Integrate changes.
- Update versions
- [x] Guide selections in `versions.cmake` and ensure that the paraview
http URL source is the _DEFAULT_ source.
- [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.11.1-RC1
- [x] ARG SUPERBUILD_TAG=v5.11.1-RC1
- [x] ARG PARAVIEW_VERSION_STRING=paraview-5.11
- [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.11.1-RC1"`
- 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`)
- Create a commit which will be tagged:
- [x] `git commit --allow-empty -m "paraview: add release 5.11.1"`
- [x] Create tag: `git tag -a -m 'ParaView superbuild 5.11.1-RC1' v5.11.1-RC1 HEAD`
- Force `5.11.1-RC1` in CMakeLists.txt
- [x] Append to the top of CMakeLists.txt (After project...) The following
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.11.1-RC1" CACHE STRING "Force version to 5.11.1-RC1" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- [x] Create fixup commit with the above changes `git commit -a --fixup=@`. The fixup commit will prevent merging of the temporary code above; it will be removed in a future step.
- [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 e39c9fe7beebc506fc3640b9ec579ba61dba65db`
- [x] 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.
- [x] Remove fixup commit: `git reset --hard @^`
- [x] Get positive review
- [x] Force push `git push -f gitlab`
- [x] `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
- [ ] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.11.1-RC1.app/`
- [ ] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.11.1-RC1.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
- Python. Open the Python shell and run
- Plugins are present and load properly
- OSPRay raycasting and pathtracing runs ("Enable Ray Tracing" property in View panel)
- OptiX pathtracing runs (not macOS)
- 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] Linux EGL
- [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.11/`)
- [ ] Ask @jonthan.volks (Kitware comm team) 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.11
```
- [ ] Test download links on https://www.paraview.org/download
# Push tags
- [x] In the `paraview` repository, run `git push origin v5.11.1-RC1`.
- [x] In the `paraview-superbuild` repository, run `git push origin v5.11.1-RC1`.
# Spack
- [ ] 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
- [ ] Submit a Merge Request for release that updates the version to 5.11.1 in https://gitlab.kitware.com/paraview/paraview-docs/-/blob/master/doc/source/conf.py` for `paraview-docs`
- [ ] Upload versioned documentation to `https://github.com/kitware/paraview-docs` (see `https://github.com/Kitware/paraview-docs/blob/master/README.md`)
- [ ] Tag the HEAD of release in [ParaView docs](https://gitlab.kitware.com/paraview/paraview-docs/-/tags) with v5.11.1.
- [ ] Activate the tag on [readthedocs](https://readthedocs.org/projects/paraview/versions/) and build it [here](https://readthedocs.org/projects/paraview/)
- [ ] Go to readthedocs.org and activate
- [ ] Write and publish blog post with release notes.
- [ ] 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:
- [ ] Request from comm@kitware.com an update of version number in "Download Latest Release" text on www.paraview.org
- [ ] 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.11.1 (Winter 2023)Ryan Krattigerryan.krattiger@kitware.comRyan Krattigerryan.krattiger@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21770Create a repository of spack build examples2023-06-12T16:09:41-04:00W. Alan ScottCreate a repository of spack build examplesPlease create a repository of spack build examples. We are basically looking for a toolbox of examples.Please create a repository of spack build examples. We are basically looking for a toolbox of examples.https://gitlab.kitware.com/paraview/paraview/-/issues/21765BUG: pqLoadDataReaction doesn't emit loadedData() when using default readers2023-02-09T13:39:25-05:00Jonah SedamBUG: pqLoadDataReaction doesn't emit loadedData() when using default readersThe pqLoadDataReaction class does not emit the loadedData() signal when used with a reader set as default in ".settings.RepresentedArrayListSettings.ReaderDetails" of UserSettings.json. This interferes with extensions wishing to customiz...The pqLoadDataReaction class does not emit the loadedData() signal when used with a reader set as default in ".settings.RepresentedArrayListSettings.ReaderDetails" of UserSettings.json. This interferes with extensions wishing to customize behavior of readers after the file has been read.
related merge request: !6171https://gitlab.kitware.com/paraview/paraview/-/issues/21760Allow Conduit information to be made available in ParaView Catalyst Python sc...2023-11-08T21:14:55-05:00Andrew BauerAllow Conduit information to be made available in ParaView Catalyst Python scriptsParaView Catalyst Python scripts should have a mechanism in order to allow the Python script to access the Conduit information passed through the Catalyst V2 API. This would allow the Python script to access information passed through Co...ParaView Catalyst Python scripts should have a mechanism in order to allow the Python script to access the Conduit information passed through the Catalyst V2 API. This would allow the Python script to access information passed through Conduit for doing programmatic things inside of the Python script. As an example, it may be useful to determine all of the channels available in `gridwriter.py` so that the proper channel name can be passed set for the registrationName. Currently the channel name is hard-coded. Another example is being able to change the Python processing pipeline based on information passed through the Catalyst V2 API.https://gitlab.kitware.com/paraview/paraview/-/issues/21759ParaView Catalyst v2 API doesn't have a Python API2023-08-10T08:35:06-04:00Andrew BauerParaView Catalyst v2 API doesn't have a Python APIParaView Catalyst's V2 API hasn't implemented a Python API. Ideally this should be done without changing the Catalyst V2 API for backwards ABI compatibility.
When this is done there should also be a Python Catalyst V2 example.ParaView Catalyst's V2 API hasn't implemented a Python API. Ideally this should be done without changing the Catalyst V2 API for backwards ABI compatibility.
When this is done there should also be a Python Catalyst V2 example.https://gitlab.kitware.com/paraview/paraview/-/issues/21732Implement Color Legend Interactivity property2023-01-12T09:58:57-05:00gabokamazeImplement Color Legend Interactivity propertyColor Legend in Render View can be dragged & dropped with left-click mouse, allowing automatic switching from any `WindowLocation` property value toward `‘AnyLocation’`.
A similar GUI behavior is available for the Orientation Axes. But c...Color Legend in Render View can be dragged & dropped with left-click mouse, allowing automatic switching from any `WindowLocation` property value toward `‘AnyLocation’`.
A similar GUI behavior is available for the Orientation Axes. But contrary to the latter, no kind of `Color Legend Interactivity` property is implemented. In consequence, the Color Legend can be innintentionate dragged, that can be annoying.
Such feature (`Color Legend Interactivity`) would be appreciated.
See following original forum post : https://discourse.paraview.org/t/prevent-legend-dragging-automatic-switch-to-windowlocation-anylocation/11119https://gitlab.kitware.com/paraview/paraview/-/issues/21724New ParaView web pages missing publications list2024-02-06T18:45:53-05:00Kenneth MorelandNew ParaView web pages missing publications listThe old ParaView web site had a convenient page that listed the most relevant ParaView publications as well as providing some suggestions on which publications to use when citing the software. This is very helpful to the research communi...The old ParaView web site had a convenient page that listed the most relevant ParaView publications as well as providing some suggestions on which publications to use when citing the software. This is very helpful to the research community as well as for research-oriented funding sources like DOE that want to show ParaView impact.
However, this page is missing from the recent ParaView web page redesign. Can we bring this back? Or at the very least provide in an obvious place a way to reference the ParaView software in a scientific journal.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21710HyperTreeGrid HTG Writer produces broken htg in appended mode after calculator2023-03-24T04:30:51-04:00maximilian-techHyperTreeGrid HTG Writer produces broken htg in appended mode after calculatorThe HyperTreeGrid writer produces broken files with more than one array.
The files are fixable but the HyperTreeGrid reader has another issue when reading files of HTG version 2.0 files (see this issue paraview/paraview#21711).
The ori...The HyperTreeGrid writer produces broken files with more than one array.
The files are fixable but the HyperTreeGrid reader has another issue when reading files of HTG version 2.0 files (see this issue paraview/paraview#21711).
The original file as well as the modified file are appended.
* [randomHTG-pv511_unmodified.htg](/uploads/9b545319fc63d006f3f54bf6558c5b54/randomHTG-pv511_unmodified.htg)
* [randomHTG-pv511_modified.htg](/uploads/08dd2e9d7acf0eb9738b5549aa73274f/randomHTG-pv511_modified.htg)
Steps to reproduce a broken HTG (using Paraview v5.11.0)
* Create random HyperTreeGrid Source (`Source -> Alphabetical -> HyperTreeGrid (Random)`)
* Add a new vector array using the `Calculator` and formula `Depth*iHat`)
* Save the calculator with `CTRL+S` to a `*.htg` file in appended mode without compression
* Try open this file (it will fail)
Inspecting the file with VIM reveals three errors
* The header of the file is partially overwritten (` RangeMax="5"02"yperTreeGrid" version="2.0" ...`)
* The array `Depth` has empty offset
* The array `Result` has the wrong offset (in fact the offset of `Depth`)
This errors are fixable by hand
* Reconstruct the file header with `<VTKFile type="HyperTreeGrid" version="2.0" byte_order="LittleEndian" header_type="UInt32">`
* Move the offset of the `Result` array to the `Depth` array
* Calculate `Result` offset by hand ( `4 Byte (HeaderSize) + 65354*8 Byte (depth array size) + 4166 Byte (depth array offset) = 527002 Byte` )
This file can be opened by Paraview without problems.https://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/21679Add option to embed PVSM state file text in PNG2022-12-20T15:24:16-05:00Cory Quammencory.quammen@kitware.comAdd option to embed PVSM state file text in PNGPNG images can store arbitrary text in key/value pairs. See the function `vtkPNGWriter::AddText(const char* key, const char* value)` for details.
Add an option in the Save Screenshot feature that will create the text for a PVSM state fi...PNG images can store arbitrary text in key/value pairs. See the function `vtkPNGWriter::AddText(const char* key, const char* value)` for details.
Add an option in the Save Screenshot feature that will create the text for a PVSM state file and save that text in the PNG.
Note that the current key/value storage mechanism in `vtkPNGWriter` uses compression `PNG_TEXT_COMPRESSION_NONE` because the text is expected to be small. For large chunks of text, like a PVSM file, it is recommended to use `PNG_TEXT_COMPRESSION_zTXt`.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21676Paraview 5.11 and Latex fonts2022-12-01T09:00:38-05:00Nabil G.Paraview 5.11 and Latex fontsdear experts
we built Paraview with external dependencies (system ones) like e.g system matplotlib, system freetype, etc.
Unfortunately with 5.11.0, if I want to label a variable with latex fonts, Paraview crashes with attached backtra...dear experts
we built Paraview with external dependencies (system ones) like e.g system matplotlib, system freetype, etc.
Unfortunately with 5.11.0, if I want to label a variable with latex fonts, Paraview crashes with attached backtrace.
![image](/uploads/b5ed7c57fb02057e2c20d9b9ee478215/image.png)
Before investigating this further, I can see that similar issues have been already reported but not further discussed.
I welcome hints or suggestions.
thanks
[pv-5.11.txt](/uploads/2aad5827f2017e951478774bfd2cacb0/pv-5.11.txt)https://gitlab.kitware.com/paraview/paraview/-/issues/21672EnSight case writer writes full data for all processes2022-11-25T18:27:35-05:00Tomáš KarabelaEnSight case writer writes full data for all processesWhen running in parallel, saving to EnSight Gold writes full geometry from each process, instead of just writing the piece that belongs to that process.
**Steps to reproduce**
- start a parallel `pvserver`, eg:
```
cd ParaView-5.11.0-...When running in parallel, saving to EnSight Gold writes full geometry from each process, instead of just writing the piece that belongs to that process.
**Steps to reproduce**
- start a parallel `pvserver`, eg:
```
cd ParaView-5.11.0-MPI-Linux-Python3.9-x86_64
./mpiexec -np 4 ./pvserver
```
- connect to the server
- create Unstructured Cell Types source
- File > Save Data... > EnSight File, save as `test.case`
This creates four identical sets of EnSight Gold geometry and variable files (with .case files currently missing, see #18242):
```
57K test.0.00000.geo
5,5K test.0.00000_n.DistanceToCenter
5,5K test.0.00000_n.Polynomial
57K test.1.00000.geo
5,5K test.1.00000_n.DistanceToCenter
5,5K test.1.00000_n.Polynomial
57K test.2.00000.geo
5,5K test.2.00000_n.DistanceToCenter
5,5K test.2.00000_n.Polynomial
57K test.3.00000.geo
5,5K test.3.00000_n.DistanceToCenter
5,5K test.3.00000_n.Polynomial
```
Each of these contains the full mesh, which can at the moment be checked by creating the .case file manually and loading it into Paraview:
```
cat <<EOF >test.0.case
FORMAT
type: ensight gold
GEOMETRY
model: test.0.00000.geo
# variable files omitted
EOF
```
When saving the same Unstructured Cell Types source but choosing to save it as Parallel VTK XML Unstructured Grid (.pvtu), the individual .vtu pieces only contain part of the original dataset:
```
567 test.pvtu
28K test/test_0.vtu
28K test/test_1.vtu
28K test/test_2.vtu
28K test/test_3.vtu
```
This can be checked by reading the indiviudal .vtu file into Paraview. It's also apparent when comparing the filesize with a .vtu file written from serial Paraview for the same dataset:
```
105K test-serial.vtu
```
![Screenshot_from_2022-11-25_23-32-58](/uploads/b778292f5fb49e0b5f7d965e50925706/Screenshot_from_2022-11-25_23-32-58.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21618Adding Export Animated Scene command to Python2022-10-24T05:12:24-04:00Xabier Morales FerezAdding Export Animated Scene command to PythonAdding a Python command for the Export Animated Scene tool, similar to ExportView(), to automatically export the scenes through macros.Adding a Python command for the Export Animated Scene tool, similar to ExportView(), to automatically export the scenes through macros.https://gitlab.kitware.com/paraview/paraview/-/issues/21599Feature request: make camera animation keyframing similar to other 3d programs2023-06-15T10:41:16-04:00Devin BaylyFeature request: make camera animation keyframing similar to other 3d programsI ended up writing a macro to help make this easier for my own work, but there are issues with saving the keyframes I've created #21598 . That said, I think the macro is still worth looking at as a base for a simple improvement to the an...I ended up writing a macro to help make this easier for my own work, but there are issues with saving the keyframes I've created #21598 . That said, I think the macro is still worth looking at as a base for a simple improvement to the animation workflow.
Here's the community forum link that I started with that includes the macro code. https://discourse.paraview.org/t/animation-keytime-integer-error/10454
Here's the macro code for anyone interested.
```
from paraview.simple import *
kf = CameraKeyFrame()
anim = GetAnimationScene()
## change below by dividing by total
kf.KeyTime = anim.AnimationTime/anim.EndTime
print(kf.KeyTime)
rv = GetActiveViewOrCreate("RenderView")
print(rv)
campos = rv.CameraPosition
camfoc = rv.CameraFocalPoint
up = rv.CameraViewUp
kf.Position = campos
kf.FocalPoint = camfoc
kf.ViewUp =up
print(campos,camfoc)
pscale = rv.CameraParallelScale
# typically the camera will have been added after the default one
# todo figure out a better way to select by name Camera
cue = anim.Cues[1]
print(cue)
cue.KeyFrames.append(kf)
print("appended frame")
```https://gitlab.kitware.com/paraview/paraview/-/issues/21579Change the way pqItemViewSearchWidget is applied.2022-09-28T12:05:17-04:00David ThompsonChange the way pqItemViewSearchWidget is applied.Currently `pqPVApplicationCore::startSearch()` has a hard-wired list of search exclusions (`pqSpreadsheetViewModel`), but some custom applications need to exclude additional model-views.
Rather than a fixed list of exclusions, we should...Currently `pqPVApplicationCore::startSearch()` has a hard-wired list of search exclusions (`pqSpreadsheetViewModel`), but some custom applications need to exclude additional model-views.
Rather than a fixed list of exclusions, we should query each `QAbstractItemView` to see if a [dynamic property](https://doc.qt.io/qt-6/qobject.html#setProperty) has been added to signal it should be excluded. Then pqSpreadsheetViewModel should set this property in its constructor and custom applications can do this as well. Only QAbstractItemViews without this property will be searched.
FYI @bob.obara @jwilson1881https://gitlab.kitware.com/paraview/paraview/-/issues/21578Wrong vtkSMProperty::CreateNewPrettyLabel behavior2022-11-01T22:09:26-04:00NicolasBWrong vtkSMProperty::CreateNewPrettyLabel behavior`vtkSMProperty::CreateNewPrettyLabel(const char*)` has two problems:
- when encountering names with multiple uppercase letters at the beginning of its argument, it will introduce a wrong space (eg: `FLUENTRenderCore` should become `FLUEN...`vtkSMProperty::CreateNewPrettyLabel(const char*)` has two problems:
- when encountering names with multiple uppercase letters at the beginning of its argument, it will introduce a wrong space (eg: `FLUENTRenderCore` should become `FLUENTRender Core` but becomes `F LUENTRender Core`).
- when encountering acronyms followed by words, words will not be split (which is normal according to the current intended behavior) (eg: `FLUENTRenderCore` should better become `FLUENT Render Core` but would become `FLUENTRender Core`).
Steps to reproduce first problem:
Run the function with a custom main:
```cpp
int main(void) {
std::cout << CreateNewPrettyLabel("MYSpace") << std::endl;
std::cout << CreateNewPrettyLabel("MYSPACE") << std::endl;
std::cout << CreateNewPrettyLabel("MySPACE") << std::endl;
std::cout << CreateNewPrettyLabel("MySPace") << std::endl;
std::cout << CreateNewPrettyLabel("MySpACE") << std::endl;
std::cout << CreateNewPrettyLabel("FLUENTRenderCore") << std::endl;
}
```
It gives
```cpp
M YSpace // should give MYSpace
M YSPACE // should give MYSPACE
My SPACE // Ok
My SPace // Ok
My Sp ACE // Ok
F LUENTRender Core // should give FLUENTRender Core
```
### MR
I have done an MR that fixes both issues to better split words: `FLUENTRenderCore` would become `FLUENT Render Core`NicolasBNicolasBhttps://gitlab.kitware.com/paraview/paraview/-/issues/21568State saved to python does not capture Data Axis Grid2023-05-24T08:05:45-04:00Kenneth MorelandState saved to python does not capture Data Axis GridWhen you save ParaView state as a python file (such as with `Save Catalyst State`), it does not save the visibility of the `Data Axis Grid` if it is turned on for an object.
To replicate, do the following:
1. Load `disk_out_ref` (or an...When you save ParaView state as a python file (such as with `Save Catalyst State`), it does not save the visibility of the `Data Axis Grid` if it is turned on for an object.
To replicate, do the following:
1. Load `disk_out_ref` (or any other data).
2. Turn on `Data Axis Grid` for that object. (Note, this is different than `Axis Grid`.)
3. Click on `Save State` and save to a .py file (not a .pvsm file).
4. Reset the ParaView session.
5. Open the python shell (`View` -> `Python Shell`).
6. Click on `Run Script` and load the state script just saved.
7. When the script is run, the data axis grid is not visible.
The state file is not capturing the `*Display.DataAxesGrid.GridAxesVisibility = 1` necessary to turn on the data axis grid for the object.https://gitlab.kitware.com/paraview/paraview/-/issues/21544Broken volume rendering on MacOS Monterey 12.1 M1 Max2023-06-07T22:12:31-04:00Linnea PalmstromBroken volume rendering on MacOS Monterey 12.1 M1 MaxTo reproduce, load fast uniform grid source and apply a threshold from -10 to 10 (the default settings) in ParaView 5.11.0 RC1. Then switch to a volume representation. It does not appear to clear the last frames as you move the camera an...To reproduce, load fast uniform grid source and apply a threshold from -10 to 10 (the default settings) in ParaView 5.11.0 RC1. Then switch to a volume representation. It does not appear to clear the last frames as you move the camera and the background color changes to black.
@patchett2002
@ethan.stam
@maxwelljackson002
![Screen_Shot_2022-09-08_at_1.17.53_PM](/uploads/a5029a0e6a545398f1972683ce707992/Screen_Shot_2022-09-08_at_1.17.53_PM.png)5.12 (Winter 2023)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21532Animated clip flickering in 5.11 RC 12023-06-15T09:38:04-04:00Nicolas VuailleAnimated clip flickering in 5.11 RC 1Steps to reproduce:
* Sphere
* Clip
* AnimationView: add track for Clip1 / Clip type - Offset
* configure track: value go from -1 to 1
* play animation
It happens to have some random flickering. See also attached video.
![animated...Steps to reproduce:
* Sphere
* Clip
* AnimationView: add track for Clip1 / Clip type - Offset
* configure track: value go from -1 to 1
* play animation
It happens to have some random flickering. See also attached video.
![animatedClipFlicker](/uploads/211fd0334165159aa6d4b7436ee3fc12/animatedClipFlicker.mp4)
Tested on linux with official binaries of 5.11 RC 1. GPU: NVIDIA GeForce RTX 3070 Mobile
Also seen on Windows (off. binaries of RC1 too)
Not able to reproduce on master, nor in my own build of 5.11 RC1