Skip to content
This repository was archived by the owner on Jun 16, 2018. It is now read-only.

Feature list

Jump to bottom
sleemans edited this page Aug 12, 2014 · 8 revisions

Please add your contribution to this page for dissemination purposes. Please add:

  • Short description of your module/function + who
  • Value for user
  • Cool features (even 'nerdy' ones)
  • Interesting info
  • Technical info

Mission files Rob van Wijk / Nicky Gerritsen

We have defined a way to describe the missions and challenges in a way that our software can understand and process. Using XML you can define the missions, scores and descriptions, it is even 'readable', check out this example: https://github.com/FirstLegoLeague/fllscoring/blob/master/challenges/xml/2012.xml

The advantage is that now you can easily translate the missions and can present the scoring form in your own language to the teams during your event. This standard also allows you to switch between different challenges without changing the software. You can even create your own challenges (if you know XML) and use the scoring software. Other software could use the same XML files for their challenges, so it can become the standard.

Cool features

  • Easy translation into local language
  • A validator is present to check if there are no mistakes
  • Flexible mission definitions and scoring options

Technical info

Scores log / ranking

Martin Poelstra

Teams can play in one or more rounds, in one or more 'stages' of the tournament (practice rounds, qualifying rounds, final, etc.). Scores may be entered on a variety of devices, for example using the Scoresheet on an iPad. However, there should also be a way to 'manually' enter scores into the system.

Additionally, it is to be expected that errors are made (wrong team number, wrong round number, etc.) while entering scores, so there must be a way to 'moderate' all scores.

The Scores module provides an integrated view of:

  • Scores Log: flat list of all score entries (for all stages and rounds), in order of entry.
  • Scores Matrix: tables listing each team and their scores for each round, ordered by current rank, one table per tournament-stage.
  • Published Ranking: basically the same as the Scores Matrix, but contains published scores (i.e. verified and approved for publication to external scores displays, website, etc.)

The Scores Matrix provides the birds eye overview of scores and ranking, and automatically highlights 'validation errors' (e.g. multiple scores for same round of a team). If errors are found, these can be corrected in the Scores Log.

When no errors are found, the current matrix can be published, which will make these scores available for other services (such as live web feed, displays in public viewing areas, etc.). Depending on the organizer's preference, it should be possible to publish all scores (per stage), or only the scores of e.g. the first two rounds (even if some teams have already played their third round).

The Scores Matrix automatically computes ranking based on rounds played, taking e.g. no-show and disqualification into account. It also handles multiple teams having the exact same rank (which typically happens during the first few matches of a stage).

Status (updated 2014-07-30):

  • after first dev weekend (2014-07-13): initial score log and matrix views have been created, still mostly using example content.
  • in progress (not yet pushed to Github): Angular services have been created for storing stages and scores, unit tests have been updated and expanded, automatic ranking computation in progress, not all tests pass yet.
  • major remaining items (after in-progress changes have been pushed): display of validation errors, editing of scores, publish functionality.

User interface

Sander Leemans

The user interface is the part of the application the users see and work with. Several use cases have been identified (see other parts of this site). Several devices (pc, mac, iPhone, iPad, Android, Windows Phone) were considered, such that for instance referees easily fill in the scores using a tablet, the administration easily manage teams on a desktop, and team queuers have quick overviews of match progress.

Nerdy feature: the interface even optimises for orientation on tablets and phones: rotate the phone, and the interface seamlessly adapts by showing or hiding buttons. Try it!

Clone this wiki locally