ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-08-17T13:03:50-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20231TPL: updates2021-08-17T13:03:50-04:00Utkarsh AyachitTPL: updates**ParaView:**
| Library | current-version (in source) | latest-version (upstream) | status |
| --- | --- | --- | --- |
| cgns | 4.1.1 | 4.1.2 | <ul><li> - [x] paraview/paraview!4418 </li></ul> |
| pro...**ParaView:**
| Library | current-version (in source) | latest-version (upstream) | status |
| --- | --- | --- | --- |
| cgns | 4.1.1 | 4.1.2 | <ul><li> - [x] paraview/paraview!4418 </li></ul> |
| protobuf | 3.11.2 | 3.13 | <ul><li> - [x] paraview/paraview!4418 </li></ul> |
**VTK:**
| Library | current-version (in source) | latest-version (upstream) | status |
| --- | --- | --- | --- |
| diy2 | | | <ul><li> - [ ] </li></ul> |
| doubleconversion | 3.1.5 | 3.1.5 | <ul><li> - [x] </li></ul> |
| eigen | 3.3.7| 3.3.7 | <ul><li> - [x] </li></ul> |
| exodusII | | | <ul><li> - [ ] </li></ul> |
| expat | 2.2.9 | 2.2.9 | <ul><li> - [x] </li></ul> |
| fides | | | <ul><li> - [ ] </li></ul> |
| freetype | 2.10.1 | [2.10.2](https://www.freetype.org/index.html) | <ul><li> - [x] vtk/vtk!7290 </li></ul> |
| gl2ps | 1.4.1 | [1.4.2](https://gitlab.onelab.info/gl2ps/gl2ps/-/releases) | <ul><li> - [x] vtk/vtk!7291 </li></ul> |
| glew | 2.1.0 | [2.1.0](http://glew.sourceforge.net/)| <ul><li> - [x] </li></ul> |
| h5part | 1.6.6 | [1.6.6](https://codeforge.lbl.gov/projects/h5part/) | <ul><li> - [x] </li></ul> |
| hdf5 | 1.10.6 | [1.12.0](https://www.hdfgroup.org/downloads/hdf5/) | <ul><li> - [ ] </li></ul> |
| ioss | | | <ul><li> - [ ] </li></ul> |
| jpeg | 2.0.3 | [2.0.5](https://github.com/libjpeg-turbo/libjpeg-turbo/tags) | <ul><li> - [x] vtk/vtk!7292 </li></ul> |
| jsoncpp | 1.9.2 | [1.9.4](https://github.com/open-source-parsers/jsoncpp/tags) | <ul><li> - [x] vtk/vtk!7294 </li></ul> |
| kissfft | | | <ul><li> - [ ] </li></ul> |
| libharu | 2.4.0 (unreleased) | 2.3.0 | <ul><li> - [x] </li></ul> |
| libproj | 4.9.3 | 4.9.3 | <ul><li> - [x] </li></ul> |
| libxml2 | 2.9.10 | [2.9.10](https://github.com/GNOME/libxml2/tags)| <ul><li> - [x] </li></ul> |
| loguru | 2.1.0 | [2.1.0](https://github.com/emilk/loguru/tags) | <ul><li> - [x] </li></ul> |
| lz4 | 1.9.2 | [1.9.2](https://github.com/lz4/lz4/tags) | <ul><li> - [x] </li></ul> |
| lzma | 5.2.4 | [5.2.5](https://tukaani.org/xz/) | <ul><li> - [ ] </li></ul> |
| mpi4py | 3.0.1 | [3.0.3](https://bitbucket.org/mpi4py/mpi4py/downloads/) | <ul><li> - [ ] </li></ul> |
| netcdf | 4.7.3| [4.7.4](https://www.unidata.ucar.edu/software/netcdf/) | <ul><li> - [x] vtk/vtk!7295 </li></ul> |
| ogg | 1.3.4 | [1.3.4](https://xiph.org/downloads/) | <ul><li> - [x] </li></ul> |
| pegtl | 2.8.1 | [2.8.3](https://github.com/taocpp/PEGTL/tags) | <ul><li> - [ ] vtk/vtk!7296 </li></ul> |
| png | 1.6.37 | [1.6.37](http://www.libpng.org/pub/png/libpng.html) | <ul><li> - [x] </li></ul> |
| pugixml | 1.10 | [1.10](https://pugixml.org/) | <ul><li> - [x] </li></ul> |
| sqlite | 3.30.1| [3.33.0](https://www.sqlite.org/download.html) | <ul><li> - [ ] </li></ul> |
| theora | 1.1.1 | [1.1.1](https://www.theora.org/downloads/)| <ul><li> - [x] </li></ul> |
| tiff |4.1.0 | [4.1.0](https://gitlab.com/libtiff/libtiff/-/tags) | <ul><li> - [x] </li></ul> |
| utf8 |2.3.4 | [2.3.4](https://sourceforge.net/projects/utfcpp/files/utf8cpp_2x/)| <ul><li> - [x] </li></ul> |
| verdict | 1.2.0 | | <ul><li> - [ ] </li></ul> |
| vpic | | | <ul><li> - [ ] </li></ul> |
| vtkm | | | <ul><li> - [ ] </li></ul> |
| xdmf2 | | | <ul><li> - [ ] </li></ul> |
| xdmf3 | | | <ul><li> - [ ] </li></ul> |
| zfp | 0.5.5 | [0.5.5](https://github.com/LLNL/zfp/tags)| <ul><li> - [x] </li></ul> |
| zlib | 1.2.11 | [1.2.11](https://zlib.net/) | <ul><li> - [x] </li></ul> |5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20230Update third-party packages2020-09-30T15:53:37-04:00Cory Quammencory.quammen@kitware.comUpdate third-party packagesTodo - Find which packages have newer releases and update.Todo - Find which packages have newer releases and update.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/20229Catalyst configuration on windows fails with CMake < 3.152021-09-16T18:44:07-04:00Mathieu Westphal (Kitware)Catalyst configuration on windows fails with CMake < 3.15With CMake 3.13.1, ParaView configuration fails on windows with the following :
```
-- conduit::float64 native type: double
CMake Error at ThirdParty/catalyst/vtkcatalyst/catalyst/cmake/catalyst-macros.cmake:69 (install):
install Li...With CMake 3.13.1, ParaView configuration fails on windows with the following :
```
-- conduit::float64 native type: double
CMake Error at ThirdParty/catalyst/vtkcatalyst/catalyst/cmake/catalyst-macros.cmake:69 (install):
install Library TARGETS given no DESTINATION!
Call Stack (most recent call first):
Clients/InSitu/CMakeLists.txt:86 (catalyst_library)
```
Upgrading to 3.18.1 (or any version > 3.15) fixes the issue.5.10 (Fall 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20228Add an Open With option2020-09-24T20:47:53-04:00W. Alan ScottAdd an Open With optionPlease add an Open With option to the File menu. This will allow users to open datasets with whatever reader they want.Please add an Open With option to the File menu. This will allow users to open datasets with whatever reader they want.https://gitlab.kitware.com/paraview/paraview/-/issues/20227Labels are overlapping in the Color Legend2024-03-27T12:19:16-04:00W. Alan ScottLabels are overlapping in the Color LegendLabels are overlapping in the Color Legend. Here is how to replicate:
* ParaView 5.8.0, and master, Linux, local server.
* Load vessel_out.e (Attached). All vars on. Apply.
* Last timestep.
* Paint by _disp.
* Drag the color legend...Labels are overlapping in the Color Legend. Here is how to replicate:
* ParaView 5.8.0, and master, Linux, local server.
* Load vessel_out.e (Attached). All vars on. Apply.
* Last timestep.
* Paint by _disp.
* Drag the color legend to be horizontal, under the dataset.
* Now, drag the color legend to be wider and narrower. The labels will overlap.
Attaching a screenshot.
Workaround is in the Color Legend Editor. You can turn off Automatic Label Format, and then change the format.
![Screen_Shot_2020-09-24_at_3.55.28_PM](/uploads/6f172402f63908242133a6a6ba176a3f/Screen_Shot_2020-09-24_at_3.55.28_PM.png)5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/20226text.Position is not updated correctly in Python2022-01-17T21:01:31-05:00W. Alan Scotttext.Position is not updated correctly in PythonThe Position and Position2 variables are not being updated correctly in Python. Here is how to replicate:
* Linux, 5.8.0 and master, local server.
* View/ Python View.
* Enter the following text into the Python View.
```
text1=Text()...The Position and Position2 variables are not being updated correctly in Python. Here is how to replicate:
* Linux, 5.8.0 and master, local server.
* View/ Python View.
* Enter the following text into the Python View.
```
text1=Text()
text1.Text="my text"
text1Display = Show(text1)
text1Display.WindowLocation = 'UpperCenter';
Render()
print text1Display.Position2, text1Display.Position
```
* Bug - Position and Position2 should show that the text is in the upper middle of the view. They report back that text is in the lower left corner. This is a bug.
* Bug - If you now open the Properties tab "Use Coordinates", these also show that the text is in the lower left corner. Again, this is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/20225Capture Screenshot to the Clipboard colorbar wrong on paste2021-09-23T20:38:03-04:00John PatchettCapture Screenshot to the Clipboard colorbar wrong on paste![Screen_Shot_2020-09-22_at_9.57.26_PM](/uploads/906778622a96cd86be7c08617aa3da9a/Screen_Shot_2020-09-22_at_9.57.26_PM.png)
Screen shot shows the rendering when the copy to clipboard button on the top of the view was selected. on the rig...![Screen_Shot_2020-09-22_at_9.57.26_PM](/uploads/906778622a96cd86be7c08617aa3da9a/Screen_Shot_2020-09-22_at_9.57.26_PM.png)
Screen shot shows the rendering when the copy to clipboard button on the top of the view was selected. on the right is the image that was pasted into a word doc. This was done in 5.8.1 on mac, not tested with master.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20224vtm file crashes with slice2024-03-07T20:47:16-05:00W. Alan Scottvtm file crashes with sliceWe have a semi repeatable crash when slicing a vtm dataset. This can frequently be replicated, but unfortunately, it appears to be somewhat random with regards to when it occurs. It also appears totally random which cells internally sh...We have a semi repeatable crash when slicing a vtm dataset. This can frequently be replicated, but unfortunately, it appears to be somewhat random with regards to when it occurs. It also appears totally random which cells internally show the issue. Here is how to replicate:
* ParaView 5.8.0, or master, builtin server, Linux.
* Load dataset named vtm_only_5888_elements.vtm. Variables don't matter. Apply.
* Although it shouldn't matter, -Z.
* Slice. Origin: 0,0,0. Normal: 0,0,1. Apply.
This should crash. If it doesn't, delete the slice and create it again.
It is crashing in void vtkPolyData::ComputeBounds(), at
```
for (auto cellId = 0; cellId < numCells; ++cellId)
{
cellA[ca]->GetCellAtId(cellId, npts, pts);
for (ptIdx = 0; ptIdx < npts; ++ptIdx)
{
>>>> ptUses[pts[ptIdx]] = 1;
}
}
```
where cellA[ca]->GetCellAtId (3 lines above) is returning pts[ptIdx] == bazillions, which is causing a set fault accessing the ptUsers array.
Directions on getting the dataset will be sent to Utkarsh and Berk.
Here is a stack trace:
```
73 0x408109 ./paraview() [0x408109]
72 0x7f63b8199545 __libc_start_main + 245
71 0x4105cb ./paraview() [0x4105cb]
70 0x7f63b5b08364 QCoreApplication::exec() + 132
69 0x7f63b5affada QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 298
68 0x7f63b5b575df QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 95
67 0x7f63a2fbe45c g_main_context_iteration + 44
65 0x7f63a2fbe049 g_main_context_dispatch + 345
64 0x7f6384af3450 /snip/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x86450) [0x7f6384af3450]
63 0x7f63b5ea5a9b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 171
62 0x7f63b5ecc205 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 261
61 0x7f63b5eca8bb QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1739
60 0x7f63b5b014c8 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 280
59 0x7f63b76f19c4 QApplication::notify(QObject*, QEvent*) + 628
58 0x7f63b76ea64c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
57 0x7f63b7742aa1 /snip/bin/../lib/libQt5Widgets.so.5(+0x1b2aa1) [0x7f63b7742aa1]
56 0x7f63b774064b /snip/bin/../lib/libQt5Widgets.so.5(+0x1b064b) [0x7f63b774064b]
55 0x7f63b76f0f6f QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) + 447
54 0x7f63b5b014c8 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 280
53 0x7f63b76f1f1f QApplication::notify(QObject*, QEvent*) + 1999
52 0x7f63b76ea64c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
51 0x7f63b77263c8 QWidget::event(QEvent*) + 472
50 0x7f63b77d6714 QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 212
49 0x7f63b77d654a /snip/bin/../lib/libQt5Widgets.so.5(+0x24654a) [0x7f63b77d654a]
48 0x7f63b77d522a /snip/bin/../lib/libQt5Widgets.so.5(+0x24522a) [0x7f63b77d522a]
47 0x7f63b77d5042 QAbstractButton::clicked(bool) + 50
46 0x7f63b5b2e9da QMetaObject::activate(QObject*, int, int, void**) + 1898
45 0x7f63b6f8ef56 /snip/bin/../lib/libpqComponents-pv5.8.so.1(+0x344f56) [0x7f63b6f8ef56]
44 0x7f63b6ece451 pqPropertiesPanel::apply() + 621
43 0x7f63b6f8f627 pqPropertiesPanel::applied(pqProxy*) + 71
42 0x7f63b5b2e9da QMetaObject::activate(QObject*, int, int, void**) + 1898
41 0x7f63b7e0350b /snip/bin/../lib/libpqApplicationComponents-pv5.8.so.1(+0x23f50b) [0x7f63b7e0350b]
40 0x7f63b7cc270a pqApplyBehavior::onApplied(pqProxy*) + 78
39 0x7f63b7cc27cf pqApplyBehavior::applied(pqPropertiesPanel*, pqProxy*) + 117
38 0x7f63b7cc33dd pqApplyBehavior::showData(pqPipelineSource*, pqView*) + 359
37 0x7f63a9afae60 vtkSMParaViewPipelineControllerWithRendering::ShowInPreferredView(vtkSMSourceProxy*, int, vtkSMViewProxy*) + 612
36 0x7f63a9afba6c vtkSMParaViewPipelineControllerWithRendering::UpdatePipelineBeforeDisplay(vtkSMSourceProxy*, int, vtkSMViewProxy*) + 642
35 0x7f63b4df1a19 vtkSMSourceProxy::UpdatePipeline(double) + 183
34 0x7f63b4df2063 vtkSMSourceProxy::PostUpdateData(bool) + 71
33 0x7f63b4d82643 vtkSMProxy::PostUpdateData(bool) + 231
32 0x7f63ad9dbf85 vtkObject::InvokeEvent(unsigned long, void*) + 61
31 0x7f63ad9dba78 /snip/bin/../lib/libvtkCommonCore-pv5.8.so.1(+0x70aa78) [0x7f63ad9dba78]
30 0x7f63ad802ea7 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 67
29 0x7f63b53906b6 /snip/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x596b6) [0x7f63b53906b6]
28 0x7f63b539071a /snip/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x5971a) [0x7f63b539071a]
27 0x7f63b53a210b /snip/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x6b10b) [0x7f63b53a210b]
26 0x7f63b5b2e9da QMetaObject::activate(QObject*, int, int, void**) + 1898
25 0x7f63b677c043 /snip/bin/../lib/libpqCore-pv5.8.so.1(+0x157043) [0x7f63b677c043]
24 0x7f63b6722247 pqPipelineSource::dataUpdated() + 31
23 0x7f63b677cb0b pqPipelineSource::dataUpdated(pqPipelineSource*) + 71
22 0x7f63b5b2e9da QMetaObject::activate(QObject*, int, int, void**) + 1898
21 0x7f63b6f85baa /snip/../lib/libpqComponents-pv5.8.so.1(+0x33bbaa) [0x7f63b6f85baa]
20 0x7f63b6e182f1 pqDataInformationModel::dataUpdated(pqPipelineSource*) + 237
19 0x7f63b67138ef pqOutputPort::getDataInformation() const + 81
18 0x7f63b4df219e vtkSMSourceProxy::GetDataInformation(unsigned int) + 130
17 0x7f63b4d555c2 vtkSMOutputPort::GetDataInformation() + 218
16 0x7f63b4d55969 vtkSMOutputPort::GatherDataInformation() + 463
15 0x7f63b4d80cec vtkSMProxy::GatherInformation(vtkPVInformation*) + 340
14 0x7f63b4c5ce52 vtkPVSessionBase::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) + 62
13 0x7f63b4c6114f vtkPVSessionCore::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) + 141
12 0x7f63b4c61077 vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned int) + 485
11 0x7f63b2474e00 vtkPVDataInformation::CopyFromObject(vtkObject*) + 926
10 0x7f63b2473aed vtkPVDataInformation::CopyFromCompositeDataSet(vtkCompositeDataSet*) + 35
9 0x7f63b2473704 vtkPVDataInformation::CopyFromCompositeDataSetInitialize(vtkCompositeDataSet*) + 74
8 0x7f63b246abe1 vtkPVCompositeDataInformation::CopyFromObject(vtkObject*) + 689
7 0x7f63b2474e00 vtkPVDataInformation::CopyFromObject(vtkObject*) + 926
6 0x7f63b2473b46 vtkPVDataInformation::CopyFromCompositeDataSet(vtkCompositeDataSet*) + 124
5 0x7f63b24735f6 vtkPVDataInformation::AddFromMultiPieceDataSet(vtkCompositeDataSet*) + 190
4 0x7f63b2474ea3 vtkPVDataInformation::CopyFromObject(vtkObject*) + 1089
3 0x7f63b2473f97 vtkPVDataInformation::CopyFromDataSet(vtkDataSet*) + 565
2 0x7f63aeff16a7 vtkDataSet::GetBounds() + 37
1 0x7f63af1af662 vtkPolyData::ComputeBounds() + 656
0 0x7f63b81ad3f0 /lib64/libc.so.6(+0x363f0) [0x7f63b81ad3f0]
```5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/20223AMReX reload file series does not work2021-04-29T20:51:20-04:00Armin WehrfritzAMReX reload file series does not workWhen a AMReX file (i.e. directory) series is loaded in ParaView, the reload "Dataset->Reload Files->Find new files" functionality does not work - the reader simply ignores the newly added directories.
Tested with ParaView 5.8.1.When a AMReX file (i.e. directory) series is loaded in ParaView, the reload "Dataset->Reload Files->Find new files" functionality does not work - the reader simply ignores the newly added directories.
Tested with ParaView 5.8.1.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20222AMReX reader ignores time information2021-09-07T21:35:52-04:00Armin WehrfritzAMReX reader ignores time informationMany AMReX-based simulation codes write checkpoints/datasets at non-uniform time intervals. The datasets contain however the time information in the Header file. It would be nice if ParaView was to read and use that information.
Tested ...Many AMReX-based simulation codes write checkpoints/datasets at non-uniform time intervals. The datasets contain however the time information in the Header file. It would be nice if ParaView was to read and use that information.
Tested with ParaView 5.8.1.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20221Change Extract Generator to Extractors2020-11-17T07:43:44-05:00W. Alan ScottChange Extract Generator to ExtractorsPlease change the "Extract Generator" menu to be "Extractors".Please change the "Extract Generator" menu to be "Extractors".5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20220Cell Center Filter Doesn't Update During Time Stepping2020-11-10T21:38:51-05:00Joel A. KuleszaCell Center Filter Doesn't Update During Time Stepping# Summary
A `Cell Centers` filter applied to time-dependent cell data does not update for a different grid geometry. Tested on ParaView 5.8.1-1220-g186faf4526 using macOS 10.15.6.
# Example
1. Load attached `cell_center_noupdate.xdmf...# Summary
A `Cell Centers` filter applied to time-dependent cell data does not update for a different grid geometry. Tested on ParaView 5.8.1-1220-g186faf4526 using macOS 10.15.6.
# Example
1. Load attached `cell_center_noupdate.xdmf2` and load all data.
2. Color by `I` and advance in time. The cell geometry updates correctly and the coloring also updates correctly. That is, timestep 0 has a 3x3x1 grid and timestep 1 has a 3x3x2 grid.
3. Go to timestep 0.
4. Apply `Cell Centers` filter, choose 3D Glyphs representation. 3x3 arrows oriented along the $x$ axis should be visible (perhaps colored by `I`). This is correct.
5. Advance in time.
As a result of advancing in time, I've seen freezes, crashes, or the wrong number of misoriented vectors.
One can also go to timestep 1, apply `Cell Centers`, glyphs, etc., and observe the vectors correctly but then moving to timestep 0 causes issues (generally displaying six glyphs of various shading including NaN values).
# Notes
* My interest is in applying this to vector data; however, for simplicity scalar data is used here. The same sorts of behavior occurs for vector data.
* The "Vertex Cells" toggle in the `Cell Centers` filter appears to have no effect on this (mis)behavior.
* Avoiding the `Cell Centers` filter and explicitly creating a grid with the correct number/position of nodes does update correctly, which is what leads me to believe this is a `Cell Centers` filter issue.
CC: @ethan.stam @patchett2002
[cell_center_noupdate.xdmf2](/uploads/f9f0d9f3bcf041a71164fbdd369293f0/cell_center_noupdate.xdmf2)
Unclassified per ADC:jmc5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20219pqAnimationModel assert failure and stackoverflow while moving the timebar in...2023-12-20T12:37:58-05:00Guillaume GindrepqAnimationModel assert failure and stackoverflow while moving the timebar in "SnapToTimeSteps" in debug mode.pqAnimationModel assert failure and stackoverflow while moving the timebar in "SnapToTimeSteps" in debug mode.
It happens when no temporal dataset is loaded.
Steps to reproduce:
* Launch Paraview in Debug mode
* View -> Animation View...pqAnimationModel assert failure and stackoverflow while moving the timebar in "SnapToTimeSteps" in debug mode.
It happens when no temporal dataset is loaded.
Steps to reproduce:
* Launch Paraview in Debug mode
* View -> Animation View
* Switch to "Snap To TimeSteps" mode
* Click and drag the time bar
* Assert failure and stackoverflow
```sh
Debug Error!
Program: C:\Qt\5.15.0\msvc2019_64\bin\Qt5Cored.dll
Module: 5.15.0
File: C:\Qt\5.15.0\msvc2019_64\include\QtCore/qlist.h
Line: 579
ASSERT failure in QList<T>::operator[]: "index out of range", file C:\Qt\5.15.0\msvc2019_64\include\QtCore/qlist.h, line 579
```
The callstack points to this call > pqAnimationModel::timeFromTick(int tick) Line 281 C++https://gitlab.kitware.com/paraview/paraview/-/issues/20218Catalyst 2.0: C++ fixes2021-09-14T14:38:18-04:00Utkarsh AyachitCatalyst 2.0: C++ fixesCurrently, the Catalyst2 examples are using Conduit's C++ API. That is not ABI compatible between different C++ compilers. We should fix it as follows:
1. add a new header-only header that provides C++ wrappers for the Conduit-C API to ...Currently, the Catalyst2 examples are using Conduit's C++ API. That is not ABI compatible between different C++ compilers. We should fix it as follows:
1. add a new header-only header that provides C++ wrappers for the Conduit-C API to Catalyst API.
2. Update examples to use this new C++ API.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/202172D text size different in pvbatch and gui2022-07-09T14:58:17-04:00Utkarsh Ayachit2D text size different in pvbatch and guiSteps:
* Start paraview with `-dr` i.e `paraview -dr`
* **File > Load State** and load this script: [foo.py](/uploads/b28822f959a9e76b34a8171fe9ed1a88/foo.py) (feel free to edit script to change where the image is saved.
* This will gen...Steps:
* Start paraview with `-dr` i.e `paraview -dr`
* **File > Load State** and load this script: [foo.py](/uploads/b28822f959a9e76b34a8171fe9ed1a88/foo.py) (feel free to edit script to change where the image is saved.
* This will generate a `/tmp/image.png` as follows:
![image](/uploads/e0345db59d127adfa58d77d1123ccc2b/image.png)
* Now edit the script to change the filename and run under pvbatch as follows:
```
> pvbatch -dr foo.py
```
This generates an image as follows:
![image-batch](/uploads/0140cc266035af54346bdee62bf0b199/image-batch.png)
Notice how the text sizes are different. This is incorrect.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20216Running tests to build examples is confusing2022-08-27T18:50:04-04:00Utkarsh AyachitRunning tests to build examples is confusingTime and time again people are confused that PARAVIEW_BUILD_EXAMPLES doesn't really build the examples, but instead add tests that you're supposed to run to build those examples. We need to add some mechanism to build the examples during...Time and time again people are confused that PARAVIEW_BUILD_EXAMPLES doesn't really build the examples, but instead add tests that you're supposed to run to build those examples. We need to add some mechanism to build the examples during standard build to avoid this confusion.
cc: @ben.boeckelBen BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/20215integrate Cinema volume rendering to work with ParaView GUI and in situ2020-09-21T08:41:28-04:00Andrew Bauerintegrate Cinema volume rendering to work with ParaView GUI and in situIntegrate the Cinema volume rendering algorithms at https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4353 into ParaView properly. The use case is that users are having difficulties using volume rendering in situ because it i...Integrate the Cinema volume rendering algorithms at https://gitlab.kitware.com/paraview/paraview/-/merge_requests/4353 into ParaView properly. The use case is that users are having difficulties using volume rendering in situ because it is difficult to set up an appropriate opacity transfer function before the simulation is run. We use Cinema techniques to generate a set of opacity transfer functions that can be used in situ to generate images for post hoc exploration of the data. The options for the generating the Cinema parameters are already specified in the MR's server-manager XML file for setting in the GUI and hopefully documented fully there. If the documentation for them needs to be improved, just let me know and I will do that.
The Cinema volume rendering algorithm works as an outer loop beyond existing Cinema operations of camera angle placement but would likely be independent of Cinema operations on contour, clip and slice filters as those filters are unlikely to have volume rendering performed on them.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20214CTH Block Header reader speedup2020-10-27T21:21:01-04:00W. Alan ScottCTH Block Header reader speedupHere are diffs to speed the CTH Spy reader up in the block headers code. I believe this gives just under a 2X speedup for large CTH AMR datasets. In essence, we are going to make one big read per block header, rather than little tiny o...Here are diffs to speed the CTH Spy reader up in the block headers code. I believe this gives just under a 2X speedup for large CTH AMR datasets. In essence, we are going to make one big read per block header, rather than little tiny ones for each word.
[vtkSpyPlotBlock.cxx.patch](/uploads/911afa81875bf2586293db8052f747c0/vtkSpyPlotBlock.cxx.patch)
[vtkSpyPlotBlock.h.patch](/uploads/ebf341ce6564ac54e235a9b6d4fc33e7/vtkSpyPlotBlock.h.patch)
[vtkSpyPlotIStream.cxx.patch](/uploads/ebc299e0a6aaa446bd1b478ee9b5e94b/vtkSpyPlotIStream.cxx.patch)
[vtkSpyPlotIStream.h.patch](/uploads/16fba7d860bb39e5d91ae15e100a0d37/vtkSpyPlotIStream.h.patch)
[vtkSpyPlotUniReader.cxx.patch](/uploads/0c3fc494975ffebf42af6c67b74f7f3f/vtkSpyPlotUniReader.cxx.patch)5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/20213test2020-09-16T20:47:22-04:00W. Alan Scotttesttesttesthttps://gitlab.kitware.com/paraview/paraview/-/issues/20212vtkMaskPoints hangs in parallel, if MaximumNumberofPoints < number of processes2020-09-17T04:54:48-04:00Axel GerstenbergervtkMaskPoints hangs in parallel, if MaximumNumberofPoints < number of processesHello there,
attached script demonstrates a bug in vktMaskPoints in PV 5.6.1 / VTK.
In the script, I request 2 points and enable ProportionallyDistributeMaximumNumberOfPoints.
mpirun -np 2 pvbatch [mask_points_bug.py](/uploads/89609bb...Hello there,
attached script demonstrates a bug in vktMaskPoints in PV 5.6.1 / VTK.
In the script, I request 2 points and enable ProportionallyDistributeMaximumNumberOfPoints.
mpirun -np 2 pvbatch [mask_points_bug.py](/uploads/89609bb449f48abb94ca62fe4787fab1/mask_points_bug.py), I get 2 points as expected. But running with 3 cores makes Paraview waits forever indicating an MPI issue.
Turning off ProportionallyDistributeMaximumNumberOfPoints results in 2 points*number of processes as expected for any number of cores selected.
So I think the algorithm to ProportionallyDistributeMaximumNumberOfPoints has an issue. Could it be fixed such that I always get 2 points regardless of how many cores I use?
Best regards,
Axel