Hello,
It seems that we're sort of getting the worst of both worlds right now ParaView
and Xdmf GlobalID AttributeType: Besides not being read in as "idtype", a Clip
filter removes the GlobalID attribute from the data set.
Attached is a simple XML example adapted from the Xdmf source data sets,
The XDMF in 3.6 did not have the global id attribute so it did the
unsafe thing and let filters have their way with them. It kept the
array around, but in most cases the values in the array at the end of
the pipeline were worthless.
Not that XDMF does have global ids, the clip filter (like most of
Hey Dave,
I'll definitely try this sometime early next week, but I just wanted to point
out something else, first, that may be interfering somewhere:
If you look at the output of the Xdmf reader, like you said, it has allowed
Global IDs to be set on the PointData, but they are not read in as id
Not reading in as vtkIdType is an independent bug. It is one we meant
to fix, but haven't gotten to just yet.
David E DeMarle
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x109
On Fri, Apr 23, 2010 at 4:30 PM, Eric E. Monson wrote:
> Hey Dave,
>
Hey Dave,
Unfortunately, that didn't fix it. There's something else strange going on.
The Clip filter seems to lose both the (point data) array that's set as the
Global IDs (whether int, long or idtype), plus any array that is "idtype". You
can see the latter behavior by doing Generate IDs fil
