{ "id": 5111, "title": "Submission Format", "url": "/competitions/belkin-energy-disaggregation-competition/discussion/5111", "author_name": "", "post_date": "2013-07-16T06:29:13.523Z", "votes": null, "comment_count": 10, "views": 3189, "content": "

Can you clarify if my understanding is correct:

\r\n

1. For each house, list each of the timestamps when any of the appliances is turned on as well as when it is turned off. Is this just another way to represent the information present in AllTaggingInfo in the training sets, for the testing sets?

\r\nId,House,Appliance,TimeStamp,Predicted 1,H1,30,1334300400,0 2,H1,29,1334300400,0 3,H1,15,1334300400,0\r\n

2. The list of appliances that we are required to detect is selected from the training data for that house (AllTaggingInfo) 

\r\n

Do we also need to list the appliances if it is never turned on (as shown in the sample submission)? What timestamp should

\r\n

we use for that?

\r\n

In addition, can you please provide some pointers on how to do event detection? I am a newbie and only have experience with classification.

\r\n

", "messages": [ { "id": "27263", "postDate": "07/16/2013 06:29:13", "content": "

Can you clarify if my understanding is correct:

\r\n

1. For each house, list each of the timestamps when any of the appliances is turned on as well as when it is turned off. Is this just another way to represent the information present in AllTaggingInfo in the training sets, for the testing sets?

\r\nId,House,Appliance,TimeStamp,Predicted 1,H1,30,1334300400,0 2,H1,29,1334300400,0 3,H1,15,1334300400,0\r\n

2. The list of appliances that we are required to detect is selected from the training data for that house (AllTaggingInfo) 

\r\n

Do we also need to list the appliances if it is never turned on (as shown in the sample submission)? What timestamp should

\r\n

we use for that?

\r\n

In addition, can you please provide some pointers on how to do event detection? I am a newbie and only have experience with classification.

\r\n

", "rawMarkdown": "", "votes": null }, { "id": "27273", "postDate": "07/16/2013 13:26:54", "content": "

As I undertand, you're right with 1. Then, the list of appliances and timestamps required to predict are present in the Sample Submission file, and we need to predict for all of them even if one appliance is never turned on in the test data. However, all\r\n appliances present in the Sample Submission file were turned on at least once in the training data.

\r\n

The event detection is part of the competition. One approach could be to build a classifier to predict for each timestamp 1 if there is an event, and 0 if there is no event.

", "rawMarkdown": "", "votes": null }, { "id": "27596", "postDate": "07/24/2013 14:48:54", "content": "

I'd like some further clarification on the submission format:

\n

Column 1 - ID - is this just a running number for each row?

\n

Column 2 - House - This should be [H1,H2,H3,H4] in that order?

\n

Column 3-  Appliance - This should be [1-38] for each house in that order?

\n

Column 4 - TimeStamp - The unix timestamp matching the timestamp in the Testing_XX_XX_XXXX.mat file?

\n

Column 5 - Predicted - This is [0,1] corresponding to whether that appliance is on at that timestamp?

\n

 

\n

Should the sample submission have a row *for each* timestamp in *all* of the 'Testing_XX_XX_XXXX.mat' files, or should the sample submission have a row for each start/stop time for each appliance i.e. 2*the number of events in all of the testing data?

", "rawMarkdown": "", "votes": null }, { "id": "27708", "postDate": "07/26/2013 23:56:06", "content": "

I too would like an answer to gallamine's comment above. Can anyone please clarify?

", "rawMarkdown": "", "votes": null }, { "id": "27838", "postDate": "07/30/2013 15:07:35", "content": "

Bump.

\n

Another question would be, should there be an event number of elements in the submission file? i.e. should it only be start/stop times?

", "rawMarkdown": "", "votes": null }, { "id": "27839", "postDate": "07/30/2013 15:26:18", "content": "

SampleSubmission.csv is your template for what you need to provide.  For each house, appliance, timestamp triplet listed in that file, you should fill in the Predicted column.

", "rawMarkdown": "", "votes": null }, { "id": "27840", "postDate": "07/30/2013 15:37:56", "content": "

The sample submission file only has 219,580 timestamps listed, whereas the Testing_XX_XX....mat files have ~8 million unique timestamps. My confusion was coming from this discrepancy. 

", "rawMarkdown": "", "votes": null }, { "id": "28308", "postDate": "08/06/2013 18:17:22", "content": "

So, there's no need to provide a solution for the whole Testing_XX_XX....mat files? Just the timestamps at the SampleSubmission?

", "rawMarkdown": "", "votes": null }, { "id": "28312", "postDate": "08/06/2013 18:41:53", "content": "

[quote=promeu;28308]

\n

So, there's no need to provide a solution for the whole Testing_XX_XX....mat files? Just the timestamps at the SampleSubmission?

\n

[/quote]

\n

Correct

", "rawMarkdown": "", "votes": null }, { "id": "29945", "postDate": "09/01/2013 17:38:12", "content": "

In the training files, the tagging info have start and end timestamps quantized to the nearest minute. From forum discussions (like the "Zero-length events" thread) the start timestamps are taken to mean the beginning of that minute and the end timestamps are taken to mean the end of that minute.

\n

In the submission file, there is only one timestamp. Is it intended to represent the beginning of a minute or the end of a minute? This could be pretty relevant to appliances that are turned on/off quickly (e.g. garbage disposal).

\n

Thanks in advance for any clarification!

", "rawMarkdown": "", "votes": null }, { "id": "29948", "postDate": "09/01/2013 18:16:30", "content": "

To answer my own question: this distinction doesn't matter, as long as the pattern of the training data start and end timestamps is preserved. A submission "timestamp" of "12:34:00 pm" likely means 12:34:00.000 through 12:34:59.999. In submissions, "timestamps" refer to an interval not a literal instant in time (which I am used to thinking of as the meaning of "timestamp").

", "rawMarkdown": "", "votes": null } ], "comments": [ { "id": 27273, "author_name": "luistp001", "author_url": "", "post_date": "07/16/2013 13:26:54", "content": "

As I undertand, you're right with 1. Then, the list of appliances and timestamps required to predict are present in the Sample Submission file, and we need to predict for all of them even if one appliance is never turned on in the test data. However, all\r\n appliances present in the Sample Submission file were turned on at least once in the training data.

\r\n

The event detection is part of the competition. One approach could be to build a classifier to predict for each timestamp 1 if there is an event, and 0 if there is no event.

", "votes": null, "replies": [] }, { "id": 27596, "author_name": "gallamine", "author_url": "", "post_date": "07/24/2013 14:48:54", "content": "

I'd like some further clarification on the submission format:

\n

Column 1 - ID - is this just a running number for each row?

\n

Column 2 - House - This should be [H1,H2,H3,H4] in that order?

\n

Column 3-  Appliance - This should be [1-38] for each house in that order?

\n

Column 4 - TimeStamp - The unix timestamp matching the timestamp in the Testing_XX_XX_XXXX.mat file?

\n

Column 5 - Predicted - This is [0,1] corresponding to whether that appliance is on at that timestamp?

\n

 

\n

Should the sample submission have a row *for each* timestamp in *all* of the 'Testing_XX_XX_XXXX.mat' files, or should the sample submission have a row for each start/stop time for each appliance i.e. 2*the number of events in all of the testing data?

", "votes": null, "replies": [] }, { "id": 27708, "author_name": "", "author_url": "", "post_date": "07/26/2013 23:56:06", "content": "

I too would like an answer to gallamine's comment above. Can anyone please clarify?

", "votes": null, "replies": [] }, { "id": 27838, "author_name": "gallamine", "author_url": "", "post_date": "07/30/2013 15:07:35", "content": "

Bump.

\n

Another question would be, should there be an event number of elements in the submission file? i.e. should it only be start/stop times?

", "votes": null, "replies": [] }, { "id": 27839, "author_name": "wcukierski", "author_url": "", "post_date": "07/30/2013 15:26:18", "content": "

SampleSubmission.csv is your template for what you need to provide.  For each house, appliance, timestamp triplet listed in that file, you should fill in the Predicted column.

", "votes": null, "replies": [] }, { "id": 27840, "author_name": "gallamine", "author_url": "", "post_date": "07/30/2013 15:37:56", "content": "

The sample submission file only has 219,580 timestamps listed, whereas the Testing_XX_XX....mat files have ~8 million unique timestamps. My confusion was coming from this discrepancy. 

", "votes": null, "replies": [] }, { "id": 28308, "author_name": "pabloromeu", "author_url": "", "post_date": "08/06/2013 18:17:22", "content": "

So, there's no need to provide a solution for the whole Testing_XX_XX....mat files? Just the timestamps at the SampleSubmission?

", "votes": null, "replies": [] }, { "id": 28312, "author_name": "wcukierski", "author_url": "", "post_date": "08/06/2013 18:41:53", "content": "

[quote=promeu;28308]

\n

So, there's no need to provide a solution for the whole Testing_XX_XX....mat files? Just the timestamps at the SampleSubmission?

\n

[/quote]

\n

Correct

", "votes": null, "replies": [] }, { "id": 29945, "author_name": "rosnfeld", "author_url": "", "post_date": "09/01/2013 17:38:12", "content": "

In the training files, the tagging info have start and end timestamps quantized to the nearest minute. From forum discussions (like the "Zero-length events" thread) the start timestamps are taken to mean the beginning of that minute and the end timestamps are taken to mean the end of that minute.

\n

In the submission file, there is only one timestamp. Is it intended to represent the beginning of a minute or the end of a minute? This could be pretty relevant to appliances that are turned on/off quickly (e.g. garbage disposal).

\n

Thanks in advance for any clarification!

", "votes": null, "replies": [] }, { "id": 29948, "author_name": "rosnfeld", "author_url": "", "post_date": "09/01/2013 18:16:30", "content": "

To answer my own question: this distinction doesn't matter, as long as the pattern of the training data start and end timestamps is preserved. A submission "timestamp" of "12:34:00 pm" likely means 12:34:00.000 through 12:34:59.999. In submissions, "timestamps" refer to an interval not a literal instant in time (which I am used to thinking of as the meaning of "timestamp").

", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "27263": "", "27273": "", "27596": "", "27708": "", "27838": "", "27839": "", "27840": "", "28308": "", "28312": "", "29945": "", "29948": "" }, "source": "meta" }