On Wed, Nov 10, 2021 at 11:45 PM Eric Chamberland <
eric.chamberl...@giref.ulaval.ca> wrote:
> Hi Matthew,
>
> I have joined the ex44.c example so you can see that we see.
>
> The problem is about the "f" field number which I can't see any clue in
> the documentation to what to put there... We
Hi Matthew,
I have joined the ex44.c example so you can see that we see.
The problem is about the "f" field number which I can't see any clue in
the documentation to what to put there... We are missing some
information maybe written elsewhere?
I have tried 3 different calls (lines 180-182)
Hi Matthew,
ok, I started back from your ex44.c example and added the global array
of coordinates. I just have to code the creation of the local
coordinates now.
Eric
On 2021-10-20 6:55 p.m., Matthew Knepley wrote:
On Wed, Oct 20, 2021 at 3:06 PM Eric Chamberland
On Wed, Oct 20, 2021 at 3:06 PM Eric Chamberland <
eric.chamberl...@giref.ulaval.ca> wrote:
> Hi Matthew,
>
> we tried to reproduce the error in a simple example.
>
> The context is the following: We hard coded the mesh and initial partition
> into the code (see sConnectivity and
Hi Matthew,
we tried to reproduce the error in a simple example.
The context is the following: We hard coded the mesh and initial
partition into the code (see sConnectivity and sInitialPartition) for 2
ranks and try to create a section in order to use the
DMPlexNaturalToGlobalBegin function
On Wed, Oct 6, 2021 at 5:43 PM Eric Chamberland <
eric.chamberl...@giref.ulaval.ca> wrote:
> Hi Matthew,
>
> we tried to use that. Now, we discovered that:
>
> 1- even if we "ask" for sfNatural creation with DMSetUseNatural, it is not
> created because DMPlexCreateGlobalToNaturalSF looks for a
Hi Matthew,
we tried to use that. Now, we discovered that:
1- even if we "ask" for sfNatural creation with DMSetUseNatural, it is
not created because DMPlexCreateGlobalToNaturalSF looks for a "section":
this is not documented in DMSetUseNaturalso we are asking ourselfs: "is
this a permanent
On Wed, Sep 29, 2021 at 5:18 PM Eric Chamberland <
eric.chamberl...@giref.ulaval.ca> wrote:
> Hi,
>
> I come back with _almost_ the original question:
>
> I would like to add an integer information (*our* original element
> number, not petsc one) on each element of the DMPlex I create with
>
Hi,
I come back with _almost_ the original question:
I would like to add an integer information (*our* original element
number, not petsc one) on each element of the DMPlex I create with
DMPlexBuildFromCellListParallel.
I would like this interger to be distribruted by or the same way
On Wed, Jul 21, 2021 at 2:54 PM Eric Chamberland <
eric.chamberl...@giref.ulaval.ca> wrote:
> Hi Matthew,
>
> we did it with PetscSFCreateInverseSF !
>
> It is working well without overlap, so we can go forward with this and
> compute the overlap afterward with DMPlexDistributeOverlap.
>
> That
Hi Matthew,
we did it with PetscSFCreateInverseSF !
It is working well without overlap, so we can go forward with this and
compute the overlap afterward with DMPlexDistributeOverlap.
Thanks,
Eric
On 2021-07-20 10:39 p.m., Eric Chamberland wrote:
On 2021-07-14 6:42 p.m., Matthew Knepley
On 2021-07-14 6:42 p.m., Matthew Knepley wrote:
Ah, there was a confusion of intent. GlobalToNatural() is for people
that want data transformed back into the original
order. I thought that was what you wanted. If you just want mesh
points in the original order, we give you the
transformation
On Wed, Jul 14, 2021 at 4:58 PM Eric Chamberland <
eric.chamberl...@giref.ulaval.ca> wrote:
> Hi Matthew,
>
> Ok, I did that but it segfault now. Here are the order of the calls:
>
> DMPlexCreate
>
> DMSetDimension
>
> DMPlexBuildFromCellListParallel(...)
>
> DMPlexInterpolate
>
>
Hi Matthew,
Ok, I did that but it segfault now. Here are the order of the calls:
DMPlexCreate
DMSetDimension
DMPlexBuildFromCellListParallel(...)
DMPlexInterpolate
PetscPartitioner lPart;
DMPlexGetPartitioner(lDMSansOverlap, );
PetscPartitionerSetFromOptions(lPart);
On Wed, Jul 14, 2021 at 1:18 PM Eric Chamberland <
eric.chamberl...@giref.ulaval.ca> wrote:
> Hi,
>
> I want to use DMPlexDistribute from PETSc for computing overlapping and
> play with the different partitioners supported.
>
> However, after calling DMPlexDistribute, I noticed the elements are
>
Hi,
I want to use DMPlexDistribute from PETSc for computing overlapping and
play with the different partitioners supported.
However, after calling DMPlexDistribute, I noticed the elements are
renumbered and then the original number is lost.
What would be the best way to keep track of the
16 matches
Mail list logo
