Hi,
Thanks a lot for all your inputs. Thanks Utkarsh for the pointer. I tried
to use it but some how when I select both my meshes and then try to open
python calculator, it does not happen. The tab itself is inactive when I've
selected 2 inputs.
However the ICP registration gave me the desired
Dear List,
I am attempting to have a program I use write its own VTI files, in order to
import image data into paraview more easily (we are usually using raw binary
files!).
However, during the base64 encoding, some data sizes are rejected by the
paraview reader.
As a small test case, the
Please read that:
http://www.paraview.org/Wiki/ParaViewWeb_Manta_setting
Then forget Manta and do your own manta-init.py file that will only
load your plugin... And that's it... (You can rename the file, just
make sure you keep the consistency.)
Seb
On Mon, Jun 25, 2012 at 6:52 PM, Alex
Hi,
I'm importing seismic files into paraview as .vti (Image file) to display
them as a volume but I can't get a nice display (impossible to
distinguish a layer from one to another). It seems that every cell is
interpolated with all its neighbors and therefore it creates some sort of
stains much
Thank Seb,
I'm sorry if I forget one step. But I have always Uncaught TypeError: Object
#Paraview has no method 'ImageThresholdPFE'
I did as follow:
File ImageThreshold.py
import paraview
paraview.simple.LoadPlugin('/home/.../vtkImageThreshold/bin/libImageThresholdSMPlugin.so',False)
What I'm talking about is a --batch-file not a ParaViewWeb plugin.
But never mind, if you really want to use a ParaViewWeb plugin you are
stuck by the fact that your ParaView object in JavaScript will NEVER
have your custom filter definition available. Which is NORMAL, and
that's why you get those
unfortunately I'm running this on a vis cluster, I don't see the
windows. I guess I can move one slice of the dataset to my workstation
and see if the issue remains...
On 06/25/2012 04:36 PM, Utkarsh Ayachit wrote:
Is it at all possible to view the batch render windows on the
processes? I am
Sorry I don't have any insight. The 1024 limit sounds very fishy. In
the end, it has to be something with X/OpenGL context or something
like that, but what is confusing is that it works with pvserver
(remote-rendering, right?).
Utkarsh
On Tue, Jun 26, 2012 at 10:40 AM, Burlen Loring
O another thing, try turning off
UseOffscreenRenderingForScreenshots property on the view.
view.UseOffscreenRenderingForScreenshots = 0
That's one difference between the client-server and pvbatch workflows.
Utkarsh
On Tue, Jun 26, 2012 at 10:40 AM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com
Hello,
I am trying to transform a surface using a programmable filter, and I am
unable to get the output to use the normals. Even the most basic filter:
output.PointData.append(inputs[0].PointData['Normals'], 'Normals')
results in the mesh being copied but the normals not being used. The
Hi Katie,
I'm guessing you're looking at the arrays that are available to
pseudo-color with in the GUI. Those normals usually aren't in the filter
output data set. To see what arrays are available, look under the
information tab. To create those arrays for polydata (possibly using the
extract
Thanks Andy. However, in the information tab, I see the data array called
normals after I apply the programmable filter. The array is there (and
from the spreadsheet view I know that it is identical to the case where I
copy the array) but the resulting surface does not use the array! Instead
of
Use vtkDataSetAttributes::Get/SetNormals() to access the normals.
Likewise use Get/SetTCoords() to access the texture coordinates.
od = self.GetOutput()
id = self.GetInput()
od.GetPointData().ShallowCopy(id.GetPointData())
innorm = od.GetPointData().GetNormals()
onorm = innorm.NewInstance()
Thanks David- that worked perfectly!
On Tue, Jun 26, 2012 at 2:35 PM, David E DeMarle
dave.dema...@kitware.comwrote:
Use vtkDataSetAttributes::Get/SetNormals() to access the normals.
Likewise use Get/SetTCoords() to access the texture coordinates.
od = self.GetOutput()
id = self.GetInput()
Hi,
I am currently compiling paraview 3.14.1 and using a locally installed version
of python2.7. My version of cmake is 2.8.8. The OS is Red Hat Enterprise Linux
Client release 5.8. I get the following error during compilation:
[ 0%] Built target vtkWrapPythonInit
make[2]: *** No rule to make
No luck there. I have had it set to 0 all along, but setting to 1
doesn't help. I initially suspected the xorg config, but xrandr command
confirms that the display supports the higher resolutions. Yes, it works
with pvserver remote rendering.
On 06/26/2012 07:41 AM, Utkarsh Ayachit wrote:
O
16 matches
Mail list logo
