{
  "id": 4920,
  "title": "Skeletal information in training data",
  "url": "/competitions/multi-modal-gesture-recognition/discussion/4920",
  "author_name": "",
  "post_date": "2013-06-25T09:27:05.150Z",
  "votes": null,
  "comment_count": 1,
  "views": 1142,
  "content": "<p>Dear all, we noticed that in some sequences, skeleton information appears after some initial frames. This affects to some &quot;first gestures&quot; if they are at the beginning of the sequence. Sequences 223, 225 and 228, have several gestures without skeleton information,\r\n therefore, if you use this information in your method, we advise you to discard those sequences.</p>\r\n<p>We are working to ensure that all gestures in the final evaluation data will have the skeleton information.</p>\r\n<p>Sorry for the inconvenient.</p>\r\n<p>Xavier</p>\r\n<p></p>",
  "messages": [
    {
      "id": "26200",
      "postDate": "06/25/2013 09:27:05",
      "content": "<p>Dear all, we noticed that in some sequences, skeleton information appears after some initial frames. This affects to some &quot;first gestures&quot; if they are at the beginning of the sequence. Sequences 223, 225 and 228, have several gestures without skeleton information,\r\n therefore, if you use this information in your method, we advise you to discard those sequences.</p>\r\n<p>We are working to ensure that all gestures in the final evaluation data will have the skeleton information.</p>\r\n<p>Sorry for the inconvenient.</p>\r\n<p>Xavier</p>\r\n<p></p>",
      "rawMarkdown": "",
      "votes": null
    },
    {
      "id": "26457",
      "postDate": "06/30/2013 16:09:43",
      "content": "<p>The same problem found in training data has been found in some validation samples (the ones that are used at this moment to get the score in Kaggle). For some reason, Kinect device does not recorded skeleton information for some of the sequences. Those sequences\r\n are:</p>\r\n<p>Sample00629 to Sample00639</p>\r\n<p>We are validating all the sequences of the &quot;Final evaluation Data&quot; to avoid this issue. All of you using skeleton information on your methods can assume that this information will be available for all sequences of the &quot;Final evaluation data&quot;, therefore,\r\n you can discard those sequences for the moment. Due to the reduced number of affected sequences, the scores provided by Kaggle are a good indicative on where are your methods respect to the other participants.</p>\r\n<p>Sorry for the inconvenience.</p>\r\n<p>Xavier</p>\r\n<p></p>",
      "rawMarkdown": "",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 26457,
      "author_name": "xbaro100272",
      "author_url": "",
      "post_date": "06/30/2013 16:09:43",
      "content": "<p>The same problem found in training data has been found in some validation samples (the ones that are used at this moment to get the score in Kaggle). For some reason, Kinect device does not recorded skeleton information for some of the sequences. Those sequences\r\n are:</p>\r\n<p>Sample00629 to Sample00639</p>\r\n<p>We are validating all the sequences of the &quot;Final evaluation Data&quot; to avoid this issue. All of you using skeleton information on your methods can assume that this information will be available for all sequences of the &quot;Final evaluation data&quot;, therefore,\r\n you can discard those sequences for the moment. Due to the reduced number of affected sequences, the scores provided by Kaggle are a good indicative on where are your methods respect to the other participants.</p>\r\n<p>Sorry for the inconvenience.</p>\r\n<p>Xavier</p>\r\n<p></p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "26200": "",
    "26457": ""
  },
  "source": "meta"
}