Submission Rules

The submission for this challenge consists of a single textfile in JSON format. Your submission must include exactly one entry for every sequence in the test categorie of the data. An entry consists of the sequence identifier and three lists corresponding to the three velocity components \(vx, vy, vz\). Regarding those velocity components, you must provide a value for each timestamp, i.e. the order of the values in the lists corresponds 1:1 to the given timestamps.

So conceptually your submission should look something like that:

{
  "28": {
    "vx": [ ... ],
    "vy": [ ... ],
    "vz": [ ... ]
          },
  "29": {
    "vx": [ ... ],
    "vy": [ ... ],
    "vz": [ ... ]
          },

  ...

  "88": {
    "vx": [ ... ],
    "vy": [ ... ],
    "vz": [ ... ]
          },
}

Our submission format is strict: anything missing, invalid values, or anything that should not be included like duplicates, wrong sequences, etc. will result in your submission being rejected as invalid. This is to your advantage: each team has only one submission per day, with invalid submissions not counting against that limit.

If your submission passes validation, it enters scoring and will count towards your daily submission limit. A public score will be computed according to scoring and the leaderboard will be updated, showing the world who has the most skills when it comes to eloping to the Moon!

If you struggle with the submission format, we recommend to have a look our competition starter notebook available at Github, which includes some code snippets that might help you out with the generation of valid submission files.