Thanks Barry and Sherry, it works like a charm :)
Best regards,
Felix
Zitat von Barry Smith :
Good. I have cleaned up the code and rebased the branch so if you
use it in the future you need to do
git fetch
git checkout master
git branch -D barry/2020-07-28/superlu_dist-single
git
Good. I have cleaned up the code and rebased the branch so if you use it in
the future you need to do
git fetch
git checkout master
git branch -D barry/2020-07-28/superlu_dist-single
git checkout barry/2020-07-28/superlu_dist-single
Do not just do a git pull in
PS:
I saw you committed a new version for the SUPERLU_DIST installer.
There is a missing ")" at the end of line 42.
Also I think one also has to add
self.addToArgs(args,'-DCMAKE_CXX_FLAGS:STRING','-I'+self.blasLapack.include)
as well (for me only adding the C flag raised the same error as
Yep, when I assign the mkl include directory to CPATH, it works :)
Best regards,
Felix
Zitat von Barry Smith :
On some systems, like my Mac, the environmental variable CPATH is
set to the appropriate directory for mkl.h when MKL is initialized
with
source
On some systems, like my Mac, the environmental variable CPATH is set to the
appropriate directory for mkl.h when MKL is initialized with
source /opt/intel/compilers_and_libraries/mac/bin/compilervars.sh intel64
hence the compiler can magically find mkl.h but this doesn't seem to be
Regarding MKL, superlu only uses some BLAS routines in MKL. If you have
alternative BLAS, you don't need to use MKL.
But, in my experience, on an Intel system, the compiler can correctly
include the path with mkl.h, that is, I don't need to do anything special.
I think mpiicc should work.
For the first case do
rm -rf arch-ci-linux-intel-mkl-single
looks like there might be some outdated material in that directory causing
the problem.
For the second and third I see in superlu_defs.h
#ifdef __INTEL_COMPILER
#include "mkl.h"
hence the use of Intel compiler
Felix,
The branch is ready. Just use
git checkout barry/2020-07-28/superlu_dist-single
./configure --download-superlu_dist --download-metis --download-parmetis
--download-ptscotch --with-precision=single and whatever else you use
Barry
It will automatically get the needed
Felix,
Sorry for the delay. Another issue came up with building SuperLU_DIST for
this formulation that Sherry has to look at.
We haven't forgotten you,
Barry
duplicate symbol '_FormFullA' in:
CMakeFiles/superlu_dist.dir/sreadhb.c.o
CMakeFiles/superlu_dist.dir/dreadhb.c.o
Hi Shery,
Yes, ideally we would like to compile PETSc in single precision and
simply run a single precision version of SUPERLU_DIST just like e.g.
MUMPS.
Best regards and thanks,
Felix
Zitat von "Xiaoye S. Li" :
Barry,
I have a branch 'Mixed-precision' working with single precision FP32.
Barry,
I have a branch 'Mixed-precision' working with single precision FP32. I
assume Felix wants to use superlu_dist from petsc. How do you want to
incorporate it in petsc?
https://github.com/xiaoyeli/superlu_dist
PS1: in this version, FP32 only works on CPU. FP64 and complex-FP64 all
work
Hi Sherry,
thanks, that would be awesome!
Best regards,
Felix
Quoting "Xiaoye S. Li" :
I can package a CPU version over the weekend.
Sherry
On Wed, Jul 22, 2020 at 6:04 AM wrote:
Hi Barry,
for now I just want to run everything in single on CPUs only with
SUPERLU_DIST. Maybe we will also
I can package a CPU version over the weekend.
Sherry
On Wed, Jul 22, 2020 at 6:04 AM wrote:
> Hi Barry,
> for now I just want to run everything in single on CPUs only with
> SUPERLU_DIST. Maybe we will also incorporate GPUs in the future, but
> there are no immediate plans yet. So if you could
Hi Barry,
for now I just want to run everything in single on CPUs only with
SUPERLU_DIST. Maybe we will also incorporate GPUs in the future, but
there are no immediate plans yet. So if you could provide the support,
that would be awesome.
Best regards,
Felix
Zitat von Barry Smith :
Yes. We will wait for his reply. -Sherry
On Tue, Jul 21, 2020 at 6:30 PM Barry Smith wrote:
>
> Thanks Sherry. But the CPU version runs correctly right so if Felix is
> only interested in CPUs then I could give it to him now?
>
> Barry
>
>
> On Jul 21, 2020, at 7:33 PM, Xiaoye S. Li
Thanks Sherry. But the CPU version runs correctly right so if Felix is only
interested in CPUs then I could give it to him now?
Barry
> On Jul 21, 2020, at 7:33 PM, Xiaoye S. Li wrote:
>
> Barry,
>
> We have a macro-ized basefile to produced all 4 precisions for SuperLU_DIST.
> In the
Barry,
We have a macro-ized basefile to produced all 4 precisions for
SuperLU_DIST. In the past, we didn't generate single precision code, since
there was no request.
Since now we started working on mixed precision algorithms. I generated
single precision code a few weeks ago, and fixed some
Felix,
What are your needs, do you want this for CPUs or for GPUs? Do you wish to
run all your code in single precision or just the SuperLU_Dist solver while the
rest of your code double?
If you want to run everything on CPUs using single precision then adding
the support is
Dear PETSc support team,
some time ago you told me that you are planning on releasing a version
that supports SUPERLU_DIST in single-precision soon. Can you tell me
roughly what time frame you had in mind?
Best regards,
Felix
19 matches
Mail list logo
