Re: [Paraview] [Non-DoD Source] XDMF crash

2017-01-25 Thread Burns, Andrew J CTR USARMY RDECOM ARL (US)
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Daniel Frisch Sent: Wednesday, January 25, 2017 1:44 PM To: paraview@paraview.org Subject: Re: [Paraview] [Non-DoD Source] XDMF crash All active links contained in this email were disabled. Please verify the identity of the sender, an

Re: [Paraview] [Non-DoD Source] XDMF crash

2017-01-25 Thread Daniel Frisch
iew.org] On Behalf Of Daniel > Frisch > Sent: Wednesday, January 25, 2017 1:14 PM > To: paraview@paraview.org > Subject: Re: [Paraview] [Non-DoD Source] XDMF crash > > All active links contained in this email were disabled. Please verify the > identity of the sender, and confirm

Re: [Paraview] [Non-DoD Source] XDMF crash

2017-01-25 Thread Burns, Andrew J CTR USARMY RDECOM ARL (US)
w@paraview.org Subject: Re: [Paraview] [Non-DoD Source] XDMF crash 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 th

Re: [Paraview] [Non-DoD Source] XDMF crash

2017-01-25 Thread Daniel Frisch
Hello Mr. Burns, thank you very much for your helpful answer. I changed the XDMF file. But now I have another question. Now I have problems with GridType="SubSet". ParaView doesn't view the second and third timestep. Their grids are referenced as SubSet from the first grid. This is the reason

Re: [Paraview] [Non-DoD Source] XDMF crash

2017-01-25 Thread Burns, Andrew J CTR USARMY RDECOM ARL (US)
This is because the Xdmf3 reader does not support the Hyperslab Timetype. One Time item per grid is the preferred method. Andrew Burns Software Engineer | SAIC Phone: 410-306-0409 ARL DSRC andrew.j.burns35@mail.mil -Original Message- From: ParaView