Coding Period: Week 3

3 minute read

After adding all the new features to Behavior Metrics, this week was all about going back to PilotNet implementation and exploring various augmentations.


  • Preliminaries and Explore Issues
  • Solve Issues with Pull Requests
  • Analyze the New Data Augmentations

Preliminaries and Explore Issues

With this as the beginning, this week’s task was to sort the data augmentation tools. I found the following directions (as issues):

Issue 1 (Unrelated): Update documentation for Behavior Metrics with new features

New features which were added:

  • Randomization in GUI mode and choice of randomization in script mode.
  • Minor fixes in brains to avoid broken image in loop.
  • All image data in Ros bags published as separate image topics.
  • Off-Display generation of complete analysis of a brains performance with selected config file.

All these were added to the documentation [1].

Issue (Unrelated): First Image in script mode is broken while in GUI mode works perfect

This is critically a system issue, so I will not be digging up more on this issue. The main reason is the launching time of brain and gazebo, and how the system performs the initialization.

Issue 2: More Data augmentations to PilotNet framework in DL-studio

Based on previous trainings on the current setup of PilotNet in DL-studio [2], the analysis showed that the trained brain performs quite well in all the circuits and completes them except the Montmelo circuit as shown before in [3]. Hence, the goal is to explore various data augmentations which might help in better generalization.

Issue 3: Add Stacked PilotNet framework to DL-Studio and preliminary analysis

The PilotNet setup with horizon based dataset consisting of sequentially stacked images as shown before in [4] is to be added to DL-Studio with preliminary analysis.

Solve Issues with Pull Requests

To solve the above issues and add update features, the following PRs were created:

PR 1: Updated Documentation for Behavior Metrics

The above requirements of issue 1 were fulfilled and updated.

PR 2: Added more data augmentation features

Various relevant data augmentations were chosen based on the task at hand from the ones provided by TorchVision in [5]. Mostly, minor augmnetations on color was tried as we are not expected to be color invariant. Furthermore, the gaussian blur was given the most importance. It is worth to be noted that the perspective and affine transform might also mislead as the turns might seem more curvy but the target velocity is same. Specifications about the current augmentations:

'gaussian': transforms.GaussianBlur(5, sigma=(0.1, 2.0)),
'jitter': transforms.ColorJitter(brightness=0.2, contrast=0.2, saturation=0.2, hue=0.2),
'perspective':transforms.RandomPerspective(distortion_scale=0.3, p=1.0),
'affine':transforms.RandomAffine(degrees=(-10, 10), translate=(0.1, 0.2), scale=(0.9, 1)),

PilotNet Case 1: Only Gaussian Augmentation

The first expeirment was with a simple gaussian augmentation where the image was blurred randomly with a bounded noise. An example of how the images look after transform can be seen in the following figure and the loss curve can be seen further below case 3. The loss curve is quite less for this case as the labels were normalized.

PilotNet Case 2: Gaussian and Perspective Augmentation

Then the perspective transform was added to slightly modify the perspective as shown below:

PilotNet Case 3: Gaussian, Perspective and Affine Augmentation

Finally, the affine tranformation was added to further complicate the augmentation strategy, it can be realized from the set of images given below. However, the addition of affine transform on top of perspective transform did not being any change in the learning curve as evident from the training curves further below:



Issues and Pull Requests

Issues Created


Pull Requests Created


Pull Requests Closed