First 5 minutes of hell

Cartesian product

  • mental picture: take , and replace every vertex of with a copy of
    • then connect corresponding vertices across copies according to the edges of
    • so if has 5 vertices, now I have 5 s connected together
  • it is commutative and associative (up to isomorphism, so the vertices could be remapped and it would still work)
  • cartesian product is the mechanism behind the construction of orthogonal topologies
    • binary hypercube (1D block = edge)
    • n-dimensional mesh (1D block = line)
    • n-dimensional torus (1D block = cycle)
    • we are able to build these by doing Cartesian product of simple 1D building blocks

Vertex symmetry

  • the property, where the graph looks the same from every vertex
  • “for each pair of vertices, there exists an automorfism (a bijection that preserves adjacency) (we could switch them and the graph structure would look the same)”
  • theorem:
    • if and are vertex symmetric, then the Cartesian product is also vertex symmetric
    • if is vertex-symmetric regular (not the other way!)
      • regular graph = all vertices have the same degree
      • automorphism preserves adjacency and that preservers same degrees for all pairs
      • this is also good: if all nodes have the same degrees, we can use the same routers with the same constant number of ports
  • e.g. meshes are not vertex symmetric (because no automorphism can swap inner node with the endpoint node (different degrees))
    • the property of vertex symmetry is propagated through the Cartesian product (see meshes, tori)
  • : automorphism preserves adjacency (and the distances between nodes), so max eccentricity = min eccentricity
    • in vertex-symmetric network, there is no “good” spot to put the master (this is desired, we don’t have to choose, every node is the same)
      • e.g. in non-vertex-symmetric mesh, putting master into a corner is way worse than putting it into the center

Cartesian product (Definition 4)

For graphs and , the Cartesian product is defined by: In words:

  • The vertex set is the Cartesian product of and (pairs)
  • For edges: two vertices and are adjacent in iff either they agree in the second coordinate () and are adjacent in , or they agree in the first coordinate () and are adjacent in

Equivalently (a useful mental picture): take , and replace every vertex of with a copy of ; then connect corresponding vertices across copies according to the edges of . The roles of and can be swapped (see Theorem 5 below).

Example: triangle times a 2-vertex path yields a 3-prism (two triangles connected by three parallel edges).

Commutativity and associativity (Theorem 5)

Theorem 5: the Cartesian product is commutative and associative up to isomorphism: Proof (constructive, for commutativity; associativity is similar). Define

  • is trivially a bijection
  • preserves adjacency (shown for edges of -type; the other type is symmetric): Hence is an isomorphism.

Consequences:

  • Parentheses can be dropped from longer Cartesian-product expressions
  • Iterated product notation: , , etc.
  • These properties are used extensively in the construction of orthogonal topologies

Why the Cartesian product matters for INPCs

The Cartesian product is the constructor of orthogonal direct topologies:

  • Binary hypercube: (where is a single edge)
  • n-dimensional mesh: (each factor a linear array)
  • n-dimensional torus: (each factor a cycle)

Because Theorem 5 holds up to isomorphism, these decompositions can be freely reassociated, which is what allows the hierarchical-recursivity decompositions such as .

Vertex symmetry (Definition 6)

A graph is vertex-symmetric if (An automorphism - often abbreviated a.m. - is a bijection that preserves adjacency.)

Intuition: the graph “looks the same” from any vertex. If you stand at any vertex and look around, you see an identical local structure.

Note: the definition requires only existence of at least one such automorphism for each pair. Many vertex-symmetric graphs (like ) have far more than one - as their “extra symmetry” is sometimes phrased, such graphs have much more than is needed by the definition.

Theorem 7: Cartesian product preserves vertex symmetry; vertex symmetry implies regularity

Theorem 7:

  1. If and are vertex-symmetric, then is also vertex-symmetric.
  2. vertex-symmetric regular.

Proof of (1), constructive. Since are vertex-symmetric, Define, for any : It remains to prove this mapping is a bijection preserving adjacency:

  • Bijection: follows componentwise from the bijectivity of and
  • Adjacency: if is an edge (-type) then , so , so is an edge in . Analogously for -type edges.

Finally , establishing vertex symmetry.

Proof of (2) - regularity: trivial. In a vertex-symmetric graph, for any there is an automorphism mapping one to the other. Since automorphisms preserve adjacency, they preserve degrees: . So all vertices have the same degree, i.e., is regular.

Note the converse of (2) is false: regularity does NOT imply vertex symmetry. Many regular graphs lack the automorphism structure required for vertex symmetry.

Distances in vertex-symmetric graphs (Lemma 9)

Lemma 9: for every vertex-symmetric , Proof: in a vertex-symmetric graph every vertex has the same eccentricity. For any there is an automorphism with ; automorphisms preserve distances, hence preserve eccentricity. Thus Practical consequence: in a vertex-symmetric topology, every source sees the same worst-case communication delay - there are no “bad” placements.

Example 1: vertex symmetry of the hypercube (Theorem 16)

Theorem 16: is vertex-symmetric with different automorphisms.

Proof sketch. Since (a single edge) is trivially vertex-symmetric and , Theorem 7(1) immediately yields vertex symmetry of . The explicit automorphisms are obtained by composing two independent families:

  1. Dimension permutations . For a permutation , There are such permutations. Each preserves Hamming distance, hence adjacency.

  2. Translations . For , There are such translations (one per choice of translation vector ). Each preserves adjacency, since XOR with a fixed vector preserves Hamming differences.

Composing them yields automorphisms.

Corollary 17: for any pair , there exist automorphisms with . Constructive proof: pick any (out of ), then compose with the appropriate translation: Substituting recovers , and is a bijection preserving adjacency.

The vertex symmetry definition requires only one automorphism per pair - provides of them for every pair.

Example 2: vertex symmetry of tori (Theorems 21, 22)

Theorem 21: the 1-D torus (a cycle) is vertex-symmetric. Constructive proof: for any , define the cyclic shift This is trivially a bijection; adjacency preservation follows from commutativity and associativity of modular arithmetic: Remark: besides cyclic shifts, also has mirror symmetry.

Theorem 22: is vertex-symmetric, with automorphisms being translations (vector shifts). Proof: immediate corollary of combined with Theorems 5, 7, and 21 - automorphisms are coordinate-wise cyclic shifts.

This is the strong consequence of Theorem 7(1): going from a 1-D cycle (which is trivially vertex-symmetric by rotation) to an -D torus of arbitrary dimensions preserves vertex symmetry automatically. Contrast with meshes (linear arrays, no wraparound), which are not vertex-symmetric because corner vertices have lower degree than interior vertices (regularity fails, so by Theorem 7(2) vertex symmetry must fail too).

Example 3: vertex symmetry of the wrapped butterfly (Theorem 25)

Theorem 25: the wrapped butterfly is vertex-symmetric.

is not a Cartesian-product graph (the cycle index is rigidly tied to hypercubic dimension ), so Theorem 7 does not apply directly. The automorphism must simultaneously rotate cycle indices and hypercubic dimensions - and then apply a translation to map the chosen source cycle to the chosen target cycle. For vertices and with , This example shows the general principle: even when Theorem 7 does not apply, one can often combine structural operations (rotations, translations) to exhibit a vertex-symmetric structure.

Why vertex symmetry matters for INPCs

Vertex symmetry is listed among the desirable properties of an INPC (requirements II):

  • Easier algorithm design: since every vertex looks the same, “it does not matter where the computation starts” - the root of a broadcast, the source of a reduction, or the placement of a master process is irrelevant to structural cost
  • Lemma 9 tells us diameter = radius, so the worst-case communication delay is a property of the topology, not the source
  • Vertex symmetry also implies regularity (Theorem 7(2)), which is a technological prerequisite: all routers have the same port count, so a single router component can be used throughout the machine

A non-vertex-symmetric topology (like a mesh) forces the algorithm designer to reason about “good” vs “bad” placements of processes, and the router hardware differs at the corners, edges, and interior.

Summary

The Cartesian product is the fundamental construction operator for orthogonal topologies. Its commutativity and associativity (Theorem 5) permit free reassociation of product expressions, yielding both the definition (, etc.) and the hierarchical-recursivity decompositions () of hypercubes, meshes, and tori. Vertex symmetry (Definition 6) formalizes the “same from every vertex” intuition; it is preserved by Cartesian product (Theorem 7(1)) and implies regularity (Theorem 7(2)). For vertex-symmetric graphs, diameter equals radius (Lemma 9). Concrete applications include ( automorphisms, Theorem 16), tori (translations, Theorem 22), and wrapped butterflies (which require a combined rotation-plus-translation argument since they are not pure Cartesian products, Theorem 25).

Potential exam questions

  1. State the formal definition of the Cartesian product of two graphs. Given small graphs and , draw .
  2. State and prove (or sketch) Theorem 5: the Cartesian product is commutative and associative up to isomorphism. What isomorphism do you construct for commutativity?
  3. What is the constructor of orthogonal direct topologies? Express the hypercube , mesh , and torus as Cartesian products.
  4. Define vertex symmetry. Why is it a desirable property for an interconnection network?
  5. State Theorem 7. Give the constructive proof that if and are vertex-symmetric then is vertex-symmetric - specifically, exhibit the automorphism that maps to .
  6. Prove that vertex symmetry implies regularity. Does the converse hold? If not, give an intuitive counterexample.
  7. State and prove Lemma 9: in a vertex-symmetric graph, . Why is this practically important for an INPC?
  8. State Theorem 16: how many automorphisms does have, and how are they constructed? Describe the two independent families of automorphisms and .
  9. Prove Corollary 17: for any , there are automorphisms mapping to . Write down the explicit formula.
  10. Prove Theorem 21: the 1-D torus is vertex-symmetric. Show that the cyclic shift is an automorphism.
  11. Derive Theorem 22 (vertex symmetry of the -D torus) as a corollary of Theorems 5, 7, and 21.
  12. Why is the mesh not vertex-symmetric, whereas the torus is? Which property from Theorem 7 directly rules it out for the mesh?
  13. The wrapped butterfly is vertex-symmetric (Theorem 25), but the argument does not follow from Theorem 7. Why not, and how must the automorphism be constructed instead?