[Paraview-developers] [Non-DoD Source] Bug in the xdmf Reader 3

Burns, Andrew J CTR USARMY RDECOM ARL (US) andrew.j.burns35.ctr at mail.mil
Thu Jun 30 09:05:45 EDT 2016


In this case, it looks like an issue with the "clean to grid" filter. Once the grid is initially loaded, the data is outside of the Xdmf3 reader. I'm not particularly familiar with that functionality, so I can't say specifically what is wrong.

Andrew Burns
Lockheed Martin
Software Engineer
410-306-0409
ARL DSRC
andrew.j.burns35.ctr at mail.mil

-----Original Message-----
From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Felipe Bordeu
Sent: Thursday, June 30, 2016 5:50 AM
To: ParaView Developers <paraview-developers at paraview.org>
Subject: Re: [Paraview-developers] [Non-DoD Source] Bug in the xdmf Reader 3

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. 


________________________________



ok, lest work with your file. if you look at the information tab, for the first timestep you get :
number of cells 1
number of points : 8
bounds: Z range 0 to 1 (delta: 1 )

for the second timestep you get
number of cells 2
number of points : 12
bounds: Z range 1 to 5 (delta: 4)


and if you apply a "clean to grid" filter in the information tab (of the clean to grid filter o of course) you get:

for the first timestep you get :
number of cells 1
number of points : 8
bounds: Z range 0 to 1 (delta: 1 )

for the second timestep you get 
number of cells 1
number of points : 8
bounds: Z range 1 to 3 (delta: 2)



this is wrong.

Felipe




2016-06-29 17:01 GMT+02:00 Burns, Andrew J CTR USARMY RDECOM ARL (US) <andrew.j.burns35.ctr at mail.mil < Caution-mailto:andrew.j.burns35.ctr at mail.mil > >:


	Xdmf's latest version prefers having each grid declare its time value separately.
	
	<?xml version="1.0" encoding="utf-8"?>
	<Xdmf xmlns:xi="Caution-http://www.w3.org/2001/XInclude < Caution-http://www.w3.org/2001/XInclude > " Version="2.92">
	<Domain>
	<Grid Name="Grid_T" GridType="Collection" CollectionType="Temporal"  >
	    <Grid Name="Grid_1">
	    <Time Value="1"/>
	    <Geometry Type="ORIGIN_DXDYDZ">
	      <DataItem DataType="Float" Dimensions="3" Format="XML" Precision="8">0 0 0</DataItem>
	      <DataItem DataType="Float" Dimensions="3" Format="XML" Precision="8">1. 1. 1.</DataItem>
	    </Geometry>
	    <Topology Dimensions="2 2 2" Type="3DCoRectMesh"/>
	    </Grid>
	    <Grid Name="Grid_2">
	    <Time Value="2"/>
	    <Geometry Type="ORIGIN_DXDYDZ">
	      <DataItem DataType="Float" Dimensions="3" Format="XML" Precision="8">1. 1. 1.</DataItem>
	      <DataItem DataType="Float" Dimensions="3" Format="XML" Precision="8">2. 2. 2.</DataItem>
	    </Geometry>
	    <Topology Dimensions="3 2 2" Type="3DCoRectMesh"/>
	    </Grid>
	    </Grid>
	  </Domain>
	</Xdmf>
	
	It looks to me that both grids are the same "size," one unit in each dimension. The difference is that in the second grid the first dimension is divided into three subidivisions instead of the two subdivisions in the first one. This results in cells that are 0.5x.x0.5x0.5 in the first grid and 0.33x0.5x0.5 in the second grid.
	
	If you aren't filling the cells with an attribute both grids would look the same.
	
	-Andrew Burns
	

	-----Original Message-----
	From: Paraview-developers [Caution-mailto:paraview-developers-bounces at paraview.org < Caution-mailto:paraview-developers-bounces at paraview.org > ] On Behalf Of Felipe Bordeu
	Sent: Wednesday, June 29, 2016 10:51 AM
	To: ParaView Developers <paraview-developers at paraview.org < Caution-mailto:paraview-developers at paraview.org > >
	Subject: [Non-DoD Source] [Paraview-developers] Bug in the xdmf Reader 3
	
	Hi,
	
	I'm working with 3DCoRectMesh meshes. the attached file contains 2 time steps with two 3DCoRectMesh with different topologies. Paraview only update the UpdateExtent for the first time step, making the solution of the second timestep croped.
	
	Any ideas for a fast workaround?
	I tried clean to grid but does not work.
	
	In the information tab you can see the total number of element and point is correct but after the clean to grid filter only half of the mesh is treated.
	
	using latest ParaView from web (5.1.0 64-bit windows ) Felipe
	
	
	
	




More information about the Paraview-developers mailing list