*works since I had to change PYTHON_LIBRARY to point to the lib
subdirectory of /Library/Frameworks/Python.framework/Versions/2.7/,
similar to the executable and include_dir versions
On Thu, Mar 21, 2013 at 10:59 PM, Sohail Shafii sssha...@ucdavis.eduwrote:
Importing numpy into python works.
Hi Vasilis Sassanis,
Maybe too late answer: That is because the OpenFOAM reader always
holds floating point attributes in single precision regardless of the
original precision of the data.
Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata,
Hi Guys, checking in the CMakeCache was probably enough to enlighten me
about the fact that sometimes i'm dumb ;) I had activated the VRPlugin,
but not the PARAVIEW_USE_VRUI and PARAVIEW_USE_VRPN (i don't remember
doing it in the 3.98 RC1, but it might be that i just forgot it).
Now it's
On Fri, Mar 22, 2013 at 7:54 AM, Emiliano Pastorelli hoganc...@gmail.comwrote:
Hi Guys, checking in the CMakeCache was probably enough to enlighten me
about the fact that sometimes i'm dumb ;) I had activated the VRPlugin, but
not the PARAVIEW_USE_VRUI and PARAVIEW_USE_VRPN (i don't remember
On Fri, Mar 22, 2013 at 7:54 AM, Emiliano Pastorelli hoganc...@gmail.comwrote:
Hi Guys, checking in the CMakeCache was probably enough to enlighten me
about the fact that sometimes i'm dumb ;) I had activated the VRPlugin, but
not the PARAVIEW_USE_VRUI and PARAVIEW_USE_VRPN (i don't remember
I've isolated the problem to this small script:
from paraview.simple import *
reader=ImageReader(FilePrefix= z9end.raw )
reader.DataByteOrder=1
reader.DataExtent=[1,80,1,80,1,640]
reader.DataScalarType=5
view = GetRenderView()
Show()
It works with:
- 3.10 pvbatch on FreeBSD
- 3.10 pvpython on
I'm having problems with ImageReader:
http://paraview.org/Bug/view.php?id=13953
I'm thinking about trying the CSV reader instead.
My data is a 3D array of integers.
For the ImageReader I write it in binary
form using fortran 2003 stream.
I guess I can write it in a form:
i, j, k, value
i, j,
Precision might be lost in translation to decimal text.
David E DeMarle
Kitware, Inc.
RD Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
On Fri, Mar 22, 2013 at 8:37 AM, Anton Shterenlikht me...@bristol.ac.ukwrote:
I'm having problems with ImageReader:
Hi Andy,
I have attached a tar file with all 3 source code files, the Python script and
the CMakeLists.txt file used to build the executable.
Thanks so much for helping with this.
Lucas
From: paraview-boun...@paraview.org [paraview-boun...@paraview.org] on
I just realized that paraview is using a different python (2.5) on my
system than the default one (2.7) which has numpy. Also, the paraview I got
is a compiled binary of 3.14. How do I go about pointing paraview to
python2.7.
Also, form running the saved trace using python, it looks like it
I have a build of ParaView (both 3.98.1 and master) that is failing when trying
to read raw data files. The Kitware binaries successfully read this raw data.
The error message is as follows:
ERROR: In
/src/ParaView3/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line
307
Is your version of ParaView is not built with MPI enabled? It's a bug
indeed. We should use the non-mpi ImageReader if that's indeed the
case.
On Fri, Mar 22, 2013 at 8:24 PM, Scott, W Alan wasc...@sandia.gov wrote:
I have a build of ParaView (both 3.98.1 and master) that is failing when
trying
I'm pretty sure it is off. This is on a Linux, LAN, client side build. From
CMakeCache.txt,
//Enable MPI support for parallel computing
PARAVIEW_USE_MPI:BOOL=OFF
Now that I look at the bug, sure seems to me that the MPI Image Reader
shouldn't be looked for!
How do we proceed from here?
Sorry, cut and paste error between Linux and Windoz. There are two lines
there. It should have read:
//Enable MPI support for parallel computing
PARAVIEW_USE_MPI:BOOL=OFF
Alan
-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] On
Behalf
So, assuming that we shouldn't have a reader called vtkMPIImageReader in a non
MPI build, why do I find the following in readers.xml? Is this setting up for
remote server, or is it a bug? I don't find another ImageReader in this file.
SourceProxy class=vtkMPIImageReader
Man, have I had that problem before. What I did, which finally solved it, on
Linux, was the following - both at build time and run time:
* printenv | egrep PY. Then, take anything that sets up python and
delete it.
* setenv PATH path-to-your-python-executable:$PATH (be sure
Yup, that;s bug. I am guessing in that happened somewhere during the
movement of classes for modularization in one way or the other. Can
you report a bug please? I'll have it fixed.
Utkarsh
On Fri, Mar 22, 2013 at 9:16 PM, Scott, W Alan wasc...@sandia.gov wrote:
So, assuming that we shouldn't
17 matches
Mail list logo
