In this post, we will use Keras to build a -based model (k-NN) on . Finally (and optionally) we will convert the model to or other iOS devices. cosine k-nearest neighbors top of an existing deep network CoreML for use on iPhone A Jupyter notebook with a complete code example is available here: https://github.com/sorenlind/keras-knn/ : You have a set of images and you need to find images among them which are similar to a user image. Images, however, cannot easily be compared in their raw form, so you use a neural network to extract features (or , or ) from the images. These features can be compared using cosine similarity. So you want to build a cosine-based k-NN which for any given user image can find the closest images in the database. It’s easy to build the k-NN using tools like but for several reasons (detailed below), you want a single model that handles feature extraction and neighbor computation. The basic problem is this representations codes encodings k Scikit-learn Cosine similarity is basically just dot products (on normalized vectors). This means it can be easily expressed in Keras. In fact, it can be just a . The solution is quite simple: single dense layer with precomputed weights Why not Scikit? Scikit-learn is a wonderful tool which lets you easily train and use many different Machine models. And it lets you build k-NNs not only using cosine but with several other metrics as well. So, why not take advantage of that? There are several good reasons. Let’s see. Learning Scikit-learn . By building our k-NN in Keras, we can leverage GPUs for increased inference speed. does not support GPUs Scikit-learn does not run on iOS devices. Apple’s for converting Machine Learning models to Apple’s CoreML format support Scikit-learn but only some specific model types and . The Keras model, however, can be converted to CoreML, making it easy to run your model on an iPhone. tools do the k-NN is not one of them Building the k-NN in Scikit-learn (or similar) would introduce another dependency. By building the k-NN with the same tools we use for the neural network, we can avoid introducing more dependencies. Having a single, unified model handling feature extraction and neighbor computation makes for a simpler setup. Finally, it’s a fun little exercise! The Big Picture In broad terms, the flow of the system looks like this: The steps we need to carry out are: Obtain some images making up your image database. Train or obtain a network for feature extraction. Extract features for all images in the database. Build a k-NN using the features extracted in step 3. Join the feature extraction network and the k-NN for a single, unified model. Let’s go through each step! And remember, for the complete code example, take a look at the . Jupyter notebook Build the Image Database Before we can do anything useful, we need some images. For this example, I will use images from the dataset which contains images from 101 categories such as airplanes, butterflies, helicopters, pandas, pizzas and more. From the Caltech 101 website: Caltech 101 Pictures of objects belonging to 101 categories. About 40 to 800 images per category. Most categories have about 50 images. Collected in September 2003 by Fei-Fei Li, Marco Andreetto, and Marc ‘Aurelio Ranzato. The size of each image is roughly 300 x 200 pixels. The Caltech101 dataset contains labeled images but we do not actually use the labels, so feel free to use an unlabeled dataset. A Neural Network for Feature Extraction To make things easy we will just use an off-the-shelf convolutional network trained for image classification, namely the ResNet50 network. We are not interested in the actual classification so we throw away the upper layers. This is really easy in Keras: For real-world problems you could train your own network and use that instead. If you don’t have labeled data you could use a self-supervised approach such as autoencoders. But here, we will just stick with the ResNet50 network. Extract Features With our feature extraction network in place, we can now compute a feature vector for every image in our database. We call these our vectors. When a user sends us a new query image, we will extract a feature vector from the image (again using the feature extraction network). We call this the vector. We will then compute cosine similarity between the query vector and each of the reference vectors and eventually pick the images most similar to the query image. Normally, we would compute those cosine similarities using something like SciKit-learn but we will now see how it can be done in Keras using a dense layer. reference query k How It Works The math behind this little trick is actually really simple. To understand what is going on and how it works, we need to remind ourselves how the activation of a dense layer is computed and how the cosine is computed. This results in a few insights which are listed right below. We will go through each of them in more detail further down. We can treat the reference vectors as column vectors and stack them horizontally to obtain a matrix which can be used as the weight matrix in a dense layer. For the input vector , the dense layer will compute the dot product for every column vector in the weight matrix . x · x w w W The cosine between two vectors and is defined as . Thus, the dense layer computes the cosine similarity multiplied by the product of the lengths of the two vectors. x w cos( , ) = · / (| |·| |) x w x w x w A vector can be normalized, that is transformed to a vector of length 1 (a unit vector), without affecting the direction of the vector. Thus, normalizing a vector does not affect the cosine between that vector and any other vector. That is, if is normalized, . w’ w cos( , ) = cos( , ) x w x w’ With being a unit vector, its length is 1 and can consequently be removed from the cosine equation, resulting in . By multiplying by on both sides we get that: . Pairing that with insight number 2, we get that the dense layer will compute for the query vector and every normalized reference vector in the normalized weight matrix . w’ cos( , ) = · | | x w’ x w’ / x | | x · = | |· cos( , ) x w’ x x w’ | |· cos( , ) x x w’ x w’ W’ For any particular query vector , the length is constant. Therefore, for any particular query vector , it holds that ~ that is is directly proportional to . Consequently, to find the most similar images, we can simplify the cosine computation to just . x | | x x · x w’ cos( , ), x w’ · x w’ cos( , ) x w’ k · x w’ Let us now look at each insight in a bit more detail! 1. Stacking Vectors Having extracted a feature vector for each reference image, we can treat those reference vectors as column vectors and stack them horizontally to make up a matrix. This matrix can be used as the weight matrix of a dense layer in a neural network. This layer has the correct dimensions to take as input a feature vector (computed by the feature extraction network) and output a vector with dimensionality equal to the number of reference images. In our example, will be of size 2048 by 9144. If you use another network or another dataset, you will, of course, see other dimensions. W 2. Dense Layers Compute Dot Products Let us now remind ourselves how the output or activation of a dense layer in a neural network is computed. With input vector , weight matrix , bias vector and activation function , the activation can be computed as: x W b g a = ( · + ) g x W b If we set the bias to 0 (by simply telling Keras to not use a bias) and use a linear activation we can simplify the activation as: a = · x W In other words, the activation of the dense layer (with no bias and a linear activation function) is simply the matrix product between the input vector and the weight matrix . Now, let’s remember that our was made from stacking up reference vectors computed by feeding each image in our database through our feature extraction network. Thus, each element of the vector resulting from the matrix product · is actually the dot product between input vector and a reference vector . This can be illustrated as below: x W W x W x w As you can see, for each reference vector , the dense layer computes w · x w . 3. Cosine Similarity As we briefly saw above, the cosine similarity between two vectors and is defined as . That is, the cosine similarity between two vectors is the dot product divided by the product of the lengths of the vectors. Now, we just saw in the previous section, that the dense layer basically computes a number of dot products, so this should be a hint that we could use the dense layer when computing the cosine similarities. We are not quite there yet, though. If we rewrite the cosine equation by multiplying by on both sides (and flip the sides), we get the following: x w cos( , ) = · / (| |·| |) x w x w x w | |·| | x w · = | |·| |· cos( , ) x w x w x w Since is exactly what the dense layer computes, we can now see that for the input vector a dense layer computes for each column vector in the weight matrix . · x w x, | |·| |· cos( , ) x w x w w W 4. Vector Normalization We will now briefly change the focus and look for a moment at vector normalization. All we need to remember is that given two vectors, we can change the length of one or both of them without affecting the angle between them and consequently without affecting the cosine. This means we can transform all the vectors in to vectors of length 1 (unit vectors) without affecting the cosine. We call this new matrix . In the next section we shall see how that makes computing the cosine simpler. w W w’ W’ 5. Simplifying the Cosine We will now use the knowledge that our vectors, , are all of length 1 to simplify the cosine computation. As we saw above, the cosine definition can be rewritten as: w’ · | |·| |· cos( , ) x w’ = x w’ x w’ In contrast to before, we now know that one of the vectors, namely is of length 1. This means multiplying by it has no effect, so we might as well remove it, which gives us: w’, · | |· cos( , ) x w’ = x x w’ In other words, if we normalize all the reference vectors, the dense layer will compute for the query vector and every normalized reference vector in . | |· cos( , ) x x w’ x w’ W’ 6. Proportionality So, our dense layer computes . But we set out to compute just . We might consider simply dividing by . Unfortunately, Keras has no division layer. TensorFlow has one, so we could use that. (This can be done in Keras with a Lambda layer in case you were wondering). But, if we take that approach, we will not be able to easily convert the model to CoreML (because the converter does not support Lambda layers unless you implement their computations in Swift/Objective-C and we do not want that). So we have to do something else, and luckily, the solution is simple: We can skip dividing by entirely. For any given user image, dividing each of the dot products by has the effect of normalizing the cosine such that it’s a value between -1 and 1. But it’s the same operation applied to all the reference vector products (since**| |** is constant for a given input image), and thus it does not change the ratio between them! Another way to put this is that for any particular query vector , it holds that: | |· cos( , ) x x w’ cos( , ) x w’ | | x | | x x · w’ | | x x x ~ · x w’ cos( , ) x w’ That is is directly proportional to . Remember, we do not care about the actual cosine value. All we need is to find the vectors in which result in the cosine. That is, we just need to be able to by the cosine values. Computing something that is proportional to the cosine for a particular query vector suffices because this will result in the same order. In other words, computing will suffice for our purpose — we are done! · x w’ cos( , ) x w’ k W’ greatest sort x · x w’ For input vector and every normalized vector in , the dense layer computes is constant for the particular input vector, it does not change the proportions. x w’ W’ |x|·cos( , x w’) . Since |x| That’s it for the math — we have seen that if we set the weights to the extracted reference feature vectors, the dense layer computes the dot products between the input feature vector and each of the reference vectors. And we have seen that these dot products are proportional to the cosine similarities if we just make sure to normalize the reference vectors. In short, all we have to do to find the k closest images is implement a dense layer with no bias and set its weights to the normalized feature weights! There is one final and somewhat interesting note to make about our dense layer: As we have seen, the weights we use are computed by another network, namely the feature extraction network. This is unusual and therefore worth mentioning. Normally you would learn the weights using some variant of gradient descent and back-propagation but here they are computed in advance by another network! Implementing with Keras With the math out of the way, we can add the dense layer to the ResNet50 model: Let’s now normalize the feature weights: And finally set the weights of the network dense layer: That’s all there really is to it! In the next section we will start making predictions using our new network. Predictions It is now time to make a few predictions using our network to see that it actually works! Convert to CoreML Having assured ourselves that the model works fairly well, we can now finally convert the model to CoreML as shown below. A k-NN for Classification You’ve now seen how to use the k-NN approach to search for similar images. Another (maybe even more interesting) application is to use it for image . This can be extremely useful because it can help you get away with using relatively few training examples even for problems with many thousand classes. If you think that sounds interesting, go and read my post on how I used an ! classification autoencoder and a k-NN to classify photos of over 35,000 different Magic cards Good luck and have fun implementing your own k-NN with Keras!

Flow

Apple

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

Nearest Neighbors with Keras and CoreML

Too Long; Didn't Read

Company Mentioned

Coin Mentioned

Søren L Kristiansen

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Nearest Neighbors with Keras and CoreML

Too Long; Didn't Read

Company Mentioned

Coin Mentioned

Søren L Kristiansen

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES