That worked on the ones that I've tried !!
I tried it on spatial and temporal collections of 3DCoRectMesh.
I changed some of the code to try to make parallel reads work
on collections at any level. It works on the examples I tried.
Has anyone tried parallel pvserver on their data ?
Jerry
John Biddiscombe wrote:
Jerry et al,
I've just checked in a fix.
In short, the Grid->Information pointer was being set to the outInfo
object, but for a multiblock(temporal) object with sub grids, this meant
the top level grid (container) was getting the (true) outInfo pointer
and sub grids were setting their own info, but this sub grid info never
made it to the (true) Output information.
I've passed a pointer to the "outInfo" down the RequestGridInformation
call so that individual grids maintain their own copy of their own
information, /but also copy it to the real outInfo/ when needed.
It's working for me for a simple temporal imagedata 3D slab - but I
suspect we will have future trouble when one grid puts information in
the outInfo object and then another overwrites it (multiblock etc). Test
this fix on any data you have handy and we'll see how long before it
breaks :)
JB
Classification: UNCLASSIFIED
Caveats: NONE
John, Eric,
Yes, I duplicated the problem here and it seems that the information is
not being set correctly. John, you probably understand this much better
that I do.
I'm guessing it has to do with the OutputVtkType being set to image data
but the vtkXdmfReaderGrid is actually a collection : isCollection = 1
and
isTemporal = 1.
Jerry
-----Original Message-----
From: John Biddiscombe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 20, 2008 8:20 AM
To: Eric E. Monson
Cc: Clarke, Jerry (Civ, ARL/CISD); Renato N. Elias;
[EMAIL PROTECTED]; ParaView List
Subject: Re: [Xdmf] Xdmf time series loads as Multi-block Dataset
(UNCLASSIFIED)
The only variant that is not bringing in data correctly is when I have
a temporal collection which contains a 3dCoRecMesh grid at
Same for me. I only have 3DCORECTMESH types and none of my data loads.
Time is good, but geometry is lost.
ImageData is the only datatype afaik that paraview takes all
origin/spacing/extent information directly from the information object
attached to the data, rather than the data itself. I suspect that the
information being set insiside RequestGridInformation in the xdmf
reader, is being set on the grid's individual information, object, but
not being copied into the output information. I'm looking into it.
JB
Classification: UNCLASSIFIED
Caveats: NONE
--
John Biddiscombe, email:biddisco @ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
