ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-08-23T07:59:21-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21158Add Spack installation test to CI2023-08-23T07:59:21-04:00Nils VuAdd Spack installation test to CII often encounter issues when installing ParaView and its dependencies with [Spack](https://github.com/spack/spack). Would it be possible to add a few automated tests that regularly ensure ParaView builds correctly for a few selected con...I often encounter issues when installing ParaView and its dependencies with [Spack](https://github.com/spack/spack). Would it be possible to add a few automated tests that regularly ensure ParaView builds correctly for a few selected configurations? My suggestion is to test the matrix [gcc, clang, apple-clang] x [ubuntu, macOS] for the following configuration:
```
spack install paraview +python3 +qt +hdf5
```https://gitlab.kitware.com/paraview/paraview/-/issues/21153allow save screenshot for non integer scales2024-03-07T20:23:48-05:00W. Alan Scottallow save screenshot for non integer scalesThis feature request is an extention of #21109. #21109 has the details to test saving screenshots. As mentioned at the bottom of #21109, we wish to allow users to scale screenshots to scale to non integer values. For instance, we want...This feature request is an extention of #21109. #21109 has the details to test saving screenshots. As mentioned at the bottom of #21109, we wish to allow users to scale screenshots to scale to non integer values. For instance, we want to save screenshots with a scale of 0.75 or 1.5. Then, text used for the color legend and simultaniously sources/ text should scale to this value, and also scale the same.
Again, see #21109 for details how to replicate this issue.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21151Memory display color2024-03-07T20:23:48-05:00W. Alan ScottMemory display colorI think I would recommend changing the memory display bar background color and thresholds. This is the new memory display below the renderview.
With regards to the background, it is currently quite bright and distracting. Please cha...I think I would recommend changing the memory display bar background color and thresholds. This is the new memory display below the renderview.
With regards to the background, it is currently quite bright and distracting. Please change the background color to match the background of the progress bar - i.e., a gray rather than a white. The green is OK, leave as is.
After a bit of experimenting, what I believed was happening is happening with memory. ParaView is grabbing memory for calculations and output arrays, doing calculations, then releasing calculation memory. Thus, what the memory inspector is showing is correct after processing, but a huge undercount when any processing and/or rendering is occurring.
The way I tested was on RedHat Linux. Run ParaView. Sources/ Fast Uniform Grid. Only create the Distance Squared scalars. In a terminal, start running "free -h". Either have it run every second, or keep up-arrowing. What we care about is the last entry, "available". You may want to open the memory inspector, but this isn't necessary as we can see the memory footprint on the new memory display bar. Start increasing the size of the fast uniform grid. With 64 GBytes of memory, mine was OK at about -1000 to 1000, -1000 to 1000, -400 to 400. Memory showed about 65% full. Changing the Z to -400 to 450 crashed, but as I was only increasing about 8%, it shouldn't have. Note that free gave me a low of about 9 GBytes of free memory, but a final of about 20GBytes.
Please change the thresholds for the memory display bar to go yellow at 50% memory used, and red at 60% memory used.
@mwestphal5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21149PDB Import issues2021-12-29T05:58:28-05:00Sam BroderickPDB Import issuesDear ParaView Team
A double-stranded DNA base pair is mangled when imported as a pdb.
As of 5.9.1 (5.8 did not manage calculating bonds), I can import an .xyz and calculate the bonds more or less correctly (double bonds still missing)....Dear ParaView Team
A double-stranded DNA base pair is mangled when imported as a pdb.
As of 5.9.1 (5.8 did not manage calculating bonds), I can import an .xyz and calculate the bonds more or less correctly (double bonds still missing).
The .xyz looks like this after the filter ComputeMoleculeBonds:
![xyz-import-compute-bonds](/uploads/a2cab11097a0ae738c608c5b731aa1dd/xyz-import-compute-bonds.png)
A .pdb import (with the correct format and bond assignment) looks like this (native import):
![pdb-import](/uploads/3829972512146607d7966e26368c11b4/pdb-import.png)
The hydrogen atoms are ignored, the bonds are wrong, and the atoms do not have the proper location. Using the VisIt import returns a mesh. The VisIt Silo import caused a crash.
Avogadro shows the molecule properly.
Many thanks
Samhttps://gitlab.kitware.com/paraview/paraview/-/issues/21141Color legend label format and range label format are not similar2024-03-07T20:23:48-05:00W. Alan ScottColor legend label format and range label format are not similarThe color legend label formats and range label formats are not the same, but should be. The range has an extra number in the exponent. They need to be the same. Here is how to replicate:
* 5.10.0-RC2, MacOS
* Wavelet. Apply. Surfac...The color legend label formats and range label formats are not the same, but should be. The range has an extra number in the exponent. They need to be the same. Here is how to replicate:
* 5.10.0-RC2, MacOS
* Wavelet. Apply. Surface. Color by RTData.
* Color map editor. Color legend editor.
* Advanced.
* Turn off automatic label format.
* Change Label Format to: %-#6.3e
* Change Range Label Format to: %-#6.3e
The exponents have a different number of digits. This is a bug.
![Screen_Shot_2021-12-21_at_10.57.03_AM](/uploads/abdb57fded5873eceffc2474ad16e878/Screen_Shot_2021-12-21_at_10.57.03_AM.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21140Add option in color legend to have same labels and ranges2024-03-07T20:23:48-05:00W. Alan ScottAdd option in color legend to have same labels and rangesPlease add the option to have the color legend ranges and labels use the same format. This format should probably be %-#6.3e. I know this can be manually set, but it would be nice to allow users to just click a checkbox. Make it on th...Please add the option to have the color legend ranges and labels use the same format. This format should probably be %-#6.3e. I know this can be manually set, but it would be nice to allow users to just click a checkbox. Make it on the standard dialog (not only advanced), just under Horizontal Title. Maybe call it "Consistent labels and ranges".
So, what I want is an automagic way to do the following:
* Wavelet. Apply. Surface. Color by RTData.
* Edit Color Map. Edit Color Legend.
* Advanced.
* Turn off automatic label format.
* Label Format: %-#6.3e
* Range Label Format: %-#6.3e
* OK.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21137ParFlow plugin does not build with nlohmann-json 3.10.4.2022-12-12T03:13:09-05:00Mathieu Westphal (Kitware)ParFlow plugin does not build with nlohmann-json 3.10.4.Building ParaView with ParFlow plugin fails with
```
In file included from /home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkParFlowMetaReader.cxx:3:
/home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkVectorJSON.h: In function ...Building ParaView with ParFlow plugin fails with
```
In file included from /home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkParFlowMetaReader.cxx:3:
/home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkVectorJSON.h: In function ‘void from_json(const json&, vtkTuple<A, Size>&)’:
/home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkVectorJSON.h:22:47: error: no matching function for call to ‘nlohmann::detail::type_error::create(int, std::__cxx11::basic_string<char>)’
22 | throw nlohmann::detail::type_error::create(
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
23 | 302, "type must be array, but is " + std::string(j.type_name()));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/nlohmann/detail/conversions/from_json.hpp:15,
from /usr/include/nlohmann/adl_serializer.hpp:6,
from /usr/include/nlohmann/json.hpp:51,
from /home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkParFlowMetaReader.h:11,
from /home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkParFlowMetaReader.cxx:2:
/usr/include/nlohmann/detail/exceptions.hpp:331:23: note: candidate: ‘template<class BasicJsonType> static nlohmann::detail::type_error nlohmann::detail::type_error::create(int, const string&, const BasicJsonType&)’
331 | static type_error create(int id_, const std::string& what_arg, const BasicJsonType& context)
| ^~~~~~
/usr/include/nlohmann/detail/exceptions.hpp:331:23: note: template argument deduction/substitution failed:
In file included from /home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkParFlowMetaReader.cxx:3:
/home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkVectorJSON.h:22:47: note: candidate expects 3 arguments, 2 provided
22 | throw nlohmann::detail::type_error::create(
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
23 | 302, "type must be array, but is " + std::string(j.type_name()));
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkVectorJSON.h:27:47: error: no matching function for call to ‘nlohmann::detail::type_error::create(int, const char [25])’
27 | throw nlohmann::detail::type_error::create(302, "array sizes do not match");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/nlohmann/detail/conversions/from_json.hpp:15,
from /usr/include/nlohmann/adl_serializer.hpp:6,
from /usr/include/nlohmann/json.hpp:51,
from /home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkParFlowMetaReader.h:11,
from /home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkParFlowMetaReader.cxx:2:
/usr/include/nlohmann/detail/exceptions.hpp:331:23: note: candidate: ‘template<class BasicJsonType> static nlohmann::detail::type_error nlohmann::detail::type_error::create(int, const string&, const BasicJsonType&)’
331 | static type_error create(int id_, const std::string& what_arg, const BasicJsonType& context)
| ^~~~~~
/usr/include/nlohmann/detail/exceptions.hpp:331:23: note: template argument deduction/substitution failed:
In file included from /home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkParFlowMetaReader.cxx:3:
/home/glow/work/paraview/pv1/src/Plugins/ParFlow/IO/vtkVectorJSON.h:27:47: note: candidate expects 3 arguments, 2 provided
27 | throw nlohmann::detail::type_error::create(302, "array sizes do not match");
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ninja: build stopped: subcommand failed.
```
@dcthomphttps://gitlab.kitware.com/paraview/paraview/-/issues/21136Return cell type information from EnSight reader2024-03-19T18:26:13-04:00Dave CorsonReturn cell type information from EnSight readerFor some use cases, it is desirable to have the reader return information about cell types present in the file. For example, when reading EnSight, it could contain unstructured mesh, polyhedral mesh, structured mesh, etc. If this data ...For some use cases, it is desirable to have the reader return information about cell types present in the file. For example, when reading EnSight, it could contain unstructured mesh, polyhedral mesh, structured mesh, etc. If this data is provided by the reader, we could force the use of optimized algorithms in subsequent pipelines without having to scan through the model again.https://gitlab.kitware.com/paraview/paraview/-/issues/21133Custom shortcuts are not loaded2024-03-15T11:20:48-04:00Nicolas VuailleCustom shortcuts are not loadedOn ParaView master, custom shortcut set up via `Tools / Customize Shortcuts` are correctly saved in `ParaView.conf` but they are not loaded on ParaView startup.
Steps:
- `Tools / Customize Shortcuts`
- `Load State`, press `Ctrl+Shift+...On ParaView master, custom shortcut set up via `Tools / Customize Shortcuts` are correctly saved in `ParaView.conf` but they are not loaded on ParaView startup.
Steps:
- `Tools / Customize Shortcuts`
- `Load State`, press `Ctrl+Shift+O` OK
- `File` menu correctly displays `Ctrl+Shift+O` and using the shortcut works as expected
- Close ParaView. `ParaView.conf` is correctly written.
- Launch ParaView.
-> Shortcut is not set anymore.
ParaView.conf content:
```
[pqCustomShortcuts]
File\Load_State...=Ctrl+Shift+O
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21132MacOS Night Mode Colours in File Selection bugged2021-12-13T06:21:41-05:00Denisi MuratajMacOS Night Mode Colours in File Selection buggedHi there is something wrong with the colour scheme on night mode with I presume the left text colour being pre-set. It would make sense to make this dynamic like the rest of this UI so it changes with night mode. Nice work on the Apple S...Hi there is something wrong with the colour scheme on night mode with I presume the left text colour being pre-set. It would make sense to make this dynamic like the rest of this UI so it changes with night mode. Nice work on the Apple Silicon Paraview, runs extremely quick!
Thanks,
Denis
![Screenshot_2021-12-07_at_20.46.54](/uploads/2681d41fcd5582a03315de1bc12c5c23/Screenshot_2021-12-07_at_20.46.54.png)https://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/21128Fields in "Properties" panel are unnecessarily wide, making the UI difficult ...2022-07-20T19:34:53-04:00Amin SadeghiFields in "Properties" panel are unnecessarily wide, making the UI difficult to work withOS: Ubuntu 20.04.3 LTS
ParaView Version: 5.10.0-RC1
Qt Version: 5.12.9
---
The data fields in the "Properties" panel are unnecessarily wide, thus making the panel "scrollable", which makes it difficult to work with the UI (either I nee...OS: Ubuntu 20.04.3 LTS
ParaView Version: 5.10.0-RC1
Qt Version: 5.12.9
---
The data fields in the "Properties" panel are unnecessarily wide, thus making the panel "scrollable", which makes it difficult to work with the UI (either I need to scroll every now and then), or resize the "Properties" panel to the point that makes the scroll bars go away, in which case it takes an unnecessarily huge portion of the screen.
Btw, I have a 4k monitor, in case it's relevant to the issue I'm reporting.
Thank you so much!
# ParaView's default "Properties" width
![image](/uploads/fd8c2103d32a361f63eb281e10f39a93/image.png)
# Expanding "Properties" panel to get rid of scroll bars
![image](/uploads/cda9ae4dfbf12a10e311ec643a8303b0/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21121All numpy methods put in local namespace of Macro2021-12-07T08:10:18-05:00Bob WeigelAll numpy methods put in local namespace of MacroIn the following code, `pvs.Show()` leads to the equivalent of `from numpy import *` being executed on the same line.
As a result, my variable `source` is redefined to be the function `numpy.source`.
```
import paraview.simple as pvs
...In the following code, `pvs.Show()` leads to the equivalent of `from numpy import *` being executed on the same line.
As a result, my variable `source` is redefined to be the function `numpy.source`.
```
import paraview.simple as pvs
source = pvs.ProgrammableSource()
source.Script = "import numpy as np"
print(len(locals())) # 9
print(source) # <paraview.servermanager.ProgrammableSource object at 0x128d238b0>
pvs.Show(source)
print(source) # <function source at 0x12848e550>
print(len(locals())) # 638
```https://gitlab.kitware.com/paraview/paraview/-/issues/21120Add Discontinuous Galerkin Finite Element Mesh Support to VTK/ParaView2024-03-07T20:23:47-05:00Corey Wetterer-Nelson (Kitware)Add Discontinuous Galerkin Finite Element Mesh Support to VTK/ParaViewAs part of an ongoing collaboration between Sandia National Lab and Kitware, it is desired to upgrade VTK and ParaView to fully support Discontinuous Galerkin parametrizations read in by the Ioss reader.
## Project Requirements
### Pha...As part of an ongoing collaboration between Sandia National Lab and Kitware, it is desired to upgrade VTK and ParaView to fully support Discontinuous Galerkin parametrizations read in by the Ioss reader.
## Project Requirements
### Phase I
- [x] Upgrade Ioss reader to support prototype DG Exodus mesh
- [x] The info records syntax has changed. Adapt parsing methods to follow the latest pattern.
- [ ] Support for H^Grad elements
- [x] Linear bases (hex, quad, tri elements)
- [x] Quadratic bases (hex, quad, tri elements)
- [ ] Higher order bases (hex, quad, tri elements)
- [ ] Support for H^Div elements (interpolation onto Lagrange elements of proper order)
- [x] Linear bases (hex, quad, tri elements)
- [x] Quadratic bases (hex, quad, tri elements)
- [ ] Higher order bases (hex, quad, tri elements)
- [ ] Support for H^Curl elements (interpolation onto Lagrange elements of proper order)
- [x] Linear bases (hex, quad, tri elements)
- [x] Quadratic bases (hex, quad, tri elements)
- [ ] Higher order bases (hex, quad, tri elements)
### Phase II
- [ ] Upgrade rendering support for exotic element types (above simple interpolation to Lagrange elements)
- [ ] Upgrade rendering hidden face removal for disconnected DG elements
- [ ] Upgrade VTK data model to support mismatched field order and mesh order
## Background
### VTK's Datamodel Challenge
In a classical Galerkin finite element mesh, control variables defining solution fields on the mesh are often associated with physical features of the mesh. For instance, in a linear element, control variables will be associated with the vertices of the element. Thus, when multiple elements share a physical feature, they also share control variables associated with those physical features. This ensures continuity of solution fields across elements. It is this collection of assumptions that forms the foundation of VTK's data model. No matter what elements make up a mesh, each element is made up of vertices, and the connectivity of vertices for the mesh is identical to any connectivity of control variables defining solution fields on the mesh.
This model works well for many finite element applications. However, it falls apart in a number of areas. First, for a simple geometry, it is often advantageous to use a linear mesh to define the domain, but it may be advantageous or necessary to use higher order basis functions to define solution fields, leading to a mismatch in the connectivity of the mesh and solution fields. Second, some problems require different basis functions to be used for different fields. A popular example is the stable velocity-pressure pair where pressure is described by a field one polynomial degree lower than the velocity. Here, two fields will require separate connectivity arrays to organize control variables across elements which may both be different from that describing the physical mesh. Third, some basis functions have little to no relationship with geometry at all. Modal, or spectral elements have control variables that have no physical distribution at all, only describing weights on basis functions over an element. This problem is complicated further by basis functions which take the form of vector fields over an element which could be represented by different polynomial bases in each cardinal direction. The basis function rabbit hole is remarkably deep!
In VTK's current form, the only way to visualize fields constructed by exotic basis functions is to covert to something which satisfies all of The VTK requirements above. For instance, one can always interpolate onto Lagrange polynomial elements of an appropriate order and mosey along with visualization. This can be time consuming for a user to do this themselves, and may be exceedingly wasteful with memory and computational power depending on the size of the user's problem and their particular requirements.
In order to begin addressing this, the first step will be to disconnect the mesh connectivity array from fields in VTK. This could be done by allowing for an arbitrary collection of connectivity arrays, and then assigning one of them to the geometry and the rest to fields. The second key will be to expand how shaders utilize these connectivities and draw arbitrary order fields on mismatched order meshes. For more exotic fields such as those defined by vector-valued basis functions, new shaders must be introduced to properly render.
### Discontinuous Galerkin Meshes
Moving one step away from classical Galerkin methods, it can be desirable to break that cross-element continuity, which is where Discontinuous Galerkin comes in. Here, each element has its own collection of control variables, sharing none with neighboring elements. This immediately runs into the challenge in VTK where control variables do not align with physical components of the mesh (which in this case are typically shared across elements).
(Sandia: if you would like to expand this section for other readers, that would be great!)
### Current Exodus Implementation
Currently, in order to encode discontinuous Galerkin (DG) fields on a mesh, the Exodus file format employs a novel hack. In the Exodus file, a DG field is written as a multi-component cell-centered field where each component represents an element control variable. For instance, a field described by linear H^Grad DG elements over a quad mesh will encode each scalar field by a 4-component cell-centered vector field. A field described by a quadratic H^Grad DG element over a hex mesh will encode each scalar field by a 27-component cell-centered vector field. For vector fields, each component of the vector field is described as a scalar field for the purpose of writing. Metadata for each DG field is then encoded in the info-records section of the Exodus file.
### Current Ioss Reader Implementation
At the time of this writing, the Ioss reader has been upgraded to handle the initial prototype Exodus DG file format. This is done via a few modifications. First, the info-records section of the Exodus file is parsed into a data structure which stores information about what fields on which blocks are DG fields. Second, on DG blocks of elements, the mesh is expanded so that no element shares vertices with any other element. This is done so that the eventual DG fields share the same connectivity with the mesh elements. Second, if the DG fields are quadratic, the mesh is upgraded to a quadratic mesh from the linear mesh stored in the Exodus file. This is done so that on each element, the number of vertices match the number of control variables associated with that element. We do this by interpolating extra vertices on edges, faces and the volume center of each element. Next, the routine `GetFields` was modified to filter out DG fields, and a new `GetDGFields` routine was added to properly parse the DG fields.5.13 (Summer 2024)David ThompsonDavid Thompsonhttps://gitlab.kitware.com/paraview/paraview/-/issues/21119HDF5 reader is losing it's brains remote server2024-03-07T20:23:47-05:00W. Alan ScottHDF5 reader is losing it's brains remote serverThe HDF5 reader is losing it's brains when loading a single file containing particles when using multiple ranks remote server. Here is how to replicate:
* 5.9.1/ 5.10.0-RC1, Linux, remote server (I have 16 ranks, it will show on 2).
* L...The HDF5 reader is losing it's brains when loading a single file containing particles when using multiple ranks remote server. Here is how to replicate:
* 5.9.1/ 5.10.0-RC1, Linux, remote server (I have 16 ranks, it will show on 2).
* Load file fields.exo. Apply. Wireframe. The only reason we are loading this one is that the issue seems to follow cells in this file. You do not need this file loaded to see the issue.
* Load particles.h5part. Appply.
* Change the time to be 200.
* Paint by ProcessId, and also by Solid Color, White. Notice that the single file of points was spread around the 16 ranks. Notice where the points are. (You may want to take a screenshot, so you don't have to keep bouncing back and forth.)
* Move forward one timestep.
Most of the points have disappeared! Notice that what is left is all in ProcessId 0. Further, I believe they are the points that were in process zero earlier.
* Move forward one timestep.
More of the points have disappeared! This will quickly go on until no points are visible.
* On the particles.h5part reader in the Pipeline Browser, Reload Files.
Now, all of the points for this timestep are visible once again!
To see what should be happening, open particles.h5part with a builtin server, go to timetep 200, and start moving forward in time.
I will pass the dataset to Cory and Utkarsh.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21117AddFieldArrays property panel is empty2021-12-01T08:16:32-05:00Mathieu Westphal (Kitware)AddFieldArrays property panel is emptyAddFieldArrays property panel is empty in master and ParaView 5.10.
![Screenshot_2021-12-01_130818](/uploads/be74060334b6afddf2b5a390af6b6a59/Screenshot_2021-12-01_130818.png)
In 5.9.1, it looks like this:
![Screenshot_2021-12-01_1315...AddFieldArrays property panel is empty in master and ParaView 5.10.
![Screenshot_2021-12-01_130818](/uploads/be74060334b6afddf2b5a390af6b6a59/Screenshot_2021-12-01_130818.png)
In 5.9.1, it looks like this:
![Screenshot_2021-12-01_131558](/uploads/3e3afd3e634c30dd63e6331cc2fef305/Screenshot_2021-12-01_131558.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21113update getting started guide for IOSS reader2024-03-07T20:23:46-05:00W. Alan Scottupdate getting started guide for IOSS readerPlease update the getting started guide. Paragraph 3 is now out of date (i.e., where you select variables). Maybe an idea would be to just delete this section (as variables now default to on), and add a section on Rescale to Data Range?Please update the getting started guide. Paragraph 3 is now out of date (i.e., where you select variables). Maybe an idea would be to just delete this section (as variables now default to on), and add a section on Rescale to Data Range?5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21112Enhancing pvbatch testing macro2021-11-30T15:24:35-05:00Yohann Bearzi (Kitware)Enhancing pvbatch testing macroAs proposed [here](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5339#note_1088479), the way CMake handles pvbatch should be enhanced to simplify the CMake code introduced in !5339.As proposed [here](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5339#note_1088479), the way CMake handles pvbatch should be enhanced to simplify the CMake code introduced in !5339.https://gitlab.kitware.com/paraview/paraview/-/issues/21110ResampleToImage pass partial arrays2021-12-02T07:39:24-05:00Theodore BaltisResampleToImage pass partial arraysFeature request.
Similar to how ResampleWithDataset was updated in 5.10 to pass partial arrays, add the same functionality to ResampleToImage.Feature request.
Similar to how ResampleWithDataset was updated in 5.10 to pass partial arrays, add the same functionality to ResampleToImage.https://gitlab.kitware.com/paraview/paraview/-/issues/21108HyperTreeGridToDualGrid stops working when advancing time step2022-12-13T09:44:05-05:00maximilian-techHyperTreeGridToDualGrid stops working when advancing time stepHyperTreeGridToDualGrid stops working when advancing time step. There is simply no data.
It can be reproduced by creating a HTG, duplicate it and open both as a collection then apply the HyperTreeGridToDualGrid Filter and advance the ti...HyperTreeGridToDualGrid stops working when advancing time step. There is simply no data.
It can be reproduced by creating a HTG, duplicate it and open both as a collection then apply the HyperTreeGridToDualGrid Filter and advance the time step. Then no information is shown.
I tested it with Paraview v5.9.1 (HyperTree VTK-Filetype v1.0) and Paraview v5.10-RC1 (HyperTree VTK-Filetype v2.0) .