[petsc-dev] DMPLEX cannot support two different edges for the same two vertices, hence DMPLEX cannot?

Abhyankar, Shrirang G shrirang.abhyankar at pnnl.gov
Wed Dec 1 15:37:23 CST 2021


Barry,

“Is there anything we can do to support having multiple edges between the same two vertices”

Some of my power grid datasets have multiple edges between the same two vertices and I’ve not faced an issue with DMNetwork. However, all the data was read on rank 0 only (and then distributed).

Maybe the issue is with the edges being passed on different ranks?

Thanks,
Shri
From: Barry Smith <bsmith at petsc.dev>
Date: Wednesday, December 1, 2021 at 3:19 PM
To: "Knepley, Matthew G (VISIT)" <knepley at gmail.com>, PETSc Development <petsc-dev at mcs.anl.gov>, "Abhyankar, Shrirang G" <shrirang.abhyankar at pnnl.gov>, "Zhang, Hong" <hzhang at mcs.anl.gov>, Getnet Betrie <gbetrie at anl.gov>
Subject: DMPLEX cannot support two different edges for the same two vertices, hence DMPLEX cannot?

Check twice before you click! This email originated from outside PNNL.


   Matt,

     If DMPlexBuildFromCellListParallel() is called with two edges that have the same two vertices what will happen? It looks like it ends up with an incorrect PetscSF if the two edges are passed on different ranks. Hence the DMPLEX is not valid and produces garbage.

     Neurons can be connected to themselves which seems to be breaking DMPLEX and hence DMNETWORK.

     Is there anything we can do to support having multiple edges between the same two vertices? If not is there a way we can have DMPlexBuildFromCellListParallel() generate an error automatically if there are such extra edges in the input data.

   Thanks

  Barry

In this work, the neurons are represented by vertices in the network and each synapse is a graph edge.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20211201/e8eb21c8/attachment.html>


More information about the petsc-dev mailing list