{
  "id": 5246,
  "title": "manually assigning appliances",
  "url": "/competitions/belkin-energy-disaggregation-competition/discussion/5246",
  "author_name": "",
  "post_date": "2013-07-31T12:30:53.717Z",
  "votes": null,
  "comment_count": 3,
  "views": 1513,
  "content": "<p>hi,</p>\n<p>are we allowed to manually predict the appliances (without using machine learning code, only by looking on the plots)?</p>\n<p>&nbsp;</p>",
  "messages": [
    {
      "id": "27878",
      "postDate": "07/31/2013 12:30:53",
      "content": "<p>hi,</p>\n<p>are we allowed to manually predict the appliances (without using machine learning code, only by looking on the plots)?</p>\n<p>&nbsp;</p>",
      "rawMarkdown": "",
      "votes": null
    },
    {
      "id": "27888",
      "postDate": "07/31/2013 14:07:06",
      "content": "<p>Per the <a href=\"../../../../../../wiki/BelkinEnergyDisaggregationCompetitionRules\">rules</a>, this is not allowed.</p>\n<p style=\"padding-left: 30px\">Entries may not use or incorporate information from hand labeling or human prediction of the validation dataset or test data records.</p>",
      "rawMarkdown": "",
      "votes": null
    },
    {
      "id": "27892",
      "postDate": "07/31/2013 14:50:33",
      "content": "<p>hi,</p>\n<p>thx, haven't seen that.</p>\n<p>By the way, there is a typo in the registration section</p>\n<p>BY ENTERING THE COMPETITION YOU ACCEPT THE CONDITIONS STATED IN THESE <br>OFFICIAL RULES INCLUDING THE RULES ON THE <strong>COMPEITION</strong> PAGE, AGREE TO BE <br>BOUND...</p>\n<p>One further question: Are we allowed to write signal detection code for each appliance individually (for example peak detection, power consumption), instead of having one single machine learning code which is capable to learn these features?</p>",
      "rawMarkdown": "",
      "votes": null
    },
    {
      "id": "27893",
      "postDate": "07/31/2013 14:53:44",
      "content": "<p>Thanks for pointing out the typo. Fixed now.</p>\n<p>As long as your approach is automatic it is fine. This means that if we released a new test set tomorrow, you would be able to push a button and predict the appliances without having to manually intervene.</p>",
      "rawMarkdown": "",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 27888,
      "author_name": "wcukierski",
      "author_url": "",
      "post_date": "07/31/2013 14:07:06",
      "content": "<p>Per the <a href=\"../../../../../../wiki/BelkinEnergyDisaggregationCompetitionRules\">rules</a>, this is not allowed.</p>\n<p style=\"padding-left: 30px\">Entries may not use or incorporate information from hand labeling or human prediction of the validation dataset or test data records.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 27892,
      "author_name": "jessicabombaz",
      "author_url": "",
      "post_date": "07/31/2013 14:50:33",
      "content": "<p>hi,</p>\n<p>thx, haven't seen that.</p>\n<p>By the way, there is a typo in the registration section</p>\n<p>BY ENTERING THE COMPETITION YOU ACCEPT THE CONDITIONS STATED IN THESE <br>OFFICIAL RULES INCLUDING THE RULES ON THE <strong>COMPEITION</strong> PAGE, AGREE TO BE <br>BOUND...</p>\n<p>One further question: Are we allowed to write signal detection code for each appliance individually (for example peak detection, power consumption), instead of having one single machine learning code which is capable to learn these features?</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 27893,
      "author_name": "wcukierski",
      "author_url": "",
      "post_date": "07/31/2013 14:53:44",
      "content": "<p>Thanks for pointing out the typo. Fixed now.</p>\n<p>As long as your approach is automatic it is fine. This means that if we released a new test set tomorrow, you would be able to push a button and predict the appliances without having to manually intervene.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "27878": "",
    "27888": "",
    "27892": "",
    "27893": ""
  },
  "source": "meta"
}