Extracted network mistaken for a directed network

[mkaguer]

An exception was raised in find_connected_nodes triggering an error that said, "This function is not implemented for directed networks". Talking to @ma-sadeghi I learned that a directed network has at least one bidirectional throat. When I check my network health, however, I have zero bidirectional throats. So I don't know why my network is triggering this warning. I am working on an extracted network. While I manipulated the 'pore.coords' I did not change 'throat.conns' at all. I can confirm as well that my throat.conns are conditioned well as i < j for any throat (i, j).

Click here to see where the exception was triggered.

[ma-sadeghi]

@mkaguer Could you please post a MWE (minimum working example) that reproduces the bug?

[jgostick]

This was not a bug in openpnm, but a bug in the network extractor. however, it reveals that we should have a better explanation of our 'convention' for what directed means. I am going to add this to the list of examples we should make.