{
  "id": 582988,
  "title": "How long does it take to submit the prediction?",
  "url": "/competitions/byu-locating-bacterial-flagellar-motors-2025/discussion/582988",
  "author_name": "",
  "post_date": "2025-06-04T04:55:47.854157600Z",
  "votes": null,
  "comment_count": 2,
  "views": 0,
  "content": "<p>Hello,</p>\n<p>I have been trying to submit my solution, but have not been able to so far.</p>\n<p>First, I made a code that loaded all tomograms, and I think that is quite wrong in terms of RAM. That submission is taking 8 hours so far.</p>\n<p>After that, I made another version that was loading and working with the tomograms one by one, way more friendly in terms of RAM. However, that submission is taking more than 1 hour so far. It feels a little bit shocking when that version needs just a few minutes to deal with the test set (only 3 tomograms).</p>\n<p>This is my first Kaggle competition and I do not know if I am doing something completely wrong. Is it normal to take that long for a submission?</p>\n<p>Thanks so much for your time,<br>\nIgnacio.</p>",
  "messages": [
    {
      "id": "3216771",
      "postDate": "06/04/2025 04:55:47",
      "content": "<p>Hello,</p>\n<p>I have been trying to submit my solution, but have not been able to so far.</p>\n<p>First, I made a code that loaded all tomograms, and I think that is quite wrong in terms of RAM. That submission is taking 8 hours so far.</p>\n<p>After that, I made another version that was loading and working with the tomograms one by one, way more friendly in terms of RAM. However, that submission is taking more than 1 hour so far. It feels a little bit shocking when that version needs just a few minutes to deal with the test set (only 3 tomograms).</p>\n<p>This is my first Kaggle competition and I do not know if I am doing something completely wrong. Is it normal to take that long for a submission?</p>\n<p>Thanks so much for your time,<br>\nIgnacio.</p>",
      "rawMarkdown": "Hello,\n\nI have been trying to submit my solution, but have not been able to so far.\n\nFirst, I made a code that loaded all tomograms, and I think that is quite wrong in terms of RAM. That submission is taking 8 hours so far.\n\nAfter that, I made another version that was loading and working with the tomograms one by one, way more friendly in terms of RAM. However, that submission is taking more than 1 hour so far. It feels a little bit shocking when that version needs just a few minutes to deal with the test set (only 3 tomograms).\n\nThis is my first Kaggle competition and I do not know if I am doing something completely wrong. Is it normal to take that long for a submission?\n\nThanks so much for your time,\nIgnacio.",
      "votes": null
    },
    {
      "id": "3216816",
      "postDate": "06/04/2025 06:03:33",
      "content": "<blockquote>\n  <p>the rerun test dataset contains approximately 900 tomograms. </p>\n</blockquote>\n<p>Just simply extrapolating, if your 3 test tomos run longer than 2min 24sec, the 900 will take more than 12h and you time out. </p>",
      "rawMarkdown": "> the rerun test dataset contains approximately 900 tomograms. \n\nJust simply extrapolating, if your 3 test tomos run longer than 2min 24sec, the 900 will take more than 12h and you time out.",
      "votes": null
    },
    {
      "id": "3216824",
      "postDate": "06/04/2025 06:13:50",
      "content": "<p>Thanks! That makes things quite clear.</p>",
      "rawMarkdown": "Thanks! That makes things quite clear.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 3216816,
      "author_name": "christofhenkel",
      "author_url": "",
      "post_date": "06/04/2025 06:03:33",
      "content": "<blockquote>\n  <p>the rerun test dataset contains approximately 900 tomograms. </p>\n</blockquote>\n<p>Just simply extrapolating, if your 3 test tomos run longer than 2min 24sec, the 900 will take more than 12h and you time out. </p>",
      "votes": null,
      "replies": [
        {
          "id": 3216824,
          "author_name": "ignaciosurezmartn",
          "author_url": "",
          "post_date": "06/04/2025 06:13:50",
          "content": "<p>Thanks! That makes things quite clear.</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "3216771": "Hello,\n\nI have been trying to submit my solution, but have not been able to so far.\n\nFirst, I made a code that loaded all tomograms, and I think that is quite wrong in terms of RAM. That submission is taking 8 hours so far.\n\nAfter that, I made another version that was loading and working with the tomograms one by one, way more friendly in terms of RAM. However, that submission is taking more than 1 hour so far. It feels a little bit shocking when that version needs just a few minutes to deal with the test set (only 3 tomograms).\n\nThis is my first Kaggle competition and I do not know if I am doing something completely wrong. Is it normal to take that long for a submission?\n\nThanks so much for your time,\nIgnacio.",
    "3216816": "> the rerun test dataset contains approximately 900 tomograms. \n\nJust simply extrapolating, if your 3 test tomos run longer than 2min 24sec, the 900 will take more than 12h and you time out.",
    "3216824": "Thanks! That makes things quite clear."
  },
  "source": "meta"
}