This feature is under active development. I hope I can make it usable in a
couple of weeks. Thanks.
--Junchao Zhang
On Wed, Aug 21, 2019 at 3:21 PM David Gutzwiller via petsc-users
mailto:petsc-users@mcs.anl.gov>> wrote:
Hello,
I'm currently using PETSc for the GPU acceleration of simple
Definitely I will do. Thanks.
--Junchao Zhang
On Thu, Aug 22, 2019 at 11:34 AM David Gutzwiller
mailto:david.gutzwil...@gmail.com>> wrote:
Hello Junchao,
Spectacular news!
I have our production code running on Summit (Power9 + Nvidia V100) and on
local x86 workstations, and I can definitely
On Mon, 19 Aug 2019, Smith, Barry F. via petsc-dev wrote:
>
>
>PETSc folks.
>
> This announcement is for people who access PETSc from the BitBucket
> repository or post issues or have other activities with the Bitbucket
> repository
>
>We have changed the location of the PETSc
You have a copy of parmetis installed in /usr/lib this is a systems directory
and many compilers and linkers automatically find libraries in that location
and it is often difficult to avoid have the compilers/linkers use these. In
general you never want to install external software such
On Fri, 23 Aug 2019, Smith, Barry F. via petsc-users wrote:
> bsmith@es:~$ ldd /usr/lib/libparmetis.so.3.1
> linux-vdso.so.1 => (0x7fff9115e000)
> libmpi.so.1 => /usr/lib/libmpi.so.1 (0x7faf95f87000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7faf95c81000)
>
Compilers are supposed to prefer libraries in specified -L path before system
stuff.
>>
balay@es^~ $ ls /usr/lib/lib*metis*
/usr/lib/libmetis.a/usr/lib/libmetis.so.3.1 /usr/lib/libparmetis.so@
/usr/lib/libscotchmetis-5.1.so /usr/lib/libscotchmetis.so@
/usr/lib/libmetis.so@
> On Aug 22, 2019, at 6:48 PM, Balay, Satish wrote:
>
> Compilers are supposed to prefer libraries in specified -L path before system
> stuff.
Suppose to.
>
>>>
> balay@es^~ $ ls /usr/lib/lib*metis*
> /usr/lib/libmetis.a/usr/lib/libmetis.so.3.1 /usr/lib/libparmetis.so@
>
Does this crash on a PETSc example that uses elemental? For example run
src/ksp/ksp/examples/tests/ex40.c: with the arguments
-pc_type lu -pc_factor_mat_solver_type elemental
To get the stack trace
Add the command line option -start_in_debugger noxterm when you run your
> ./ex19: symbol lookup error: /usr/lib/libparmetis.so: undefined symbol:
> ompi_mpi_comm_world
For some reason the wrong parmetis library is getting picked up. I don't know
why.
Can you copy/paste the log from the following?
cd src/snes/examples/tutorials
make
Any reason for using petsc-3.10.5 and not latest petsc-3.11?
I suggest starting from scatch and rebuilding.
And if you still have issues - send corresponding configure.log and make.log
Satish
On Thu, 22 Aug 2019, Lailai Zhu via petsc-users wrote:
> sorry, Satish,
>
> but it does not seem to
10 matches
Mail list logo
