I tracked this down and you are right. When reading EnSight files (not sos), all processes read the whole dataset and then each one extracts a piece. If you submit a request at http://paraview.org/Bug, we can address this issue in the future.
-berk On Fri, Dec 5, 2008 at 3:48 AM, Jacques Papper <[EMAIL PROTECTED]> wrote: > The grid is unstructured. It comes up as a multiblock dataset in ParaView, > but there is only one fluid volume. The other blocks are just surfaces. > Jacques > > 2008/12/4 Berk Geveci <[EMAIL PROTECTED]> >> >> The answer depends on the data type. Is it structured or unstructured? >> >> On Dec 4, 2008, at 11:49 AM, "Jacques Papper" <[EMAIL PROTECTED]> >> wrote: >> >>> Hi, >>> >>> I compiled Paraview for use in parallel. >>> I have an Ensight data set that has been output from fluent. I also have >>> the fluent .cas and .dat files (saved from a cluster run) >>> I would like to load the data using the best of paraview in parallel. >>> If I launch pvserver on 4 nodes and load the ensight data it seems that >>> it loads the data 4 times. >>> >>> What would be the best / efficient way of using the parallel >>> functionality ? Is there a way of partitioning the ensight file ? Or setting >>> up the reader so that it partitions the data at the reading stage ? Or maybe >>> is there a Fluent reader that will load in the partitions from the .cas file >>> ? >>> >>> Jacques >>> _______________________________________________ >>> ParaView mailing list >>> [email protected] >>> http://www.paraview.org/mailman/listinfo/paraview > > _______________________________________________ ParaView mailing list [email protected] http://www.paraview.org/mailman/listinfo/paraview
