{
  "id": 151427,
  "title": "Submission Error fixing",
  "url": "/competitions/prostate-cancer-grade-assessment/discussion/151427",
  "author_name": "Indranil Bhattacharya",
  "post_date": "2020-05-15T13:05:24.816000",
  "votes": 2,
  "comment_count": 0,
  "views": 0,
  "content": "<p>In this competition, we see a lot of kagglers who are struggling to submit. In fact, I was also facing the same issue. Now, once I have realized how the submission process works, I thought of sharing a notebook that shows how to create an inference kernel properly. \nKernel link is <a href=\"https://www.kaggle.com/indranilbhattacharya/image-stats-submission-trial\">here</a>.</p>\n\n<p>This is a simple LGBM model with 7 image stats features. So the model is pretty sub-standard, but the objective of the notebook is to keep everyone on the same page when it comes to submit predictions and get a score.</p>\n\n<p>The issue with submission is the following:\nWhen we are committing our kernel, the code would not be able to access the test data, so your model submission would not be prepared. Probably, because hosts do not want us to receive any information from the test data. However, when we submit, then your kernel would access the test data. Now, that is why we need to prepare an if-else statement, so that when we are just committing, sample submission file (or some other file) can be generated in the output and when we are submitting, the intended file would be submitted. Finally, keep the internet off in your inference kernels.</p>\n\n<p>Happy Kaggling</p>",
  "messages": [
    {
      "id": 849046,
      "postDate": "2020-05-15T13:05:24.817Z",
      "content": "<p>In this competition, we see a lot of kagglers who are struggling to submit. In fact, I was also facing the same issue. Now, once I have realized how the submission process works, I thought of sharing a notebook that shows how to create an inference kernel properly. \nKernel link is <a href=\"https://www.kaggle.com/indranilbhattacharya/image-stats-submission-trial\">here</a>.</p>\n\n<p>This is a simple LGBM model with 7 image stats features. So the model is pretty sub-standard, but the objective of the notebook is to keep everyone on the same page when it comes to submit predictions and get a score.</p>\n\n<p>The issue with submission is the following:\nWhen we are committing our kernel, the code would not be able to access the test data, so your model submission would not be prepared. Probably, because hosts do not want us to receive any information from the test data. However, when we submit, then your kernel would access the test data. Now, that is why we need to prepare an if-else statement, so that when we are just committing, sample submission file (or some other file) can be generated in the output and when we are submitting, the intended file would be submitted. Finally, keep the internet off in your inference kernels.</p>\n\n<p>Happy Kaggling</p>",
      "rawMarkdown": "In this competition, we see a lot of kagglers who are struggling to submit. In fact, I was also facing the same issue. Now, once I have realized how the submission process works, I thought of sharing a notebook that shows how to create an inference kernel properly. \nKernel link is [here](https://www.kaggle.com/indranilbhattacharya/image-stats-submission-trial).\n\nThis is a simple LGBM model with 7 image stats features. So the model is pretty sub-standard, but the objective of the notebook is to keep everyone on the same page when it comes to submit predictions and get a score.\n\nThe issue with submission is the following:\nWhen we are committing our kernel, the code would not be able to access the test data, so your model submission would not be prepared. Probably, because hosts do not want us to receive any information from the test data. However, when we submit, then your kernel would access the test data. Now, that is why we need to prepare an if-else statement, so that when we are just committing, sample submission file (or some other file) can be generated in the output and when we are submitting, the intended file would be submitted. Finally, keep the internet off in your inference kernels.\n\nHappy Kaggling",
      "votes": 2
    }
  ],
  "comments": [],
  "raw_markdown_by_id": {
    "849046": "In this competition, we see a lot of kagglers who are struggling to submit. In fact, I was also facing the same issue. Now, once I have realized how the submission process works, I thought of sharing a notebook that shows how to create an inference kernel properly. \nKernel link is [here](https://www.kaggle.com/indranilbhattacharya/image-stats-submission-trial).\n\nThis is a simple LGBM model with 7 image stats features. So the model is pretty sub-standard, but the objective of the notebook is to keep everyone on the same page when it comes to submit predictions and get a score.\n\nThe issue with submission is the following:\nWhen we are committing our kernel, the code would not be able to access the test data, so your model submission would not be prepared. Probably, because hosts do not want us to receive any information from the test data. However, when we submit, then your kernel would access the test data. Now, that is why we need to prepare an if-else statement, so that when we are just committing, sample submission file (or some other file) can be generated in the output and when we are submitting, the intended file would be submitted. Finally, keep the internet off in your inference kernels.\n\nHappy Kaggling"
  }
}