Re: [petsc-users] Inquiry about PetscDTSimplexQuadrature .

2023-06-23 Thread neil liu
Thanks, Matt. It seems DMPlexComputeCellGeometryFEM works well with the quadrature points to deliver Jacobian and inverse one. Will it be a good choice ? Have a good night. Thanks, On Fri, Jun 23, 2023 at 10:33 AM Matthew Knepley wrote: > On Fri, Jun 23, 2023 at 10:28 AM neil liu wrote: >

Re: [petsc-users] snes_type aspin without DA example

2023-06-23 Thread Karin
Dear Barry, I have started looking at the code but I miss an example using SNESNASMSetSubdomains. In fact I do not even find a single use of the function in PETSc. Could someone provide me with an example ? Thanks, Nicolas Le ven. 23 juin 2023 à 02:17, Barry Smith a écrit : > > A test would

Re: [petsc-users] snes_type aspin without DA example

2023-06-23 Thread Karin
In order to transfer from Python to C a list of int, real or bool as an input, there are the functions iarray_i, iarray_r and iarray_b. In order to transfer from C to Python a list of int, real, bool or pointers as an output, there are the functions oarray_i, oarray_r, oarray_b and oarray_p.

Re: [petsc-users] hypre-ILU vs hypre Euclid

2023-06-23 Thread Mark Adams
Alexander, let me add that Ilu is pretty commodity, and is available with our vendor, back ends, and that is probably the more reliable route. Hyper’s AMG Solver is state of the art, but their ilu is not their focus. Mark. On Fri, Jun 23, 2023 at 12:11 AM Jed Brown wrote: > It looks like

[petsc-users] Inquiry about PetscDTSimplexQuadrature .

2023-06-23 Thread neil liu
Dear Petsc developers, I am learning *PetscDTSimplexQuadrature *and plan to use it. I found that, in the biunit simplex (tetra), (-1,-1,-1),(1,-1,-1),(-1,1,-1),(-1,-1,1), degree 1: npoints 4, the sum of weights = 4/3(the volume of this simplex) degree 2 : npoints 8; For my previous experience, I

Re: [petsc-users] Inquiry about PetscDTSimplexQuadrature .

2023-06-23 Thread Matthew Knepley
On Fri, Jun 23, 2023 at 10:28 AM neil liu wrote: > Dear Petsc developers, > > I am learning *PetscDTSimplexQuadrature *and plan to use it. > I found that, in the biunit simplex (tetra), > (-1,-1,-1),(1,-1,-1),(-1,1,-1),(-1,-1,1), > degree 1: npoints 4, the sum of weights = 4/3(the volume of

Re: [petsc-users] hypre-ILU vs hypre Euclid

2023-06-23 Thread Alexander Lindsay
Thanks all for your replies. Mark, I’m a little unclear on what you said. My understanding is that PETSc ILU is serial only (or can be used as the sub PC in DD PCs).On Jun 23, 2023, at 3:35 AM, Mark Adams wrote:Alexander, let me add that Ilu is pretty commodity, and is available with our vendor,

Re: [petsc-users] hypre-ILU vs hypre Euclid

2023-06-23 Thread Alexander Lindsay
Based on https://github.com/hypre-space/hypre/issues/937 it sounds like hypre-ILU is under active development and should be the one we focus on bindings for. It does support 64 bit indices and GPU On Fri, Jun 23, 2023 at 8:36 AM Alexander Lindsay wrote: > Thanks all for your replies. Mark, I’m

Re: [petsc-users] Scalable Solver for Incompressible Flow

2023-06-23 Thread Alexander Lindsay
Hi Jed, I will come back with answers to all of your questions at some point. I mostly just deal with MOOSE users who come to me and tell me their solve is converging slowly, asking me how to fix it. So I generally assume they have built an appropriate mesh and problem size for the problem they

Re: [petsc-users] snes_type aspin without DA example

2023-06-23 Thread Barry Smith
Look at SNESSetUp_NASM() src/snes/nasm/nasm.c and see the if (dm) case. It calls DMCreateDomainDecomposition() to get subdms and then calls DMCreateDomainDecompositionScatters() to get the scatters that would be passed to SNESNASMSetSubdomains(). Then it builds the subsnes. These are the

Re: [petsc-users] snes_type aspin without DA example

2023-06-23 Thread Barry Smith
Take a look at setNestSubVecs() in /src/binding/petsc4py/src/petsc4py/PETSc/Vec.pyx it seems to deal with passing an array of PETSc objects. Likely there are additional instances where arrays of objects are passed between Python and C. I do not understand this code, but the Python

Re: [petsc-users] snes_type aspin without DA example

2023-06-23 Thread Karin
Thanks Barry, I'll check it out. Le ven. 23 juin 2023 à 18:57, Barry Smith a écrit : > > Take a look at setNestSubVecs() > in /src/binding/petsc4py/src/petsc4py/PETSc/Vec.pyx it seems to deal with > passing an array of PETSc objects. Likely there are additional instances > where arrays of

Re: [petsc-users] Scalable Solver for Incompressible Flow

2023-06-23 Thread Pierre Jolivet
> On 23 Jun 2023, at 9:39 PM, Alexander Lindsay > wrote: > > Ah, I see that if I use Pierre's new 'full' option for > -mat_schur_complement_ainv_type That was not initially done by me (though I recently tweaked MatSchurComplementComputeExplicitOperator() a bit to use KSPMatSolve(), so that

Re: [petsc-users] Scalable Solver for Incompressible Flow

2023-06-23 Thread Pierre Jolivet
> On 23 Jun 2023, at 10:06 PM, Pierre Jolivet wrote: > > >> On 23 Jun 2023, at 9:39 PM, Alexander Lindsay >> wrote: >> >> Ah, I see that if I use Pierre's new 'full' option for >> -mat_schur_complement_ainv_type > > That was not initially done by me Oops, sorry for the noise, looks like

Re: [petsc-users] Scalable Solver for Incompressible Flow

2023-06-23 Thread Alexander Lindsay
I guess it is because the inverse of the diagonal form of A00 becomes a poor representation of the inverse of A00? I guess naively I would have thought that the blockdiag form of A00 is A00 On Fri, Jun 23, 2023 at 10:18 AM Alexander Lindsay wrote: > Hi Jed, I will come back with answers to all

Re: [petsc-users] Scalable Solver for Incompressible Flow

2023-06-23 Thread Alexander Lindsay
Ah, I see that if I use Pierre's new 'full' option for -mat_schur_complement_ainv_type that I get a single iteration for the Schur complement solve with LU. That's a nice testing option On Fri, Jun 23, 2023 at 12:02 PM Alexander Lindsay wrote: > I guess it is because the inverse of the diagonal

[petsc-users] Petsc 3.19.2 to 3.18.0 error possibility.

2023-06-23 Thread Paweł Stebliński via petsc-users
I am micromagnetic (MAGPAR) software developer. Old Magpar version has been using petsc 3.1-p8. I have decided to upgrade to petsc 3.19.2 with avx512 support. Unfortunately there appeared an error during software testing. Error appeares in ranning code after proper compiling and linking. The

Re: [petsc-users] Petsc 3.19.2 to 3.18.0 error possibility.

2023-06-23 Thread Barry Smith
Could you send us the exact error output that occurs? Cut and paste the run command and the entire error message. Also send the configure options you used. Have you tried configuring the later PETSc versions with all optimization turned off; use --with-debugging=1 --with-cflags='-g -O0'