Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • $\begingroup$ Can you add some explanations to the code, please? $\endgroup$ Commented Oct 29, 2018 at 7:40
  • $\begingroup$ Okay, now I see how it works. But it is not trivial, with all the bit-position-encodings of the cells. Why not make the answer a bit more educational? $\endgroup$ Commented Oct 29, 2018 at 7:47
  • $\begingroup$ @Szabolcs Please see my update and tell me if it is sufficient. $\endgroup$ Commented Oct 29, 2018 at 14:55
  • $\begingroup$ I forgot to respond, but yes, of course it was. $\endgroup$ Commented Oct 31, 2018 at 17:46
  • $\begingroup$ @Szabolcs Now that I have tuned ntabV I think you might find its performance interesting, e.g. I can run ntabV[300, 300] in under a second, whereas IGLatticeMesh["Hexagonal", {300, 300}] alone takes almost eleven. $\endgroup$ Commented Nov 1, 2018 at 0:03