Why Hyperdimensional Socks Never Match
The nature of computing in hyperdimensions is a strange and wonderful place. I have only started to scratch the surface by reading a paper by Kanerva. Not only is it interesting from a computer science standpoint, it’s also interesting from a cognitive science point of view. In fact, it could hold the key to better model AI and general reasoning. This blog is a casual stroll through some of the main points of Kanerva’s paper along with examples in Clojure to make it tangible. First things first, what is a hyperdimension?
What is a Hyperdimension and Where Are My Socks?
When we are talking about hyperdimensions, we are really talking about lots of dimensions. A vector has dimensions. A regular vector could have three dimensions [0 1 1]
, but a hyperdimensional vector has tons more, like 10,000 or 100,000. We call these big vectors hypervectors for short, which makes them sound really cool. Although the vectors could be made up of anything, we are going to use vectors made up of zeros and ones. To handle big computing with big vectors in a reasonable amount of time, we are also going to use sparse vectors. What makes them sparse is that most of the space is empty, (zeros). In fact, Clojure has a nice library to handle these sparse vectors. The core.matrix project from Mike Anderson is what we will use in our examples. Let’s go ahead and make some random hypervectors.
First we import the core.matrix libraries and set the implementation to vectorz which provides fast double precision vector math.
1 2 3 4 5 

Next we set the sz of our hypervectors to be 100,000. We also create a function to generate a random sparse hypervector by choosing to put ones in about 10% of the space.
1 2 3 4 5 6 7 8 

Now we can generate some.
1 2 3 4 5 6 

You can think of each of this hypervectors as random hyperdimensional sock, or hypersock, because that sounds cooler. These hypersocks, have curious properties. One of which is that they will ~never match.
Hypersocks never match
Because we are dealing with huge amount of dimensions, a mathematically peculiar probability distribution occurs. We can take a random hypervector to represent something, then take another one and they will different from each by about 100 STD. We can take another one and it too, will be 100 STD from the other ones. For practical purposes, we will run out of time before we will run of vectors that are unrelated. Because of this, any two hypersocks will never match each other.
How can we tell how similar two hypersocks are? The cosine to tell the similarity between two vectors. This is determined by the dot product. We can construct a cosine similarity function to give us a value from 1 to 1 to measure how alike they are with 1 being the same and 1 being the complete opposite.
1 2 3 

If we look at the similarity of a hypervector with itself, the result is ~1. With the other random hypervectors, it is ~0.
1 2 3 4 5 6 

There are other cool things we can do with hypervectors, like do math with them.
The Hamming Distance of Two Hypersocks
We can add hypervectors together with a sum mean vector. We add the vector of 1s and 0s together then we divide the resulting vector by the number of total vectors. Finally, to get back to our 1s and 0s, we round the result.
1 2 3 

The interesting thing about addition is that the result is similar to all the vectors in it. For example, if we add a and b together to make x, x = a + b
, then x will be similar to a and similar to b.
1 2 3 4 

You can also do a very simple form of multiplication on vectors with 1s and 0s with using XOR. We can do this by add the two vectors together and then mapping mod 2
on each of the elements.
1 2 3 

We can actually use this xormul
to calculate the Hamming distance, which is an important measure of error detection. The Hamming distance is simply the sum of all of the xor multiplied elements.
1 2 3 4 5 6 

This illustrates a point that xor multiplication randomizes the hypervector, but preserves the distance. In the following example, we xor multiply two random hypervectors by another and the hamming distance stays the same.
1 2 3 4 5 6 7 8 9 10 11 12 

So you can xor multiply your two hypersocks and move them to a different point in hyperspace, but they will still be the same distance apart.
Another great party trick in hyperspace, is the ability to bind and unbind hypervectors for use as map like pairs.
Using Hypervectors to Represent Maps
A map of pairs is a very important data structure. It gives the ability to bind symbols to values and then retrieve those values. We can do this with hypervectors too. Consider the following structure:
1 2 3 

We can now create hypervectors to represent each of these values. Then we can xor the hypervector symbol to the hypervector value and sum them up.
1 2 3 4 5 6 7 8 9 10 

Now, we have a sum of all these things and we want to find the value of the favorite sock. We can unbind it from the sum by xor multiplying the favoritesock hypervector x
. Because of the property that xor multiplication both distributes and cancels itself out.
1


We can compare the result with the known values and find the closest match.
1 2 3 4 5 6 7 

Conclusion
We have seen that the nature of higher dimensional representation leads to some very interesting properties with both representing data and computing with it. These properties and others form the foundation of exciting advancements in Cognitive Computing like word vectors. Future posts will delve further into these interesting areas. In the meantime, I encourage you to read Kanerva’s paper on your own and to find comfort in that when you can’t find one of your socks, it’s not your fault. It most likely has something to do with the curious nature of hyperspace.
Thanks to Ross Gayler for bringing the paper to my attention and to Joe Smith for the great conversations on SDM