Introduction

The objective of our ML system is to be able to extract the image type and color from the images of the advertisers' inventories.

Currently supported values:

• Image type:

  • Dealer, Stock, Placeholder

• Color:

  • Black, Blue, Brown, Burgundy, Green, Grey, Orange, Pink, Purple, Red, White, Yellow

The classification of the images is triggered after an SRPScrape process finished collecting the inventory data of an advertiser. The ML server responds with the type and color of each image, using the cached values if the image was previously tagged. If any of the images cannot be downloaded to be tagged they are skipped.

So far we've worked with two different approaches for image tagging.

**It's important to note that only the Image Type model training is managed by us. The color model however was created and managed by another company and it's not under our control.

ML Results caching

Most advertisers' inventories don't change much from day to day, so in order to avoid classifying the same images multiple times, we use a cache system in the ML servers.

The first time an image arrives at the ML System we calculate an image key based on different data from the request, such as the HTTP headers. After the image is classified we store an entry for that image key with the image type and color.

This process improves the ML performance by a lot because it avoids downloading and classifying all the images from the advertisers every day. It also allows the existence of manual fixes of the image classifications done by our staff or the client.

There is an important caveat, however. In order for the cache system to work optimally, the CDNs used by advertisers have to provide these HTTP headers with the image metadata for us to be able to create a correct image_key.

Some advertisers work with CDNs that don't use the aforementioned information correctly or it is unexistent, in these cases we have to download and use the raw data of the image to create the key.

Known weaknesses and issues

 Edit

Weakness: Model Accuracy decays over time

Our datasets are created from images that are currently within our systems.
This causes the accuracy of classifications to decay over time due to new advertisers coming to the system with different types of images.
The periodical retrains of the model are done to mitigate this decay.

The decay in the accuracy for non-car vehicles is even worse because most of the new advertisers are only car dealers. This makes that over time, the % of non-car vehicles in the training data set is lower and lower, making the retrains not so effective in mitigating the decay of accuracy for other vehicle types

Weakness: High overall accuracy and extreme local accuracy values

After a new iteration of models is trained, we test them against the test data set to extract metrics as accuracy or recall. The accuracy of the models against the test set is usually around 90-94%.

Images of the same advertiser tend to be similar to each other. This causes the local accuracy (accuracy within the advertiser) to usually present more extreme values.

• Advertisers with easy to classify images will have accuracies of around 100%

• Advertisers with conflicting images will have lower accuracies

Issue: Crop of Images with multiple vehicles

When the crop of an image is extracted, the model identifies all the vehicles of the image and extracts the biggest of all. This usually doesn't cause issues because normally the vehicle that we want the advertiser wants to highlight is the biggest but some problematic Placeholder images were found where the crop made it very difficult to identify it as a placeholder image.

Criteria for Image tagging

We use the following criteria to tag the images that are going into the training dataset

• Dealer Images: Images of real vehicles

• Stock Images: Computer generated images with white background

  • In previous models, we also included all types of CGIs but it lowered the overall accuracy of the model and caused other issues.

Understanding the results from ML

The data returned from the ML server is appended to the scrapped vehicles and stored in the advertiser's Sitemap.

When you take a look at the sitemap image and color classification you will see something like this:

Open

1. Image Type received from ML system

   1. This value defaults to “Placeholder” if the ML system could not return a value

2. Color received from ML System

   1. This value defaults to null if the ML system could not return a value

   2. If the color value is configured in the scrape the ML classification for the model is not applied

3. Image Type Manual fix

   1. Image Type manual fix list selects the value returned from the ML system or defaults to Placeholder if None is received.

4. Color Manual fix

   1. Color manual fix list selects the value returned from the ML system or defaults to “Black” if None is received

5. Example of Placeholder tagged from ML system: {Image Type = Placeholder, Color = None}

   1. As you see, as color is not tagged, 5 is not showing anything

   2. Previously tagged Placeholders were {Image Type = Placeholder, Color = 'N/A'}. If you find some of these they are cached values.

       Edit

When you change any value from the Manual fixes list and press the “update” button at the bottom of the list the following happens:

• A historical entry of manual fix is stored in the DB with information of what/who/when the change was made

• The change is pushed to the ML server to modify the cached values for the image type/color of that image

Understanding "Weird" results

There are some cases when by just taking a look at the advertiser sitemap you know that something went wrong with the classification. Here is a list of known cases that can happen:

ML System failed to respond to the request

• How to identify:

  • Lot of images classified as {Image Type = 'Placeholder', Color = 'None'} when they are not obvious placeholder

    • Example: 

      Open

      

• Solution:

  • Relaunch the scrape and if the problem persists contact the dev team.

Placeholder manual fix made by advertisers

• How to identify:

  • The image is classified as {Image Type = 'Placeholder', Color != 'None'}

  • Example: 

    Open

    

• Solution:

  • Manually retag it back or just ignore it. After all the last word on the classification comes from the advertisers.

Different criteria for image types between the advertisers and us

This case documented on 2021-11 is a good example of discrepancies in classifications.

There were two problematic situations happening simultaneously:

1. They used digitally created/enhanced images that under our criteria were “Stock” Images so we manually retagged but the advertiser considered them Dealer images

   1. We concluded that we would only manually retag OBVIOUS misclassifications

   2. We concluded that we would only add to the ML training sets significative examples of each class leaving out conflicting images.

2. The CDN that distributed the images changes the URL and image headers after a few days

   1. This makes the manual retag to not “stay” because for us the image coming after a few days is different due to the image_key calculation

This is a hard case to identify and solve so it probably has to be addressed on an advertiser to advertiser way when it happens.

Examples of conflicting images:

Open

Vehicle 1

Open

Vehicle 2

Open

Vehicle 4

Open

Vehicle 3

Vehicles 1 & 2 are real cars or very realistic CGI (image 1?) over a static background.

Vehicles 3 & 4 are very similar images from two different dealers.

Different criteria between advertisers that share image CDN

We currently have no images with conflicting classifications but there is potential when advertisers share inventory. When storing the classification of an image we store it by image_key|image_url without linking it to an advertiser. This can lead to the scenario where two advertisers that share CDN are manually reclassifying the images against each other.

 Edit

ML Manual fixes and model retrains

We added the option to manually reclassify any image present in a Sitemap in order to handle conflicting images and to have historical data of which type of images are most commonly misclassified.

When a manual fix is requested from the backend panel or frontend:

• A request is sent to the ML server to change the image type or color of that image (identified by its image_key).

• A historical entry of manual fix is saved in the DB with the data of the reclassification, the advertiser the image belongs to, and who did the fix.

Training a new model

After some time passed from the last retrain or if we find very obvious issues with the current model a new one is trained.

The steps followed to train a new model are the following:

Analysis Phase

This step is only done if the model train is caused by a particular issue. We try to analyze why the issue is happening by analyzing both the images incorrectly tagged and the original dataset.

From this phase, we extract information about which images can be causing the issue so we can filter them out from the original dataset and avoid including more examples of that type. Sometimes we also notice things such as imbalances in the number of images for each image type of the data set which can be fixed by looking for new images of that type or by performing some data augmentation.

Dataset Creation Phase

In this step, we work on the creation of the new dataset. We usually use the previous model dataset as a baseline and add/remove images from it in order to improve the results. This is the most tedious and long phase because it has to be done manually by the dev team.

If in the analysis phase we detected some images that could cause issues, the first step is to manually check the original data set and prune all those types of images from it.

Once this is done we begin with the regular process to add images to the dataset:

1. Download all the ML manual fixes for image type done from the last retrain date.

2. Apply automatic filters to delete images that are too small

3. Manually check them to delete misclassification from the client and conflicting images

4. Apply the crop model on them if required

5. Split the resulting images in train/test dataset

6. Extend the previous dataset with the new data.

 Edit

Model Training/Test Phase

With the new dataset, we are ready to begin the training phase.

The training of the new model has to be done in one of the ML servers and the service is down while we train the new models. We create from 4 to 8 new models with different parameter configurations and test them against the test set to see if the preliminary results are valid and have an accuracy/recall high enough to be put in production.

If the training was triggered by very bad results on a particular advertiser we sometimes create an ad-hoc test dataset with the advertiser to check the results for that particular advertiser.

Once one of the new models is selected for production, it is deployed and monitored for the following days. If none of the models are good enough we go back to the Analysis phase and work on improving the dataset again.

 Edit