On Sun, Aug 28, 2022 at 5:36 PM Mike Michell wrote:
> Thank you for the reply.
>
> I think it can be more helpful for me if the attached sample code
> (DMInterpolation_Mod.tar) could be checked by you.
>
Okay, you are right. I will run it tomorrow.
Thanks,
Matt
> If you run the
Is there a way to automatically check the package language? If so, we will do
that check right at the beginning of configure to limit the user's need to read
the PETSc documentation before getting to work :-)
> On Aug 28, 2022, at 2:09 PM, Andreas Hauffe
> wrote:
>
> Hi,
>
> perhaps it
Hi,
perhaps it is possible to add a short hint in the documentation
(https://petsc.org/main/install/windows/) for Windows OS with a
non-english default language. It is important, that the compiler is
installed with english language pack, so that all compiler output is in
english. Otherwise
Hi list,
I tried to compile PETSC with MUMPS on a Windows platform with intel
compilers. I think there is a bug in "mumps_io.h" since there is a
additional underscore in the upper case function names in line 36 and
line 41. With my configuration I have to change line 36 from
Hi
I'm working on a finite volume implementation using DMPlex. I was wondering
what the best-considered way to add cell variables to the DM that we don't
want to be part of the ksp/snes solve. As far as I can tell, if I add an
extra section with those, they will still be part of the F and U
On Sun, Aug 28, 2022 at 12:11 PM Mike Michell wrote:
> Thank you for the reply.
>
> *I cannot quite understand. Are you saying that you have inhomogeneous
> Dirichlet conditions on the boundary, and a 0 guess in the interior, and
> you get all zeros from interpolation? Yes, we have no way of
Thank you for the reply.
*I cannot quite understand. Are you saying that you have inhomogeneous
Dirichlet conditions on the boundary, and a 0 guess in the interior, and
you get all zeros from interpolation? Yes, we have no way of getting
boundary values into the operator. You could conceivably
On Sun, Aug 28, 2022 at 8:51 AM Mike Michell wrote:
> Hi, thank you for the reply.
>
> I was able to manage mapping from cell-center to vertex. Basically, in
> Fortran, it seems DMCreateInterpolation() requires the optional scaling
> vector as a mandatory argument, which is strange.
>
It needs
Hi, thank you for the reply.
I was able to manage mapping from cell-center to vertex. Basically, in
Fortran, it seems DMCreateInterpolation() requires the optional scaling
vector as a mandatory argument, which is strange.
My dmplex has zero overlap layer over the procs, and there is no ghost
