Our Team

Daniel Gavrilov
Team Leader

Axel Goetz
Chief Editor

Api Hasthanasombat
Chief Researcher

Team Collaboration

We decided to use Trello, a Kanban style tool, for sharing ideas and setting deadlines. Trello is a tool that allows you to communicate by creating lists, which contain cards. It is a very flexible tool that gives you an easy overview and quick access to important information.

Next we still needed a way to share documents and collaborate on the creation of those documents. We found that Google Drive was an ideal solution since it was free and very easy-to-use.

Version Control

Since we all wanted to develop together, we had to use source control. This would allow us to make changes at the same time and if anything went wrong, we could simply revert back to the last commit.

All of us were used to using Git and Github therefore we decided to use both. However someone would usually set up a repository and then everyone would contribute to that one. But for this project, we needed various repositories for different projects. Therefore we decided to set up an organization, so all of the repositories are in one place.

Our organization’s profile can be found on this link.

Work Packages

For the second part of the term, we assigned each team member various responsibilities. This does not necessarily mean that he had to finish the entire work package on their own but they were responsible for completing it before the internal deadline. Below you can see some of the most important work packages, together with the person responsible.

Api Hasthanasombat

  • Designed segment-generating algorithm
  • Unit tests
  • Implemented websockets
  • Video

Axel Goetz

  • Simulating real-time environment
  • Implemented websockets
  • Implemented segment-generating algorithm
  • Concurrency

Daniel Gavrilov

  • Design and implemented UI
  • Non-linear time scale for visualization
  • Visualized reports on a map
  • Layered approach to algorithm

How we made this website

This website is generated using Jekyll, and the source code it is generated from is available on our website repo.

We chose Jekyll because it allowed us to write all our content in Markdown and have reusable templates which relieve us from editing plain HTML and making mistakes. Our website is modularised, with a separate header, footer, different content layouts for different pages, which allows us to iterate quickly, with changes propagating across all the pages.

Finally, we use a deploy script to automatically sync our locally generated folder with the server folder. It simply asks for our CS username & password and uses rsync to synchronise the folders.