configure the filter, to change the second input (clik wrng obj), I have the
warning message dialog, then clik OK then he segfault. [?]
1831
QAbstractItemModel::endRemoveRows: Invalid index ( 7 , 0 ) in model
pqPipelineModel(0x4942310)
1837
1844
1855
[4]+ Segmentation fault paraview
<<320.gif>>
This issue has been fixed in CVS late last week. Is your ParaView
up-to-date?
Utkarsh
On Sun, Dec 6, 2009 at 6:24 PM, Bam Ting wrote:
> configure the filter, to change the second input (clik wrng obj), I have
> the warning message dialog, then clik OK then he segfault. [?]
>
> 1831
> QAbstractI
Hi there,
I try to use the OpenGL2 Rendering backend in Paraview 5.0.1 on Archlinux with
an nvidia graphics card.
The setup involves running paraview with VirtualGL in a x2go session, and I
always get the following error:
———
ERROR: In
/home/gk772/abs/paraview/src/ParaView-v5.0.1-source/VTK/Re
When I try to run pvpython on this computer, it segfaults trying to import
servermanager. If I try to open the python shell from inside paraview,
paraview crashes.
[dor...@dave experiment]$ pvpython
Python 2.6 (r26:66714, Mar 17 2009, 11:44:21)
[GCC 4.4.0 20090313 (Red Hat 4.4.0-0.26)] on linux2
T
Paraview segfaults when attempting to read Armadillo.ply from Stanford:
http://graphics.stanford.edu/pub/3Dscanrep/armadillo/Armadillo.ply.gz
The segfault happens both with the system PV on Fedora 20 :
$ rpm -q paraview
paraview-4.1.0-1.fc20.x86_64
and with the nightly dashboard version.
This
Hi,
I'm trying to reproduce a simulation with ParaView 4.3.1 and it always
crashes when I start it. You can find the backtrace below:
=
Process id 6681 Caught SIGSEGV at 0x925b124 address not mapped to object
Program Stack:
WARNING: The s
As I understand it VirtualGL should transparently forward OpenGL/GLX/etc
calls from the server to the client so that the client GPU is used. So my
guess would be to first try running PV on the client and see if it works.
If that seems to work fine then you know your client graphics supports PVs
use
I've had similar issues with VirtulGL and VTK in the past. The "Shader
object was not initialized, cannot attach it." error is often the result of
some sort of required OpenGL version support for a specific call is
lacking. A few questions:
- Are you able to run on the actual machine without
Dear Chuck, dear Ken,
thanks for the replies.
> I've had similar issues with VirtulGL and VTK in the past. The "Shader
> object was not initialized, cannot attach it." error is often the result of
> some sort of required OpenGL version support for a specific call is lacking.
> A few question
Hi Harald,
I don't have an answer to your VGL problem yet, but in the mean time, are
you tied to having to use it that way? If not, you also have the option of
running ParaView in client / server mode which may actually be more ideal
for your situation: i.e. with pvserver running on the headless
Dear Chuck,
thanks a lot for this suggestion. I never thought about this approach for this
setup!
That would probably really be a great solution. I’ll give this tomorrow a try.
Thank you!
Harald
> Am 11.04.2016 um 20:54 schrieb Chuck Atkins :
>
> Hi Harald,
>
> I don't have an answer to your
If I use this option via the X-server on the remote machine:
> I don't have an answer to your VGL problem yet, but in the mean time, are you
> tied to having to use it that way? If not, you also have the option of
> running ParaView in client / server mode which may actually be more ideal for
>
> I have: Server Type = Client/Server
> Host=localhost
> Port=11772
> Command: ssh -L 11772:remote-box:11772 user@remote-box pvserver
> --server-port=11772
>
When remotely launching a pvserver in this sort of configuration (i.e. egl
+ directly via an ssh command), a few things make this easier
Dear Chuck,
thanks a lot for your continued support.
> • Server Type = Client / Server (reverse connection)
> • Port: 11772
> • Command:
> xterm -e ssh -R 11772:localhost:11772 user@remotebox
> /path/to/install/bin/pvserver --disable-xdisplay-test --reverse-connection
> --clie
Unfortunately I suspect this is an issue with NVIDIA driver. Their EGL
support is still brand new and currently seems to be fairly brittle between
driver releases so perhaps best to wait until it settles a bit and just
stick with X for now :-(. Are you able to use the X+OpenGL2 (i.e. no egl)
pvser
> Unfortunately I suspect this is an issue with NVIDIA driver. Their EGL
> support is still brand new and currently seems to be fairly brittle between
> driver releases so perhaps best to wait until it settles a bit and just stick
> with X for now :-(. Are you able to use the X+OpenGL2 (i.e. no
The X+OpenGL2 via pvserver works fine for me now.
However, my colleagues with older local laptops do have some trouble.
My local system uses:
OpenGL Version 4.1 INTEL-10.6.33
OpenGL Renderer Intel Iris Graphics 6100
This works nicely.
With an older graphics card like:
OpenGL Version 3.3 INTEL-10
Hi,
just to round this thread up:
The problem with the limited screen (the ungarbled output is VGA 640x480) can
be resolved by
using offscreen rendering, so I guess this is somewhat related to the graphics
card, though the
connection information still shows the nvidia card being used in that ca
Hi,
running ParaView 5.3 (self-compiled or binaries from the webpage) i got
an segfault. Find the output of the debug below. However - using
ParaView 5.2 everything is fine.
In 5.3 i tried Qt4 and Qt5, OpenGL and OpenGL2 - always the same.
Any ideas?
Stefan
paraview --enable-bt
ASSE
I've committed a fix a little while ago. Try updating again.
Utkarsh
On Mon, May 11, 2009 at 12:29 PM, David Doria wrote:
> When I try to run pvpython on this computer, it segfaults trying to import
> servermanager. If I try to open the python shell from inside paraview,
> paraview crashes.
>
>
Hello!
I am facing a segfault with a custom filter. Here a minimalistic setup
to reproduce the problem, Ubuntu 10.10 64bit:
I have copied the original vtkImageClip class, as well as its
ServerManager xml part, merely renaming it to vtkMyImageResample. I
have added a plugin like
ADD_PARAVIEW_PLU
This is indeed a bug in vtkPLYReader. Attached is a patch that fixes the issue.
diff --git a/IO/PLY/vtkPLYReader.cxx b/IO/PLY/vtkPLYReader.cxx
index 437d87a..9cfe657 100644
--- a/IO/PLY/vtkPLYReader.cxx
+++ b/IO/PLY/vtkPLYReader.cxx
@@ -289,8 +289,8 @@ int vtkPLYReader::RequestData(
if ( int
Hi Sergi,
Could you clarify when you are seeing this crash? Is it right when starting
ParaView or when first loading a data set?
Thanks,
Cory
On Tue, Jun 23, 2015 at 8:55 AM, Sergi Mateo Bellido <
sergi.mateo.bell...@gmail.com> wrote:
> Hi,
>
> I'm trying to reproduce a simulation with ParaVie
Sergi,
I can confirm the crash you are seeing in the same location in the code.
I'm looking for the cause.
What software produced these data files?
Thanks,
Cory
On Wed, Jul 1, 2015 at 1:59 AM, Sergi Mateo Bellido <
sergi.mateo.bell...@gmail.com> wrote:
> Hi Cory,
>
> Thanks for your answer. I
Hi Cory,
Thanks for your time. These data files have been produced by a software
that I'm developing with some colleagues.
Best regards,
Sergi
On 07/01/2015 03:59 PM, Cory Quammen wrote:
Sergi,
I can confirm the crash you are seeing in the same location in the
code. I'm looking for the ca
Hi Sergi,
I played with your data set a little but haven't found what is wrong. I am
suspicious of two things in the data file, the extent and the offset in the
second data array (it looks too small).
What are the dimensions of your grid? Note that the whole extent upper
values need to be the dim
Hi Cory,
Thanks for your time. I have been playing a bit with the files too and I
realized that replacing the whole_extent of each *.vti by the whole
dataset everything works.
I would like to generate something like this:
http://vtk.1045678.n5.nabble.com/Example-vti-file-td3381382.html . In
Sergi,
Your VTI file extents should only describe the region of the whole image
they occupy, so you are on the right track. In situations like these where
it isn't obvious what is wrong, I tend to start from the beginning with a
very small example and build up from there. For example, you could st
Hi Cory,
Your intuition was right: the problem is related in some way with the
offset. I've changed the DataMote to ASCII and everything worked :)
Note that in this mode the offset field is not used, instead of that VTK
generates a DataArray.
I would like to know how the offset is computed
Hi again,
I've just tried storing the data as a binary and It crashes. In this
case we are not using the offset field either.
May the problem be related to the data compression?
Best,
Sergi
On 07/17/2015 03:38 PM, Sergi Mateo Bellido wrote:
Hi Cory,
Your intuition was right: the problem i
Hello Stefan
Does this happen when you startup ParaView, if not, what are you tring to
do before the segfault ?
It looks like you are trying to Load a file while connected to a server, is
that right ?
Regards,
Mathieu Westphal
On Thu, May 4, 2017 at 9:06 AM, Stefan Melber wrote:
> Hi,
>
> run
Hello Stefan
Can you try to reproduce your problem by running paraview without user
settings:
./bin/paraview -dr
Regards,
Mathieu Westphal
On Thu, May 4, 2017 at 9:27 AM, Mathieu Westphal <
mathieu.westp...@kitware.com> wrote:
> Hello Stefan
>
> Does this happen when you startup ParaView, if n
Hi Mathieu,
no - not connected to a server - just the GUI version without. However
- seems the user settings! With "-dr" it works. I will try what happens
when i delete my user-preferences for v5.3 ...
Stefan
Hello Stefan
Can you try to reproduce your problem by running paraview withou
Hi,
fixed. It was the user-configuration. The (broken) ini-file has a size
of 37 MB instead of 700 kB of an working one. Dont ask me why this file
was broken ...
Thanks for the fast solution!
Stefan
Hello Stefan
Can you try to reproduce your problem by running paraview without user
Dominik,
Can you attach the full source tar ball please? Would just make it
easier to try it out.
Thanks
Utkarsh
On Mon, May 23, 2011 at 8:12 AM, Dominik Szczerba wrote:
> Hello!
>
> I am facing a segfault with a custom filter. Here a minimalistic setup
> to reproduce the problem, Ubuntu 10.10
Hi,
The archive is here:
http://otoro.ethz.ch/~dominik/tmp/plugin.tar.bz2
Once again, the filter vtkMyImageResample is just a copy of
vtkImageChangeInformation with a customised name. I have also tried
vtkImageClip and vtkImageExtractVoi - they all segfault in the same
location. Note, removing t
I have found out the reason to be VTK and ParaView conflict. It's
described on the Wiki, but I was not aware I have this problem,
because the libs listed by ldd plugin.so were pointing to ParaVIew's
VTK. But I do have VTK built independently elsewhere, if I rename it ,
the problem is gone. Apparent
Hi Matthieu,
My hunch is that there is a problem with the OpenGL provided by VirtualBox
with 3D acceleration enabled. I have not found 3D acceleration to work well
with my Ubuntu 140.04 installation, so I just disable it.
Could you try disabling 3D acceleration and see if ParaView still crashes?
What Cory suggested may be it. I can't spot anything fishy in the
CMakeCache.txt. Also try running another OpenGL enabled app, eg.
glxgears to see if that works. I believe it's provided by the
`mesa-utils` package on Ubuntu.
Utkarsh
On Mon, Sep 14, 2015 at 10:05 AM, Cory Quammen wrote:
> Hi Matt
org
Subject: Re: [Paraview] Segfault in ParaView 4.4 RC2
What Cory suggested may be it. I can't spot anything fishy in the
CMakeCache.txt. Also try running another OpenGL enabled app, eg.
glxgears to see if that works. I believe it's provided by the
`mesa-utils` package on Ubuntu.
Utkarsh
On Mon,
Matthieu,
> - If I run the application from the VM's graphical interface, it runs fine.
> It only gives me the OpenGL warning I mentioned before. BUT the generated
> file has a big black area (see image_2.png attached). Also I see a window
> appear for a brief moment with the correct (full) vie
Matthieu,
Good news, I just saw the black window issue too on my build. I'll
track it down and get back to you.
Utkarsh
On Tue, Sep 15, 2015 at 9:12 AM, Utkarsh Ayachit
wrote:
> Matthieu,
>
>> - If I run the application from the VM's graphical interface, it runs fine.
>> It only gives me the O
NVM...those were from your original tarball. I thought they were
generated as an output from my run :). It's indeed an X issue in both
cases. Couple of options:
1. Do a Mesa3D build locally on the VM. Then set LD_LIBRARY_PATH to
point to the generated OpenGL libs and run ParaView/Catalyst. That'll
m: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
Sent: Tuesday, September 15, 2015 8:31 AM
To: Dorier, Matthieu
Cc: Cory Quammen; paraview@paraview.org
Subject: Re: [Paraview] Segfault in ParaView 4.4 RC2
NVM...those were from your original tarball. I thought they were
generated as an output from my ru
ier, Matthieu
[mdor...@anl.gov]
Sent: Tuesday, September 15, 2015 11:00 AM
To: Utkarsh Ayachit
Cc: paraview@paraview.org
Subject: Re: [Paraview] Segfault in ParaView 4.4 RC2
Thanks a lot Utkarsh!
In the mean time I tried my code on the Blue Waters machine at NCSA and it
works like a charm, so yes,
> From: ParaView [paraview-boun...@paraview.org] on behalf of Dorier, Matthieu
> [mdor...@anl.gov]
> Sent: Tuesday, September 15, 2015 11:00 AM
> To: Utkarsh Ayachit
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] Segfault in ParaView 4.4 RC2
>
@paraview.org
Subject: Re: [Paraview] Segfault in ParaView 4.4 RC2
Matthieu,
Simply set the CMake variable OPENGL_glu_LIBRARY to empty. I think
you're pointing it to non-existant
/home/mdorier/local/mesa/lib/libGLU.so and hence the issue. If I am
not mistaken, GLU is optional only required for ce
> From: Utkarsh Ayachit [utkarsh.ayac...@kitware.com]
> Sent: Tuesday, September 15, 2015 3:21 PM
> To: Dorier, Matthieu
> Cc: paraview@paraview.org
> Subject: Re: [Paraview] Segfault in ParaView 4.4 RC2
>
> Matthieu,
>
> Simply set the CMake variable OPENGL_glu_LIBRARY to empty. I
Dear All,
I would like to use xdmf file format for exporting polyhedral mesh
results from a CFD code to be opened with Paraview. If I'm not wrong
Paraview 5.2.0 should be able to read/write such kind o files.
Just to understand the format of the xmf file, I've been trying to open a
very easy
ng problem with
client/server.
Paraview is compiled on a remote cluster with osmesa support, by hand (paraview
superbuild still fails at this time), it is v5.3.0-489-gdbdb86747e.
If I launch pvserver (mpirun -np 2 pvserver ) on the remote cluster and try to
connect from my PC, paraview segfaul
Hi all,
I've had a serious issue since last week now:
Whenever I visualize a polygonal Mesh in the Slice View or orthogonal slice
view:
- in slice view: Paraview crashes as soon as I click on any of the slice
cursors to grab it to another position.
- in orthographic slice view: I can scroll i
Hi,
I try to use hdf5-hyperslabs for the Geometry-section,
but this results in a segmentation fault of paraview 3.4.0 and 3.6.1.
Any ideas? I attached an example.
Greetings
Jens
test_geom_hslab.h5
Description: Binary data
http://www.w3.org/2001/XInclude"; >
with git master from this afternoon, I'm experiencing segfaults when I
try to open the color scale editor. seems to be related to
vtkPVProminentValuesInformation. As soon as I get 4 or more ranks I have
the segfault. Is this a known issue?
Program received signal SIGSEGV, Segmentation fault.
0
I'm having problems when using data with polyhedron cells. I get a
segfault when I run append data on the attached datasets. I've got a very
simple example - two datasets, one with 3 cells and other with 2 cells.
The steps to reproduce:
Load polyhedron1.vtu
Load polyhedron2.vtu
Select both, cho
Hi Alessandro,
I just tested the .xmf file on my Linux work-station using the ParaView
5.2 binaries from the Kitware webpage and everything works as expected.
Also, reading the .vtu file and saving the data as xdmf works correctly
on my machine.
I don't have a Windows PC and have never tested t
(paraview superbuild still fails at this time), it is
> v5.3.0-489-gdbdb86747e.
>
> If I launch pvserver (mpirun -np 2 pvserver ) on the remote cluster and try
> to connect from my PC, paraview segfault:
>
> ERROR: In
> /HA/sources/begou/PARAVIEW/build-thor/superbuild/paraview/s
On Mon, Jun 19, 2017 at 7:18 AM, Vogel Dorian wrote:
> Hi all,
>
> I've had a serious issue since last week now:
>
> Whenever I visualize a polygonal Mesh in the Slice View or orthogonal slice
> view:
>
> - in slice view: Paraview crashes as soon as I click on any of the slice
> cursors to grab it
Hello Cory,
Thanks for the follow-up.
Unfortunately I do still experience this issue, I gathered a bit more
information on the behavior of the issue:
Still using a 1x1x1 @(0,0,0) box:
-open second layout as tab
-open orthographic sliceview
-I can scroll on all slice views but ONLY in one d
Dorian,
Thanks for the followup and workaround. If you could share the data
set with me or tell me how to create it with a ParaView source, I can
take a closer look.
Thanks,
Cory
On Fri, Jul 7, 2017 at 4:33 AM, Vogel Dorian wrote:
> Hello Cory,
>
> Thanks for the follow-up.
>
>
>
> Unfortunatel
Hi Cory,
I am actually using the "Box" source, and just let the default settings for it:
X/Y/Z length = 1, center = (0,0,0).
Btw: It still occurs on a freshly compiled Paraview v5.4.0 with up-to-date mesa.
Best,
--
Dorian Vogel
On Friday, July 7, 2017 3:17:00 PM CEST Cory Quammen wrote:
Dorian,
Thanks for clarifying the source. Sorry I didn't understand from your
earlier email.
I just tried again with the official ParaView 5.4.0 binary and was
able to reproduce your crash.
I'll write up a bug report.
Thanks!
Cory
On Fri, Jul 7, 2017 at 9:23 AM, Vogel Dorian wrote:
> Hi Cory,
Greetings,
I'm using the SC17 preview of 5.5 of ParaView. I first noticed this error
with my own dataset but it appears with the simple test.csv I've included.
To reproduce the segfault:
Load the attached (or presumably any) CSV points file.
Run the TableToPoints filter.
Assign the X/Y/Z column d
Steps to reproduce:
Start pvserver running parallel 2 ranks
Open the attached dataset, load b array
Slice the dataset such that the slice contains no data from at least one
rank.
Color slice by b array magnitude (default)
Open the color scale editor -> crash
I added the test dataset to the bug
Hi Burlen,
I'm working on it. It shouldn't take too long to fix. Thanks for the report.
David
On May 6, 2013, at 1:13 PM, Burlen Loring wrote:
> Steps to reproduce:
>
> Start pvserver running parallel 2 ranks
> Open the attached dataset, load b array
> Slice the dataset such that the
great, thanks!
On 05/06/2013 12:17 PM, David Thompson wrote:
Hi Burlen,
I'm working on it. It shouldn't take too long to fix. Thanks for the report.
David
On May 6, 2013, at 1:13 PM, Burlen Loring wrote:
Steps to reproduce:
Start pvserver running parallel 2 ranks
Open the attached
Below is the fix:
diff --git a/Filters/Core/vtkAppendFilter.cxx
b/Filters/Core/vtkAppendFilter.cxx
index 674135c..1f8878f 100644
--- a/Filters/Core/vtkAppendFilter.cxx
+++ b/Filters/Core/vtkAppendFilter.cxx
@@ -302,6 +302,7 @@ int vtkAppendFilter::RequestData(
if (ug && ds->GetCellType(ce
Hi Paul,
thanks for providing the fix. Do you mind pushing that patch to gerrit and
adding Utkarsh and I as a reviewer?
Thanks,
Seb
PS: More information can be found here on how to push a patch to gerrit.
http://www.vtk.org/Wiki/VTK/Git/Develop
On Mon, Jan 6, 2014 at 12:35 PM, Paul Edwards wr
In my ongoing quest to get a filter to process multiple time steps worth of
data into a single result field I've attempted to derive a C++ vtk filter from
vtkMultiTimeStepAlgorithm. However, the attached simple example segfaults out
when I try to apply it in paraview. All it should do is a sh
The output warnings you are seeing are unrelated and fixed in master.
Can reproduce the bug with 5.4.1 binary on linux.
David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
On Tue, Dec 5, 2017 at 2:10 PM, Wyatt Spear wrote:
> Gr
Nope, 5.4.1 seems to work correctly.
=Wyatt
On Tue, Dec 5, 2017 at 11:29 AM, David E DeMarle
wrote:
> The output warnings you are seeing are unrelated and fixed in master.
>
> Can reproduce the bug with 5.4.1 binary on linux.
>
>
>
>
> David E DeMarle
> Kitware, Inc.
> Principal Engineer
> 21 Co
Crashes for me.
David E DeMarle
Kitware, Inc.
Principal Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909
On Tue, Dec 5, 2017 at 2:59 PM, Wyatt Spear wrote:
> Nope, 5.4.1 seems to work correctly.
> =Wyatt
>
> On Tue, Dec 5, 2017 at 11:29 AM, David E DeMarle > wrote:
I just tried it with my larger data set (easier to select individual cells)
and it crashed with 5.4.1. I'm not sure what the difference was with the
smaller data set in 5.4.1 that let it work.
=Wyatt
On Tue, Dec 5, 2017 at 12:00 PM, David E DeMarle
wrote:
> Crashes for me.
>
>
> David E DeMarle
Hi,
I get a segfault with the git version
f7aac037722d9d13b75d9fdb15a1053c0874c6c6. Here is a minimal set of
steps to reproduce:
$ wget -O mug.e
https://github.com/idaholab/moose/blob/devel/examples/ex01_inputfile/mug.e?raw=true
$ paraview mug.e
Click "Apply"
Click "View -> Multi-block Inspector
Mark,
You're simply missing a call to `this->SetNumberOfOutputPorts(1)` in
your constructor. That will get past the segfault.
Besides that, look at `vtkTemporalArrayOperatorFilter` as an example
for how to overload `RequestDataObject` to create correct output
dataset type, `RequestInformation` to
Utkarsh,
Thanks, that was a very helpful reference to vtkTemporalArrayOperatorFilter.
Mark
From: Utkarsh Ayachit
Sent: Monday, November 27, 2017 1:16:22 PM
To: Messner, Mark Christian
Cc: paraview@paraview.org
Subject: Re: [Paraview] Segfault with simple C
Hi,
In the meantime I found out that the segfault only happens when pvpython is
being run inside a NX session (see http://www.nomachine.com/). So, most likely
there is nothing wrong with ParaView, I simply need an additional installation
compiled with Mesa instead of OpenGL, to be used in NX sessi
Yup, I can reproduce it. I've pushed a fix
(http://www.paraview.org/Bug/view.php?id=15367).
Attached is the patch against git/master.
On Mon, Mar 9, 2015 at 3:29 PM, Ondřej Čertík wrote:
> Hi,
>
> I get a segfault with the git version
> f7aac037722d9d13b75d9fdb15a1053c0874c6c6. Here is a minimal
I simplified the example and found, that the segfault is independed of
hyperslab.
The attached simplified xdmf-file segfaults in paraview 3.4 and 3.6, too.
Any ideas?
This should work. At least I found an example and cannot see the
difference:
www.hpc.lsu.edu/training/20090304/presentations/sciviz
Hi,
apologies for bumping my own message, but looking at the thread view
[1] of the mailing list archives I just realised that strangely my
email was filed under a completely unrelated thread (even though I
hadn't replied to any messages) and maybe this is why it got lost in
people's inboxes.
So
Hi,
It sounds like you probably have multiple versions of the vtk libraries
installed someplace in your path. Maybe the FEniCS package ships it's own
version of the vtk libraries? If FEniCS imports a different version of
vtk, then paraview won't be able to import vtk within the same memory
space
Hi Pat!
[Apologies for sending you this twice, I accidentally didn't hit 'reply
all'.]
Many thanks for the detailed reply! Indeed, I'm suspecting a conflict
between different vtk versions, but I don't know which ones could be the
culprits. I'm not sure the issue is actually related to the FEniCS
See, if you can "import vtk", then you're probably importing a version of
the vtk libraries that are different than the ones ParaView uses. What
version of ParaView are you using and how did you install ParaView? Did
you build from source, install the binaries from paraview.org, or apt-get
instal
Hi Pat,
many thanks for your reply and further thoughts. I haven't been able to
conduct more in-depth debugging yet, but from what you have said I'm not
even sure that's necessary since you say that incompabilities are to be
expected anyway.
However, does this mean that using Paraview in conjunct
Hi Max,
Maybe you could back up a bit and explain what you're trying to
accomplish? Maybe we can suggest another approach that will work while
avoiding the incompatibilities vtk version requirements of dolfin and
paraview.
Have you tried running your script using 'pvpython' as the interpreter
in
Hi Pat,
Maybe you could back up a bit and explain what you're trying to
> accomplish? Maybe we can suggest another approach that will work while
> avoiding the incompatibilities vtk version requirements of dolfin and
> paraview.
>
Of course! Apologies that I didn't explain this in more detail be
85 matches
Mail list logo
