{
  "id": 278398,
  "title": "Did I miss something? Why do my Submissions have different execution times? ",
  "url": "/competitions/rsna-miccai-brain-tumor-radiogenomic-classification/discussion/278398",
  "author_name": "",
  "post_date": "2021-10-14T05:27:16.069752200Z",
  "votes": 4,
  "comment_count": 2,
  "views": 0,
  "content": "<p>Hi to all! <br>\nI noticed that the same execution time notebooks when you press the Submission button are executed at different times and differences not in a few minutes but in 8-9 hours. For example, I experimented with one notebook and pressed the Submission button twice in a row: after the first click, the notebook was executed for 9 hours, after the second for 15 minutes. There seemed to be no problem with this bug, but according to the rules of Kaggle, to use Submission for the final results, they must be fully executed. So the real deadline is not at 11:59 PM UTC, but at 11:59 PM UTC minus the notebook execution time. As a result, this bug puts participants in an unequal position, as any notebooks launched in the last 8 hours of the competition may not be accepted, but should be, because their normal execution time is shorter. <br>\nDid I just encounter such a bug or did anyone else encounter it?</p>",
  "messages": [
    {
      "id": "1544146",
      "postDate": "10/14/2021 05:27:16",
      "content": "<p>Hi to all! <br>\nI noticed that the same execution time notebooks when you press the Submission button are executed at different times and differences not in a few minutes but in 8-9 hours. For example, I experimented with one notebook and pressed the Submission button twice in a row: after the first click, the notebook was executed for 9 hours, after the second for 15 minutes. There seemed to be no problem with this bug, but according to the rules of Kaggle, to use Submission for the final results, they must be fully executed. So the real deadline is not at 11:59 PM UTC, but at 11:59 PM UTC minus the notebook execution time. As a result, this bug puts participants in an unequal position, as any notebooks launched in the last 8 hours of the competition may not be accepted, but should be, because their normal execution time is shorter. <br>\nDid I just encounter such a bug or did anyone else encounter it?</p>",
      "rawMarkdown": "Hi to all! \nI noticed that the same execution time notebooks when you press the Submission button are executed at different times and differences not in a few minutes but in 8-9 hours. For example, I experimented with one notebook and pressed the Submission button twice in a row: after the first click, the notebook was executed for 9 hours, after the second for 15 minutes. There seemed to be no problem with this bug, but according to the rules of Kaggle, to use Submission for the final results, they must be fully executed. So the real deadline is not at 11:59 PM UTC, but at 11:59 PM UTC minus the notebook execution time. As a result, this bug puts participants in an unequal position, as any notebooks launched in the last 8 hours of the competition may not be accepted, but should be, because their normal execution time is shorter. \nDid I just encounter such a bug or did anyone else encounter it?",
      "votes": null
    },
    {
      "id": "1544319",
      "postDate": "10/14/2021 08:33:53",
      "content": "<p>I guess it depends on how long and often everyone at Kaggle uses GPU.<br>\nIf many use it, it slows.<br>\nWe have to care about time for submission especially around the deadline, based on the past competition.</p>",
      "rawMarkdown": "I guess it depends on how long and often everyone at Kaggle uses GPU.\nIf many use it, it slows.\nWe have to care about time for submission especially around the deadline, based on the past competition.",
      "votes": null
    },
    {
      "id": "1544334",
      "postDate": "10/14/2021 08:55:26",
      "content": "<p>I already understood this, but not all participants were warned about it, especially beginners, as in my opinion the organizers should clearly indicate on the timeline page that Submission for the possibility of their choice as the final result must be completely executed.</p>",
      "rawMarkdown": "I already understood this, but not all participants were warned about it, especially beginners, as in my opinion the organizers should clearly indicate on the timeline page that Submission for the possibility of their choice as the final result must be completely executed.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1544319,
      "author_name": "drtausamaru",
      "author_url": "",
      "post_date": "10/14/2021 08:33:53",
      "content": "<p>I guess it depends on how long and often everyone at Kaggle uses GPU.<br>\nIf many use it, it slows.<br>\nWe have to care about time for submission especially around the deadline, based on the past competition.</p>",
      "votes": null,
      "replies": [
        {
          "id": 1544334,
          "author_name": "aikhmelnytskyy",
          "author_url": "",
          "post_date": "10/14/2021 08:55:26",
          "content": "<p>I already understood this, but not all participants were warned about it, especially beginners, as in my opinion the organizers should clearly indicate on the timeline page that Submission for the possibility of their choice as the final result must be completely executed.</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "1544146": "Hi to all! \nI noticed that the same execution time notebooks when you press the Submission button are executed at different times and differences not in a few minutes but in 8-9 hours. For example, I experimented with one notebook and pressed the Submission button twice in a row: after the first click, the notebook was executed for 9 hours, after the second for 15 minutes. There seemed to be no problem with this bug, but according to the rules of Kaggle, to use Submission for the final results, they must be fully executed. So the real deadline is not at 11:59 PM UTC, but at 11:59 PM UTC minus the notebook execution time. As a result, this bug puts participants in an unequal position, as any notebooks launched in the last 8 hours of the competition may not be accepted, but should be, because their normal execution time is shorter. \nDid I just encounter such a bug or did anyone else encounter it?",
    "1544319": "I guess it depends on how long and often everyone at Kaggle uses GPU.\nIf many use it, it slows.\nWe have to care about time for submission especially around the deadline, based on the past competition.",
    "1544334": "I already understood this, but not all participants were warned about it, especially beginners, as in my opinion the organizers should clearly indicate on the timeline page that Submission for the possibility of their choice as the final result must be completely executed."
  },
  "source": "meta"
}