Acknowledgement sent
to Drew Parsons <[email protected]>:
New Bug report received and forwarded. Copy sent to Debian Science Maintainers <[email protected]>.
(Thu, 21 May 2020 03:18:04 GMT) (full text, mbox, link).
Source: metis
Severity: normal
We're discussing introducing a 64 bit-build for the computational
stack. This refers to 64-bit addressing to cells in meshes, etc.
c.f. Bug#953116 (petsc)
Bug#961108 (openmpi)
https://lists.debian.org/debian-science/2020/05/msg00051.html
BLAS is already 64-bit enabled.
For the 64-bit environment to work, it needs to be carried through all
along the library stack, from BLAS to PETSc.
MUMPS is in the middle. Its docs indicate that its 64-bit support
requires METIS to be 64-bit enabled.
Probably we want 2 separate builds, 32-bit (the current libmetis-dev)
and a separate 64-bit libmetis64-dev.
Opening this bug to track the chain of 64-bit package dependencies.
Subject: Re: Bug#961183: metis: providing a 64-bit build
Date: Thu, 21 May 2020 12:24:31 0800
Should add a caveat on the urgency: this bug report is Wishlist, really.
That's because mumps uses scotch rather than metis. This is because
parmetis is not available (not-free).
If the licence for parmetis became free, then we would use it with mumps
(and would be looking for a 64-bit build).
Drew
Acknowledgement sent
to Drew Parsons <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Science Maintainers <[email protected]>.
(Sat, 05 Jun 2021 11:36:03 GMT) (full text, mbox, link).
Package: metis
Followup-For: Bug #961183
64-bit integers are now available for several libraries.
64-bit PETSc is able to use 64-bit SuperLU-Dist, which we don't
currently have.
64-bit SuperLU-Dist requires 64-bit metis.
In principle 64-bit metis is simple to configure: set IDXTYPEWIDTH to
64 in metis.h.
The challenge that we need to address is the location of metis.h.
Currently it's located in /usr/include/metis.h (for the standard 32-bit build)
To distinguish between standard and 64-bit builds, we'd probably want to place
the 64-bit header in /usr/include/metis64/metis.h
-I/usr/include/metis64 can then be used by client applications. The
remaining challenge is that /usr/include/metis.h might be found
instead of /usr/include/metis64/metis.h, since -I/usr/include will
also often be used in build scripts.
I think the best solution is to "break" the builds of client
applications by moving the standard header from /usr/include/metis.h
to /usr/include/metis/metis.h. Then client applications will need to
be updated to add -I/usr/include/metis when using the standard build.
Acknowledgement sent
to Anton Gladky <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Science Maintainers <[email protected]>.
(Sat, 05 Jun 2021 15:09:02 GMT) (full text, mbox, link).
Well, theoretically we can do it. But we need to do some kind
of a transition for all dependencies.
Regards
Anton
Am Sa., 5. Juni 2021 um 13:36 Uhr schrieb Drew Parsons <[email protected]
>:
> ...<skip>
> I think the best solution is to "break" the builds of client
> applications by moving the standard header from /usr/include/metis.h
> to /usr/include/metis/metis.h. Then client applications will need to
> be updated to add -I/usr/include/metis when using the standard build.
>
Subject: Re: Bug#961183: metis: providing a 64-bit build
Date: Sat, 05 Jun 2021 17:21:18 0200
Doing it through a formal transition request is sensible. There's a
backlog of numerical library upgrades (some still in the NEW queue)
waiting for bullseye to get released. Perhaps we can run this transition
at the same time as the others, process them all as a bulk transition.
We'll set it up in experimental first, of course.
I'll prepare the list of affected packages.
Drew
On 2021-06-05 17:07, Anton Gladky wrote:
> Well, theoretically we can do it. But we need to do some kind
> of a transition for all dependencies.
>
> Regards
>
> Anton
>
> Am Sa., 5. Juni 2021 um 13:36 Uhr schrieb Drew Parsons
> <[email protected]>:
>
>> ...<skip>
>> I think the best solution is to "break" the builds of client
>> applications by moving the standard header from /usr/include/metis.h
>> to /usr/include/metis/metis.h. Then client applications will need
>> to
>> be updated to add -I/usr/include/metis when using the standard
>> build.
Acknowledgement sent
to Drew Parsons <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Science Maintainers <[email protected]>.
(Sat, 05 Jun 2021 16:03:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Drew Parsons <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Science Maintainers <[email protected]>.
(Sat, 05 Jun 2021 16:06:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Drew Parsons <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Science Maintainers <[email protected]>.
(Sat, 12 Jun 2021 23:24:03 GMT) (full text, mbox, link).
Package: metis
Followup-For: Bug #961183
Hi Anton, I've prepared packaging for a 64-bit that I'm happy to push
(and upload).
Would you like me to push to salsa (experimental branch) for inspection?
Drew
Acknowledgement sent
to Anton Gladky <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Science Maintainers <[email protected]>.
(Sun, 13 Jun 2021 05:06:02 GMT) (full text, mbox, link).
Hi Drew,
> Would you like me to push to salsa (experimental branch) for inspection?
Yes, please.
Anton
Am So., 13. Juni 2021 um 01:24 Uhr schrieb Drew Parsons <[email protected]
>:
> Package: metis
> Followup-For: Bug #961183
>
> Hi Anton, I've prepared packaging for a 64-bit that I'm happy to push
> (and upload).
>
> Would you like me to push to salsa (experimental branch) for inspection?
>
> Drew
>
> --
> debian-science-maintainers mailing list
> [email protected]
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
>
Subject: Re: Bug#961183: metis: providing a 64-bit build
Date: Sun, 13 Jun 2021 10:35:12 0200
On 2021-06-13 07:02, Anton Gladky wrote:
> Hi Drew,
>
>> Would you like me to push to salsa (experimental branch) for
> inspection?
>
> Yes, please.
OK, pushed to experimental branch.
Bring the question of REALTYPEWIDTH to mind (the size of floating point
numbers). The "64-bit support" in other packages essentially concerns
integers (indexing) not floating point numbers, so I figure we don't
need to change REALTYPEWIDTH as well. Or if we do want to change
REALTYPEWIDTH, then we might want to change it in the standard build
too.
For comparison, SuperLU-Dist just uses double for values. Hypre uses
HYPRE_Real, which can be configured to single or double or longdouble
(default double). SCOTCH is mainly working with indices (integers
defined as SCOTCH_Num) but internally uses double more often than float
when it needs floating point numbers (it does use both). PETSc uses
PetscReal which can be configured single or double, float128 or fp16
(default double).
I figure it's simplest not to change REALTYPEWIDTH unless there's a
specific known need to make the change. We need to set IDXTYPEWIDTH to
64 to support extremely large systems with billions of degrees of
freedom, but that doesn't necessarily mean the floating point value at
each index also requires higher precision. On the other hand changing to
REALTYPEWIDTH=64 (even in standard libmetis) might better match the
default of other packages.
Apart from that question, I'm happy with the patch. As far as I'm
concerned it's ready to upload to experimental.
Drew
Acknowledgement sent
to PICCA Frederic-Emmanuel <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Science Maintainers <[email protected]>.
(Sun, 13 Jun 2021 09:09:02 GMT) (full text, mbox, link).
Subject: RE:Bug#961183: metis: providing a 64-bit build
Date: Sun, 13 Jun 2021 08:58:38 0000
Hello,
why there is no pkgconfig files provided with metis and metis64.
this simplify the configuration of packages depending on these libraries.
Cheers
Fred
Acknowledgement sent
to Drew Parsons <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Science Maintainers <[email protected]>.
(Tue, 15 Jun 2021 20:48:03 GMT) (full text, mbox, link).
Package: metis
Followup-For: Bug #961183
Hi Fred, I guess the simple reason why there's no pkgconfig for Metis
is that upstream does not provide one.
We could add one ourselves easily enough. But SCOTCH-Metis
compatibility would want to be taken into consideration. Historically
SCOTCH-Metis never had full compatibility (#506033, #653647), but
they're about to make a new release expected to address that.
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.