{
  "id": 210364,
  "title": "\"Submission Scoring Error\"",
  "url": "/competitions/cassava-leaf-disease-classification/discussion/210364",
  "author_name": "",
  "post_date": "2021-01-10T14:53:10.320466700Z",
  "votes": null,
  "comment_count": 1,
  "views": 0,
  "content": "<p>Hi everyone<br>\nGot error on my submissions \"Submission Scoring Error\", worked fine on my local PC …<br>\nHow can I review the issues and fix? is there runtime limitation for model? mine took ~4.5H on my local PC</p>\n<p>is this a global issue? </p>\n<p>Thanks in advance<br>\nYuval.</p>",
  "messages": [
    {
      "id": "1147503",
      "postDate": "01/10/2021 14:53:10",
      "content": "<p>Hi everyone<br>\nGot error on my submissions \"Submission Scoring Error\", worked fine on my local PC …<br>\nHow can I review the issues and fix? is there runtime limitation for model? mine took ~4.5H on my local PC</p>\n<p>is this a global issue? </p>\n<p>Thanks in advance<br>\nYuval.</p>",
      "rawMarkdown": "Hi everyone\nGot error on my submissions \"Submission Scoring Error\", worked fine on my local PC …\nHow can I review the issues and fix? is there runtime limitation for model? mine took ~4.5H on my local PC\n\nis this a global issue? \n\nThanks in advance\nYuval.",
      "votes": null
    },
    {
      "id": "1148224",
      "postDate": "01/11/2021 02:37:07",
      "content": "<p>It's a global issue for Kaggle competitions that require this type of submission process.  To protect competitions from fairly smart folks cheating; the current submission system has been devised that is a real hindrance to novice users (or even old users like myself).  It's yet another example seen over my 74 years of life where rules to stop the bad 1% have a unhappy impact on the other 99%.  Hopefully a year or so from now Kaggle will have created a submission system that provides us users with more feedback on these errors.</p>\n<p>There are multiple discussion posts in this competition and in other recent competitions that you can search for some clues.  The reasons for error are so numerous that you need to gain the skill set of trouble shooting the Kaggle submission process - sadly this is mostly a skill set not easy used in the real world - of course learning to trouble shoot is a usable skill set - so maybe they are doing us a favor with the current submission system :)</p>\n<p>IF you do want help - my suggestion is to make your kernel public - than come back with a request for help in a new discussion post.  Sometimes the error is one that many of us have stumbled across and fixed.  For sure, your first step should be to \"Run All\" inside the kernel.  </p>\n<p>There is a runtime limitation (depends on use of TPU, or GPU or no accelerator) - but you should see that error on your submissions list - \"Notebook Timeout\"</p>",
      "rawMarkdown": "It's a global issue for Kaggle competitions that require this type of submission process.  To protect competitions from fairly smart folks cheating; the current submission system has been devised that is a real hindrance to novice users (or even old users like myself).  It's yet another example seen over my 74 years of life where rules to stop the bad 1% have a unhappy impact on the other 99%.  Hopefully a year or so from now Kaggle will have created a submission system that provides us users with more feedback on these errors.\n\nThere are multiple discussion posts in this competition and in other recent competitions that you can search for some clues.  The reasons for error are so numerous that you need to gain the skill set of trouble shooting the Kaggle submission process - sadly this is mostly a skill set not easy used in the real world - of course learning to trouble shoot is a usable skill set - so maybe they are doing us a favor with the current submission system :)\n\nIF you do want help - my suggestion is to make your kernel public - than come back with a request for help in a new discussion post.  Sometimes the error is one that many of us have stumbled across and fixed.  For sure, your first step should be to \"Run All\" inside the kernel.  \n\nThere is a runtime limitation (depends on use of TPU, or GPU or no accelerator) - but you should see that error on your submissions list - \"Notebook Timeout\"",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1148224,
      "author_name": "pcjimmmy",
      "author_url": "",
      "post_date": "01/11/2021 02:37:07",
      "content": "<p>It's a global issue for Kaggle competitions that require this type of submission process.  To protect competitions from fairly smart folks cheating; the current submission system has been devised that is a real hindrance to novice users (or even old users like myself).  It's yet another example seen over my 74 years of life where rules to stop the bad 1% have a unhappy impact on the other 99%.  Hopefully a year or so from now Kaggle will have created a submission system that provides us users with more feedback on these errors.</p>\n<p>There are multiple discussion posts in this competition and in other recent competitions that you can search for some clues.  The reasons for error are so numerous that you need to gain the skill set of trouble shooting the Kaggle submission process - sadly this is mostly a skill set not easy used in the real world - of course learning to trouble shoot is a usable skill set - so maybe they are doing us a favor with the current submission system :)</p>\n<p>IF you do want help - my suggestion is to make your kernel public - than come back with a request for help in a new discussion post.  Sometimes the error is one that many of us have stumbled across and fixed.  For sure, your first step should be to \"Run All\" inside the kernel.  </p>\n<p>There is a runtime limitation (depends on use of TPU, or GPU or no accelerator) - but you should see that error on your submissions list - \"Notebook Timeout\"</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "1147503": "Hi everyone\nGot error on my submissions \"Submission Scoring Error\", worked fine on my local PC …\nHow can I review the issues and fix? is there runtime limitation for model? mine took ~4.5H on my local PC\n\nis this a global issue? \n\nThanks in advance\nYuval.",
    "1148224": "It's a global issue for Kaggle competitions that require this type of submission process.  To protect competitions from fairly smart folks cheating; the current submission system has been devised that is a real hindrance to novice users (or even old users like myself).  It's yet another example seen over my 74 years of life where rules to stop the bad 1% have a unhappy impact on the other 99%.  Hopefully a year or so from now Kaggle will have created a submission system that provides us users with more feedback on these errors.\n\nThere are multiple discussion posts in this competition and in other recent competitions that you can search for some clues.  The reasons for error are so numerous that you need to gain the skill set of trouble shooting the Kaggle submission process - sadly this is mostly a skill set not easy used in the real world - of course learning to trouble shoot is a usable skill set - so maybe they are doing us a favor with the current submission system :)\n\nIF you do want help - my suggestion is to make your kernel public - than come back with a request for help in a new discussion post.  Sometimes the error is one that many of us have stumbled across and fixed.  For sure, your first step should be to \"Run All\" inside the kernel.  \n\nThere is a runtime limitation (depends on use of TPU, or GPU or no accelerator) - but you should see that error on your submissions list - \"Notebook Timeout\""
  },
  "source": "meta"
}