{
  "id": 70014,
  "title": "Did anyone experience a submission bug today?",
  "url": "/competitions/PLAsTiCC-2018/discussion/70014",
  "author_name": "",
  "post_date": "2018-10-29T22:35:55.106923400Z",
  "votes": 3,
  "comment_count": 4,
  "views": 0,
  "content": "<p>I made a submission as usual but the score was 13.112 (yes, 13+). So I debugged, debugged and debugged, but didn't find anything wrong. So I turned back to a previous version of my kernel, which was submitted yesterday and scored 1.333. Well, SURPRISINGLY, 13.104...</p>\n\n<p>Just wondering if someone experienced the same...</p>",
  "messages": [
    {
      "id": "412278",
      "postDate": "10/29/2018 22:35:55",
      "content": "<p>I made a submission as usual but the score was 13.112 (yes, 13+). So I debugged, debugged and debugged, but didn't find anything wrong. So I turned back to a previous version of my kernel, which was submitted yesterday and scored 1.333. Well, SURPRISINGLY, 13.104...</p>\n\n<p>Just wondering if someone experienced the same...</p>",
      "rawMarkdown": "I made a submission as usual but the score was 13.112 (yes, 13+). So I debugged, debugged and debugged, but didn't find anything wrong. So I turned back to a previous version of my kernel, which was submitted yesterday and scored 1.333. Well, SURPRISINGLY, 13.104...\n\nJust wondering if someone experienced the same...",
      "votes": null
    },
    {
      "id": "412379",
      "postDate": "10/30/2018 05:32:57",
      "content": "<p>Sorry about that! I went ahead and fixed the underlying sorting issue and rescored the affected submissions.</p>",
      "rawMarkdown": "Sorry about that! I went ahead and fixed the underlying sorting issue and rescored the affected submissions.",
      "votes": null
    },
    {
      "id": "412800",
      "postDate": "10/30/2018 19:50:07",
      "content": "<p>Jeff, thanks very much!</p>",
      "rawMarkdown": "Jeff, thanks very much!",
      "votes": null
    },
    {
      "id": "413677",
      "postDate": "11/01/2018 11:00:32",
      "content": "<p>I had a different bug.  After submission upload completed I pressed make submission button, and the previous submission score appeared. I refreshed, I opened the LB page, none were showing my last sub being scored.  I resubmitted it therefore, and when that one uploaded, the missing one appeared!  As a result I lost one sub as I submitted twice the same.</p>\n\n<p>It would be great to:</p>\n\n<ol>\n<li><p>Fix this long standing bug where the previous sub score is shown.</p></li>\n<li><p>Add a check that the last submission file is not the same as the previous one.</p></li>\n<li><p>Or, have the ability to cancel scoring of a submission.</p></li>\n</ol>\n\n<p>Items 2 and 3 are to mitigate the bug of item 1.</p>",
      "rawMarkdown": "I had a different bug.  After submission upload completed I pressed make submission button, and the previous submission score appeared. I refreshed, I opened the LB page, none were showing my last sub being scored.  I resubmitted it therefore, and when that one uploaded, the missing one appeared!  As a result I lost one sub as I submitted twice the same.\n\nIt would be great to:\n\n 1. Fix this long standing bug where the previous sub score is shown.\n\n 2. Add a check that the last submission file is not the same as the previous one.\n\n 3. Or, have the ability to cancel scoring of a submission.\n\nItems 2 and 3 are to mitigate the bug of item 1.",
      "votes": null
    },
    {
      "id": "436700",
      "postDate": "12/10/2018 19:14:20",
      "content": "<p>I am wondering if a bug in the scoring or in the submission from kernel has reemerged. I have 3 quite different submissions today that mysteriously score the same 0.917</p>",
      "rawMarkdown": "I am wondering if a bug in the scoring or in the submission from kernel has reemerged. I have 3 quite different submissions today that mysteriously score the same 0.917",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 412379,
      "author_name": "jeffmoser",
      "author_url": "",
      "post_date": "10/30/2018 05:32:57",
      "content": "<p>Sorry about that! I went ahead and fixed the underlying sorting issue and rescored the affected submissions.</p>",
      "votes": null,
      "replies": [
        {
          "id": 412800,
          "author_name": "lfcpeng17",
          "author_url": "",
          "post_date": "10/30/2018 19:50:07",
          "content": "<p>Jeff, thanks very much!</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 436700,
          "author_name": "iprapas",
          "author_url": "",
          "post_date": "12/10/2018 19:14:20",
          "content": "<p>I am wondering if a bug in the scoring or in the submission from kernel has reemerged. I have 3 quite different submissions today that mysteriously score the same 0.917</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 413677,
      "author_name": "cpmpml",
      "author_url": "",
      "post_date": "11/01/2018 11:00:32",
      "content": "<p>I had a different bug.  After submission upload completed I pressed make submission button, and the previous submission score appeared. I refreshed, I opened the LB page, none were showing my last sub being scored.  I resubmitted it therefore, and when that one uploaded, the missing one appeared!  As a result I lost one sub as I submitted twice the same.</p>\n\n<p>It would be great to:</p>\n\n<ol>\n<li><p>Fix this long standing bug where the previous sub score is shown.</p></li>\n<li><p>Add a check that the last submission file is not the same as the previous one.</p></li>\n<li><p>Or, have the ability to cancel scoring of a submission.</p></li>\n</ol>\n\n<p>Items 2 and 3 are to mitigate the bug of item 1.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "412278": "I made a submission as usual but the score was 13.112 (yes, 13+). So I debugged, debugged and debugged, but didn't find anything wrong. So I turned back to a previous version of my kernel, which was submitted yesterday and scored 1.333. Well, SURPRISINGLY, 13.104...\n\nJust wondering if someone experienced the same...",
    "412379": "Sorry about that! I went ahead and fixed the underlying sorting issue and rescored the affected submissions.",
    "412800": "Jeff, thanks very much!",
    "413677": "I had a different bug.  After submission upload completed I pressed make submission button, and the previous submission score appeared. I refreshed, I opened the LB page, none were showing my last sub being scored.  I resubmitted it therefore, and when that one uploaded, the missing one appeared!  As a result I lost one sub as I submitted twice the same.\n\nIt would be great to:\n\n 1. Fix this long standing bug where the previous sub score is shown.\n\n 2. Add a check that the last submission file is not the same as the previous one.\n\n 3. Or, have the ability to cancel scoring of a submission.\n\nItems 2 and 3 are to mitigate the bug of item 1.",
    "436700": "I am wondering if a bug in the scoring or in the submission from kernel has reemerged. I have 3 quite different submissions today that mysteriously score the same 0.917"
  },
  "source": "meta"
}