[petsc-dev] DMPlex redistribution

Matthew Knepley knepley at gmail.com
Mon Mar 27 06:14:56 CDT 2023

On Mon, Mar 27, 2023 at 12:30 AM Adrian Croucher <a.croucher at auckland.ac.nz>

> hi
> I am testing my code against the latest PETSc release branch, having
> built it mostly with PETSc 3.15 until now.
> An error is coming up when I read in a DMPlex, distribute it, add extra
> cells etc. to it (to represent dual porosity subsurface flow) and then
> re-distribute it for load balancing:
> [0]PETSC ERROR: Petsc has generated inconsistent data
> [0]PETSC ERROR: Point SF contains 25 which is a cell
> [0]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting.
> [0]PETSC ERROR: Petsc Release Version 3.18.5, unknown
> /home/acro018/software/geothermal/waiwera/code/petsc-3.19-debug/mesh_test
> on a v3.19-debug named en-354401 by acro018 Mon Mar 27 14:28:07 2023
> [0]PETSC ERROR: Configure options --with-x --download-cmake
> --download-hdf5 --download-zlib --download-netcdf --download-pnetcdf
> --download-exodusii --download-triangle --download-ptscotch
> --download-chaco --download-hypre
> [0]PETSC ERROR: #1 DMPlexCheckPointSF() at
> /home/acro018/software/PETSc/code/src/dm/impls/plex/plex.c:8875
> [0]PETSC ERROR: #2 DMPlexCreateNumbering_Plex() at
> /home/acro018/software/PETSc/code/src/dm/impls/plex/plex.c:8147
> [0]PETSC ERROR: #3 DMPlexCreatePartitionerGraph_Native() at
> /home/acro018/software/PETSc/code/src/dm/impls/plex/plexpartition.c:153
> [0]PETSC ERROR: #4 DMPlexCreatePartitionerGraph() at
> /home/acro018/software/PETSc/code/src/dm/impls/plex/plexpartition.c:514
> [0]PETSC ERROR: #5 PetscPartitionerDMPlexPartition() at
> /home/acro018/software/PETSc/code/src/dm/impls/plex/plexpartition.c:781
> [0]PETSC ERROR: #6 DMPlexDistribute() at
> /home/acro018/software/PETSc/code/src/dm/impls/plex/plexdistribute.c:1820
> [0]PETSC ERROR: #7 ../src/mesh.F90:3618
> The code still runs and appears to produce correct results. Has some new
> checking been added which might be showing up a problem that was already
> there? Any other clues as to how to approach it?

Yes, it is a new check. I do not expect cells that are shared until we
create an overlap. We
can just put in a flag to shut it off, since otherwise it is a great check
for finding bugs. Can
you show me how you add cells, so we can make a small example that tests
this to go in



> - Adrian
> --
> Dr Adrian Croucher
> Senior Research Fellow
> Department of Engineering Science
> University of Auckland, New Zealand
> email: a.croucher at auckland.ac.nz
> tel: +64 (0)9 923 4611

What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener

https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20230327/75fffb41/attachment-0001.html>

More information about the petsc-dev mailing list