ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-11-10T21:54:07-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/20276RedistributeDataSet generate a strange result with polydata2020-11-10T21:54:07-05:00Mathieu Westphal (Kitware)RedistributeDataSet generate a strange result with polydataUsing cow.vtp, here is the result for RedisitributeDataSet:
![image](/uploads/61b14f01ad21be2daa7b19334d783326/image.png)
Here is the D3 result:
![image](/uploads/6c225ce5cc9a986c1e8e6f0ae2de6f7a/image.png)Using cow.vtp, here is the result for RedisitributeDataSet:
![image](/uploads/61b14f01ad21be2daa7b19334d783326/image.png)
Here is the D3 result:
![image](/uploads/6c225ce5cc9a986c1e8e6f0ae2de6f7a/image.png)5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20271Extracts: set start and end time not usable in xml test, have the same pqeven...2020-10-13T18:52:21-04:00Ethan StamExtracts: set start and end time not usable in xml test, have the same pqevent calls@utkarsh.ayachit @cory.quammen
I can't use Set Start Time and Set End Time from an Extract's property in a recorded xml test. I tried looking for options, but can't find anything to differentiate between the two in a test.
To reproduc...@utkarsh.ayachit @cory.quammen
I can't use Set Start Time and Set End Time from an Extract's property in a recorded xml test. I tried looking for options, but can't find anything to differentiate between the two in a test.
To reproduce:
1. Start ParaView and create an image extract generator
2. Start test recording: Tools -> Record test
3. Check box for "Use start time", and set its start time
4. Check box for "Use end time", and set its end time
5. Stop record test
Resulting xml:
```xml
<?xml version="1.0" ?>
<pqevents>
<pqevent object="pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/PropertiesFrame/ProxyPanel/Trigger/ProxySelectionWidget/frame/ChosenProxyWidget/CheckableProperty/CheckBox" command="set_boolean" arguments="true" />
<pqevent object="pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/PropertiesFrame/ProxyPanel/Trigger/ProxySelectionWidget/frame/ChosenProxyWidget/CheckableProperty/1pqIntVectorPropertyWidget0/LineEdit0" command="set_string" arguments="1" />
<pqevent object="pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/PropertiesFrame/ProxyPanel/Trigger/ProxySelectionWidget/frame/ChosenProxyWidget/CheckableProperty/CheckBox" command="set_boolean" arguments="true" />
<pqevent object="pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/PropertiesFrame/ProxyPanel/Trigger/ProxySelectionWidget/frame/ChosenProxyWidget/CheckableProperty/1pqIntVectorPropertyWidget0/LineEdit0" command="set_string" arguments="2" />
</pqevents>
```
Video:
![compressed](/uploads/3de3d1b87d2882e39d5104b3aee30b56/compressed.gif)5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20268Clean up paraview.org with regards to ParaView Guide2021-07-07T13:00:04-04:00W. Alan ScottClean up paraview.org with regards to ParaView GuideIn the paraview.org website, when you go Resources/ ParaView guide, you get to https://www.paraview.org/paraview-guide/. In this day of online documentation, please have this page go directly to the online ParaView guide, located here: ...In the paraview.org website, when you go Resources/ ParaView guide, you get to https://www.paraview.org/paraview-guide/. In this day of online documentation, please have this page go directly to the online ParaView guide, located here: https://docs.paraview.org/en/latest/. Further, let's get rid of the paper book version of the ParaView Guide. The current one is ParaView 4.3. If no one has complained in the last half decade, no one is reading it.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/20267Usage logger2021-01-21T19:45:58-05:00W. Alan ScottUsage loggerPlease add a usage logger in ParaView. Due to Apple Security Hardening, this is becoming problematic within Catalina. Here is what is desired:
* Please add the ability for ParaView to look for a known file, such as logging-commands.txt...Please add a usage logger in ParaView. Due to Apple Security Hardening, this is becoming problematic within Catalina. Here is what is desired:
* Please add the ability for ParaView to look for a known file, such as logging-commands.txt. If this file exists, please read it and parse it. Within this file should be the name of a known website. Also, within this file should be a template for a write to a website.
* When ParaView is started, create a 'curl' command, to this known website, with information passed to the website as per the template.
an example template could be: user='${USER}'&platform='${LOG_PLATFORM}'&date='${DATE}'&product='${LOG_PRODUCT}'&version='${PARAVIEW_VERSION} Obviously, LOG_PLATFORM would have to be read from the file. USER and LOG_PRODUCT and PARAVIEW_VERSION could either come internally or be read in from the file. DATE would have to be internal, since it changes.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20260Please move the Time Inspector2021-12-22T14:58:18-05:00W. Alan ScottPlease move the Time InspectorPlease move the Time Inspector to be at the BOTTOM of the renderview window, not on the right. This is a wide, short set of widgets, they don't belong to the side.Please move the Time Inspector to be at the BOTTOM of the renderview window, not on the right. This is a wide, short set of widgets, they don't belong to the side.5.11 (Spring 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20256Isosurface is incorrect for client-server connection2020-11-10T21:45:19-05:00Boonthanome NouanesengsyIsosurface is incorrect for client-server connectionFor a particular dataset, the isosurfaces look incorrect, and are very different from ones generated locally. The contours made locally look correct. This is with the current master of Paraview, as of Oct 5th. See screenshots below.
Whe...For a particular dataset, the isosurfaces look incorrect, and are very different from ones generated locally. The contours made locally look correct. This is with the current master of Paraview, as of Oct 5th. See screenshots below.
When creating the contour (both remotely and locally), an error appears:
```
ERROR: In /usr/projects/paraview/boonth/ParaView-git/VTK/Common/DataModel/vtkImageData.cxx, line 1280
vtkImageData (0x23bc410): No Scalar Field has been specified - assuming 1 component!
```
The dataset used: [overpressure.tar.gz](/uploads/4565c540846b45250ee48d74bc4f87fc/overpressure.tar.gz)
How to reproduce: use a client-server connection, load the data. Use a Contour filter, and generate 20 iso values from 0 to 1,000 evenly. Then generate contours.
Contours generated with client-server (below)
![pv-master-remote](/uploads/a522a1a5be8809986a7014a8b7520c6c/pv-master-remote.png)
Contours generated with a local Paraview client (below)
![pv-master-local](/uploads/cc33f4a5a0a3ef8d0590abfb7e1507a5/pv-master-local.png)
@patchett2002 @cory.quammen5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20255Add option to MergeBlocks to only merge pieces2020-10-20T12:34:25-04:00Boonthanome NouanesengsyAdd option to MergeBlocks to only merge piecesCurrently the MergeBlocks filter will merge all pieces and blocks in a Multiblock dataset. For Flag users, they generally do not want to merge blocks, but merge together pieces that make up a block. Otherwise, they will lose information ...Currently the MergeBlocks filter will merge all pieces and blocks in a Multiblock dataset. For Flag users, they generally do not want to merge blocks, but merge together pieces that make up a block. Otherwise, they will lose information between blocks (see block structure image below). Please add an option to MergeBlocks to only merge multipiece datasets.
![blocks](/uploads/8591b3150c6ac8b4dbc9bc3355955d4d/blocks.png)
@patchett2002 @cory.quammen @utkarsh.ayachit5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20251Multi-block with transparency causes disappearing blocks2020-12-02T17:53:33-05:00Aron HelserMulti-block with transparency causes disappearing blocksIf you set an opacity < 1 with the multi-block inspector on the second or later block, it will disappear after interaction.
Steps to reproduce:
- create a Sphere, create a Superquadritic
- Select both, use as input to a Group Datasets f...If you set an opacity < 1 with the multi-block inspector on the second or later block, it will disappear after interaction.
Steps to reproduce:
- create a Sphere, create a Superquadritic
- Select both, use as input to a Group Datasets filter
- In the multiblock inspector, double-click the opacity of the second block, and set to 0.8
- The initial display still shows the second block as fully opaque.
- Rotate the view, and the second block disappears completely.
Note if you set an opacity < 1 on the first block by itself, the display appears correct. If both blocks have opacity < 1, they both disappear.
Selecting the block still shows the wireframe selection.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://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/20239XML Readers Recognize GlobalIDs as VTKIDType Automatically2020-10-06T17:29:12-04:00John PatchettXML Readers Recognize GlobalIDs as VTKIDType AutomaticallyOlder XML writers don't write IDType=1 which causes a misrepresentation of the GlobalID as not a special global ID array. The readers should recognize. @utkarsh.ayachit @boonthOlder XML writers don't write IDType=1 which causes a misrepresentation of the GlobalID as not a special global ID array. The readers should recognize. @utkarsh.ayachit @boonth5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://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/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/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/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/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/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/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/20201Cleanup extracts output directory2020-10-28T19:45:27-04:00Utkarsh AyachitCleanup extracts output directoryCurrently, in master, i've added $ENV{VAR} as a mehcanism to runtime override output directory. Let's remove that since it will conflict with this [proposal](https://discourse.paraview.org/t/standardizing-string-substitutions/4719/11).Currently, in master, i've added $ENV{VAR} as a mehcanism to runtime override output directory. Let's remove that since it will conflict with this [proposal](https://discourse.paraview.org/t/standardizing-string-substitutions/4719/11).5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachit