Hi everybody,
just a (very) simple question:
Which Paraview/VTK file readers already have full support for ghost/halo
data when running in parallel?
thanks
ps.: In fact, I'd like to figure out how I could get rid of my parallel
interfaces among partitions.
--
Renato N. Elias
All readers should support ghost cells as long as:
- They support cell data
- They support unsigned char data
(Note: you need ghost cells not points for this to work).
All you have to do is to add a cell array called vtkGhostLevels to
your data. Cells that are internal should have a value of
Hi Berk, thanks for your answer.
I think I'm missing something you said cells only?!
If I understood this subject correctly, a cell should be considered ghost if
it's held by more than one partition/process, isn't it?! In this case,
there'll be an overlapped layer of elements. The problem is
Hi Renato,
I think I'm missing something you said cells only?!
If I understood this subject correctly, a cell should be considered ghost if
it's held by more than one partition/process, isn't it?! In this case,
there'll be an overlapped layer of elements. The problem is that my MPI
Berk: Do you have the ability to mark a node as owned by one partition
and as ghost on
other partitions?
Yes! We classify processes as master and slaves according to their ranking
numbers. After this we can assign the shared node to a master (which will
take care of shared computations) and
Great. Ping me in a 2-3 months - we should have started making changes
to the ghost level stuff by then. Until then, you should be able to
use D3 to redistribute data and generate (cell) ghost levels as
needed. So the following should work
reader - D3 - extract surface
-berk
On Tue, Mar 1, 2011
Hi
I'm trying to build 2 independent views with the option of independent
filtering *and *joined filtering of the same data/object. I want 2 users to
use ParaView with independent head-tracking, allow them to independently
apply filters to the same dataset, have the option of sharing the filters
pqVRPNStarter.cxx is only looking at the active view and that too the
active view when the plugin was loaded and hence it works only with 1
view.
You can access all available views from API on
pqApplicationCore::instance()-getServerManagerModel() (findItems).
pqServerManagerModel also fires
On Fri, Feb 25, 2011 at 4:24 AM, Natalie Happenhofer
natalieh...@hotmail.com wrote:
Dear all,
I'm encountering problems using Paraview in Client/Server Mode. I'm using
ParaView 3.8.0-RC2, the remote system where the pvserver is started, is
Gentoo Linux 4.4.3 and the client is started on my
Greg,
I think we all agree with you here. The discussion of the padding was not
intended to be a justification for image inconsistencies. Rather it is
intended to help us identify what is causing the problems and try to
prevent reintroducing more grievous artifacts that the padding was
Hi,
I've read in a CAS file, which Paraview read in a Multi-block dataset, which
contains within it a unstructured grid.
Initially I had a problem where all of the data items were one-tuple arrays.
So I created a UVW (3-tuple velocity) array and added it to the pipeline this
way using a
By any chance, does this multi-block dataset contain a block that does not
have arrays (scalars and/or vectors)? That's probably why those filters are
disabled. You can always use Extract Blocks to extract the block you are
interested in and then apply the filter. As for the Programmable Filter,
Hi,
Let me correct myself; the block contained inside is a vtkStructuredGrid. I
did a printout what is in the pipeline (self.GetInput()):
p, li { white-space: pre-wrap; }
vtkMultiBlockDataSet (0x3a7c1d0)
Debug: Off
Modified Time: 164250
Reference Count: 2
Registered Events: (none)
13 matches
Mail list logo
