I couldn't reproduce the crash. I wonder if it has to do with the
Volume Mapper used. Try changing the value of the property
VolumeRenderingMode in the state file to 2 i.e. Ray Cast Only or
some of the other values, as listed in the domain for that property
in the state file. Does that over come
On 19.12.2012 at 6:05 AM, Aashish Chaudhary wrote:
Hi Deb,
You can use this vector reader (uses GDAL) and ParaView plugin to load your
SRTM DEM. I will see if we can this reader and plugin into ParaView proper.
I have long desired it but we don't have any direct funding for it but
nonetheless I
Nice to know there's still a good chance that the GDAL vector reader
could go into ParaView proper. The reader has been working so great
for me for more than a year that I really hope to see it fully
integrated with ParaView/VTK.
Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
Thanks Takuya for your help and encouragement. I will update the reader to
VTK 6 (almost done) and will get into VTK / ParaView.
Best,
On Wed, Dec 19, 2012 at 8:26 AM, Takuya OSHIMA
osh...@eng.niigata-u.ac.jpwrote:
Nice to know there's still a good chance that the GDAL vector reader
could go
Hello,
I am running Paraview in batch mode using a Python script to analyze my data.
However, after looping through few files ny script gets terminated because of a
memory overload. Is it possible to deallocate the used memory after a file has
been processed?
Currently I am using the Delete()
Hi Sebastian,
What version of ParaView are you using? Pre-3.14 suffered from
http://www.paraview.org/Bug/view.php?id=12424. An issue similar to what
you described and a workaround for it got discussed last year, see
http://markmail.org/message/72qrmqwjaxmgsa7h.
Karl
Sebastian wrote, On
On Wed, Dec 19, 2012 at 4:14 PM, deb ot...@hush.ai wrote:
Hi Aashish,
Attached image looks correct. I attached the same rendered by qgis (gdal)
and also 2-page PDF file describing the dataset, provided by DLR
Cool!
I'm not creating this data, but use it ready made.
If by missing band
It works but I see the following errors...
ERROR: In
C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\OpenGL\vtkOpenGLExtension
Manager.cxx, line 385
vtkOpenGLExtensionManager (0DC19440): Extension GL_VERSION_1_2 could
not be loaded.
ERROR: In
Hello Karl,
thank you for your message. I am using Paraview 3.14.1 (64bit).
This is what my script looks like:
# SETTINGS
directory_pvtu= '/scratch/mesh3mm_SEM/'
directory_csv = '/scratch/mesh3mm_SEM/Z085_velocity_data/'
file_number_start = 373527
file_number_end = 640332
Not sure why it isn't garbage collecting for you, but you might try
moving the entire pipeline setup out of the loop and then inside the
loop just call the two set filenames to modify the existing pipeline
before calling Write().
David E DeMarle
Kitware, Inc.
RD Engineer
21 Corporate Drive
I believe the filter won't get deleted until after the proxy goes out of
scope. If I'm right, you need to call Delete() on it and then have the
variable that's holding the proxy either go out of scope or set to
something else.
Andy
On Wed, Dec 19, 2012 at 4:36 PM, David E DeMarle
I think you need to replace del writer with Delete(writer).
ParaView has a proxy manager that keeps all proxies. Proxies will not be
deleted when the python reference is deleted, you must explicitly call
paraview.simple.Delete(). The return value of CreateWriter is a proxy, so
it must be
12 matches
Mail list logo
