Skip to content

Repository for my implementation of the Viagogo Coding Challenge

License

Notifications You must be signed in to change notification settings

cyberbeast/viagogochallenge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Viagogo Coding Challenge

Problem Statement

Write a program which accepts a user location as a pair of co-ordinates, and returns a list of the five closest events, along with the cheapest ticket price for each event.

Running the Program

This implementation was programmed in python 3.6. Make sure python 3 is installed on the machine which you intend to use for the evaluation of this implementation.

To run the program, type the following command in a terminal:

python3 main.py

Expected Output

Please Input Coordinates:
> 4,2
Closest Events to (4,2):
Event 2 - $4.61, Distance 2
Event 29 - $15.47, Distance 2
Event 80 - $19.53, Distance 2
Event 15 - $12.45, Distance 3
Event 23 - $1.02, Distance 3

Running Unit Tests

This implementation uses python's unittest framework for testing. Unit tests have been defined in tests.py. This step is not required for running the program.

The unit tests can be called by typing the following command in a terminal:

python3 tests.py

Expected Output

.......
----------------------------------------------------------------------
Ran 7 tests in 0.001s

OK

Assumptions

  • My implementation is based on the following class relationship diagram.

UML Class Diagram for Viagogo Coding Challenge

  • The maximum number of tickets that can be assigned to a randomly generated event has an upper limit on MAX_NUMBER_OF_TICKETS which is set to a default value of 100. When randomly populating the grid with events, the number of tickets that are assigned to an event is determined by a random number 'n' such that 0 <= n <= MAX_NUMBER_OF_TICKETS.
  • Similarly, the maximum price of a randomly generated ticket is capped by MAX_TICKET_PRICE which is set to a default value of 500. When randomly generating tickets, the price of each ticket is determined by a random number 'p' such that 0 < p <= MAX_TICKET_PRICE.
  • The seed value for all the random value generator functions used throughout the program are controlled by SEED_VALUE. This variable is set to a default value of 3. This is done to ensure reproducibility of the random population of the grid with events, tickets and locations.

Other Questions

How might you change your program if you needed to support multiple events at the same location?

  • This program can utilize a list data structure as a data variable inside the Location class. The essence of this modification would be to hold pointers to the Event object that are mapped to this location.
class Location:
    def __init__(self, location, ...):
        ...
        self.x, self.y = location
        self.eventsAtThisLocation = [<event.Event Object>,...]
        ...

How would you change your program if you were working with a much larger world size?

  • For working with a much larger world size and assuming that finding n nearest events is the only query my system needs to respond to, I would try to utilize an optimized strategy on top of a tree-like data structure for representing the world. For example, an R-Tree is a data structure that can be used to effectively store the multi-dimensional information that is used to represent the geographic co-ordinates.

    • A very high level algorithm for incorporating these changes into my implementation would be:
      1. Populate the world by consuming all the random events into an R-Tree. The leaves of this R-Tree would be actual Event class objects as defined in the current implementation.
      2. When querying for the nearest n neighboring events, traverse the R-Tree from the root node, while inserting nodes (representing sub-regions) which overlap the queried location into a queue. Each node in the queue that is a sub-tree is recursively expanded recursively in the same manner. The processing stops when either the required number of neighbors have been found or all the nodes (sub-regions) have been visited.
  • The primary motivation for moving towards a tree-like structure in this regards arises due to the fact that when looking for the n nearest events, the search space for finding these n events need not span the entire input space. In other words, when looking for the top n closest events in New York, the resultant geographical space where these events might exist, would highly unlikely be in Tokyo (unless our world contains very few locations and/or events).

  • Representing the world using an R-Tree would optimize searching by reducing the search space of valid possible regions where a "nearest" event might be at every stage of traversing down the R-Tree.

  • Another benefit of accessing information in this manner is the improvement in time-complexity. Search/Access time-complexity would be O(log n).

  • A min-heap could also be used to optimize the storage of the tickets for a particular event.

  • The image below (accessed from https://upload.wikimedia.org/wikipedia/commons/4/46/R%2A-tree_built_using_topological_split.png) shows an R-Tree representation of US Postal Districts. R-Tree

About

Repository for my implementation of the Viagogo Coding Challenge

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages