Hello Aashish,
sorry for my late response: Yes, I would like to have some more information
and the link to your collaboration repro. Thank you for that. Is there also
an how-to available for using VRPlugin?
Is this new plugin a part of the refactoring work you mentioned in your post
(http://public
Hello all,
Till last week I used vtkCosmoReader to read .cosmo files.
Now I try to use its parallel version,
and I have a few questions.
I noticed that there are more functions, like SetRL
and SetOverlap.
I set them, should I call update() after that?
i tried to run this:
vtkPCosmoReader *co
Hello,
I asked a student to get familiar with vtk formats to later write scripts to
extract geometry and scalar/property data from a simulation tool to be
visualized in PARAVIEW.
There are two books offered related to vtk (Textbook and User's Guide). Would
one of those be helpful for the stude
On Tue, Oct 25, 2011 at 10:19 AM, Torsten Lange wrote:
> Hello,
>
> I asked a student to get familiar with vtk formats to later write scripts to
> extract geometry and scalar/property data from a simulation tool to be
> visualized in PARAVIEW.
>
> There are two books offered related to vtk (Textbo
You are looking for a file called VTK-file-formats.pdf which explains the
"legacy" file formats. There are some XML based file formats that might also be
useful. Just depends what the simulation is writing.
http://www.vtk.org/VTK/img/file-formats.pdf
The VTK file formats (both the legacy and the xml-based versions) are
described in the VTK User's Guide. There is also a file posted on the VTK
Wiki (URL below) that gives the same information.
http://www.vtk.org/Wiki/images/5/51/VTK-File-Formats.pdf
-Ken
On 10/25/11 10:19 AM, "Torsten Lange"
Ok, thank you for all response!
Torsten
Am Dienstag 25 Oktober 2011, 17:27:46 schrieb Moreland, Kenneth:
> The VTK file formats (both the legacy and the xml-based versions) are
> described in the VTK User's Guide. There is also a file posted on the VTK
> Wiki (URL below) that gives the same in
> Ok, thank you for all response!
>
Sorry for my noise. I guess I should not be commenting on a book that
I have 20 miles away from me at work. I am glad the others cleared
that up..
John
___
Powered by www.kitware.com
Visit other Kitware open-source pr
I am currently working on adding MPI Support and better read times to
the LSDyna reader and noticed that
we currently don't have any test files. So if anybody has reasonable
sized files that can be added to the VTK/ParaView
test suite it would be greatly appreciated.
--
Robert Maynard
___
Hi,
I have to analyse very big data up to 20TB in the next time. To do this
I start a pvdataserver, pvrenderserve and a paraview client whith a
small testfile.
config.pvx##
##config end
mpirun -np 4 ./pvdataserver config.pvx
./pvrenderserver
Hi,
if you use a single pvserver instead of pvdataserver and
pvrenderserver do you still have the problem?
You should be able to use all the filters with a remote server.
On Tue, Oct 25, 2011 at 2:58 PM, René Widera wrote:
> Hi,
>
> I have to analyse very big data up to 20TB in the next time. To
Help?
[ 44%] Building C object
Utilities/IceT/src/communication/CMakeFiles/IceTMPI.dir/mpi.c.o
cd
/nfs/tmp2/rcook/ParaView/3.12/ParaView-3.12.0-RC2-build/Utilities/IceT/src/communication
&& /usr/local/bin/mpicc -DIceTMPI_EXPORTS -DVTK_PYTHON_BUILD
-I/usr/global/tools/Kitware/Paraview/3.11/c
Hey Rich, is this paraview master? What settings have you turned on? Just
Build Shared, PARAVIEW_USE_MPI and Python?
On Tue, Oct 25, 2011 at 8:43 PM, Cook, Rich wrote:
> Help?
>
> [ 44%] Building C object
> Utilities/IceT/src/communication/CMakeFiles/IceTMPI.dir/mpi.c.o
> cd
> /nfs/tmp2/rcook/Pa
Works for me! Here is a snippet from our python script.
Alan
mpiDir =
'/apps/x86_64/mpi/openmpi/intel-11.1-f064-c064/openmpi-1.4.2_oobpr
cMakeVars = cMakeVars +\
'-DMPI_LIBRARY:FILEPATH="'+mpiDir+'/lib/libmpi.so;'+\
mpiDir+'/lib/libopen-rte.so;'+\
mp
I have been tweaking for days on my CMakeCache.txt.
I don't know which are relevant to this but, here's a start:
Thanks!
BTW, I searched through our mpi headers and could not find a reference to
MPI_IN_PLACE. I'm wondering if there is a version of MPI which is being
assumed. We are using mvapic
Ah, thanks,
perhaps this only works with OpenMPI... I'll investigate whether I can use
that.
Paraview is hard as hell to build.
-- Rich
On Oct 25, 2011, at 5:59 PM, Scott, W Alan wrote:
> Works for me! Here is a snippet from our python script.
>
> Alan
>
>mpiDir =
> '/apps/x86_64
You shouldn't be tweaking the Cache! :-P It should work with openmpi,
mpich2, msmpi intel mpi etc.
On Tue, Oct 25, 2011 at 9:04 PM, Cook, Rich wrote:
> Ah, thanks,
> perhaps this only works with OpenMPI... I'll investigate whether I can use
> that.
> Paraview is hard as hell to build.
> -- Rich
Hi,
I am currently trying to do some shader operations in a standard C++ filter.
This filter (inherits from vtkMultiBlockDataSetAlgorithm, resides in
VTK/Graphics) will be used to voxelize a polygonal object (basically the result
of the contour filter) and write the results to a 3D texture.
I
The problem I think is that MPI_IN_PLACE is supported only by MPI-2
whereas your MPI library probably implements MPI 1.x.
MPI_IN_PLACE was not in IceT until PV 3.10.1. I had given up trying to
install PV 3.12 series on a supercluster that only has MPI 1.2 support
so would really appreciate if the
Richard
In an emergency, you can simply paste
#define MPI_IN_PLACE ((void *) 1)
into files where you're getting a build error to shut the compiler up and
produce a test build to work with.
If you're not actually using the functions, you won't get any run time errors.
(of course, if you ar
20 matches
Mail list logo