[Paraview] Fail to get the mapper of a volume actor!
Hi All, I used the codes following to get the mapper of a volume actor, but I get NULL while *volume *is not NULL. * vtkAbstractMapper3D *mapper = NULL; if ( (volume = vtkVolume::SafeDownCast(propCandidate)) != NULL ) mapper = volume->GetMapper(); * Why? Thanks for any advice! Best wishes! ___ 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
Re: [Paraview] PYTHONPATH for prebuilt MAC OSX Paraview
Yes I am experiencing the same trouble with my system python but
pypython works very nicely
Thanks
Colin
Quoting pat marion :
The 'paraview' directory is the module. Python treats directories that
contain a __init__.py file as modules. So you want your python path to
contain "/Applications/ParaView 3.10.1.app/Contents/Python", and drop the
/paraview ending.
But, I recommend you use pvpython instead of python. The paraview python
modules may not be compatible with your system python. Using pvpython also
ensures that all paths are set correctly, so you don't need to set
PYTHONPATH. You can find pvpython at:
/Applications/ParaView\ 3.10.1.app/Contents/bin/pvpython
If you want to try system python, you need to:
export PYTHONPATH=/Applications/ParaView\
3.10.1.app/Contents/Python:/Applications/ParaView\
3.10.1.app/Contents/Libraries
export DYLD_LIBRARY_PATH=/Applications/ParaView\
3.10.1.app/Contents/Libraries
I'm not sure it will work for you though. On my system, python aborts when
the modules are loaded.
Pat
On Fri, Sep 30, 2011 at 11:51 AM, Colin McAuliffe
wrote:
Hello all,
As I understand it, to take advantage of python scripting the PYTHONPATH
variable must be set manually. I have added:
PYTHONPATH="/Applications/**ParaView 3.10.1.app/Contents/Python/**
paraview:${PYTHONPATH}"
export PYTHONPATH
Which is the location of .py modules. I am not able to locate the module
paraview however. Where would this module be located?
Thanks
--
Colin McAuliffe
PhD Candidate
Columbia University
Department of Civil Engineering and Engineering Mechanics
__**_
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
--
Colin McAuliffe
PhD Candidate
Columbia University
Department of Civil Engineering and Engineering Mechanics
___
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
[Paraview] rendering problem!!
Dear Users, I am facing problem while rendering images/animation. i found the information about openGL rendering what does the following lines mean? is it possible/not to render the images in my sys? [naveen@localhost ~]$ glxinfo | grep rende libGL warning: 3D driver claims to not support visual 0x5b direct rendering: Yes OpenGL renderer string: Mesa DRI Intel(R) G33 20061017 is their any thing i need to install to overcome this problem? plz help me. thanking you Naveen ___ 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
Re: [Paraview] FW: FW: Coloured isosurfaces when running MPI
Philip, Great bug report. I also had trouble with replicated colours when using rectilinear grid but due to time constraints didn't have time to track down the problem. In my case I was able to switch to ImageData since my grids were regular at the time and the problem went away. However with your detailed post I'll have another crack at locating the problem. My own suspicion was that the contouring and everything works fine, the scalars are actually correct, but somewhere in the mpi collection of the results, something gets gathered up wrongly. It seemed to me that the extent handling / piece requests for rectilinear grids was somehow broken - [pause for 5 minutes] Loading the rect2.vtk dataset and following your example I see the problem, but I also see that if you add a process ID filter and then open a spreadsheet view, you can see the original elevation values are correctly computed (as we'd expect), but then looking at the contour filter and seeing the values of elevation matched to processId and they're clearly wrong (in the spreadsheet you can select the points with zero elevation and they're visibly in the wrong place). I'll pursue this further . JB -Original Message- From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] On Behalf Of Philipp Schlatter Sent: 01 October 2011 15:32 To: paraview@paraview.org Subject: Re: [Paraview] FW: FW: Coloured isosurfaces when running MPI Dear all, sorry for warming up this older bug report; but I just tried out version 3.12 RC2, and I found that the bug (at least I believe it is one) is still present. As the problem is really being very important for my work, but presumably also for many others, I am taking the opportunity to bring it up once more. The issue is as follows: If I load a rectilinear grid, and then plot isosurfaces of the data with a certain "color by" turned on, I am experiencing that the colouring is not done correctly depending on the number of MPI processes paraview/pvserver is running on. Let me illustrate that with a simple example: The pipeline is simply reading data (for instance RectGrid2.vtk from the examples), then applying the Elevation filter to get a second scalar to do the colouring; in the example we just use elevation along the x axis. Then, we plot a bunch of isosurfaces to illustrate the problem: 1) one isosurface for the actual data (scalars), coloured by elevation. This gives a repeated colour pattern as shown in the screenshot: http://dl.dropbox.com/u/39264314/paraview/Screenshot.png and http://dl.dropbox.com/u/39264314/paraview/mpi_2.png The correct colour of course would be one single sequence starting from blue to red as the elevation gradually changes without jumping. This is shown in another screenshot, obtained with one single MPI processor: http://dl.dropbox.com/u/39264314/paraview/mpi_1.png: All is ok. For instance running on 10 processors, we get an even more strange picture: http://dl.dropbox.com/u/39264314/paraview/mpi_10.png It appears to me that the data structure that is use to colour the isosurfaces is not properly recomputed on each processor, but rather computed on one, and then used on all the others, although their own data would require different data. There are a few workarounds, see below, however they are not practical as both the memory footprint is increased considerably, but also the quality of the rendering is very poor when going to unstructured grids. The background of the issue is that I am intending to visualise large data sets and plot isosurfaces of say vorticity which is then coloured by a velocity component. Due to the size of the dataset I would like to use parallel visualisation, instead of just running serially on very fat nodes. I believe that such a visualisation technique is quite common in our area, which makes me think that the present bug is quite important. Of course I would be happy to provide more information (e.g. the state file: http://dl.dropbox.com/u/39264314/paraview/mpitest.pvsm), or also fill in an official bug report if this helps. Best regards, Philipp Schlatter KTH Mechanics, Stockholm, Sweden. -Original Message- From: Philipp Schlatter [mailto:pschl...@mech.kth.se] Sent: den 1 juli 2011 16:40 To: pat marion Cc: paraview@paraview.org Subject: Re: [Paraview] FW: FW: Coloured isosurfaces when running MPI Thanks! The "Compute Normals" is checked in the contour filter after the CleanToGrid filter, however the Gouraud shading does not work. But using an additional "Generate Surface Normals" then does the trick, at least partially. The contours look nicer than without Gouraud shading, obviously, but the best result (and also the cheapest one, I will use it on large data sets) would still be obtained when directly doing a contour on the original rectilinear data without transforming it to unstructured. Thus, I was wondering whether I should submit the present case
Re: [Paraview] PYTHONPATH for prebuilt MAC OSX Paraview
The 'paraview' directory is the module. Python treats directories that
contain a __init__.py file as modules. So you want your python path to
contain "/Applications/ParaView 3.10.1.app/Contents/Python", and drop the
/paraview ending.
But, I recommend you use pvpython instead of python. The paraview python
modules may not be compatible with your system python. Using pvpython also
ensures that all paths are set correctly, so you don't need to set
PYTHONPATH. You can find pvpython at:
/Applications/ParaView\ 3.10.1.app/Contents/bin/pvpython
If you want to try system python, you need to:
export PYTHONPATH=/Applications/ParaView\
3.10.1.app/Contents/Python:/Applications/ParaView\
3.10.1.app/Contents/Libraries
export DYLD_LIBRARY_PATH=/Applications/ParaView\
3.10.1.app/Contents/Libraries
I'm not sure it will work for you though. On my system, python aborts when
the modules are loaded.
Pat
On Fri, Sep 30, 2011 at 11:51 AM, Colin McAuliffe wrote:
> Hello all,
>
> As I understand it, to take advantage of python scripting the PYTHONPATH
> variable must be set manually. I have added:
>
> PYTHONPATH="/Applications/**ParaView 3.10.1.app/Contents/Python/**
> paraview:${PYTHONPATH}"
> export PYTHONPATH
>
> Which is the location of .py modules. I am not able to locate the module
> paraview however. Where would this module be located?
>
> Thanks
>
> --
> Colin McAuliffe
> PhD Candidate
> Columbia University
> Department of Civil Engineering and Engineering Mechanics
> __**_
> 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
>
___
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
Re: [Paraview] FW: FW: Coloured isosurfaces when running MPI
Dear all, sorry for warming up this older bug report; but I just tried out version 3.12 RC2, and I found that the bug (at least I believe it is one) is still present. As the problem is really being very important for my work, but presumably also for many others, I am taking the opportunity to bring it up once more. The issue is as follows: If I load a rectilinear grid, and then plot isosurfaces of the data with a certain "color by" turned on, I am experiencing that the colouring is not done correctly depending on the number of MPI processes paraview/pvserver is running on. Let me illustrate that with a simple example: The pipeline is simply reading data (for instance RectGrid2.vtk from the examples), then applying the Elevation filter to get a second scalar to do the colouring; in the example we just use elevation along the x axis. Then, we plot a bunch of isosurfaces to illustrate the problem: 1) one isosurface for the actual data (scalars), coloured by elevation. This gives a repeated colour pattern as shown in the screenshot: http://dl.dropbox.com/u/39264314/paraview/Screenshot.png and http://dl.dropbox.com/u/39264314/paraview/mpi_2.png The correct colour of course would be one single sequence starting from blue to red as the elevation gradually changes without jumping. This is shown in another screenshot, obtained with one single MPI processor: http://dl.dropbox.com/u/39264314/paraview/mpi_1.png: All is ok. For instance running on 10 processors, we get an even more strange picture: http://dl.dropbox.com/u/39264314/paraview/mpi_10.png It appears to me that the data structure that is use to colour the isosurfaces is not properly recomputed on each processor, but rather computed on one, and then used on all the others, although their own data would require different data. There are a few workarounds, see below, however they are not practical as both the memory footprint is increased considerably, but also the quality of the rendering is very poor when going to unstructured grids. The background of the issue is that I am intending to visualise large data sets and plot isosurfaces of say vorticity which is then coloured by a velocity component. Due to the size of the dataset I would like to use parallel visualisation, instead of just running serially on very fat nodes. I believe that such a visualisation technique is quite common in our area, which makes me think that the present bug is quite important. Of course I would be happy to provide more information (e.g. the state file: http://dl.dropbox.com/u/39264314/paraview/mpitest.pvsm), or also fill in an official bug report if this helps. Best regards, Philipp Schlatter KTH Mechanics, Stockholm, Sweden. -Original Message- From: Philipp Schlatter [mailto:pschl...@mech.kth.se] Sent: den 1 juli 2011 16:40 To: pat marion Cc: paraview@paraview.org Subject: Re: [Paraview] FW: FW: Coloured isosurfaces when running MPI Thanks! The "Compute Normals" is checked in the contour filter after the CleanToGrid filter, however the Gouraud shading does not work. But using an additional "Generate Surface Normals" then does the trick, at least partially. The contours look nicer than without Gouraud shading, obviously, but the best result (and also the cheapest one, I will use it on large data sets) would still be obtained when directly doing a contour on the original rectilinear data without transforming it to unstructured. Thus, I was wondering whether I should submit the present case also as a bug report, as I guess also other people might need coloured isosurfaces when running MPI? Best regards, Philipp On Fri, 01 Jul 2011 15:53:18 +0200, pat marion wrote: > Hi Philipp, > > You need to check the "Compute Normals" box on the properties panel of > the contour filter. Alternatively, you can apply the "Generate > Surface Normals" > to any polydata dataset to enable correct Gouraud shading. > > Pat > > On Wed, Jun 29, 2011 at 11:24 AM, Philipp Schlatter > wrote: > >> Thanks a lot for the help! >> Concerning the suggested workaround, I have a follow-up question: How >> would one get the Gouraud shading of the isocontours working? In my >> case I will get properly coloured isocontours, but they seem to have >> uniform shade for each triangle as opposed to an interpolated shade. >> >> Thanks, >> philipp >> >> >> On Wed, 29 Jun 2011 14:34:34 +0200, Karl König wrote: >> >> Hi Philipp, >>> >>> It seems you have hit a bug in the Contour filter occurring with > 1 >>> pvserver process and rectilinear grid input. I can reproduce the >>> issue you reported as such: >>> >>> Load ParaView, connect to > 1 pvserver processes Open >>> Data/RectGrid2.vtk (e.g. from git://vtk.org/VTKData.git) Calculator >>> filter, operation: "coordsX", >>>Result Array Name: "Result", Apply Contour filter, Contour by >>> "scalars", Compute Normals, >>>Isosurface Value 0.5, Apply >>> Representation "Surface", Color by "Result" >>
Re: [Paraview] paraview not running!!!
Hello, It looks like there is something not working with your 3D video card. Make sure you have the 3D acceleration enabled on your video card. À+ Pierre PS: it is better if we keep our discussion on the list: you'll get much more audience, therefore much more help. Le 01/10/2011 05:55, naveen kumar claviota: Dear Pierre, Finally i am able to run paraview. now i am facing problems while rendering, it is showing the error mesg as follows while rendering current screen shot X Error: GLXBadContext 154 Extension:143 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x14606b6 Warning: In /home/kitware/Dashboards/ MyTests/ParaView-master/source/ParaViewCore/ServerManager/vtkSMRenderViewProxy.cxx, line 878 vtkSMRenderViewProxy (0x90e18a0): Disabling offscreen rendering since empty image was detected. and while trying to render the animation it is showing X Error: GLXBadContext 154 Extension:143 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1496aa2 X Error: GLXBadContext 154 Extension:143 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1496aa3 X Error: GLXBadContext 154 Extension:143 (Uknown extension) Minor opcode: 5 (Unknown request) Resource id: 0x1496aa4 how should i procede? help me Naveen -- Pierre Chevalier Géologue EI Mesté Duran 32100 Condom Tél+fax :09 75 27 45 62 05 62 28 06 83 06 37 80 33 64 Émail : pierrechevaliergeolCHEZfree.fr icq# : 10432285 skype : pierre.chevalier1967 http://pierremariechevalier.free.fr/pierre_chevalier_geologue ___ 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
[Paraview] Descripe H5T_ARRAY or H5T_COMPOUND with xdmf
HI,
I would descripe a h5 file with a array of compound types or array of
array[3].
h5dump -H h5array_0_0_0.h5 create the follow output:
DATASET "e_global_cell_pos" {
DATATYPE H5T_ARRAY { [3] H5T_STD_I32LE }
DATASPACE SIMPLE { ( 434176 ) / ( 434176 ) }
}
DATASET "e_momentum" {
DATATYPE H5T_COMPOUND {
H5T_IEEE_F32LE "x";
H5T_IEEE_F32LE "y";
H5T_IEEE_F32LE "z";
}
DATASPACE SIMPLE { ( 434176 ) / ( 434176 ) }
}
I search for a way to descripe with xdmf to read in e_momentum or
e_global_cell_pos.
I have test:
Format="HDF5">
h5array_0_0_0.h5:/data/0/e_global_cell_pos
and
Format="HDF5">
h5array_0_0_0.h5:/data/0/e_global_cell_pos
and many more but nothing work.
thanks for help
___
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
[Paraview] Descripe H5T_ARRAY or H5T_COMPOUND with xdmf
HI,I would descripe a h5 file with a array of compound types or array of array[3].h5dump -H h5array_0_0_0.h5 create the follow output: DATASET "e_global_cell_pos" { DATATYPE H5T_ARRAY { [3] H5T_STD_I32LE } DATASPACE SIMPLE { ( 434176 ) / ( 434176 ) } } DATASET "e_momentum" { DATATYPE H5T_COMPOUND { H5T_IEEE_F32LE "x"; H5T_IEEE_F32LE "y"; H5T_IEEE_F32LE "z"; } DATASPACE SIMPLE { ( 434176 ) / ( 434176 ) } }I search for a way to descripe with xdmf to read in e_momentum or e_global_cell_pos.I have test: h5array_0_0_0.h5:/data/0/e_global_cell_pos and h5array_0_0_0.h5:/data/0/e_global_cell_pos and many more but nothing work.thanks for help SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
___
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
