{
  "id": 665381,
  "title": "SAMPLE_SUBMISSION.CSV - Submission Fails",
  "url": "/competitions/csiro-biomass/discussion/665381",
  "author_name": "",
  "post_date": "2026-01-01T03:28:00.965599400Z",
  "votes": 6,
  "comment_count": 5,
  "views": 0,
  "content": "<p>I am stuck in the high 0.60's so went looking thru new shared notebooks for some ideas.</p>\n<p>For reasons unknown to us, kaggle elected to include this file(sample_submission.csv) in the input but the file IS NOT present in the private test folder when you make a submission.  So your notebook fails when you do a submission but works OK when you just do a Save Version.  This has been mentioned by me and others in a number of posts but the notebooks I looked at were all recently created and were reading this file.</p>\n<p>For three notebooks that I forked I had successful submissions when I changed sample_submission.csv to test.csv.   Not sure that will work for everyone's use of the file, but I think it will.</p>",
  "messages": [
    {
      "id": "3384351",
      "postDate": "01/01/2026 03:28:00",
      "content": "<p>I am stuck in the high 0.60's so went looking thru new shared notebooks for some ideas.</p>\n<p>For reasons unknown to us, kaggle elected to include this file(sample_submission.csv) in the input but the file IS NOT present in the private test folder when you make a submission.  So your notebook fails when you do a submission but works OK when you just do a Save Version.  This has been mentioned by me and others in a number of posts but the notebooks I looked at were all recently created and were reading this file.</p>\n<p>For three notebooks that I forked I had successful submissions when I changed sample_submission.csv to test.csv.   Not sure that will work for everyone's use of the file, but I think it will.</p>",
      "rawMarkdown": "I am stuck in the high 0.60's so went looking thru new shared notebooks for some ideas.\n\nFor reasons unknown to us, kaggle elected to include this file(sample_submission.csv) in the input but the file IS NOT present in the private test folder when you make a submission.  So your notebook fails when you do a submission but works OK when you just do a Save Version.  This has been mentioned by me and others in a number of posts but the notebooks I looked at were all recently created and were reading this file.\n\nFor three notebooks that I forked I had successful submissions when I changed sample_submission.csv to test.csv.   Not sure that will work for everyone's use of the file, but I think it will.",
      "votes": null
    },
    {
      "id": "3384408",
      "postDate": "01/01/2026 07:35:41",
      "content": "<p>Thank you.</p>",
      "rawMarkdown": "Thank you.",
      "votes": null
    },
    {
      "id": "3384641",
      "postDate": "01/01/2026 16:39:31",
      "content": "<p>Still looking for ideas - three things stuck me today in that adventure.</p>\n<ol>\n<li>This discussion got a down vote.  </li>\n<li>The number of up votes for notebooks that contain this error and cannot generate a successful submission.</li>\n<li>Looking closely at those up votes there is the appearance that folks are gaming the Code process much like Discussion and Datasets.  I am hoping that kaggle has processes in place to identify cross competition up voting.  I hate to see Code have to go the same way that Discussion and Data sets went.</li>\n</ol>",
      "rawMarkdown": "Still looking for ideas - three things stuck me today in that adventure.\n\n1.  This discussion got a down vote.  \n2.  The number of up votes for notebooks that contain this error and cannot generate a successful submission.\n3.  Looking closely at those up votes there is the appearance that folks are gaming the Code process much like Discussion and Datasets.  I am hoping that kaggle has processes in place to identify cross competition up voting.  I hate to see Code have to go the same way that Discussion and Data sets went.",
      "votes": null
    },
    {
      "id": "3384784",
      "postDate": "01/02/2026 00:33:18",
      "content": "<p>you're totally right. After trying all the solutions that supposedly 'work' (just because they have the most votes), it was just a waste of time</p>",
      "rawMarkdown": "you're totally right. After trying all the solutions that supposedly 'work' (just because they have the most votes), it was just a waste of time",
      "votes": null
    },
    {
      "id": "3384787",
      "postDate": "01/02/2026 00:43:38",
      "content": "<p>It has always been a bit of an issue on Kaggle that folks give up-votes without a good look.  Sadly in this competition I gave a few of those that did not work a vote.  If I had not been so aware of the sample_submission.csv issue I would have not noticed on several more that I was ready to up vote :)   </p>\n<p>I have reported one that looks like some gaming going on for votes.  </p>\n<p>My lesson learned - unless a shared notebook has a score - don't up vote it based on appearance - fork and run it!  </p>",
      "rawMarkdown": "It has always been a bit of an issue on Kaggle that folks give up-votes without a good look.  Sadly in this competition I gave a few of those that did not work a vote.  If I had not been so aware of the sample_submission.csv issue I would have not noticed on several more that I was ready to up vote :)   \n\nI have reported one that looks like some gaming going on for votes.  \n\nMy lesson learned - unless a shared notebook has a score - don't up vote it based on appearance - fork and run it!",
      "votes": null
    },
    {
      "id": "3384913",
      "postDate": "01/02/2026 08:36:09",
      "content": "<p>Same here. </p>",
      "rawMarkdown": "Same here.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 3384408,
      "author_name": "markdjadchenko",
      "author_url": "",
      "post_date": "01/01/2026 07:35:41",
      "content": "<p>Thank you.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 3384641,
      "author_name": "pcjimmmy",
      "author_url": "",
      "post_date": "01/01/2026 16:39:31",
      "content": "<p>Still looking for ideas - three things stuck me today in that adventure.</p>\n<ol>\n<li>This discussion got a down vote.  </li>\n<li>The number of up votes for notebooks that contain this error and cannot generate a successful submission.</li>\n<li>Looking closely at those up votes there is the appearance that folks are gaming the Code process much like Discussion and Datasets.  I am hoping that kaggle has processes in place to identify cross competition up voting.  I hate to see Code have to go the same way that Discussion and Data sets went.</li>\n</ol>",
      "votes": null,
      "replies": [
        {
          "id": 3384784,
          "author_name": "giovannyrodrguez",
          "author_url": "",
          "post_date": "01/02/2026 00:33:18",
          "content": "<p>you're totally right. After trying all the solutions that supposedly 'work' (just because they have the most votes), it was just a waste of time</p>",
          "votes": null,
          "replies": [
            {
              "id": 3384787,
              "author_name": "pcjimmmy",
              "author_url": "",
              "post_date": "01/02/2026 00:43:38",
              "content": "<p>It has always been a bit of an issue on Kaggle that folks give up-votes without a good look.  Sadly in this competition I gave a few of those that did not work a vote.  If I had not been so aware of the sample_submission.csv issue I would have not noticed on several more that I was ready to up vote :)   </p>\n<p>I have reported one that looks like some gaming going on for votes.  </p>\n<p>My lesson learned - unless a shared notebook has a score - don't up vote it based on appearance - fork and run it!  </p>",
              "votes": null,
              "replies": []
            }
          ]
        }
      ]
    },
    {
      "id": 3384913,
      "author_name": "hassanrazzaq11",
      "author_url": "",
      "post_date": "01/02/2026 08:36:09",
      "content": "<p>Same here. </p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "3384351": "I am stuck in the high 0.60's so went looking thru new shared notebooks for some ideas.\n\nFor reasons unknown to us, kaggle elected to include this file(sample_submission.csv) in the input but the file IS NOT present in the private test folder when you make a submission.  So your notebook fails when you do a submission but works OK when you just do a Save Version.  This has been mentioned by me and others in a number of posts but the notebooks I looked at were all recently created and were reading this file.\n\nFor three notebooks that I forked I had successful submissions when I changed sample_submission.csv to test.csv.   Not sure that will work for everyone's use of the file, but I think it will.",
    "3384408": "Thank you.",
    "3384641": "Still looking for ideas - three things stuck me today in that adventure.\n\n1.  This discussion got a down vote.  \n2.  The number of up votes for notebooks that contain this error and cannot generate a successful submission.\n3.  Looking closely at those up votes there is the appearance that folks are gaming the Code process much like Discussion and Datasets.  I am hoping that kaggle has processes in place to identify cross competition up voting.  I hate to see Code have to go the same way that Discussion and Data sets went.",
    "3384784": "you're totally right. After trying all the solutions that supposedly 'work' (just because they have the most votes), it was just a waste of time",
    "3384787": "It has always been a bit of an issue on Kaggle that folks give up-votes without a good look.  Sadly in this competition I gave a few of those that did not work a vote.  If I had not been so aware of the sample_submission.csv issue I would have not noticed on several more that I was ready to up vote :)   \n\nI have reported one that looks like some gaming going on for votes.  \n\nMy lesson learned - unless a shared notebook has a score - don't up vote it based on appearance - fork and run it!",
    "3384913": "Same here."
  },
  "source": "meta"
}