Thanks for reporting Paul. The issue is now fixed (http://paraview.org/Bug/view.php?id=12527). The fix will make it into git-master at the next gatekeeper review and will be included in 3.12.
Attached is the patch for same. Utkarsh On Tue, Aug 16, 2011 at 3:48 AM, Paul Melis <[email protected]> wrote: > Sure, I have a simplified dataset for you showing the problem. It also > shows a crasher bug (load dataset, add process id scalars filter, add > histogram -> crash) > > Paul > > On 08/15/2011 10:27 PM, Utkarsh Ayachit wrote: >> That sounds like a bug. Can you share the dataset? I can send you an >> url you can use to upload the dataset directly to us. >> >> Utkarsh >> >> On Mon, Aug 15, 2011 at 10:54 AM, Paul Melis <[email protected]> wrote: >>> On 08/15/2011 04:17 PM, Paul Melis wrote: >>>> With a dataset stored in Xdmf I get an interesing data duplication >>>> result. The set consists of 55296 points, each with associated scalar >>>> and vector values. See below for the XML file and HDF5 layout. >>>> >>>> [...] >>>> >>>> <?xml version="1.0"?> >>>> <Xdmf> >>>> <Domain> >>>> <Grid GridType="Uniform" Name="Neurons-0"> >>>> <Topology NodesPerElement="55296" TopologyType="Polyvertex"/> >>> >>> Hmmm, I seem to have the Topology tag not completely correct, >>> "NodesPerElement" should be "NumberOfElements". With that correction I >>> get at least the same number of cells as number of points. This makes me >>> wonder about the other attributes I used in the .xmf file. >>> The data duplication issue remains, though. >>> >>> Paul >>> _______________________________________________ >>> 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 >>> > >
commit c5c8fdee2a180669bcb5c0260e53e5f477da1408 Author: Utkarsh Ayachit <[email protected]> Date: Tue Aug 16 10:16:09 2011 -0400 Fixed BUG #12527. Fixed parallel read issue for unstructured grids. Fixed the reader to only read unstructure grids on root node when reading in parallel. For structured grids, the update extents are respected. While for composite datasets, we distribute the leaves among processes. diff --git a/vtk/vtkXdmfHeavyData.cxx b/vtk/vtkXdmfHeavyData.cxx index 8aeebb4..972c10e 100644 --- a/vtk/vtkXdmfHeavyData.cxx +++ b/vtk/vtkXdmfHeavyData.cxx @@ -83,6 +83,12 @@ vtkDataObject* vtkXdmfHeavyData::ReadData() { if (this->Domain->GetNumberOfGrids() == 1) { + // There's just 1 grid. Now in serial, this is all good. In parallel, we + // need to be care: + // 1. If the data is structured, we respect the update-extent and read + // accordingly. + // 2. If the data is unstructrued, we read only on the root node. The user + // can apply D3 or something to repartition the data. return this->ReadData(this->Domain->GetGrid(0)); } @@ -430,6 +436,11 @@ vtkDataObject* vtkXdmfHeavyData::ReadUnstructuredGrid(XdmfGrid* xmfGrid) { vtkSmartPointer<vtkUnstructuredGrid> ugData = vtkSmartPointer<vtkUnstructuredGrid>::New(); + if (this->Domain->GetNumberOfGrids() == 1 && this->Piece != 0) + { + ugData->Register(NULL); + return ugData; + } XdmfTopology* xmfTopology = xmfGrid->GetTopology(); XdmfArray* xmfConnectivity = xmfTopology->GetConnectivity();
_______________________________________________ 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
