: [Paraview] Python interpreter not being created for
coprocessing?
** **
Ok, glad to hear that coprocessing is working in some fashion. Now to
figure out how to get it running properly with your desired configuration.
Unfortunately at this point I don't know how to move forward except for
trying
)
VTK/CMakeLists.txt:334 (include)
Mark
*From:* Andy Bauer [mailto:andy.ba...@kitware.com]
*Sent:* Monday, August 27, 2012 11:59 AM
*To:* Vanmoer, Mark W
*Cc:* paraview@paraview.org
*Subject:* Re: [Paraview] Python interpreter not being created for
coprocessing
(include)
** **
Mark
** **
*From:* Andy Bauer [mailto:andy.ba...@kitware.com]
*Sent:* Monday, August 27, 2012 11:59 AM
*To:* Vanmoer, Mark W
*Cc:* paraview@paraview.org
*Subject:* Re: [Paraview] Python interpreter not being created for
coprocessing?
** **
Hi Mark
: paraview@paraview.org
Subject: Re: [Paraview] Python interpreter not being created for coprocessing?
Hmm, ParaView has been undergoing a lot of changes lately so it's been a bit
unstable. I just checked out a clean version and built it without any problems.
The SHA from
*Cc:* paraview@paraview.org
*Subject:* Re: [Paraview] Python interpreter not being created for
coprocessing?
** **
** **
On Thu, Aug 23, 2012 at 4:00 PM, Vanmoer, Mark W mvanm...@illinois.edu
wrote:
Two questions – is there a way to tell ctest where the ParaViewData is
without
/vtkModuleTop.cmake:52 (vtk_module_check)
VTK/CMakeLists.txt:334 (include)
Mark
From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Monday, August 27, 2012 11:59 AM
To: Vanmoer, Mark W
Cc: paraview@paraview.org
Subject: Re: [Paraview] Python interpreter not being created for coprocessing?
Hi Mark
, 2012 3:06 PM
To: Vanmoer, Mark W
Cc: paraview@paraview.org
Subject: Re: [Paraview] Python interpreter not being created for coprocessing?
On Thu, Aug 23, 2012 at 4:00 PM, Vanmoer, Mark W
mvanm...@illinois.edumailto:mvanm...@illinois.edu wrote:
Two questions - is there a way to tell ctest where
:* paraview@paraview.org
*Subject:* Re: [Paraview] Python interpreter not being created for
coprocessing?
** **
Hi Mark,
I think I can guess what the problem is but can't be certain without some
more information. My guess is that you're using ParaView 3.14.1 for this
and you're trying to use
, 2012 1:32 PM
To: Vanmoer, Mark W
Cc: paraview@paraview.org
Subject: Re: [Paraview] Python interpreter not being created for coprocessing?
It looks like you've built it properly. At least I don't see anything that
looks wrong. I think the reason you didn't get any coprocessing tests
Bauer [mailto:andy.ba...@kitware.com]
*Sent:* Thursday, August 23, 2012 1:32 PM
*To:* Vanmoer, Mark W
*Cc:* paraview@paraview.org
*Subject:* Re: [Paraview] Python interpreter not being created for
coprocessing?
** **
It looks like you've built it properly. At least I don't see anything
Hello,
I'm setting up someone's code to use coprocessing with OSMesa and
openmpi/pgi/cuda fortran on NCSA's Forge using ParaView from the git repo. I'm
getting segfaults and pgdbg gives me this error when coprocessorinitialize is
called:
[0] Signalled SIGSEGV at 0x2B62188CFD9A, function
Hi Mark,
I think I can guess what the problem is but can't be certain without some
more information. My guess is that you're using ParaView 3.14.1 for this
and you're trying to use the fortran interface but haven't built ParaView
with Python enabled. There were some dependency issues there that
12 matches
Mail list logo