I did file it: 9376. Bug 9252 appears related. David E DeMarle Kitware, Inc. R&D Engineer 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-371-3971 x109
On Mon, Nov 16, 2009 at 12:37 PM, David E DeMarle <[email protected]> wrote: > Paraview generally treats raw binary files as completely regular data. > You do not need an indexing/header file in this case. When you > instantiate the raw reader it asks the user what the extent, spacing, > data type, endianness etc are. > > Xdmf can index into binary files generically. However this capability > was added to the XDMF library after paraview 3.6, and I do not know if > even the PV interface to XDMF in the development head allows that. > > David E DeMarle > Kitware, Inc. > R&D Engineer > 28 Corporate Drive > Clifton Park, NY 12065-8662 > Phone: 518-371-3971 x109 > > > > On Mon, Nov 16, 2009 at 12:32 PM, Anton Shterenlikht > <[email protected]> wrote: >> On Mon, Nov 16, 2009 at 12:13:02PM -0500, David E DeMarle wrote: >>> ParaView requires an xdmf file the help it interpret the contents of >>> hdf5 files. See www.xdmf.org for an explanation of the xdmf format. >> >> I see.. >> >> And what about raw binary files, how is the data >> interpreted? Do I also need to supply some plain >> text data description to go with it? >> >> many thanks >> anton >> >> -- >> Anton Shterenlikht >> Room 2.6, Queen's Building >> Mech Eng Dept >> Bristol University >> University Walk, Bristol BS8 1TR, UK >> Tel: +44 (0)117 331 5944 >> Fax: +44 (0)117 929 4423 >> > _______________________________________________ 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 ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
