Skip to main content

Deep Learning based CBIR 101 (Part 2): the basics

In part 1 of this series a definition of CBIR has been given. Let's now understand what's the typical flow for it. The diagram in figure 1 shows that there are two parts, one that happens offline and another which is online:


Figure 1

Starting from an image storage, a preliminary trained Deep Neural Network is used to extract the features from images. Extracted features are then stored in a feature database. This happens offline any time new images are added to the storage. What happens online is the search process itself. Any time a user uploads a query image, the same Deep Neural Network used for feature extraction is used to extract the input image features. Then the distance from the query image features and the features in the database are computed. The closer the distance, the higher the relevance is. The closest features are then sorted and the corresponding images are returned as results.

Basic implementation: data set preparation

To make things more clear, let's start a first simple implementation using a supervised Deep Learning approach for feature extraction.
The data set used for this example is the Food 101 data set. It contains images of food recipes from international cuisine classified in 101 categories (classes). Its size is about 5 GB and contains 1000 images for each class. The structure of the ZIP archive includes:
  • an image directory, which contains all the images grouped into sub-directories, one for each food class;
  • a meta directory, which contains four text files:
    • classes.txt: the list of class names;
    • labels.txt: a list of verification labels;
    • train.txt: the list of the training images;
    • test.txt: the list of the test images.
Figure 2 shows a sample of the images in this data set.


Figure 2

Unfortunately there are no separate directories for training and test images: you have to split them by yourself (a sample Python script would be provided in GitHub later on). Once the train/test split has been done, the training of the Deep Neural Network (a CNN) could start.
The next post will walk through the details of the feature extraction.

Comments

Popular posts from this blog

Shipping and analysing MongoDB logs using the Streamsets Data Collector, ElasticSearch and Kibana

In order to show that the considerations done in my last post are general for any log shipping purpose, let's see now how the same process applies to a more real use case scenario: the log shipping and analysis of a MongoDB database logs. MongoDB logs pattern Starting from the release 3.0 (I am considering the release 3.2 for this post) the MongoDB logs come with the following pattern: <timestamp> <severity> <component> [<context>] <message> where:     timestamp is in iso8601-local format.     severity is the level associated to each log message. It is a single character field. Possible values are F (Fatal), E (Error), W (Warning), I (Informational) and D (Debug).     component is for a functional categorization of the log message. Please refer to the specific release of MongoDB you're using to know the full list of possible values.     context is the specific context for a me...

Load testing MongoDB using JMeter

Apache JMeter ( http://jmeter.apache.org/ ) added support for MongoDB since its 2.10 release. In this post I am referring to the latest JMeter release (2.13). A preliminary JMeter setup is needed before starting your first test plan for MongoDB. It uses Groovy as scripting reference language, so Groovy needs to be set up for our favorite load testing tool. Follow these steps to complete the set up: Download Groovy from the official website ( http://www.groovy-lang.org/download.html ). In this post I am referring to the Groovy release 2.4.4, but using later versions is fine. Copy the groovy-all-2.4.4.jar to the $JMETER_HOME/lib folder. Restart JMeter if it was running while adding the Groovy JAR file. Now you can start creating a test plan for MongoDB load testing. From the UI select the MongoDB template ( File -> Templates... ). The new test plan has a MongoDB Source Config element. Here you have to setup the connection details for the database to be tested: The Threa...

Turning Python Scripts into Working Web Apps Quickly with Streamlit

 I just realized that I am using Streamlit since almost one year now, posted about in Twitter or LinkedIn several times, but never wrote a blog post about it before. Communication in Data Science and Machine Learning is the key. Being able to showcase work in progress and share results with the business makes the difference. Verbal and non-verbal communication skills are important. Having some tool that could support you in this kind of conversation with a mixed audience that couldn't have a technical background or would like to hear in terms of results and business value would be of great help. I found that Streamlit fits well this scenario. Streamlit is an Open Source (Apache License 2.0) Python framework that turns data or ML scripts into shareable web apps in minutes (no kidding). Python only: no front‑end experience required. To start with Streamlit, just install it through pip (it is available in Anaconda too): pip install streamlit and you are ready to execute the working de...