[vtkusers] Fwd: XDMF and hyperslabs

victor sv victorsv at gmail.com
Thu Aug 27 05:04:20 EDT 2015 

Ok, thanks David,

I think that versioning number is not the only problem, I know that XDMF is
under active development and the last commit of (git://
public.kitware.com/Xdmf2.git) repository is:

commit 06d2b52b133772a8c3368135a8d31c0de3dc0a3c
Author: Kenneth Leiter <kenneth.leiter at arl.army.mil>
Date:   Mon Jul 21 11:44:59 2014 -0400

This is my last questin, there isn't any new feature or commit since 2014?

Thanks again for your patience, you are very kind.
Víctor.

2015-08-26 16:55 GMT+02:00 David E DeMarle <dave.demarle at kitware.com>:

> That is in fact the xdmf 3 repository.
>
> The lib's versioning scheme and ParaView's versioning scheme have
> disagreed since xdmf 1.
>
> lib: 1  1.5 2
> pv: 1  2.0 3
>
> Sorry for the confusion I introduced it back in xdmf2 as a workaround for
> technical issues with the old CVS repository.
>
>
>
>
>
>
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
> On Wed, Aug 26, 2015 at 6:31 AM, victor sv <victorsv at gmail.com> wrote:
>
>> Hi David,
>>
>> it seems that if I go to the "Version 3" (
>> http://www.xdmf.org/index.php/Version_3) section of the XDMF web page it
>> only has a link to XDMF version 2 git repository (git://
>> public.kitware.com/Xdmf2.git).
>>
>> I cannot find a public repo for XDMF v3, could you send me a link to the
>> public git repo for XDMF v3?
>>
>> Thanks again,
>> Víctor.
>>
>> 2015-08-26 5:38 GMT+02:00 David E DeMarle <dave.demarle at kitware.com>:
>>
>>> Hi Victor,
>>>
>>> ARL and Kitware are the primary developers of Xdmf, but everyone is
>>> invited to contribute  to the project.
>>>
>>> Yes xdmf3 has not yet replaced xdmf2 within ParaView. The binaries for
>>> the next ParaView release (the release candidate should have it) will have
>>> both turned on. Over the next few releases xdmf2 will be deprecated and
>>> then removed from ParaView.
>>>
>>> xdmf itself can be built apart from VTK. On the xdmf wiki there are
>>> links to the repositories that you can check out to build it standalone.
>>> What you see in VTK/Thirdparty is a clone of parts of that standalone
>>> library. The VTK interface to it is in VTK/IO.
>>>
>>> hth
>>>
>>>
>>>
>>> David E DeMarle
>>> Kitware, Inc.
>>> R&D Engineer
>>> 21 Corporate Drive
>>> Clifton Park, NY 12065-8662
>>> Phone: 518-881-4909
>>>
>>> On Wed, Aug 19, 2015 at 12:03 PM, victor sv <victorsv at gmail.com> wrote:
>>>
>>>> Thanks Dan,
>>>>
>>>> it was an error in the XDMF file and it seems that is a valid format
>>>> for Xdmf2. I comment the error between lines below.
>>>>
>>>> In a post that I sent to XDMF mailing list they say me that Xdmf3 is
>>>> not by default in Paraview and I have to compile the sources with the
>>>> correct options enabling Xdmf3.
>>>>
>>>> My problem with the versions is that the XDMF documentation and library
>>>> versions is not "synchronized". It seems that Kitware is who is developing
>>>> Xdmf3, but there isn't an stand-alone library, it only exists inside VTK
>>>> project. I'm right?
>>>>
>>>> Thanks again,
>>>> Víctor.
>>>>
>>>>
>>>> 2015-08-18 4:09 GMT+02:00 Dan Lipsa <dan.lipsa at kitware.com>:
>>>>
>>>>> There are (advanced) options to enable either xdmf2 or xdmf3 in VTK.
>>>>>
>>>>> On Fri, Aug 14, 2015 at 6:27 AM, victor sv <victorsv at gmail.com> wrote:
>>>>>
>>>>>>
>>>>>> ---------- Forwarded message ----------
>>>>>> From: victor sv <victorsv at gmail.com>
>>>>>> Date: 2015-08-14 12:25 GMT+02:00
>>>>>> Subject: XDMF and hyperslabs
>>>>>> To: vtkdev <vtk-developers at vtk.org>, vtk-users at vtk.org, "
>>>>>> paraview at paraview.org" <paraview at paraview.org>
>>>>>>
>>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> I'm trying to create and visualize an XDMF/HDF5 file containing a
>>>>>> partitioned mesh using hyperslabs.
>>>>>>
>>>>>> Is this supported by Paraview/VTK ??
>>>>>>
>>>>>> The HDF5 (solution1.h5) looks as follows:
>>>>>>
>>>>>> GROUP "/" {
>>>>>>    GROUP "Grid" {
>>>>>>       DATASET "Connectivities" {
>>>>>>          DATATYPE  H5T_STD_I32BE
>>>>>>          DATASPACE  SIMPLE { ( 18 ) / ( 18 ) }
>>>>>>          DATA {
>>>>>>          (0): 0, 1, 2, 3, 2, 1, 4, 5, 6, 7, 6, 5, 6, 7, 8, 9, 8, 7
>>>>>>          }
>>>>>>       }
>>>>>>       DATASET "Coordinates" {
>>>>>>          DATATYPE  H5T_IEEE_F64BE
>>>>>>          DATASPACE  SIMPLE { ( 20 ) / ( 20 ) }
>>>>>>          DATA {
>>>>>>          (0): 0, 0, 1, 0, 0, 0.5, 1, 0.5, 0, 0.5, 1, 0.5, 0, 1, 1, 1,
>>>>>> 0, 1.5,
>>>>>>          (18): 1, 1.5
>>>>>>          }
>>>>>>       }
>>>>>>       DATASET "Solution" {
>>>>>>          DATATYPE  H5T_IEEE_F64BE
>>>>>>          DATASPACE  SIMPLE { ( 10 ) / ( 10 ) }
>>>>>>          DATA {
>>>>>>          (0): 0, 0, 0, 0, 1, 1, 1, 1, 1, 1
>>>>>>          }
>>>>>>       }
>>>>>>    }
>>>>>> }
>>>>>>
>>>>>> And the XDMF file to represent  a 2-triangle (4 points) piece of the
>>>>>> full mesh is:
>>>>>>
>>>>>> <?xml version="1.0" encoding="utf-8"?>
>>>>>> <Xdmf xmlns:xi="http://www.w3.org/2001/XInclude">
>>>>>>   <Domain>
>>>>>>     <Grid CollectionType="Spatial" GridType="Collection" Name="Mesh">
>>>>>>       <Grid Name="Grid1">
>>>>>>         <Topology Dimensions="6" Type="Triangle">
>>>>>>           <DataItem ItemType="HyperSlab" Dimensions="6"
>>>>>> Type="HyperSlab">
>>>>>>
>>>>>
>>>> The problem is here, the correct dimensions are 2 (triangles) and not 6
>>>> (integers)
>>>>
>>>>             <DataItem Dimensions="3 1" Format="XML"> 0 1 6 </DataItem>
>>>>>>             <DataItem DataType="Int" Dimensions="18" Format="HDF"
>>>>>> Precision="4">solution1.h5:Grid/Connectivities</DataItem>
>>>>>>           </DataItem>
>>>>>>         </Topology>
>>>>>>         <Geometry GeometryType="XY">
>>>>>>           <DataItem ItemType="HyperSlab" Dimensions="8"
>>>>>> Type="HyperSlab">
>>>>>>             <DataItem Dimensions="3 1" Format="XML"> 0 1 8 </DataItem>
>>>>>>             <DataItem DataType="Float" Dimensions="20" Format="HDF"
>>>>>> Precision="8">solution1.h5:Grid/Coordinates</DataItem>
>>>>>>           </DataItem>
>>>>>>         </Geometry>
>>>>>>       </Grid>
>>>>>>     </Grid>
>>>>>>   </Domain>
>>>>>> </Xdmf>
>>>>>>
>>>>>> I'm trying to use the syntax explained at the XDMF webpage (
>>>>>> http://www.xdmf.org/index.php/XDMF_Model_and_Format ), but I'm
>>>>>> feeling confused about the version of the documentation and current version
>>>>>> of XDMF library included in VTK library.
>>>>>>
>>>>>> Can anyone give me some info about this?
>>>>>> It is XDMFv3 already public ?
>>>>>>
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Víctor.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Powered by www.kitware.com
>>>>>>
>>>>>> Visit other Kitware open-source projects at
>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>
>>>>>> Please keep messages on-topic and check the VTK FAQ at:
>>>>>> http://www.vtk.org/Wiki/VTK_FAQ
>>>>>>
>>>>>> Search the list archives at: http://markmail.org/search/?q=vtkusers
>>>>>>
>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>> http://public.kitware.com/mailman/listinfo/vtkusers
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the VTK FAQ at:
>>>> http://www.vtk.org/Wiki/VTK_FAQ
>>>>
>>>> Search the list archives at: http://markmail.org/search/?q=vtkusers
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://public.kitware.com/mailman/listinfo/vtkusers
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20150827/b704ba94/attachment.html>

More information about the vtkusers mailing list