Layouts#

Native layout engines within Graphistry.

We recommend using the various plugins for additional layouts, such as for tree and hierarchical data diagramming.

Contents:

Layout plugins: igraph, graphviz, and more#

Several plugins provide a large variety of additional layouts:

  • cuGraph : GPU-accelerated FA2, a naive version of Graphistry’s layout engine

  • graphviz: Especially strong at tree and hierarchical data diagramming such as the dot engine

  • igraph : A variety of layouts, including Sugiyama, Fruchterman-Reingold, and Kamada-Kawai

  • NetworkX: A variety of layouts

LayoutsMixin#

Base class for protocol classes.

Protocol classes are defined as:

class Proto(Protocol):
    def meth(self) -> int:
        ...

Such classes are primarily used with static type checkers that recognize structural subtyping (static duck-typing).

For example:

class C:
    def meth(self) -> int:
        return 0

def func(x: Proto) -> int:
    return x.meth()

func(C())  # Passes static type check

See PEP 544 for details. Protocol classes decorated with @typing.runtime_checkable act as simple-minded runtime protocols that check only the presence of given attributes, ignoring their type signatures. Protocol classes can be generic, they are defined as:

class GenProto[T](Protocol):
    def meth(self) -> T:
        ...