ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-10-21T03:45:01-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21608ray traced volumes show widgets in CS/Parallel2022-10-21T03:45:01-04:00David E. DeMarleray traced volumes show widgets in CS/ParallelI am trying parallel ray traced volume rendering in ParaView 5.11.rc1 and widgets are drawn when they should not be.
To reproduce, build 5.11.rc1 tag, enable MPI and RayTracing/OSPRay. Start up two process pvserver and connect to it, use...I am trying parallel ray traced volume rendering in ParaView 5.11.rc1 and widgets are drawn when they should not be.
To reproduce, build 5.11.rc1 tag, enable MPI and RayTracing/OSPRay. Start up two process pvserver and connect to it, use remote rendering. Turn on Ray Tracing.
Looks like some new orientation widgets are being drawn now.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21601Keyframes from the animation view are not saved in python state files2023-07-19T09:31:27-04:00Devin BaylyKeyframes from the animation view are not saved in python state filesKeyframes from the animation view are not saved in python state files
Steps to reproduce:
- run ParaView
- Source, Cone, Apply
- Create a simple animation with keyframes in the animation view
- File -> SaveState -> .py
- .py file does n...Keyframes from the animation view are not saved in python state files
Steps to reproduce:
- run ParaView
- Source, Cone, Apply
- Create a simple animation with keyframes in the animation view
- File -> SaveState -> .py
- .py file does not contains any code related to keyframes and loading the state back, keyframes are not present
Note: keyframes are saved in the python trace file, so this is not due to a missing python API.
Original issue:
When I create keyframes for a camera animation cue either manually through the widget or with the macro mentioned in #21600 and #21599 I don't see any python lines generated in the file that related to the animation data. Here's the result https://github.com/DevinBayly/paraview_code/blob/main/debugging.py of the same operations that produced this file https://github.com/DevinBayly/paraview_code/blob/f12a062d0f8cca601e1815e157283ba9d9638d17/debugging.pvsm
Seems like this is a bug? This issue was created at the suggestion of @mwestphal on the community forum https://discourse.paraview.org/t/camera-animation-state-isnt-saving/10486/3https://gitlab.kitware.com/paraview/paraview/-/issues/21598Camera animation state isn't saving2022-10-13T15:07:06-04:00Devin BaylyCamera animation state isn't savingI'm finding that the keyframes that I'm inserting using my macro method (https://discourse.paraview.org/t/animation-keytime-integer-error/10454) don't survive a save, close and reload of the pvsm file. Any ideas about how to make these a...I'm finding that the keyframes that I'm inserting using my macro method (https://discourse.paraview.org/t/animation-keytime-integer-error/10454) don't survive a save, close and reload of the pvsm file. Any ideas about how to make these animation keyframes stick?
Here's a link to a screen cap with the issue shown.
https://drive.google.com/file/d/17EeDeTmN5fDGOg7LpN0GxM1fja47of6_/view?usp=sharing
I'm using paraview 5.11.
This is a copy of the issue from the community forum https://discourse.paraview.org/t/camera-animation-state-isnt-saving/10486.https://gitlab.kitware.com/paraview/paraview/-/issues/21597Qt/Components/pqSettingsDialog.cxx:1062022-10-13T00:44:52-04:00NicolasBQt/Components/pqSettingsDialog.cxx:106https://gitlab.kitware.com/paraview/paraview/-/issues/21596Qt/Components/pqLightsInspector.cxx:1562022-10-13T00:44:54-04:00NicolasBQt/Components/pqLightsInspector.cxx:156https://gitlab.kitware.com/paraview/paraview/-/issues/21595Qt/ApplicationComponents/pqAddToFavoritesReaction.cxx:1002022-10-13T00:44:57-04:00NicolasBQt/ApplicationComponents/pqAddToFavoritesReaction.cxx:100https://gitlab.kitware.com/paraview/paraview/-/issues/21594pvserver will not start because of NodeEditor - ParaView 5.11 RC12022-10-27T11:06:25-04:00Nabil G.pvserver will not start because of NodeEditor - ParaView 5.11 RC1Dear experts,
while trying to update our application with Paraview 5.11 RC1, we hit this issue about launching pvserver because of the presence of NodeEditor
I don't know if others reported about this issue.
Do you know whether one can c...Dear experts,
while trying to update our application with Paraview 5.11 RC1, we hit this issue about launching pvserver because of the presence of NodeEditor
I don't know if others reported about this issue.
Do you know whether one can control the automatic upload of NodeEditor when compiling Paraview?
Thanks for your valuable help.
regards.
```
Stack trace:
27 0x40225e pvserver() [0x40225e]
26 0x7f88476bc042 __libc_start_main + 242
25 0x402794 pvserver() [0x402794]
24 0x4024be pvserver() [0x4024be]
23 0x7f8845fbd184 vtkInitializationHelper::Initialize(int, char**, int, vtkCLIOptions*, bool) + 80
22 0x7f8845fbd823 vtkInitializationHelper::InitializeMiscellaneous(int) + 133
21 0x7f88450c1972 vtkPVPluginLoader::LoadPluginsFromPluginSearchPath() + 392
20 0x7f88450c1fac vtkPVPluginLoader::LoadPluginsFromPath(char const*) + 954
19 0x7f88450beaa6 /xxxxxxxxxxxxxxxxxxxxxxxxx/ParaView/lib/libvtkRemotingCore-pv5.11.so.1(+0xdcaa6) [0x7f88450beaa6]
18 0x7f88450c2949 vtkPVPluginLoader::LoadPluginInternal(char const*, bool) + 1973
17 0x7f8842ecfe6c vtkDynamicLoader::OpenLibrary(char const*, int) + 68
16 0x7f88424c9b63 vtksys::DynamicLoader::OpenLibrary(std::string const&, int) + 103
15 0x7f88424a8428 dlopen + 72
14 0x7f88424a8bd9 /lib64/libdl.so.2(+0x2bd9) [0x7f88424a8bd9]
13 0x7f88477d2293 _dl_catch_error + 51
12 0x7f88477d21c8 _dl_catch_exception + 136
11 0x7f88424a839c /lib64/libdl.so.2(+0x239c) [0x7f88424a839c]
10 0x7f88478d21ae /lib64/ld-linux-x86-64.so.2(+0x151ae) [0x7f88478d21ae]
9 0x7f88477d21c8 _dl_catch_exception + 136
8 0x7f88478d2c94 /lib64/ld-linux-x86-64.so.2(+0x15c94) [0x7f88478d2c94]
7 0x7f88477d2225 _dl_catch_exception + 229
6 0x7f88478ce8f1 /lib64/ld-linux-x86-64.so.2(+0x118f1) [0x7f88478ce8f1]
5 0x7f88478ce7e2 /lib64/ld-linux-x86-64.so.2(+0x117e2) [0x7f88478ce7e2]
4 0x7f87fb7a2649 /xxxxxxxxxxxxxxxxxxxxxxxxx/ParaView/lib/paraview-5.11/plugins/NodeEditor/NodeEditor.so(+0x16649) [0x7f87fb7a2649]
3 0x7f87fb7a2309 /xxxxxxxxxxxxxxxxxxxxxxxxx//ParaView/lib/paraview-5.11/plugins/NodeEditor/NodeEditor.so(+0x16309) [0x7f87fb7a2309]
2 0x7f87fc613b9e QGuiApplication::palette() + 14
1 0x7f87fc61258c /lib64/libQt5Gui.so.5(+0x10358c) [0x7f87fc61258c]
0 0x7f88476d1ab0 /lib64/libc.so.6(+0x3cab0) [0x7f88476d1ab0]
( 4.605s) [pvserver ] :0 FATL| Signal: SIGSEGV
Erreur de segmentation (core dumped)
```https://gitlab.kitware.com/paraview/paraview/-/issues/21587Selection modifier should be enabled with frustum based selections (Select Po...2022-10-18T10:43:26-04:00Joachim PouderouxSelection modifier should be enabled with frustum based selections (Select Points/Cells Through)Since recent changes introducing the `Selection Editor`, it is possible to perform operations with frustum based selections.
However, selection modifiers (Plus and Minus buttons) are still disabled.
See `pqRenderViewSelectionReaction.cx...Since recent changes introducing the `Selection Editor`, it is possible to perform operations with frustum based selections.
However, selection modifiers (Plus and Minus buttons) are still disabled.
See `pqRenderViewSelectionReaction.cxx:1022` & `1030` where `SELECT_FRUSTUM_CELLS` and `SELECT_FRUSTUM_POINTS` are not managed.
@spiros.tsalikis @mwestphalSpiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21586Clarify the Data Arrays in the Inforation Tab2022-10-04T19:12:17-04:00W. Alan ScottClarify the Data Arrays in the Inforation TabThe Information Tab/ Data Arrays section shows min and max for variables. It was unclear that this was not for the dataset, but rather the current time step. We added text that said: "Current Data Time: ##" just above this block. It ...The Information Tab/ Data Arrays section shows min and max for variables. It was unclear that this was not for the dataset, but rather the current time step. We added text that said: "Current Data Time: ##" just above this block. It has been lost. Please bring it back.
A good test case is can.exo, comparing 5.9.1 against 5.11.0-RC1.5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21585Rescale to visible data range fails2022-11-01T21:43:14-04:00W. Alan ScottRescale to visible data range failsRescale to visible data range fails. Here is how to replicate:
* 5.11.0-RC1. Builtin server.
* Can.ex2. Apply. Don't rotate it.
* Paint by ACCL.
* Move forward one timestep.
* Rescale to visible data range.
Nothing happens. This is...Rescale to visible data range fails. Here is how to replicate:
* 5.11.0-RC1. Builtin server.
* Can.ex2. Apply. Don't rotate it.
* Paint by ACCL.
* Move forward one timestep.
* Rescale to visible data range.
Nothing happens. This is a bug.
@cory.quammen5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21583XRInterface plugin uses Qt element's texts for conditions2022-11-16T06:09:01-05:00NicolasBXRInterface plugin uses Qt element's texts for conditionsIn `XRInterface/Plugin/pqXRInterfaceDockPanel.cxx`, the plugin uses three times Qt element labels for comparison in conditions (lines [282](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/XRInterface/Plugin/pqXRInterfa...In `XRInterface/Plugin/pqXRInterfaceDockPanel.cxx`, the plugin uses three times Qt element labels for comparison in conditions (lines [282](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Plugins/XRInterface/Plugin/pqXRInterfaceDockPanel.cxx#L282), 319 and 349 in latest master). Could it be refactored ?
```cpp
if (this->Internals->sendToXRButton->text() == "Send to XR") // Line 282
if (this->Internals->attachToCurrentViewButton->text() == "Attach to Current View") // Line 319
if (this->Internals->cConnectButton->text() == "Connect") // Line 349
```
This cause problems for MR !5934 and will cause problem in the future: as the UI file may be translated during the localization process, these comparison will break the code.
@tiffany.chhim @thomas.galland @mwestphalNicolasBNicolasBhttps://gitlab.kitware.com/paraview/paraview/-/issues/21576Allow IOSS reader caching to be turned off2024-03-14T10:21:15-04:00W. Alan ScottAllow IOSS reader caching to be turned offThe IOSS reader is currently caching the mesh (I believe). This works well unless a user has huge data, and is holding timesteps in individual restarts. Then, each restart's mesh is cached, and we end up growing memory until ParaView d...The IOSS reader is currently caching the mesh (I believe). This works well unless a user has huge data, and is holding timesteps in individual restarts. Then, each restart's mesh is cached, and we end up growing memory until ParaView dies.
Please add the ability in the IOSS reader to stop caching the mesh. Make it advanced, default off. I believe Utkarsh gave us the solution in the patch named patch.patch, found here: #21340 .5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21574Convert To Point Cloud filter should default to Vertex cells2022-10-18T16:06:12-04:00Kenneth MorelandConvert To Point Cloud filter should default to Vertex cellsWhen you create a `Convert To Point Cloud` filter, the default value for `Cell Generation Mode` is `Polyvertex cell`. The default should be changed to `Vertex cells`. From a naïve user's perspective, the result of either will look the sa...When you create a `Convert To Point Cloud` filter, the default value for `Cell Generation Mode` is `Polyvertex cell`. The default should be changed to `Vertex cells`. From a naïve user's perspective, the result of either will look the same. But `Polyvertex cell` is a dangerous representation that will absolutely break operations down the road if users try to apply filters like `Threshold`, `Extract Cells By Region`, or `Point Data To Cell Data`.
The small amount of memory that the polyvertex cell type saves is absolutely not worth the heartache it can cause. Furthermore, this change should be backward-compatible. There are no operations that work on polyvertex that will not also work with single vertex cells.https://gitlab.kitware.com/paraview/paraview/-/issues/21573Histogram 2D crash with cell data2022-10-18T11:22:13-04:00Kenneth MorelandHistogram 2D crash with cell dataThe Histogram 2D filter (new with ParaView 5.11) crashes on some inputs. To replicate, do the following.
1. Load this file: [histogram-2d-error.vtk](/uploads/f7ae74103581e57d7c9e20aed6e79a85/histogram-2d-error.vtk)
2. Add the `Histogram...The Histogram 2D filter (new with ParaView 5.11) crashes on some inputs. To replicate, do the following.
1. Load this file: [histogram-2d-error.vtk](/uploads/f7ae74103581e57d7c9e20aed6e79a85/histogram-2d-error.vtk)
2. Add the `Histogram 2D` filter
As soon as you add the filter, ParaView crashes.
I suspect the problem is that the data contains only cell data. You can work around the problem by running `Cell Data to Point Data`.5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21572State script with calculator does not work in client-server mode2022-10-20T19:16:21-04:00Kenneth MorelandState script with calculator does not work in client-server modeWhile using ParaView remotely to Andes at OLCF, I noticed a problem with python files that I saved as state files. (I am using ParaView 5.10.0, which is the latest version installed on OLCF.) The Python interpreter seems to have trouble ...While using ParaView remotely to Andes at OLCF, I noticed a problem with python files that I saved as state files. (I am using ParaView 5.10.0, which is the latest version installed on OLCF.) The Python interpreter seems to have trouble setting enumerated properties from a string.
I can replicate the problem with the following steps.
1. Connect to andes. (I suspect any remote server connection will have similar behavior, but I have not tested that.)
2. Load a dataset with cell data. (I used can.ex2.)
3. Create a `Calculator` filter. Set the `Attribute Type` to `Cell Data`. Enter something (anything) for the script.
4. Save the state as a python file.
5. Reset the session.
6. Load the python file just created (either with load state or with the python shell).
* An error occurs here.
[Here is the python script I created.](/uploads/546f8185c0127f6455b38cedc81a7ace/test.py)
The part of the script that creates the two pipeline objects is this:
```py
# create a new 'IOSS Reader'
canex2 = IOSSReader(registrationName='can.ex2', FileName=['/ccs/home/kmorel/data/paraview-examples/can.ex2'])
canex2.ElementBlocks = ['block_1', 'block_2']
canex2.NodeBlockFields = ['accl', 'displ', 'vel']
canex2.ElementBlockFields = ['eqps']
canex2.NodeSets = []
canex2.SideSets = []
# create a new 'Calculator'
calculator1 = Calculator(registrationName='Calculator1', Input=canex2)
calculator1.AttributeType = 'Cell Data'
calculator1.Function = 'eqps'
```
The error seems to occur on the line `calculator1.AttributeType = 'Cell Data'`. I suspect the problem is that the reader pipeline object is not updated before the calculator is created, and somehow the enumeration object is not set up correctly. For some reason, this only occurs in client-server mode. I don't see a problem when running locally.
The full error I get is here:
```
Traceback (most recent call last):
File "/Applications/ParaView-5.10.0.app/Contents/Python/paraview/servermanager.py", line 496, in __setattr__
setter(self, value)
File "/Applications/ParaView-5.10.0.app/Contents/Python/paraview/servermanager.py", line 2612, in setProperty
return self.SetPropertyWithName(propName, value)
File "/Applications/ParaView-5.10.0.app/Contents/Python/paraview/servermanager.py", line 355, in SetPropertyWithName
prop.SetData(arg)
File "/Applications/ParaView-5.10.0.app/Contents/Python/paraview/servermanager.py", line 866, in SetData
convertedValues = list(map(self.ConvertValue, values))
File "/Applications/ParaView-5.10.0.app/Contents/Python/paraview/servermanager.py", line 984, in ConvertValue
raise ValueError("%s is not a valid value." % value)
ValueError: Cell Data is not a valid value.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Applications/ParaView-5.10.0.app/Contents/Python/paraview/servermanager.py", line 500, in __setattr__
_bc.setattr_fix_value(self, name, value, setter)
File "/Applications/ParaView-5.10.0.app/Contents/Python/paraview/_backwardscompatibilityhelper.py", line 467, in setattr_fix_value
raise ValueError("'%s' is not a valid value for %s!" % (value, pname))
ValueError: 'Cell Data' is not a valid value for AttributeType!
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<string>", line 63, in <module>
File "/Applications/ParaView-5.10.0.app/Contents/Python/paraview/servermanager.py", line 504, in __setattr__
raise ValueError("%s is not a valid value for attribute %s." % (value, name))
ValueError: Cell Data is not a valid value for attribute AttributeType.
```Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/215695.11-RC1 crash - clip+box, then reset-bounds2022-10-18T10:17:43-04:00Menno Deij - van Rijswijk5.11-RC1 crash - clip+box, then reset-boundsSteps to reproduce:
- Sources > Sphere > Apply
- Filters > Clip
- Choose Box
- Click "Reset Bounds".
Hourglass -> Crash.Steps to reproduce:
- Sources > Sphere > Apply
- Filters > Clip
- Choose Box
- Click "Reset Bounds".
Hourglass -> Crash.5.11 (Spring 2022)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21566IOSS writer is non-fonctional and segfaults with unstructured grid2023-06-07T21:39:10-04:00Mathieu Westphal (Kitware)IOSS writer is non-fonctional and segfaults with unstructured gridI've been testing the IOSS Exodus writer, it seems just non fonctionnal.
1. Saving a image data or poly data in IOSS Exodus do not save anything and fails with (tested with Wavelet/Cone):
```
( 47.207s) [paraview ]vtkDemandDriv...I've been testing the IOSS Exodus writer, it seems just non fonctionnal.
1. Saving a image data or poly data in IOSS Exodus do not save anything and fails with (tested with Wavelet/Cone):
```
( 47.207s) [paraview ]vtkDemandDrivenPipeline:776 ERR| vtkPVCompositeDataPipeline (0x55d46408c7c0): Input for connection index 0 on input port index 0 for algorithm vtkIOSSWriter (0x55d463a4e900) is of type vtkImageData, but a vtkPartitionedDataSetCollection is required.
```
2. Saving a PartitionedDataSetCollection do save a file but reading it back is empty (test with PartitionedDataSetCollectionSource)
3. Saving an unstructured grid segfaults with (test with UnstructuredCellTypes):
```
Breakpoint 1 at 0x7ffff7e3f49c
(gdb) bt
#0 0x00007ffff7e3f49c in ?? () from /usr/lib/libc.so.6
#1 0x00007ffff7def958 in raise () from /usr/lib/libc.so.6
#2 0x00007ffff7dd953d in abort () from /usr/lib/libc.so.6
#3 0x00007fffed699833 in __gnu_cxx::__verbose_terminate_handler () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#4 0x00007fffed6a5cfc in __cxxabiv1::__terminate (handler=<optimized out>) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#5 0x00007fffed6a5d69 in std::terminate () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
#6 0x00007fffed6a5fcd in __cxxabiv1::__cxa_throw (obj=<optimized out>, tinfo=0x7fffed8291e0 <typeinfo for std::runtime_error>, dest=0x7fffed6bd470 <std::runtime_error::~runtime_error()>)
at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_throw.cc:98
#7 0x00007fffe6e49f32 in vtkNodeBlock::vtkNodeBlock (this=0x55555bbc05d0, pdc=0x555559dd0ef0, name="nodeblock_1", controller=0x555555a56f40, writer=0x55555bc27750) at /home/glow/dev/paraview/pv1/src/VTK/IO/IOSS/vtkIOSSModel.cxx:383
#8 0x00007fffe6e5f7d5 in std::_Construct<vtkNodeBlock, vtkPartitionedDataSetCollection*&, char const (&) [12], vtkSmartPointer<vtkMultiProcessController>&, vtkIOSSWriter*&> (__p=0x55555bbc05d0)
at /usr/include/c++/12.2.0/bits/stl_construct.h:119
#9 0x00007fffe6e5e062 in std::allocator_traits<std::allocator<void> >::construct<vtkNodeBlock, vtkPartitionedDataSetCollection*&, char const (&) [12], vtkSmartPointer<vtkMultiProcessController>&, vtkIOSSWriter*&> (__p=0x55555bbc05d0)
at /usr/include/c++/12.2.0/bits/alloc_traits.h:635
#10 0x00007fffe6e5c68e in std::_Sp_counted_ptr_inplace<vtkNodeBlock, std::allocator<void>, (__gnu_cxx::_Lock_policy)2>::_Sp_counted_ptr_inplace<vtkPartitionedDataSetCollection*&, char const (&) [12], vtkSmartPointer<vtkMultiProcessController>&, vtkIOSSWriter*&> (this=0x55555bbc05c0, __a=...) at /usr/include/c++/12.2.0/bits/shared_ptr_base.h:604
#11 0x00007fffe6e5a41d in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count<vtkNodeBlock, std::allocator<void>, vtkPartitionedDataSetCollection*&, char const (&) [12], vtkSmartPointer<vtkMultiProcessController>&, vtkIOSSWriter*&> (this=0x7fffffffc718, __p=@0x7fffffffc710: 0x0, __a=...) at /usr/include/c++/12.2.0/bits/shared_ptr_base.h:971
#12 0x00007fffe6e57d0e in std::__shared_ptr<vtkNodeBlock, (__gnu_cxx::_Lock_policy)2>::__shared_ptr<std::allocator<void>, vtkPartitionedDataSetCollection*&, char const (&) [12], vtkSmartPointer<vtkMultiProcessController>&, vtkIOSSWriter*&> (this=0x7fffffffc710, __tag=...) at /usr/include/c++/12.2.0/bits/shared_ptr_base.h:1712
#13 0x00007fffe6e54919 in std::shared_ptr<vtkNodeBlock>::shared_ptr<std::allocator<void>, vtkPartitionedDataSetCollection*&, char const (&) [12], vtkSmartPointer<vtkMultiProcessController>&, vtkIOSSWriter*&> (this=0x7fffffffc710,
__tag=...) at /usr/include/c++/12.2.0/bits/shared_ptr.h:464
#14 0x00007fffe6e5038e in std::make_shared<vtkNodeBlock, vtkPartitionedDataSetCollection*&, char const (&) [12], vtkSmartPointer<vtkMultiProcessController>&, vtkIOSSWriter*&> () at /usr/include/c++/12.2.0/bits/shared_ptr.h:1010
#15 0x00007fffe6de2e38 in vtkIOSSModel::vtkIOSSModel (this=0x7fffffffc860, dataset=0x555559dd0ef0, writer=0x55555bc27750) at /home/glow/dev/paraview/pv1/src/VTK/IO/IOSS/vtkIOSSModel.cxx:825
#16 0x00007fffe6dcaed2 in vtkIOSSWriter::RequestData (this=0x55555bc27750, request=0x55555bc03570, inputVector=0x55555b66ab40) at /home/glow/dev/paraview/pv1/src/VTK/IO/IOSS/vtkIOSSWriter.cxx:206
#17 0x00007ffff0c7ddd0 in vtkDataObjectAlgorithm::ProcessRequest (this=0x55555bc27750, request=0x55555bc03570, inputVector=0x55555b66ab40, outputVector=0x55555bc02d10)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkDataObjectAlgorithm.cxx:86
#18 0x00007ffff0c8a62b in vtkExecutive::CallAlgorithm (this=0x555559e26710, request=0x55555bc03570, direction=1, inInfo=0x55555b66ab40, outInfo=0x55555bc02d10)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkExecutive.cxx:734
#19 0x00007ffff0c809b8 in vtkDemandDrivenPipeline::ExecuteData (this=0x555559e26710, request=0x55555bc03570, inInfo=0x55555b66ab40, outInfo=0x55555bc02d10)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:461
#20 0x00007ffff0c73bd9 in vtkCompositeDataPipeline::ExecuteData (this=0x555559e26710, request=0x55555bc03570, inInfoVec=0x55555b66ab40, outInfoVec=0x55555bc02d10)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:162
#21 0x00007ffff0c7ff65 in vtkDemandDrivenPipeline::ProcessRequest (this=0x555559e26710, request=0x55555bc03570, inInfoVec=0x55555b66ab40, outInfoVec=0x55555bc02d10)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:260
#22 0x00007ffff0dd6adc in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x555559e26710, request=0x55555bc03570, inInfoVec=0x55555b66ab40, outInfoVec=0x55555bc02d10)
at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:343
#23 0x00007ffff0c8079d in vtkDemandDrivenPipeline::UpdateData (this=0x555559e26710, outputPort=0) at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:418
#24 0x00007ffff0dd6e6c in vtkStreamingDemandDrivenPipeline::Update (this=0x555559e26710, port=0, requests=0x0) at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:417
#25 0x00007ffff0dd6cf5 in vtkStreamingDemandDrivenPipeline::Update (this=0x555559e26710, port=0) at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:380
#26 0x00007ffff0c694d2 in vtkAlgorithm::Update (this=0x55555bc27750, port=0) at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkAlgorithm.cxx:1491
#27 0x00007ffff0c6949d in vtkAlgorithm::Update (this=0x55555bc27750) at /home/glow/dev/paraview/pv1/src/VTK/Common/ExecutionModel/vtkAlgorithm.cxx:1485
#28 0x00007fffe6dca654 in vtkIOSSWriter::Write (this=0x55555bc27750) at /home/glow/dev/paraview/pv1/src/VTK/IO/IOSS/vtkIOSSWriter.cxx:117
#29 0x00007fffec3f9967 in vtkIOSSWriterCommand (arlu=0x555555a6fb60, ob=0x55555bc27750, method=0x55555bb91759 "Write", msg=..., resultStream=...)
at /home/glow/dev/paraview/pv1/build/CMakeFiles/vtkIOIOSSCS/vtkIOSSWriterClientServer.cxx:300
#30 0x00007ffff566e270 in vtkClientServerInterpreter::CallCommandFunction (this=0x555555a6fb60, cname=0x7fffe6e66783 "vtkIOSSWriter", ptr=0x55555bc27750, method=0x55555bb91759 "Write", msg=..., result=...)
at /home/glow/dev/paraview/pv1/src/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:810
#31 0x00007ffff566c60f in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x555555a6fb60, css=..., midx=0) at /home/glow/dev/paraview/pv1/src/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:424
#32 0x00007ffff566baf2 in vtkClientServerInterpreter::ProcessOneMessage (this=0x555555a6fb60, css=..., message=0) at /home/glow/dev/paraview/pv1/src/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:265
#33 0x00007ffff566b955 in vtkClientServerInterpreter::ProcessStream (this=0x555555a6fb60, css=...) at /home/glow/dev/paraview/pv1/src/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:235
#34 0x00007ffff52f01ae in vtkPVSessionCore::ExecuteStreamInternal (this=0x555555f85250, stream=..., ignore_errors=false) at /home/glow/dev/paraview/pv1/src/Remoting/ServerManager/vtkPVSessionCore.cxx:620
#35 0x00007ffff52eff5e in vtkPVSessionCore::ExecuteStream (this=0x555555f85250, location=1, stream=..., ignore_errors=false) at /home/glow/dev/paraview/pv1/src/Remoting/ServerManager/vtkPVSessionCore.cxx:590
#36 0x00007ffff52ebc64 in vtkPVSessionBase::ExecuteStream (this=0x555555f91060, location=1, stream=..., ignore_errors=false) at /home/glow/dev/paraview/pv1/src/Remoting/ServerManager/vtkPVSessionBase.cxx:165
#37 0x00007ffff5456dce in vtkSMProxy::ExecuteStream (this=0x55555bc34be0, stream=..., ignore_errors=false, location=1) at /home/glow/dev/paraview/pv1/src/Remoting/ServerManager/vtkSMProxy.cxx:2406
#38 0x00007ffff5512cf1 in vtkSMWriterProxy::UpdatePipeline (this=0x55555bc34be0) at /home/glow/dev/paraview/pv1/src/Remoting/ServerManager/vtkSMWriterProxy.cxx:74
#39 0x00007ffff7a34c28 in pqSaveDataReaction::saveActiveData (filename=...) at /home/glow/dev/paraview/pv1/src/Qt/ApplicationComponents/pqSaveDataReaction.cxx:189
#40 0x00007ffff7a344b8 in pqSaveDataReaction::saveActiveData () at /home/glow/dev/paraview/pv1/src/Qt/ApplicationComponents/pqSaveDataReaction.cxx:125
#41 0x00007ffff78e6a8f in pqSaveDataReaction::onTriggered (this=0x555555e5c760)
```
FYI @\_transfer-utkarsh.ayachit @cory.quammen5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21565Ensight case writer do not write actual case file2023-07-10T21:16:00-04:00Mathieu Westphal (Kitware)Ensight case writer do not write actual case fileEnsight case writer do not write actual case file
Steps to repro:
- Run ParaView
- UnstructuredCellTypes, Apply
- File -> SaveData -> test.case
- Many files are created, but there is no test.case and nothing that can be opened by ParaV...Ensight case writer do not write actual case file
Steps to repro:
- Run ParaView
- UnstructuredCellTypes, Apply
- File -> SaveData -> test.case
- Many files are created, but there is no test.case and nothing that can be opened by ParaView out of the box
FYI @caitlin.ross @cory.quammen5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21562Opacity and Color Value default in MultiBlock Inspector2022-12-20T15:39:31-05:00Maxwell JacksonOpacity and Color Value default in MultiBlock Inspector@ethan.stam @cory.quammen
The default for the opacity in the MultiBlock Inspector should be at 100 instead of 0 when double clicking the wheel for opacity
To recreate
- Use bake.e example
- View -> MultiBlock Inspector
- Double click t...@ethan.stam @cory.quammen
The default for the opacity in the MultiBlock Inspector should be at 100 instead of 0 when double clicking the wheel for opacity
To recreate
- Use bake.e example
- View -> MultiBlock Inspector
- Double click the second wheel to the left of block_1
Opacity defaults at 0 instead of 100, essentially making the block disappear
Also, when setting a custom color for the block, the value for `Val` defaults to 0. This makes it so whatever is chosen in the color picker will end up as black. We think the default value for `Val` should be 100 instead.
To recreate:
- Use bake.e example
- View -> MultiBlock Inspector
- Double click the first wheel to the left of block_1
- Change the color in the color selector widget. The end result is black.
- Increase `Val` to 100, now the color shows up5.12 (Winter 2023)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/21560Calculator documentation is incomplete in both 5.10.1 and 5.11.02022-10-06T10:55:51-04:00Phil SmithCalculator documentation is incomplete in both 5.10.1 and 5.11.0Please document all the functions the calculator can use on the input line. For example, I used avg(scaler) and it produces a useable output. This particular function is not listed in the documentation at docs.paraview.org. What other fu...Please document all the functions the calculator can use on the input line. For example, I used avg(scaler) and it produces a useable output. This particular function is not listed in the documentation at docs.paraview.org. What other functions can you call from the calculator that are not listed? This applies to both 5.10.1 and 5.11.0.
For 5.11.0 there are three icons/buttons that are above the entry field on the right. The functionality of these icons/buttons needs to be documented. It appears the first icon lists any expressions that you have saved, so you can use them. The second icon appears to save the current expression to an expressions list. The third button appears to open the expressions list, so the user can search for an expression that has been saved; add, remove, import or export any expressions that have been used in the past.5.11 (Spring 2022)