Change at https://gitlab.com/petsc/petsc/-/merge_requests/6382
Satish
On Tue, 18 Apr 2023, Satish Balay via petsc-users wrote:
> I think its best if configure can handle this automatically (check for broken
> compilers). Until then - perhaps we should use:
>
>
> diff --git a/include/petsc/pri
It sounds like we should do reference counting on the internal data
structures used by COO>.
--Junchao Zhang
On Wed, Apr 26, 2023 at 3:59 PM Barry Smith wrote:
>
>Yes, it looks like a bug since no one tested this situation.
>
>MatSetPreallocationCOO() is pretty heavy memory-wise. It ess
Yes, it looks like a bug since no one tested this situation.
MatSetPreallocationCOO() is pretty heavy memory-wise. It essentially keeps a
copy of all the coo_i, coo_j indices within the Mat as well as the usual matrix
information. So in your scenario, you will have two copies of all this
Dear PETSc developers,
I am trying to use the MatSetValuesCOO function (very appropriate and
performant for my case) but I am encountering a problem when I use it on
a Mat obtained with MatDuplicate. It seems that the non-zero pattern is
preserved by MatDuplicate, but not the "COO information"
> --with-opengl-dir=/usr/include/GL
Try:
--with-opengl=1
Assuming you have these installed
balay@petsc-gpu-01:~$ dpkg -S /usr/lib/x86_64-linux-gnu/libGL.so
/usr/lib/x86_64-linux-gnu/libGLU.so
libgl-dev:amd64: /usr/lib/x86_64-linux-gnu/libGL.so
libglu1-mesa-dev:amd64: /usr/lib/x86_64-linux-gnu/
yes - if you need mumps:
./configure --download-mpich --download-mumps --download-scalapack
make
make check
Also we recommend using latest petsc release - i.e petsc-3.19.0
Satish
On Wed, 26 Apr 2023, 권승리 / 학생 / 항공우주공학과 wrote:
> thank you.
>
> As you said, I did run the command. But I didn't
thank you.
As you said, I did run the command. But I didn't remove the "arch"
directory.
//
cd #petcs_dir
make
//
After that, makefile works well.
But errors are occured like as below,
[0]PETSC ERROR: - Error Message
On Wed, Apr 26, 2023 at 6:42 AM 권승리 / 학생 / 항공우주공학과
wrote:
> Thank you for your reply.
>
> This problem occurred after I downloaded mpich.
>
This is not the reason. The error say "libpetsc is not located
in /home/ksl/petsc/arch-linux-c-debug/lib". So there is some reason it is
not there.
> Is
Remove the "arch" directory to start with a clean build. If the new build
fails then send use the configure and make .log files
On Wed, Apr 26, 2023 at 6:42 AM 권승리 / 학생 / 항공우주공학과
wrote:
> Thank you for your reply.
>
> This problem occurred after I downloaded mpich.
>
> Is there any way to solv
Thank you for your reply.
This problem occurred after I downloaded mpich.
Is there any way to solve this problem? Or Do I have to reinstall PETSc?
Best regards
Seung Lee Kwon
2023년 4월 26일 (수) 오후 7:05, Matthew Knepley 님이 작성:
> On Wed, Apr 26, 2023 at 6:02 AM 권승리 / 학생 / 항공우주공학과
> wrote:
>
>>
On Wed, Apr 26, 2023 at 6:02 AM 권승리 / 학생 / 항공우주공학과
wrote:
> Dear developers
>
> Could you recommend the error messages below?
>
> /home/ksl/petsc/arch-linux-c-debug/bin/mpicxx -Wall -Wwrite-strings
> -Wno-strict-aliasing -Wno-unknown-pragmas -Wno-lto-type-mismatch
> -fstack-protector -fvisibilit
Dear developers
Could you recommend the error messages below?
/home/ksl/petsc/arch-linux-c-debug/bin/mpicxx -Wall -Wwrite-strings
-Wno-strict-aliasing -Wno-unknown-pragmas -Wno-lto-type-mismatch
-fstack-protector -fvisibility=hidden -g -O0 -I/home/ksl/petsc/include
-I/home/ksl/petsc/arch-linux-c
12 matches
Mail list logo
