This Message Is From an External Sender
This message came from outside your organization.
hi Matt,
I've made a bit of progress with this, using a debugger. I wasn't setting the overlap for my dual-porosity DM, so it was defaulting to zero, and when it got to the DMPlexCheckPointSF() call it was doing the check for cells in the overlap when it shouldn't have been (this is only triggered "if (!overlap)"). Now I do a DMPlexSetOverlap() to make sure the dual-porosity DM has the same overlap as the original DM. That gets rid of the error raised in DMPlexCheckPointSF(), as the overlap is now 1. However it is still falling over further on, when it tries to stratify the redistributed DM: [0]PETSC ERROR: Petsc has generated inconsistent data [0]PETSC ERROR: New depth 2 range [0,141) overlaps with depth 1 range [0,141) [0]PETSC ERROR: #1 DMPlexCreateDepthStratum() at /home/acro018/software/PETSc/code/src/dm/impls/plex/plex.c:4087 [0]PETSC ERROR: #2 DMPlexStratify() at /home/acro018/software/PETSc/code/src/dm/impls/plex/plex.c:4211 [0]PETSC ERROR: #3 DMPlexDistributeCones() at /home/acro018/software/PETSc/code/src/dm/impls/plex/plexdistribute.c:1164 [0]PETSC ERROR: #4 DMPlexMigrate() at /home/acro018/software/PETSc/code/src/dm/impls/plex/plexdistribute.c:1659 [0]PETSC ERROR: #5 DMPlexDistribute() at /home/acro018/software/PETSc/code/src/dm/impls/plex/plexdistribute.c:1778 I have checked the depth label on my dual-porosity DM for a simple example in which this error is raised, and the label looks correct to me. However I have a memory of trying DMPlexStratify() on my dual-porosity DMs in the past and it not liking them. I create the depth label by copying its values from the original DM and then explicitly assigning depth values for the new dual-porosity cells, vertices, faces & edges. When the DM is redistributed I'd have thought it shouldn't be necessary (at least in my case) to stratify as the depth label is already there and just needs to be redistributed as well? But I guess that might not always be the case. Has anything changed in this part of the PETSc code recently that might make this stop working? - Adrian -- Dr Adrian Croucher Senior Research Fellow Department of Engineering Science Waipapa Taumata Rau / University of Auckland, New Zealand email: a.crouc...@auckland.ac.nz tel: +64 (0)9 923 4611
