[Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN
Burns, Andrew J CTR USARMY RDECOM ARL (US)
andrew.j.burns35.ctr at mail.mil
Mon Feb 13 08:41:16 EST 2017
In Xdmf3's reader, the assignment of variables occurs in XdmfArray::populateItem. The evaluation of the function occurs in XdmfFunction "|" denotes XdmfFunction::chunk (effectively concatenate). From there it should be a bunch of XdmfArray::insert calls.
Xdmf3's source in Paraview is under Paraview/VTK/ThirdParty/xdmf3.
Andrew Burns
Software Engineer | Parsons
Phone: 410-306-0409
ARL DSRC
andrew.j.burns35.ctr at mail.mil
-----Original Message-----
From: ParaView [mailto:paraview-bounces at paraview.org] On Behalf Of Frederic Perez
Sent: Saturday, February 11, 2017 6:03 PM
To: paraview at paraview.org
Subject: Re: [Paraview] [Non-DoD Source] XDMF makes paraview crash with JOIN
All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.
----
Hi,
I have been looking closely into this problem in the past few days, and I have never been able to make the Xdmf3 reader to JOIN any HDF5 data. Neither with the JOIN() syntax nor with the "$0|$1" one. At least to populate an Attribute's DataItem. The Xdmf2 reader works until 10 elements are joined.
To go further in this investigation, could someone point me to the source code of the Xdmf3 reader, specifically where the "joining"
takes place?
Cheers
Fred
2017-02-08 23:24 GMT+01:00 Frederic Perez <fredericperez1 at gmail.com>:
> I must have done something wrong in my previous attempt with Xdmf3,
> because it no longer crashes. Note that it works even without your
> suggestion, as the JOIN() syntax works.
>
> Now the problem is that, when I click "Apply", I get the following error:
> "Failed to locate selected scalars. Will use image scalars by default
> No scalar values found for texture input!"
>
> Note that the same exact file works with Xdmf instead of Xdmf3.
>
> Fred
>
>
> 2017-02-08 22:54 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US)
> <andrew.j.burns35.ctr at mail.mil>:
>> I think that is because Xdmf3 uses different syntax for concatenation. Try using Function="$0|$1|$2|$3|$4|$5|$6|$7|$8|$9" with the Xdmf3 reader.
>>
>> -Andrew Burns
>>
>> -----Original Message-----
>> From: Frederic Perez [Caution-mailto:fredericperez1 at gmail.com]
>> Sent: Wednesday, February 08, 2017 4:50 PM
>> To: Burns, Andrew J CTR USARMY RDECOM ARL (US)
>> <andrew.j.burns35.ctr at mail.mil>
>> Cc: paraview at paraview.org
>> Subject: Re: [Non-DoD Source] [Paraview] XDMF makes paraview crash
>> with JOIN
>>
>> I tried both, but Xdmf3 makes ParaView crash even earlier (directly after opening the file) while Xdmf2 makes it crash upon "Apply".
>>
>> Fred
>>
>> 2017-02-08 22:28 GMT+01:00 Burns, Andrew J CTR USARMY RDECOM ARL (US)
>> <andrew.j.burns35.ctr at mail.mil>:
>>> Are you using the Xdmf2 or Xdmf3 reader?
>>>
>>> Andrew Burns
>>> Software Engineer | Parsons
>>> Phone: 410-306-0409
>>> ARL DSRC
>>> andrew.j.burns35.ctr at mail.mil
>>>
>>> -----Original Message-----
>>> From: ParaView [Caution-mailto:paraview-bounces at paraview.org] On
>>> Behalf Of Frederic Perez
>>> Sent: Wednesday, February 08, 2017 3:39 PM
>>> To: paraview at paraview.org
>>> Subject: [Non-DoD Source] [Paraview] XDMF makes paraview crash with
>>> JOIN
>>>
>>> All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.
>>>
>>>
>>>
>>>
>>> ----
>>>
>>> Hi all,
>>>
>>> I have successfully used the JOIN Function for the XDMF reader to concatenate the data from several HDF5 files.
>>>
>>> <Xdmf Version="3.0">
>>> <Domain>
>>> <Grid GridType="Uniform">
>>> <Topology Name="Fields topology"
>>> TopologyType="2DCoRectMesh" Dimensions="21 10"/>
>>> <Geometry Name="Fields geometry" GeometryType="ORIGIN_DXDY">
>>> <DataItem Format="XML" NumberType="float"
>>> Dimensions="2">0.0 0.0</DataItem>
>>> <DataItem Format="XML" NumberType="float"
>>> Dimensions="2">0.3 0.06</DataItem>
>>> </Geometry>
>>> <Attribute Name="By" Center="Node" AttributeType="Scalar">
>>> <DataItem ItemType="Function"
>>> Function="JOIN($0,$1,$2,$3,$4,$5,$6,$7,$8,$9)" Dimensions="21 10">
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000002/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000007/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000012/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000017/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000022/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000027/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000032/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000037/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000042/By</DataItem>
>>> <DataItem ItemType="Uniform" NumberType="Float"
>>> Precision="8" Dimensions="21"
>>> Format="HDF">mystuff.h5:/0000000047/By</DataItem>
>>> </DataItem>
>>> </Attribute>
>>> </Grid>
>>> </Domain>
>>> </Xdmf>
>>>
>>> However, this technique only works when joining a maximum of 10 different pieces of data. If I add one DataItem in the JOIN Function, ParaView crashes upon clicking "Apply".
>>>
>>> Is there a reason for this? Am I doing something wrong? Is there a workaround?
>>>
>>> Cheers
>>> Fred
>>> _______________________________________________
>>> Powered by Caution-Caution-www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> Caution-Caution-http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> Caution-Caution-http://paraview.org/Wiki/ParaView
>>>
>>> Search the list archives at:
>>> Caution-Caution-http://markmail.org/search/?q=ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> Caution-Caution-http://public.kitware.com/mailman/listinfo/paraview
_______________________________________________
Powered by Caution-www.kitware.com
Visit other Kitware open-source projects at Caution-http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at: Caution-http://paraview.org/Wiki/ParaView
Search the list archives at: Caution-http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
Caution-http://public.kitware.com/mailman/listinfo/paraview
More information about the ParaView
mailing list