Hey everyone,
\n\nUpdate to this post. Just a heads up headed into the weekend that we're likely going to be closer to the 48-business-hours side of our usual timeline than on the one-day turnaround side. As you can tell with the oddly formatted leaderboard and drastically reduced team size, our process got stuck midway through so we're working on fixing that.
\n\nDon't fear! We didn't remove 2,000 of you as cheaters 😉 , but we've encountered a few snags in the meantime.
\n\nThanks for your patience!
", "messages": [ { "id": 699789, "postDate": "2019-12-21T00:03:22.433Z", "content": "Hey everyone,
\n\nUpdate to this post. Just a heads up headed into the weekend that we're likely going to be closer to the 48-business-hours side of our usual timeline than on the one-day turnaround side. As you can tell with the oddly formatted leaderboard and drastically reduced team size, our process got stuck midway through so we're working on fixing that.
\n\nDon't fear! We didn't remove 2,000 of you as cheaters 😉 , but we've encountered a few snags in the meantime.
\n\nThanks for your patience!
", "rawMarkdown": "Hey everyone,\n\nUpdate to [this post](https://www.kaggle.com/c/ashrae-energy-prediction/discussion/122296). Just a heads up headed into the weekend that we're likely going to be closer to the 48-business-hours side of our usual timeline than on the one-day turnaround side. As you can tell with the oddly formatted leaderboard and drastically reduced team size, our process got stuck midway through so we're working on fixing that.\n\nDon't fear! We didn't remove 2,000 of you as cheaters 😉 , but we've encountered a few snags in the meantime. \n\nThanks for your patience!", "votes": 20 }, { "id": 701673, "postDate": "2019-12-23T18:53:16.223Z", "content": "@addisonhoward can we please get an update 3?:)
", "rawMarkdown": "@addisonhoward can we please get an update 3?:)", "votes": 3, "replies": [ { "id": 701684, "postDate": "2019-12-23T19:11:17.977Z", "content": "Ahmet: they said 48h business hours... => ~6 business days => Given Xmas + week-end, maybe New Year Eve or next year...
", "rawMarkdown": "Ahmet: they said 48h business hours... => ~6 business days => Given Xmas + week-end, maybe New Year Eve or next year...", "votes": 3 }, { "id": 701687, "postDate": "2019-12-23T19:14:34.660Z", "content": "I think they meant 2 business days by 48 hours. But I believe we have to wait until 2020 too.
", "rawMarkdown": "I think they meant 2 business days by 48 hours. But I believe we have to wait until 2020 too.", "votes": 2 } ] }, { "id": 701813, "postDate": "2019-12-24T00:22:26.290Z", "content": "Quick update - we have a working draft containing ~40,000 rescores but need to check some edge cases to make sure we didn't miss valid submissions and to run additional tests to ensure that updating the scores kicks off all of the correct jobs downstream, like reinstating the ~1000+ teams that vanished from the LB. This will take additional time, but will not be done until after Christmas. We will post another update or the scores on the PST afternoon of the 26th. Thank you all for your patience!
", "rawMarkdown": "Quick update - we have a working draft containing ~40,000 rescores but need to check some edge cases to make sure we didn't miss valid submissions and to run additional tests to ensure that updating the scores kicks off all of the correct jobs downstream, like reinstating the ~1000+ teams that vanished from the LB. This will take additional time, but will not be done until after Christmas. We will post another update or the scores on the PST afternoon of the 26th. Thank you all for your patience!", "votes": 2 }, { "id": 701786, "postDate": "2019-12-23T22:58:14.860Z", "content": "Plus the eve´s and time to be clear and forget the last drunking night, this has to be taken in account !
", "rawMarkdown": "Plus the eve´s and time to be clear and forget the last drunking night, this has to be taken in account !\n" }, { "id": 701705, "postDate": "2019-12-23T19:56:09.267Z", "content": "Gone like it is, it seems that I will know my final position for my birthday : January13Th next year...
\n\nHope it will be kind of a gift ;-)
", "rawMarkdown": "Gone like it is, it seems that I will know my final position for my birthday : January13Th next year...\n\nHope it will be kind of a gift ;-) " }, { "id": 700404, "postDate": "2019-12-22T00:10:14.673Z", "rawMarkdown": "", "isDeleted": true } ], "comments": [ { "id": 701673, "author_name": "Ahmet Erdem", "author_url": "", "post_date": "2019-12-23T18:53:16.223000", "content": "@addisonhoward can we please get an update 3?:)
", "votes": 3, "replies": [ { "id": 701684, "author_name": "eagle4", "author_url": "", "post_date": "2019-12-23T19:11:17.977000", "content": "Ahmet: they said 48h business hours... => ~6 business days => Given Xmas + week-end, maybe New Year Eve or next year...
", "votes": 3, "replies": [] }, { "id": 701687, "author_name": "Ahmet Erdem", "author_url": "", "post_date": "2019-12-23T19:14:34.660000", "content": "I think they meant 2 business days by 48 hours. But I believe we have to wait until 2020 too.
", "votes": 2, "replies": [] } ] }, { "id": 701813, "author_name": "Sohier Dane", "author_url": "", "post_date": "2019-12-24T00:22:26.290000", "content": "Quick update - we have a working draft containing ~40,000 rescores but need to check some edge cases to make sure we didn't miss valid submissions and to run additional tests to ensure that updating the scores kicks off all of the correct jobs downstream, like reinstating the ~1000+ teams that vanished from the LB. This will take additional time, but will not be done until after Christmas. We will post another update or the scores on the PST afternoon of the 26th. Thank you all for your patience!
", "votes": 2, "replies": [] }, { "id": 701786, "author_name": "mezoganet", "author_url": "", "post_date": "2019-12-23T22:58:14.860000", "content": "Plus the eve´s and time to be clear and forget the last drunking night, this has to be taken in account !
", "votes": 0, "replies": [] }, { "id": 701705, "author_name": "mezoganet", "author_url": "", "post_date": "2019-12-23T19:56:09.267000", "content": "Gone like it is, it seems that I will know my final position for my birthday : January13Th next year...
\n\nHope it will be kind of a gift ;-)
", "votes": 0, "replies": [] }, { "id": 700404, "author_name": "", "author_url": "", "post_date": "2019-12-22T00:10:14.673000", "content": "", "votes": 0, "replies": [] } ], "raw_markdown_by_id": { "699789": "Hey everyone,\n\nUpdate to [this post](https://www.kaggle.com/c/ashrae-energy-prediction/discussion/122296). Just a heads up headed into the weekend that we're likely going to be closer to the 48-business-hours side of our usual timeline than on the one-day turnaround side. As you can tell with the oddly formatted leaderboard and drastically reduced team size, our process got stuck midway through so we're working on fixing that.\n\nDon't fear! We didn't remove 2,000 of you as cheaters 😉 , but we've encountered a few snags in the meantime. \n\nThanks for your patience!", "701673": "@addisonhoward can we please get an update 3?:)", "701813": "Quick update - we have a working draft containing ~40,000 rescores but need to check some edge cases to make sure we didn't miss valid submissions and to run additional tests to ensure that updating the scores kicks off all of the correct jobs downstream, like reinstating the ~1000+ teams that vanished from the LB. This will take additional time, but will not be done until after Christmas. We will post another update or the scores on the PST afternoon of the 26th. Thank you all for your patience!", "701786": "Plus the eve´s and time to be clear and forget the last drunking night, this has to be taken in account !\n", "701705": "Gone like it is, it seems that I will know my final position for my birthday : January13Th next year...\n\nHope it will be kind of a gift ;-) ", "700404": "" } }