ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:23:44-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/20330v5.9-RC1 going full screen (F11) in C/S mode crashes2024-03-07T20:23:44-05:00Jean M. Favrev5.9-RC1 going full screen (F11) in C/S mode crasheswhen connecting my desktop client to a remote ParaView server (1 node, 1 task, with EGL or with osmesa), with an empty pipeline, going to full screen (F11) crashes ParaView immediately.
the same does not happen with 5.8 compiled with th...when connecting my desktop client to a remote ParaView server (1 node, 1 task, with EGL or with osmesa), with an empty pipeline, going to full screen (F11) crashes ParaView immediately.
the same does not happen with 5.8 compiled with the same options/compilers on client and server by myself. server-side, I see:
```
( 13.978s) [pvserver ]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x7d5ba0): Could not receive tag. 1
( 13.978s) [pvserver ]vtkTCPNetworkAccessMana:297 ERR| vtkTCPNetworkAccessManager (0x6e7b40): Some error in socket processing.
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20310Save data with Extract Surface with sidesets crashes2024-03-07T20:47:17-05:00W. Alan ScottSave data with Extract Surface with sidesets crashesWe have a crash when trying to save data that is derived from the Extract Surfaces filter for sidesets. Here is how to replicate:
* Master, Linux (and Mac), builtin server.
* Open can.exo. Advanced. Turn off all blocks. Turn on Sets...We have a crash when trying to save data that is derived from the Extract Surfaces filter for sidesets. Here is how to replicate:
* Master, Linux (and Mac), builtin server.
* Open can.exo. Advanced. Turn off all blocks. Turn on Sets/ Unnamed set ID: 4. Apply.
* Extract Surface. Apply.
* File/ Save Data. Exodus data. Take defaults. OK.
This will crash with the following:
```
Stack trace:
60 0x407baa /.../paraview() [0x407baa]
59 0x7f7d3964f545 __libc_start_main + 245
58 0x40780a /.../paraview() [0x40780a]
57 0x7f7d3727e364 QCoreApplication::exec() + 132
56 0x7f7d37275ada QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 298
55 0x7f7d372cd5df QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 95
54 0x7f7d26d0745c g_main_context_iteration + 44
53 0x7f7d26d073a8 /lib64/libglib-2.0.so.0(+0x4c3a8) [0x7f7d26d073a8]
52 0x7f7d26d07049 g_main_context_dispatch + 345
51 0x7f7d0a64c450 /.../plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x86450) [0x7f7d0a64c450]
50 0x7f7d3761ba9b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 171
49 0x7f7d37642205 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 261
48 0x7f7d376408bb QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1739
47 0x7f7d372774c8 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 280
46 0x7f7d38cab9c4 QApplication::notify(QObject*, QEvent*) + 628
45 0x7f7d38ca464c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
44 0x7f7d38cfcaa1 /../bin/../lib/libQt5Widgets.so.5(+0x1b2aa1) [0x7f7d38cfcaa1]
43 0x7f7d38cfa3a2 /../bin/../lib/libQt5Widgets.so.5(+0x1b03a2) [0x7f7d38cfa3a2]
42 0x7f7d38caaf6f QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) + 447
41 0x7f7d372774c8 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 280
40 0x7f7d38cabf1f QApplication::notify(QObject*, QEvent*) + 1999
39 0x7f7d38ca464c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
38 0x7f7d38e1997b QMenu::event(QEvent*) + 171
37 0x7f7d38ce03c8 QWidget::event(QEvent*) + 472
36 0x7f7d38e17783 QMenu::mouseReleaseEvent(QMouseEvent*) + 403
35 0x7f7d38e168cf /../bin/../lib/libQt5Widgets.so.5(+0x2cc8cf) [0x7f7d38e168cf]
34 0x7f7d38e0f83c /../bin/../lib/libQt5Widgets.so.5(+0x2c583c) [0x7f7d38e0f83c]
33 0x7f7d38ca096c QAction::activate(QAction::ActionEvent) + 204
32 0x7f7d38c9e4d2 QAction::triggered(bool) + 50
31 0x7f7d372a49da QMetaObject::activate(QObject*, int, int, void**) + 1898
30 0x7f7d392f25ef pqSaveDataReaction::saveActiveData() + 1423
29 0x7f7d392f1867 pqSaveDataReaction::saveActiveData(QString const&) + 1399
28 0x7f7d366998e1 vtkSMWriterProxy::UpdatePipeline() + 113
27 0x7f7d3653cf75 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
26 0x7f7d3653df4b vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
25 0x7f7d3653e112 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
24 0x7f7d340eddbd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
23 0x7f7d340edb1e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
22 0x7f7d340ed3ed vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
21 0x7f7d340ecd89 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
20 0x7f7d2e24f24e vtkPExodusIIWriterCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 446
19 0x7f7d340ecd89 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
18 0x7f7d2e25bb01 vtkExodusIIWriterCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 1121
17 0x7f7d340ecd89 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
16 0x7f7d2e6b81c0 vtkWriterCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 1920
15 0x7f7d2b5e367c vtkWriter::Write() + 44
14 0x7f7d32133fbd vtkStreamingDemandDrivenPipeline::UpdateWholeExtent() + 333
13 0x7f7d32134d4a vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 282
12 0x7f7d32105386 vtkDemandDrivenPipeline::UpdateData(int) + 134
11 0x7f7d32133989 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 953
10 0x7f7d321063c6 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 310
9 0x7f7d32100bb1 vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 113
8 0x7f7d32103d47 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 55
7 0x7f7d32109b1e vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 62
6 0x7f7d1cd15fa6 vtkExodusIIWriter::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 310
5 0x7f7d1cd1efed vtkExodusIIWriter::WriteData() + 1197
4 0x7f7d1cf5d8f3 vtkPExodusIIWriter::CheckParameters() + 83
3 0x7f7d1cd1ea48 vtkExodusIIWriter::CheckParametersInternal(int, int) + 136
2 0x7f7d1cd1bb1a vtkExodusIIWriter::CreateDefaultMetadata() + 346
1 0x7f7d1cd131f7 vtkExodusIIWriter::CreateSetsMetadata(vtkModelMetadata*) + 1703
0 0x7f7d396633f0 /lib64/libc.so.6(+0x363f0) [0x7f7d396633f0]
```
@cory.quammen @utkarsh.ayachit Crash, thus probably needs to be fixed for 5.9.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20292Please update documentation on vtk and paraview file formats2024-03-12T21:57:37-04:00W. Alan ScottPlease update documentation on vtk and paraview file formatsPlease update the documentation on vtk file formats.
* Please update the legacy format documentation, and the new legacy format documentation.
* Please document the xml format.
* Please place these documents in the ParaView Guide. If ...Please update the documentation on vtk file formats.
* Please update the legacy format documentation, and the new legacy format documentation.
* Please document the xml format.
* Please place these documents in the ParaView Guide. If this information is outside of the ParaView ReadTheDocs, please add links in the ParaView Guide to this documentation.
* Please include all ParaView file formats, such as pvt* files.
* Please include how each file format works in the serial/ parallel environment. (Utkarsh may want to clarify.)
This task will slide to be right after the 5.9 release.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20242Disabled Filters does not give status information on OS X2024-01-02T11:18:33-05:00W. Alan ScottDisabled Filters does not give status information on OS XDisabled Filters does not give status information on OS X. This is true for Kitware nightly, as of September 30, 2020. Extractors does not work on OS X either. OS is Catalina.Disabled Filters does not give status information on OS X. This is true for Kitware nightly, as of September 30, 2020. Extractors does not work on OS X either. OS is Catalina.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20227Labels are overlapping in the Color Legend2024-03-27T12:19:16-04:00W. Alan ScottLabels are overlapping in the Color LegendLabels are overlapping in the Color Legend. Here is how to replicate:
* ParaView 5.8.0, and master, Linux, local server.
* Load vessel_out.e (Attached). All vars on. Apply.
* Last timestep.
* Paint by _disp.
* Drag the color legend...Labels are overlapping in the Color Legend. Here is how to replicate:
* ParaView 5.8.0, and master, Linux, local server.
* Load vessel_out.e (Attached). All vars on. Apply.
* Last timestep.
* Paint by _disp.
* Drag the color legend to be horizontal, under the dataset.
* Now, drag the color legend to be wider and narrower. The labels will overlap.
Attaching a screenshot.
Workaround is in the Color Legend Editor. You can turn off Automatic Label Format, and then change the format.
![Screen_Shot_2020-09-24_at_3.55.28_PM](/uploads/6f172402f63908242133a6a6ba176a3f/Screen_Shot_2020-09-24_at_3.55.28_PM.png)5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/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/20206Mesh in vtm file appears incorrect when displayed as Surface with Edges repre...2024-03-07T20:47:16-05:00Boonthanome NouanesengsyMesh in vtm file appears incorrect when displayed as Surface with Edges representation-- Update --
This issue has been resolved. Turning on and off blocks is still an issue, though. See below.
When loading a certain vtm file, and showing the mesh, it appears incorrect. Below is a screenshot. The mesh should be composed o...-- Update --
This issue has been resolved. Turning on and off blocks is still an issue, though. See below.
When loading a certain vtm file, and showing the mesh, it appears incorrect. Below is a screenshot. The mesh should be composed of rectangles.
![screenshot](/uploads/b986a3d3d7d4d0fc22d0b63f9fbdc6c0/screenshot.png)
Here is the dataset I am loading: [Material_Remap.zip](/uploads/711f9f9c01866a95c40104a7dbec0b12/Material_Remap.zip)
To reproduce:
- load the dataset
- show Surface With Edges
I am also getting strange rendering behavior when turning on and off blocks in the Multi-block Inspector.
This occurs in Paraview 5.8.1 and the current master branch version. It does not happen in Paraview 5.8.0.
@patchett2002 @cory.quammen
-- Update --
The above issue of rendering the mesh edges incorrectly seems to have been resolved. Though, I am still having rendering issues when turning blocks on and off in the Multi-block Inspector. Below is a screenshot of the same dataset when hiding the material blocks. This is using the latest master as of Sept. 15.
![hiding_blocks](/uploads/247574420b73ac6e0be2d563ca47f2d9/hiding_blocks.png)5.13 (Summer 2024)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20147Better visibility of Web features2024-03-07T20:47:16-05:00Sebastien JourdainBetter visibility of Web featuresParaView has several capabilities for exporting and visualizing data in the Web but those features are pretty well hidden for non experts.
Ideally we would like to streamline their usage. The list below try to capture the various improv...ParaView has several capabilities for exporting and visualizing data in the Web but those features are pretty well hidden for non experts.
Ideally we would like to streamline their usage. The list below try to capture the various improvements that could be made.
- For easy visualization sharing
- [ ] Export scene
- [ ] Add a HTML export format that will automatically bundle Glance with the single timestep scene.
- [x] Leave the vtkjs export as-is with its optional capability to embed a viewer
- [ ] Export time based scene
- [ ] Use the export now feature to produce web friendly time based output with checkbox that will allow you to either pick .vtkjs or .html in term of format and maybe the set of fields you actually want to export.
- For ParaViewWeb type of application
- [x] python -m visualizer/divvy/glance/lite
- [ ] Do we want to have a way to start them from the UI as a separate process?
- Documentation
- [ ] python -m usage
- [ ] HTML export
- [ ] vtk.js export + Glance online
- [ ] Time based scene export + web capability
- Help menu in ParaView
- [ ] Add entry to start Glance or get access to its location (file) ?
- [ ] Glance should be advertise as "ParaView Web base lightweight viewer"?
For time based data export some work will be required in Glance to actually provide animation and time control.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20081PartitionedDatasetCollection master bug2024-03-14T11:33:02-04:00Utkarsh AyachitPartitionedDatasetCollection master bugThis lists set of issues we need to address to make sure partitioned-dataset collection (PDC) i.e. the data type produced by IOSS reader is supported correctly.
Critical issues:
* [x] Selection support: since composite-id (CI), which we...This lists set of issues we need to address to make sure partitioned-dataset collection (PDC) i.e. the data type produced by IOSS reader is supported correctly.
Critical issues:
* [x] Selection support: since composite-id (CI), which we used for multiblock (MB) datasets, cannot be used with PDC in parallel as the structure is not same across ranks. We need to add support for "selectors" when defining selections.
* [x] Multiblock inspector needs to needs to be updated to use Data Assembly and setup display properties using data-assembly paths.
* [x] RedistributeDataSet filter load balancing (paraview/paraview#20437)
* [x] RedistributeDataSet filter and global cell ids paraview/paraview#20438
* [x] block name changes (paraview/paraview#20439)
* [x] vtkPythonSelector and subsetting (paraview/paraview#20488)
* [x] XML writers for PD/PDC don't seem to work as expected in parallel. (paraview/paraview#20641)
* [x] parallel selection issue (paraview/paraview#19395)
* [x] local rendering issue (paraview/paraview#20654)
* [ ] update chart representation to work with PDC instead of MBs (paraview/paraview#20679)
* [ ] Plot Data doesn't support Partitioned Data Set Collections #21267
* [x] hover-on tooltips don't work (paraview/paraview#20777)
* [x] partition balancer (paraview/paraview#20802)
Important issues:
* [ ] update plot selection over time to produce PDC instead of MB
* [x] Group datasets filter (paraview/paraview#20690)
* [x] Group timesteps filter (paraview/paraview#20660)
Noncritical issues:
* [ ] Saving a non distributed partitioned dataset segfault #20942
* [x] We need a new geometry filter that doesn't convert PDC to MB instead keeps it as PDC.
* [ ] We need a new mapper that replaces vtkCompositePolyDataMapper where properties are specified using data-assembly
* [ ] vtkAngularPeriodicFilter doesn't work with PDC
* [ ] ReaderAlgorithm bug: paraview/paraview#206405.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/19997Compression option when saving AVI files on windows has no effect2024-03-07T20:47:14-05:00Cory Quammencory.quammen@kitware.comCompression option when saving AVI files on windows has no effectParaView 5.8 binaries from Kitware, Windows
Steps to reproduce:
* Open ParaView
* Open the `can.ex2` example file
* File -> Save Animation...
* In the file chooser, choose the file type to be "VFW AVI" pick a file location
* In the "Sav...ParaView 5.8 binaries from Kitware, Windows
Steps to reproduce:
* Open ParaView
* Open the `can.ex2` example file
* File -> Save Animation...
* In the file chooser, choose the file type to be "VFW AVI" pick a file location
* In the "Save Animation Options", set **Quality** to "0 (worst quality, smaller file)". Click OK.
* Now save the animation again to a different file, but this time set **Quality** to "2 (best quality, larger file)". Click OK.
The exported AVIs are exactly the same size and have the same MD5 sum.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19956Selection tracing not working correctly with certain filters2024-03-07T20:47:14-05:00Mathieu Westphal (Kitware)Selection tracing not working correctly with certain filtersPlotSelectionOverTime and FFTOfSelectionOverTime are failing to generate a trace line when they are created if a selection exists.
If no selection exists, the trace is as follows: `plotSelectionOverTime1 = PlotSelectionOverTime(Input=str...PlotSelectionOverTime and FFTOfSelectionOverTime are failing to generate a trace line when they are created if a selection exists.
If no selection exists, the trace is as follows: `plotSelectionOverTime1 = PlotSelectionOverTime(Input=stress00, Selection=None)`, so, imo, the Selection being not traced correctly yet prevent the creation of the filter.
Steps to reproduce :
* Wavelet, Apply
* Select cells on
* Tools -> Start trace -> incremental
* PlotSelectionOverTime
* no line for creating the filter.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19773Plot over line is failing on Cray2024-03-07T20:47:13-05:00W. Alan ScottPlot over line is failing on CrayPlot over line is failing on cray clusters. This is specific to Mutrino. Here is how to replicate:
* 5.8.0, remote server (1 rank), Cray, Linux.
* Note that 5.7.0 appears to work correctly. Reason unknown.
* Open disk_out_ref.exo. ...Plot over line is failing on cray clusters. This is specific to Mutrino. Here is how to replicate:
* 5.8.0, remote server (1 rank), Cray, Linux.
* Note that 5.7.0 appears to work correctly. Reason unknown.
* Open disk_out_ref.exo. All vars on. Apply.
* Plot over line. Apply.
See attached image.![Capture](/uploads/76ad557b215fc035d551a6bfd246af13/Capture.PNG)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19771Ray caster and path tracer improvements2024-03-07T20:47:13-05:00Andrew BauerRay caster and path tracer improvementsThe GUI should be cleaned up for ray caster and path tracer options. Items include
1) it would be great to add in more materials to the default list of materials. I was able to find some stuff on discourse that I liked and I'm using the...The GUI should be cleaned up for ray caster and path tracer options. Items include
1) it would be great to add in more materials to the default list of materials. I was able to find some stuff on discourse that I liked and I'm using the materials from those instead of the default ones in PV 5.8.
2) it would be nice if the Ray Tracing section in the Properties panel could be moved to be next to the Ray Traced Rendering section (or maybe they can be combined somehow though that seems unlikely)
3) the options need to be better linked in the GUI to what they can affect. for example, I think the OptiX pathtracer doesn't have the Denoise capability but if I have Samples Per Pixel set to 4 or greater then the Denoise option becomes available. Similarly I think Shadows is only relevant for OSPRay raycaster but it is always available. Another one is that materials seems to only be a valid option for the pathtracers and not OSPRay raycaster. I think this would go a long way towards making the ray tracing functionality in PV much more user friendly.
4) if a material is set for a filter output then the color legend should by default be not visible. Steps to reproduce the annoying behavior in 5.8 is:
a. Create a Wavelet source and change to Surface representation
b. Enable Ray Tracing then set Back End to OSPRay pathtracer
c. Make the Color Legend not visible
d. Hide the Wavelet output and then show the Wavelet output again -- the color legend is now visible again.
It looks like this is a general bug that's been fixed in master but it's probably worthwhile to check that reasonable there's reasonable behavior for ray tracing as well.
5) what functionality works in parallel? I didn't try anything in parallel yet but didn't see anything in the upcoming changes to the documentation specifying what worked and didn't work in parallel. I know at one time this was only serial functionality and maybe that's not true anymore.
6) It may be useful to have more than a single JSON material file. This causes issues with state files if there are multiple materials loaded.5.13 (Summer 2024)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/19689resampleToImage filter sets color legend min wrong2024-03-07T20:47:12-05:00W. Alan ScottresampleToImage filter sets color legend min wrongThe ResampleToImage filter sets the min wrong on the color legend. The Rescale to Data Range fails, as does Rescale to Data Range over All Timesteps. The only workaround is to use Rescale to Custom Data Range.
Here is how to replicate...The ResampleToImage filter sets the min wrong on the color legend. The Rescale to Data Range fails, as does Rescale to Data Range over All Timesteps. The only workaround is to use Rescale to Custom Data Range.
Here is how to replicate:
* 5.8.0, Linux, builtin server.
* disk_out_ref.exo. All vars on. Apply.
* Color by Temp. Note the min and max. It is about 290 to 910.
* Volume Render. This is what it should look like.
* Resampe to Image. Apply.
Notice that the color legend is now 0 to 910. This is a bug.
Because this makes huge data difficult, and is confusing, marking as required.
@patchett2002 @boonth5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19649Select cells through in parallel does not trace correctly2024-03-07T20:47:12-05:00W. Alan ScottSelect cells through in parallel does not trace correctlySelect cells through in parallel does not trace correctly. Here is how to replicate:
* Start with ParaView full screen.
* I believe has to be in parallel. 64 ranks, Linux, 5.8.0-RC2.
* Start Trace.
* Open Watney's sparc-wall.exo.144.*....Select cells through in parallel does not trace correctly. Here is how to replicate:
* Start with ParaView full screen.
* I believe has to be in parallel. 64 ranks, Linux, 5.8.0-RC2.
* Start Trace.
* Open Watney's sparc-wall.exo.144.*. All vars on. Apply.
* So that we have more control, letz zoom in. Adjust Camera/ Zoom In 4 times.
* Surface with edges.
* Select Cells Through. Now, what I want to do is select about 6 cells in the blue (cone) region, abutting against the green block. I will add a screenshot.
* Extract Selection. Apply.
* Stop Trace. Save as a macro.
* Now, hover cells on. For me, the upper left cell is 14846.
* Reset Session.
* Run the macro.
* Frequently, nothing shows up. Sometimes, the wrong cells show up. As I just wrote up this bug report, nothing shows up.
This is a bug.5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19611Catalyst live tests have gone missing2024-03-07T20:47:12-05:00Utkarsh AyachitCatalyst live tests have gone missingSeveral catalyst live tests e.g. CatalystLivePause, CatalystLiveSetBreakpoint, etc. are no longer being run.
Suspect they were lost during modularization refactor. We need to enable those.
cc: @ben.boeckel @cory.quammenSeveral catalyst live tests e.g. CatalystLivePause, CatalystLiveSetBreakpoint, etc. are no longer being run.
Suspect they were lost during modularization refactor. We need to enable those.
cc: @ben.boeckel @cory.quammen5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19469SSH connection - add option to keep terminal windows open2024-03-07T20:47:11-05:00W. Alan ScottSSH connection - add option to keep terminal windows openWhen debugging the code in a default_servers.pvsc, using the new embedded ssh code, please add the option to keep the windows or OS X terminal open. Error messages are happening in these windows, and then the windows are going away! Th...When debugging the code in a default_servers.pvsc, using the new embedded ssh code, please add the option to keep the windows or OS X terminal open. Error messages are happening in these windows, and then the windows are going away! This makes it impossible to debug. Optionally, if this is hard, add the ability to write a file with this information, default off.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19455Smarter Python traces2024-03-07T20:47:11-05:00W. Alan ScottSmarter Python tracesI worked with a user today trying to get scripts ready to process hundreds of large exodus runs. This was a time consuming and detailed endeavor. I would like to propose the following:
Lets add code, commented out, to all Python scrip...I worked with a user today trying to get scripts ready to process hundreds of large exodus runs. This was a time consuming and detailed endeavor. I would like to propose the following:
Lets add code, commented out, to all Python scripts that trivially allow the Python to be controled through parameters. In other words, something like this:
```
# The following code can be uncommented, and used with parameters.
# You would then use this code as follows to batch process lots of directories:
# ../pvbatch thisBatchFile directoryIn1 fileIn1 directoryOut1 fileOut1
# ../pvbatch thisBatchFile directoryIn2 fileIn2 directoryOut2 fileOut2
# ../pvbatch thisBatchFile directoryIn3 fileIn3 directoryOut3 fileOut3
# Uncomment the following lines to use parametres, and comment out the exodusReader0.
# inputDirectoryName = argument[1]
# inputFileName = argument[2]
# outputDirectoryName = argument[3]
# outputFileName = argument[4]
# exodusReader0 = ExodusReader([inputDirectoryName+inputFileName+'.e.1234.0000'])
exodusReader0 = ExodusReader('/home/alan/data/pizzaInput/myfile.e.1234.0000'])
do really important and complex stuff
# SaveScreenshot(outputDirectoryName+outputFileName+'.png')
SaveScreenshot(/home/alan/data/pizzaOutput/myfile.png')
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19298SILO files not reading in time correctly2024-03-07T20:47:09-05:00W. Alan ScottSILO files not reading in time correctlyWe have a SILO dataset that is not loading time correctly. This works correctly with VisIt (3.0.1) and with EnSight. Here is how to replicate.
* 5.7.0 RC2, builtin server, Linux
* Load dataset EM_v5b_264. There will be 5 files to thi...We have a SILO dataset that is not loading time correctly. This works correctly with VisIt (3.0.1) and with EnSight. Here is how to replicate.
* 5.7.0 RC2, builtin server, Linux
* Load dataset EM_v5b_264. There will be 5 files to this dataset, you load all 5. There are also lots of other files in this directory, they may be important also. Note that ParaView is incorrectly not identifying this dataset as Silo. Thus, you have to choose Files of type: All Files (*). Then, chose EM_v5b_264. Chose VisItSiloReader. OK. Don't turn any variables on, we are good to go. Apply.
* Move forward 1 timestep.
The time on this timestep is incorrect. It shows as 1 (both in the time controls, on the information tab and annotate time). It should be time of 503.453.
This is a bug.
Dataset is from an external customer. This customer will get dataset to Kitware. Note that customer can pass dataset to me, and I can then pass it to Kitware.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19170document all of the block and id names2024-03-07T20:47:07-05:00W. Alan Scottdocument all of the block and id namesPlease add documentation somewhere that explains the different cell, point and block ids. Include the idiosyncrasies for different readers, especially Exodus and CGNS. At least cover cell and point id, globalnodeid/globalelementid, ped...Please add documentation somewhere that explains the different cell, point and block ids. Include the idiosyncrasies for different readers, especially Exodus and CGNS. At least cover cell and point id, globalnodeid/globalelementid, pedegrenodeid/pedegreelementid, ids, blocks (from the files), blocks (internal to ParaView), etc.
This is a Watney bug.5.13 (Summer 2024)