I am going to limit my responses to technical parts. It's too early in
the morning for anything else :).
> Yes, all these timer loops in paraview are annoying.
I am not sure there "many" timer loops in ParaView. Please feel free
to elaborate. Even this collaboration timer comes into play only
Yes, you just need to import the appropriate module in python.
e.g.
@exportRpc("my.test.rpc")
def myTestRPCFunction(self):
from paraview.vtk.vtkIOImage import vtkImageReader2Factory
reader = vtkImageReader2Factory.CreateImageReader(filename)
from
I am not sure I follow what you're doing, but here are a few things to note.
1. vtkSMProxy::UpdateVTKObjects() is called to push changes done to a
property. Thus, only needs to be called on the proxy whose properties
you're changing. Thus, if you are chaning "CompositeDataSetIIndex"
property on
New binaries for linux have been uploaded. Please give them a go.
Thanks
Utkarsh
On Thu, Jun 9, 2016 at 7:10 PM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
> Roger that. I've getting a new build. I switched to using a new build
> machine -- looks like that was premature.
gt; callback that does the same server event processing only when a new event
> has occurred? I mean, all of VTK and ParaView is event based, why not the
> server message processing?
>
> Peter
>
> 2016-06-09 18:29 GMT+02:00 Utkarsh Ayachit <utkarsh.ayac...@kitware.com>:
>&
kage with libembree...
>
>
>
> On 09.06.2016 19:27, Zhixuan Cao wrote:
>>
>> Very happy to hear that. Is there any documentation about the detail of
>> new features? For example, what is the exact equation for the new feature
>> SPH interpolation?
&g
ple, what is the exact equation for the new feature
>> SPH interpolation?
>> > On Jun 9, 2016, at 10:59 AM, Utkarsh Ayachit
>> > <utkarsh.ayac...@kitware.com> wrote:
>> >
>> > Folks,
>> >
>> > ParaView 5.1.0-RC1 is now available for dow
Here's the fix:
diff --git a/main.cxx b/main.cxx
index dd47991..0f679ba 100644
--- a/main.cxx
+++ b/main.cxx
@@ -65,7 +65,7 @@ int main(int argc, char* argv[]){
vtkSMSessionProxyManager* pxm = session->GetSessionProxyManager();
//Collaboration:
- vtkSMCollaborationManager
Folks,
ParaView 5.1.0-RC1 is now available for download [1]. For fixes that
went into this release, refer to the change log on bug tracker [2].
Detailed release notes coming soon.
- The ParaView team
[1] http://www.paraview.org/download/
[2] http://www.paraview.org/Bug/changelog_page.php
In theory, you can do this using a Python animation cue too... let me
see how that can be put together.
On Wed, Jun 8, 2016 at 8:50 AM, David E DeMarle
wrote:
>
> If the slice stays fixed relative to the bounding box of the moving object,
> try a python calculator to
t; We did indeed build 5.0.1 (with your updates) and the connect_id is the
> same on both ends …..
>
>
>
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone: 410-278-6266
>
>
>
>
> -----Original Me
> Utkarsh - I was able to get a clean build with this OSMesa patch - but it
> looks like the OSMesa pvserver is not compatible with the production 5.0.1
> client??
That's not the case. It should be compatible, so long are you're
building 5.0.1 on the server side too.
>
See pqServer::processServerNotification() [1]. You'll need to call
vtkNetworkAccessManager::ProcessEvents(..) "on idle" to process events
being received from the other client.
[1]
https://gitlab.kitware.com/paraview/paraview/blob/master/Qt/Core/pqServer.cxx#L376-401
On Tue, Jun 7, 2016 at 8:54
Here's a MR for update superbuild that builds OSMesa 11.2.2. I've only
updated OSMesa. I'll tackle mesa-glx next.
https://gitlab.kitware.com/paraview/paraview-superbuild/merge_requests/114
Utkarsh
On Mon, Jun 6, 2016 at 12:31 PM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
~~~~
> Joseph G. Hennessey Ph.D., Lockheed Martin
> Army Research Lab
> DOD Supercomputing Resource Center
>
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Thursday, June 02, 2016 4:19 PM
> To: H
on the second one.
> So I was wondering what change could have actually caused the above error.
>
>
> On Jun 2, 2016, at 4:26 PM, Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
> wrote:
>
> No, you don't need to recompile ParaView.
>
> On Thu, Jun 2, 2016 at 2:1
> Would it be sufficient to change the cmake flags OSMESA_INCLUDE_DIR and
> OSMESA_LIBRARY in CMakeCache file to point to the external build of Mesa
> 11.x.x?
Pretty much (and setting a few other vars to empty including
OPENGL_gl_LIBRARY etc, see the arguments to add_extra_cmake_args()
call in
No, you don't need to recompile ParaView.
On Thu, Jun 2, 2016 at 2:19 PM, Sangeetha Banavathi Srinivasa
wrote:
> Hello,
>
> I wanted to know if ParaView should be recompiled on HPC clusters after
> upgrading GPU drivers?
>
> Thanks,
> Sangeetha
>
> And I have tried replacing the library
> lib/paraview-5.0/libOSMesa.so.7
> with both libOSMesa.so from 11.1.2 and 11.2.2
> and they are both still giving the same error
Simply swapping the libraries won't work. Mesa 11.2 [1] added new API
OSMesaCreateContextAttribs() which is needed to create
but we'll probably eventually want to
> address Mesa w/X support .
>
> -Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Thursday, June 02, 2016 9:48 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
> <rich
Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone: 410-278-6266
>
>
>
>
> -Original Message-
> From: Utkarsh Ayachit <utkarsh.ayac...@kitware.com>
> Date: Thursday, June 2, 2016 at 8:37 AM
> To: Rick Angelini <richard.c.
Alas, there's nothing up-to-date. I've been meaning to write a blog
series covering various aspect of ParaView internals, but it's hard to
find some downtime to get that going. I'll try to see if I can find
the old PDF for the ParaView Guide v3 and share the old chapter
(although obsolete, but
> So there is much more to be done than adding
> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
> to the cmake flags?
As far as ParaView is concerned, no there's not much more to it.
However if your OpenGL implementation doesn't support OpenGL 3.2
(released
ar.gz;
>
>
>
>
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone: 410-278-6266
>
>
>
>
> -Original Message-
> From: ParaView <paraview-boun...@paraview.org> on behalf of Rick Ang
Call for Participation: ISAV 2016
=
ISAV2016: In Situ Infrastructures for Enabling Extreme-Scale Analysis
and Visualization
In cooperation with SIGHPC and held in conjunction with SC16: The
International Conference on High Performance Computing, Networking,
Storage and
Alan,
I am not sure I follow, but attached is a script that fetches "global
arrays" to the client side so you can do whatever you want with it. Is
that what you're looking for?
Utkarsh
On Wed, May 18, 2016 at 9:52 PM, Scott, W Alan wrote:
>
>
> If I want to get the numeric
to affect the execution logic of the filter.
>
> Andrzej
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: 27 May 2016 13:51
> To: Andrzej Peczak
> Cc: ParaView
> Subject: Re: [Paraview] Custom panel widget
>
> Andrzej,
>
for that quick fix!
>> Yes, You are right, my VTK test was using point data, so the problem
>> didn't appear.
>> Thanks again for the great support.
>>
>> On 23/05/16 19:08, Utkarsh Ayachit wrote:
>>>
>>> Here's a fix for the same:
>>>
>>
There's a preexisting feature called "annotation" that vtkSMProxy
supports via the following API. Seems to me that'd map well to what
you're trying to do with the "user" property.
void SetAnnotation (const char *key, const char *value)
const char * GetAnnotation (const char *key)
void
> Yep - we built the HPC-side with “OpenGL2” … so does that mean that the
> pre-built Mac/Linux binaries were both built with OpenGL?Is there some
> way to check to see which OpenGL the client was built with?
The binaries distributed by paraview.org are indeed OpenGL2. The title
bar for
Rick,
I must admit this was a major "oops" in 5.0.0 and 5.0.1 releases. We
should have handled this better and I will make sure we do for 5.1.
Basically, what you have is a mismatch in rendering configurations for
client and server. One of them is build with VTK_RENDERING_BACKEND set
to OpenGL
. Of course we also would like to modify
> the distances and send it back to the filters. These values will be used to
> update the output of the filter.
>
> Andrzej
>
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: 23 May 2016
Folks,
Due to a recent spam-a-geddon, we are temporarily disabling new
account signing up on VTK/ParaView bug trackers while we figure out
how best to deal with this in the long term.
Thanks for patience,
VTK/ParaView Team
___
Powered by
Matt,
Can you confirm that both the client and server are using the same
rendering backend? Unfortunately, there's no clean way to do that
except to look at the CMakeCache.txt used to build to two. Confirm
that the VTK_RENDERING_BACKEND CMake flag is set to the same value on
both. I suspect one
:18 AM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
> Stephanie,
>
> Is it possible to share the full dataset to reproduce this issue? That
> will make things easier.
>
> Thanks,
> Ukarsh
>
> On Tue, May 24, 2016 at 3:36 AM, Stephanie Wollherr
> <wollh.
Guys,
The multiblock writer issue is unrelated -- as far as I can tell. Esp
since "If I take the image rendering out of my pipeline (comment out
the RegisterView call) and leave the VTK file writing, it runs fine
and doesn't report any leaks.".
Here's the MR if you're interested in checking it
Stephanie,
This is indeed weird, looks like I can apply the Contour filter but it
doesn't produce any output. Did you say you were writing out VTK files
before and it used to work then? Can you also share the VTK file that
was working?
Thanks
Utkarsh
On Tue, May 24, 2016 at 3:36 AM, Stephanie
Stephanie,
Is it possible to share the full dataset to reproduce this issue? That
will make things easier.
Thanks,
Ukarsh
On Tue, May 24, 2016 at 3:36 AM, Stephanie Wollherr
wrote:
>
> Hi all,
>
>
> I'm using a xdmf input file to visualize my data output
Try using the "Annotate Global Data" filter instead. You can then choose to
use the value from the field data array TIME.
On Mon, May 23, 2016 at 2:40 PM, Carlos Baumann wrote:
> Hello ParaView !
>
>
>
> I would like to annotate the actual Time using a series of .vtk files,
>
Here's a fix for the same:
https://gitlab.kitware.com/vtk/vtk/merge_requests/1517
Utkarsh
On Mon, May 23, 2016 at 11:42 AM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
> Ah okay. Looks like there's another bug with cell-data coloring and
> x3d. I've spotted the bug (I t
tml
>
>
> On 23/05/16 16:10, Utkarsh Ayachit wrote:
>>
>> And same with categorical colors. I did notice, however, it fails when
>> coloring with "Field Data" arrays. Is that what you're seeing? That
>> I'd expected would fail in VTK too. That's indeed a miss
> Is it possible to create a custom widget for a filter which would allow me to
> retrieve the results of its computation? I would like to reproduce the
> functionality of the pqDoubleVectorPropertyWidget and populate it with values
> computed by the filter. I know how to create and register
Lukasz,
> The volume rendering algorithms in Paraview are ultrafast with VTK image
> files but painfully slow with unstructured grids. I constantly have an idea
> in mind to map unstructured meshes to image files and then do the volume
> rendering.
That's indeed the reason by the "Resample to
Lukasz,
I'd suggest not to use 'ImageResampling' filter, it was a temporary fix and
clearly is buggy. A new filter has been added to ParaView "master", name
"Resample To Image". That would do what you want to do more reliably. What
platform are you running on? I can send you links to the nightly
Ramiro,
A few things to note:
+ Not sure what's the deal with 4.0.1, but it's too old at this point
so let's ignore that.
+ When you downloaded ParaView 5.0.1 from paraview.org, starting with
5.0.1, we are using a new implementation of the rendering backend for
our binaries [1]. This rendering
5.0.1 doesn't support export to PDF, I am afraid. However, "master"
does and so will "5.1"
(cc-ing Dave, just in case I am mistaken)
Utkarsh
On Thu, May 19, 2016 at 5:56 PM, Ramiro James Rebolledo Cormack
wrote:
> Hi all.
>
> I'm using paraview 4.0.1 on my ubuntu 14.04
The following should do the trick:
activesourcefile.ElementBlocks.SelectAll()
Calling help(activesourcefile.ElementBlocks) will show info about all
available API (extract below):
help(a.ElementBlocks)
Help on ArrayListProperty in module paraview.servermanager object:
class
Awesome! Glad it's working.
On Wed, May 18, 2016 at 11:48 AM, Daniel Oliveira
wrote:
> I resolved part of my problem with the command
>
> > paraview --mesa-llvm
>
> Now I can open Paraview to see my vtk files.
> I will try to compile my drivers with support to OpenGL 3.2
You may need to rebuild mesa with drivers that support OpenGL 3.2 and newer.
See this post:
https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk-7-0/
Alternatively, as the post mentions, try running the binary are
> paraview --mesa-llvm
That will use the packaged mesa libGL and
Such errors happen when downloading test data and baselines due to
either server or network issues. If you are not running tests, simply
turn OFF BUILD_TESTING CMake flag. Alternatively try again after some
time. If is was due to server issues, it typically recovers.
On Wed, May 11, 2016 at 5:54
You have to build ParaView from source with VTK_RENDERING_BACKEND
cmake variable set to OpenGL. Currently, we don't distribute binaries
legacy OpenGL backend.
On Wed, May 11, 2016 at 8:31 AM, Dennis Conklin
wrote:
> Utkarsh,
>
>
>
> As we are having trouble running
Folks,
I wanted to check if there's any objection to dropping support for OsX 10.7
(Lion) in future ParaView releases. 10.7 has been unsupported by Apple
since October 2014 [1]. This will change minimum OsX version for ParaView
to 10.8 (Mountain Lion).
Utkarsh
[1]
Following discussions with folks here, we're tabling this for another
year as the OpenGL2 backend continues to stabilize.
On Wed, May 4, 2016 at 10:33 AM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
> Folks,
>
> As we continue to make progress on the new OpenGL2 renderi
Folks,
As we continue to make progress on the new OpenGL2 rendering backend,
I wanted to get a feel from the community if there's any objection to
dropping support entirely for the legacy OpenGL1 rendering backend in
ParaView for 5.2?
Note this will only affect ParaView and ParaView-based
Nikos,
When you say you're "set the range of the contours from -0.0001 to
0.0001 but the contours levels revert back to automatic scaling", what
do you mean? Do you mean you're setting separationline.Isosurfaces to
be values in the given range, but the rendered countour is still the
same old
Alas, no. Sometimes, using sub-proxies instead may work, but depends
on your usecase.
Utkarsh
On Mon, May 2, 2016 at 2:18 PM, Dean, Kevin
wrote:
> Is there a way to do multiclass inheritance while writing your xml for a
> Plugin?
>
> Kevin Dean
>
> This
Not presently, I am afraid. I am working on refactoring save
screenshot/save animation diaglogs that will add support for a richer
Python API for the same, enabling trace to record it as well.
Utkarsh
On Fri, Apr 29, 2016 at 5:28 PM, Scott, W Alan wrote:
>
>
> When I create
This seems to be an issue with the ParaView build in OpenFOAM. It's
not packaging numpy. Alternatively, if it's using system installed
Python, you will need to install numpy on your local Python
installation.
On Sat, Apr 23, 2016 at 2:42 PM, Jun Zhang wrote:
> Hi All
>
> I am
> Very nice. I didn't know these existed. Here is another question from my
> user: Is there some detailed documentation (beyond whats in the paraview
> guide) for the programmable filter API?
Alas, no. If you have a list of things that are not covered that your
user would like described, we
> 1. Is there any documentation generally describing the input and output
> data objects that form the programmable filter API?
Chapter 14 from the ParaView Guide. And the following series of Berk's
blog posts:
https://blog.kitware.com/improved-vtk-numpy-integration/
Not entirely sure what that is. ParaView doesn't really report error
codes. What OS is this on?
On Tue, Apr 19, 2016 at 3:31 AM, Vincent BOSQUIER
wrote:
> Hi,
>
> I'm using ParaView v4.4 and I have experienced an error code 134 when
> opening the application.
> I think I hear OpenGL minimum is 3.2. Is that correct?
Yes.
> What is the minimum MESA version required?
10.5.5 or later. However, 11.2 is strongly recommended. 11.2 is
required if using OSMesa support.
___
Powered by www.kitware.com
Visit other
Here's a potential fix:
https://gitlab.kitware.com/paraview/paraview/merge_requests/744
+ Save data dialog now is the same dialog we use other places e.g.
editing scalar bar properties, which allows user to save the chosen
values to "Settings" after clicking the "Apply" button.
+ I have not
> This has always worked for me with earlier versions of
> ParaView, but something seems to have changed. It could be the newer NVidia
> driver we use since a few weeks, but like I said, I don't see issues with
> any other OpenGL application.
Paul, can you try with ParaView 5.0.0 and 4.4 binaries
have to close the terminal. I am
>> not entirely familiar with the use of the LD_LIBRARY_PATH, is there any
>> reason that this alteration would effect the operation of vim?
>>
>>
>> On Tue, 12 Apr 2016 at 22:18 sean read <read.sea...@gmail.com> wrote:
>>
I am assuming you want to change opacity using Z and color using some
other array -- if that's the case, I am afraid that's not supported
currently. You can only change the color and opacity using the same
array.
Utkarsh
On Fri, Apr 15, 2016 at 5:51 AM, Fastl, Thomas
> Tried your new version and got this:
/lib64/libpthread.so.0: version `GLIBC_2.12' not found
> (required by …
> ParaView-5.0.1-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.0/mesa-llvm/libGL.so.1)
Your linux version, I'm afraid, is too old for the Mesa binaries we ship.
Alan,
> ./paraview --mesa-llvm
> .../lib/paraview-5.0/paraview: error while loading shared libraries:
> libatomic.so.1: cannot open shared object file: No such file or directory
Can you try this binary:
Dennis,
Don't mean to distract this conversation -- I'll let Chuck follow up
on the VNC thing -- but a a small sidetrack:
Can you trying running paraview as:
> paraview --mesa-llvm
Does that work?
Utkarsh
On Wed, Apr 13, 2016 at 12:12 PM, Dennis Conklin
wrote:
Seems to be some issue on rendering remotely, period. Can you look at
the About dialog and see what OpenGL version it reports for client and
server sides?
On Mon, Apr 11, 2016 at 6:05 AM, Jung Thomas
wrote:
> Dear all,
>
> I am new to using pvserver, the problem I
Try setting your LD_LIBRARY_PATH to include the ".../lib/paraview-5.0"
directory.
On Tue, Apr 12, 2016 at 5:53 AM, sean read wrote:
> So I've downloaded paraview5.0 from the website
> http://www.paraview.org/download/nload/, and set my python path as
>
>
d, simple explanations, I get it. Nice
> feature. Why isn't it enabled by default? I.e., why do you need to load
> the optional plugin?
>
> Here is an image I created with the help of Surface LIC.
>
>
> Alan
>
>
>
> -Original Message-
> From: Utkarsh Ayachi
Nenad,
1. The ParaView binaries for 5.0/5.0.1 are built using Visual Studio
12 2013 (MSVC 18.0.31101.0).
2. For Windows, we only test ParaVIew superbuild using "Ninja"
generator, and not VS IDE. Thus, run the CMake GUI from an appropriate
Visual Studio Command prompt and choose the Ninja
.
>
> 2016-04-01 15:15 GMT+03:00 Utkarsh Ayachit <utkarsh.ayac...@kitware.com>:
>>
>> > Sorry for small offtopic, but I didn't notice any remote access issues
>> > with
>> > ParaView 5.0.1 RC2 on Windows 7 x64, but I use Linux client (FreeRDP
>> >
Alex,
This is a known issue: http://www.paraview.org/Bug/view.php?id=15716
We'll address it in the next release of ParaView.
Utkasrh
On Thu, Apr 7, 2016 at 12:46 PM, Alex Lindsay wrote:
> Hi all,
>
> I switched to Paraview 5.0.1-RC2 from 4.1.0. I am now getting the
>
On Mon, Apr 4, 2016 at 2:31 PM, Moreland, Kenneth wrote:
> To specify further, I get the same results on my Mac. I do see the LIC on the
> surface inside that hole. I was refering to the outside part of the cylinder.
> But looking more closely at the data, I see that the
All artwork in ParaView repository is released under the same
licensing terms as the code i.e with BSD 3-clause license [1].
[1] https://gitlab.kitware.com/paraview/paraview/blob/master/Copyright.txt
On Mon, Apr 4, 2016 at 4:56 AM, Muhammad Hagras wrote:
> Hi everyone,
>
> Sorry for small offtopic, but I didn't notice any remote access issues with
> ParaView 5.0.1 RC2 on Windows 7 x64, but I use Linux client (FreeRDP 1.0.2).
That's curious. Can you post the OpenGL information the About dialog reports?
___
Powered by
You cannot use ParaVIew 5.0 or later over remote desktop anymore.
ParaView now needs newer OpenGL (3.2 or later) and remote desktop uses
software OpenGL implementation that only supports OpenGL 1.1. It may
be possible to build Mesa3D (http://www.mesa3d.org/) on Windows, but I
personally don't have
BTW the comment on the last line should read "#assuming 5 < len(timesteps)".
On Thu, Mar 31, 2016 at 5:07 PM, Scott, W Alan <wasc...@sandia.gov> wrote:
> Perfect, thanks.
>
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com
Here's a sample script:
from paraview.simple import *
# Get a list of all available timesteps.
timeKeeper = GetTimeKeeper()
timesteps = timeKeeper.TimestepValues
# Now make animation scene go to a specific timestep:
scene = GetAnimationScene()
scene.AnimationTime = timesteps[5] # assuming 5 >
Lloyd,
For a headless server with K80s, you cannot use binaries distributed
from paraview.org. I'd suggesting building ParaView from source with
EGL support (refer to
https://blog.kitware.com/off-screen-rendering-through-the-native-platform-interface-egl/).
Andy, can you point Lloyd to any
> In the RequestInformation section of a
> Programmable Filter, I have the following line:
>
> if inputs[0].VTKObject.GetCell(0).GetClassName() == 'vtkPolyLine':
One should not access data in RequestInformation. Data is not expected
to be available in this pass. It can work in certain cases where
Folks,
ParaView 5.0.1 is now available for download [1]. Please refer to the
release notes on the Kitware blog [2]. As always, we look forward to
your feedback [3].
Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
Rich,
Attached is a sample script that you can run using pvpython or pvbatch or
vtkpython executables.
Utkarsh
On Tue, Mar 29, 2016 at 1:35 PM, Cook, Rich wrote:
> I'm still trying to solve my ellipsoid puzzle.
> From looking around online, I've found a promising avenue.
> Thank you for your email. I used volume(input) expression for my case and
> for the sphere from the the sources but again I got an error in both of
> cases which is AttributeError: 'builtin_function_or_method' object has no
> attribute 'NewInstance'. See picture attached.
Use "inputs[0]"
Not directly, but here's a way to do it using internal API (aka the
API may change in future).
>>> from paraview.simple import *
>>> from paraview import servermanager
>>> t = servermanager.CreateProxy("transforms", "Transform")
>>> tp = servermanager._getPyProxy(t)
>>> tp.Matrix=[1,0,0,
Looks like you're not only running on a machine without a GPU but also
without an accessible XServer. If that's the case, you'll need to use
the OSMesa version of ParaView (not sure if that's available in your
distribution) or build one yourself. This wiki page may help shed some
light on how to
David,
My responses are inline.
> Next step is to test multiCores on local. i read the doc (which speak only
> about PV v4 ...) and see that we have to compile pvserver.
Not necessarily. Only if you want to use it on HPC system with
platform specific MPI implementation. Otherwise you can simply
>
>> Utkarsh,
>> Thanks for notification. I will try this version as soon as possible.
>>
>> 2016-03-21 4:41 GMT+03:00 Utkarsh Ayachit <utkarsh.ayac...@kitware.com>:
>>>
>>> Andrew,
>>>
>>> ParaView 5.0.1-RC2 binaries are now avail
It's still there. It's an advanced property and hence not visible by
default. Just search for "Backface" in the search box on top of the
Properties panel. Or use the "gear" button. You may want to give this
post a gander:
> for info, i need to run the pvserver in mpi, + paraview cient to connect on
> it. but is there another component to launch (a renderer or like ?)
Nope, that's all you need. Check out the first chapter of the ParaView
GUide. It gives a quick overview of the executables involved and how
they play
> xxx@xxx:/data/build-paraview/install/bin$ ./mpirun -np 6 pvserver &
> [1] 23099
> [proxy:0:0@chalo-fl] HYDU_create_process (./utils/launch/launch.c:69): execvp
> error on file pvserver (No such file or directory)
Try running it as:
> ./mpirun -np 6 ./pvserver
Utkarsh
Folks,
ParaView 5.0.1-RC2 is now available for download [1]. For fixes that
went into this release, refer to the change log on bug tracker [2].
- The ParaView team
[1] http://www.paraview.org/download/
[2] http://www.paraview.org/Bug/changelog_page.php
Andrew,
ParaView 5.0.1-RC2 binaries are now available for download. Please
give them a try and let me know if are still seeing the Ensight issue.
Thanks
Utkarsh
On Thu, Mar 17, 2016 at 10:20 AM, Utkarsh Ayachit
<utkarsh.ayac...@kitware.com> wrote:
> The binaries have not yet been
Jim,
The way it is currently implemented, it's fixed after the first call
to coprocessor.DoLiveVisualization().
Utkarsh
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
> The dot "." in the array name is causing problems. Because it is a Python
> expression, the interpreter thinks you are asking for an attribute "water"
> from a class or module.
FYI, ParaView uses paraview.make_name_valid()[1] function to sanitize
array names in Python. Any character not a "_"
Hadrien,
Something's not exactly right with the build of ParaView you're using.
When I try to open the dataset with 5.0.0 binaries from paraview.org,
it opens fine when "Xdmf Reader" is selected in the Select Reader
dialog (fails with Xdmf3 Reader).
Can you try the binaries from paraview.org to
lease for Win64:
> ParaView-5.0.1-RC1-Qt4-OpenGL2-Windows-64bit.zip
> I tried the same big EnSight case and the same error appeared (stat failed).
> Should be this release "patched" or it's not corrected yet and I should wait
> for another version?
> Thanks.
>
> 2016-03-09
What dataset are you using? Can you try reproducing the same with one
of the "Sources" or datasets in ParaViewData or sharing a sample
dataset to reproduce it? Attached state file works for me.
On Mon, Mar 14, 2016 at 5:58 AM, Megdich Islem wrote:
> Hi
>
> I applied the
401 - 500 of 3111 matches
Mail list logo