{
  "id": 582388,
  "title": "Chiming my thoughts on this competition",
  "url": "/competitions/cmi-detect-behavior-with-sensor-data/discussion/582388",
  "author_name": "Ravi Ramakrishnan",
  "post_date": "2025-05-30T21:00:47.019000",
  "votes": 137,
  "comment_count": 32,
  "views": 0,
  "content": "<p>Hello all,</p>\n<p>I have participated in quite a few tabular challenges lately and have experience of success and failure in these types of assignments across my tryst with these challenges. I wish to chime a few thoughts regarding this competition in line with my participation in past editions of the challenge (PIU and Sleep States) and similar sized dataset challenges too, hoping these points will help a beginner orient himself/ herself well.</p>\n<p>Please feel free to agree/ disagree with these elements as they will surely help the reader orient him/ herself accordingly. </p>\n<ul>\n<li>The dataset appears huge with a 1.2 GB size but we have approx. 5100 sequences of data here in the training set. This translates to an effective data size of 5100 rows, making this a <strong>small data challenge</strong></li>\n<li>Past CMI competitions, especially the PIU challenge was known for its shakeups. Single models and very simple approaches prevailed while large and complex ensembles failed - this could be a directive for this competition too</li>\n<li>The metric is <strong>prone to shakeup</strong> as a few well classified points will alter the score considerably while a few poor classifications could reduce the score considerably. <strong>Be careful to design simple models that generalize well rather than a lot of complex models with questionable generalization potential</strong></li>\n<li>This is a code competition with an API - beginners transitioning with the playground competitions may find the API a bit different. Please follow the <a href=\"https://www.kaggle.com/code/sohier/cmi-2025-demo-submission\" target=\"_blank\">standard submission kernel</a> as a guideline and edit this for starters</li>\n<li>Remember to <strong>test the prediction values on a dummy train set</strong> before submitting, especially if you are new to this type of competitions - <strong>erroneous submissions are counted in the daily quota</strong>, so be careful and submit correctly </li>\n<li><strong>Non-CV backed blends and blind fuses rarely work in such assignments</strong> - stick to optimizing the CV scheme. You have 3 months going ahead and I am sure this competition does not require that long time to complete</li>\n<li>Usually such competitions will attract a lot of participants and we could witness 4500+ teams at the end of the challenge as well. <strong>A good way to approach such competitions is to set one's goals well and try and realize them as one moves along</strong>. Usually setting easy goals and achieving them all along is better than setting a far sighted and difficult goal that could become difficult to realize.</li>\n<li>Plan your time in August 2025 now and try and gauge if you could make time for this competition - <strong>this competition will conclude on Sep2, so your time in August is crucial</strong></li>\n<li>Start off with simple single models and make way for FE - this is crucial here. We don't need a baroque ensemble here- simple ML models seem to be sufficient if done well. Usually, leaders and toppers focus on FE in such competitions while the rest focus on model training - I am sure one's direction is clear here. </li>\n<li>Finally, keep <strong>track of your work with any experiment tracking tool.</strong> It could be a simple excel sheet, a tool like W&amp;B, Neptune.ai, MLOps tools like Kedro / MLFlow, etc. Experiment tracking is a good way to orient yourself with regard to ideas that worked and did not work and revisit your work later in the competition. Usually these artefacts are useful while teaming up as well as one could articulate the work done with aplomb.</li>\n<li><strong>Save the fitted models and OOF predictions as you move along and keep them handy for later use - this trick will surely help you at the end of the competition when you may want to blend and fuse submissions and models for just an extra bit of alpha</strong></li>\n</ul>\n<p>Finally, have fun - this is a fun-learning filled challenge aimed at making one better at ML models and data wrangling. One learns the best when one enjoys the work done! Try and learn along and improve yourself - the public forums will evolve with time and this is a crucial factor in your final submission. </p>\n<p>All the best for a successful competition and happy learning!<br>\nBest regards,<br>\nRavi R</p>",
  "messages": [
    {
      "id": 3214048,
      "postDate": "2025-05-30T21:00:47.020Z",
      "content": "<p>Hello all,</p>\n<p>I have participated in quite a few tabular challenges lately and have experience of success and failure in these types of assignments across my tryst with these challenges. I wish to chime a few thoughts regarding this competition in line with my participation in past editions of the challenge (PIU and Sleep States) and similar sized dataset challenges too, hoping these points will help a beginner orient himself/ herself well.</p>\n<p>Please feel free to agree/ disagree with these elements as they will surely help the reader orient him/ herself accordingly. </p>\n<ul>\n<li>The dataset appears huge with a 1.2 GB size but we have approx. 5100 sequences of data here in the training set. This translates to an effective data size of 5100 rows, making this a <strong>small data challenge</strong></li>\n<li>Past CMI competitions, especially the PIU challenge was known for its shakeups. Single models and very simple approaches prevailed while large and complex ensembles failed - this could be a directive for this competition too</li>\n<li>The metric is <strong>prone to shakeup</strong> as a few well classified points will alter the score considerably while a few poor classifications could reduce the score considerably. <strong>Be careful to design simple models that generalize well rather than a lot of complex models with questionable generalization potential</strong></li>\n<li>This is a code competition with an API - beginners transitioning with the playground competitions may find the API a bit different. Please follow the <a href=\"https://www.kaggle.com/code/sohier/cmi-2025-demo-submission\" target=\"_blank\">standard submission kernel</a> as a guideline and edit this for starters</li>\n<li>Remember to <strong>test the prediction values on a dummy train set</strong> before submitting, especially if you are new to this type of competitions - <strong>erroneous submissions are counted in the daily quota</strong>, so be careful and submit correctly </li>\n<li><strong>Non-CV backed blends and blind fuses rarely work in such assignments</strong> - stick to optimizing the CV scheme. You have 3 months going ahead and I am sure this competition does not require that long time to complete</li>\n<li>Usually such competitions will attract a lot of participants and we could witness 4500+ teams at the end of the challenge as well. <strong>A good way to approach such competitions is to set one's goals well and try and realize them as one moves along</strong>. Usually setting easy goals and achieving them all along is better than setting a far sighted and difficult goal that could become difficult to realize.</li>\n<li>Plan your time in August 2025 now and try and gauge if you could make time for this competition - <strong>this competition will conclude on Sep2, so your time in August is crucial</strong></li>\n<li>Start off with simple single models and make way for FE - this is crucial here. We don't need a baroque ensemble here- simple ML models seem to be sufficient if done well. Usually, leaders and toppers focus on FE in such competitions while the rest focus on model training - I am sure one's direction is clear here. </li>\n<li>Finally, keep <strong>track of your work with any experiment tracking tool.</strong> It could be a simple excel sheet, a tool like W&amp;B, Neptune.ai, MLOps tools like Kedro / MLFlow, etc. Experiment tracking is a good way to orient yourself with regard to ideas that worked and did not work and revisit your work later in the competition. Usually these artefacts are useful while teaming up as well as one could articulate the work done with aplomb.</li>\n<li><strong>Save the fitted models and OOF predictions as you move along and keep them handy for later use - this trick will surely help you at the end of the competition when you may want to blend and fuse submissions and models for just an extra bit of alpha</strong></li>\n</ul>\n<p>Finally, have fun - this is a fun-learning filled challenge aimed at making one better at ML models and data wrangling. One learns the best when one enjoys the work done! Try and learn along and improve yourself - the public forums will evolve with time and this is a crucial factor in your final submission. </p>\n<p>All the best for a successful competition and happy learning!<br>\nBest regards,<br>\nRavi R</p>",
      "rawMarkdown": "Hello all,\n\nI have participated in quite a few tabular challenges lately and have experience of success and failure in these types of assignments across my tryst with these challenges. I wish to chime a few thoughts regarding this competition in line with my participation in past editions of the challenge (PIU and Sleep States) and similar sized dataset challenges too, hoping these points will help a beginner orient himself/ herself well.\n\nPlease feel free to agree/ disagree with these elements as they will surely help the reader orient him/ herself accordingly. \n\n- The dataset appears huge with a 1.2 GB size but we have approx. 5100 sequences of data here in the training set. This translates to an effective data size of 5100 rows, making this a **small data challenge**\n- Past CMI competitions, especially the PIU challenge was known for its shakeups. Single models and very simple approaches prevailed while large and complex ensembles failed - this could be a directive for this competition too\n- The metric is **prone to shakeup** as a few well classified points will alter the score considerably while a few poor classifications could reduce the score considerably. **Be careful to design simple models that generalize well rather than a lot of complex models with questionable generalization potential**\n- This is a code competition with an API - beginners transitioning with the playground competitions may find the API a bit different. Please follow the [standard submission kernel](https://www.kaggle.com/code/sohier/cmi-2025-demo-submission) as a guideline and edit this for starters\n- Remember to **test the prediction values on a dummy train set** before submitting, especially if you are new to this type of competitions - **erroneous submissions are counted in the daily quota**, so be careful and submit correctly \n- **Non-CV backed blends and blind fuses rarely work in such assignments** - stick to optimizing the CV scheme. You have 3 months going ahead and I am sure this competition does not require that long time to complete\n- Usually such competitions will attract a lot of participants and we could witness 4500+ teams at the end of the challenge as well. **A good way to approach such competitions is to set one's goals well and try and realize them as one moves along**. Usually setting easy goals and achieving them all along is better than setting a far sighted and difficult goal that could become difficult to realize.\n- Plan your time in August 2025 now and try and gauge if you could make time for this competition - **this competition will conclude on Sep2, so your time in August is crucial**\n- Start off with simple single models and make way for FE - this is crucial here. We don't need a baroque ensemble here- simple ML models seem to be sufficient if done well. Usually, leaders and toppers focus on FE in such competitions while the rest focus on model training - I am sure one's direction is clear here. \n- Finally, keep **track of your work with any experiment tracking tool.** It could be a simple excel sheet, a tool like W&B, Neptune.ai, MLOps tools like Kedro / MLFlow, etc. Experiment tracking is a good way to orient yourself with regard to ideas that worked and did not work and revisit your work later in the competition. Usually these artefacts are useful while teaming up as well as one could articulate the work done with aplomb.\n- **Save the fitted models and OOF predictions as you move along and keep them handy for later use - this trick will surely help you at the end of the competition when you may want to blend and fuse submissions and models for just an extra bit of alpha**\n\nFinally, have fun - this is a fun-learning filled challenge aimed at making one better at ML models and data wrangling. One learns the best when one enjoys the work done! Try and learn along and improve yourself - the public forums will evolve with time and this is a crucial factor in your final submission. \n\nAll the best for a successful competition and happy learning!\nBest regards,\nRavi R",
      "votes": 136
    },
    {
      "id": 3214073,
      "postDate": "2025-05-30T22:13:50.360Z",
      "content": "<blockquote>\n  <blockquote>\n    <p>The dataset appears huge with a 1.2 GB   </p>\n  </blockquote>\n</blockquote>\n<p>'huge'.  <br>\nMeanwhile Geophysical Waveform data: ~500 GB 🤣  <br>\nI wish it really was huge…small data is too shaky, I don't like that…  </p>",
      "rawMarkdown": ">>The dataset appears huge with a 1.2 GB   \n\n'huge'.  \nMeanwhile Geophysical Waveform data: ~500 GB 🤣  \nI wish it really was huge...small data is too shaky, I don't like that...  ",
      "votes": 5,
      "replies": [
        {
          "id": 3214196,
          "postDate": "2025-05-31T05:04:49.420Z",
          "rawMarkdown": "",
          "votes": -1,
          "isDeleted": true,
          "replies": [
            {
              "id": 3214203,
              "postDate": "2025-05-31T05:30:44.870Z",
              "content": "<p>Sure, sure, it just made me chuckle.<br>\nI wish I had sposored resources too 🤣</p>",
              "rawMarkdown": "Sure, sure, it just made me chuckle.\nI wish I had sposored resources too 🤣\n"
            }
          ]
        }
      ]
    },
    {
      "id": 3215577,
      "postDate": "2025-06-02T12:45:58.197Z",
      "content": "<p><a href=\"https://www.kaggle.com/ravi20076\" target=\"_blank\">@ravi20076</a>  one of the problem with this type of competitions is towards the end of competition someone shares a kernel with good public score and lot of participants just blindly fork and submit that code this can lead to shakeups as good chunk of competitors are overfitting rather than solving problem at the hand</p>",
      "rawMarkdown": "@ravi20076  one of the problem with this type of competitions is towards the end of competition someone shares a kernel with good public score and lot of participants just blindly fork and submit that code this can lead to shakeups as good chunk of competitors are overfitting rather than solving problem at the hand",
      "votes": 2
    },
    {
      "id": 3218840,
      "postDate": "2025-06-06T19:18:22.940Z",
      "content": "<p>This is a great set of insights. I completely agree that simplicity often leads to the best solutions, particularly in a competition like this where the data size can be misleading. It’s easy to overcomplicate things, but focusing on feature engineering and straightforward models can work wonders.</p>\n<p>The tip about testing on a dummy train set is great. It’s a small step that can save a lot of time and effort later on.</p>\n<p>Thanks for sharing these thoughtful tips.</p>",
      "rawMarkdown": "This is a great set of insights. I completely agree that simplicity often leads to the best solutions, particularly in a competition like this where the data size can be misleading. It’s easy to overcomplicate things, but focusing on feature engineering and straightforward models can work wonders.\n\nThe tip about testing on a dummy train set is great. It’s a small step that can save a lot of time and effort later on.\n\nThanks for sharing these thoughtful tips.",
      "votes": 1
    },
    {
      "id": 3246735,
      "postDate": "2025-07-11T12:34:03.610Z",
      "content": "<p>I had exactly the same thoughts with you for this competition. But unfortunately I face memory issues even with applying a simple logistic regression model. Any help about that? What are the main steps you follow to handle this? </p>",
      "rawMarkdown": "I had exactly the same thoughts with you for this competition. But unfortunately I face memory issues even with applying a simple logistic regression model. Any help about that? What are the main steps you follow to handle this? ",
      "replies": [
        {
          "id": 3250341,
          "postDate": "2025-07-18T06:15:33.277Z",
          "rawMarkdown": "",
          "votes": -1,
          "isDeleted": true
        }
      ]
    },
    {
      "id": 3240806,
      "postDate": "2025-07-04T08:34:18.900Z",
      "content": "<p>Thank you very much for your guidance. I will proceed accordingly and focus on building a strong foundation with simple models and well-thought-out feature engineering.</p>",
      "rawMarkdown": "Thank you very much for your guidance. I will proceed accordingly and focus on building a strong foundation with simple models and well-thought-out feature engineering.\n"
    },
    {
      "id": 3217427,
      "postDate": "2025-06-05T02:17:15.573Z",
      "content": "<p><a href=\"https://www.kaggle.com/ravi20076\" target=\"_blank\">@ravi20076</a> , very useful advise , thanks for your experience sharing, After reading your article, I know how to start is better!</p>",
      "rawMarkdown": "@ravi20076 , very useful advise , thanks for your experience sharing, After reading your article, I know how to start is better!",
      "votes": 1
    },
    {
      "id": 3222517,
      "postDate": "2025-06-12T08:32:36.687Z",
      "content": "<p>Thank you very much for your recommendations. I am sure they will be of great help 😉</p>",
      "rawMarkdown": "Thank you very much for your recommendations. I am sure they will be of great help 😉"
    },
    {
      "id": 3221971,
      "postDate": "2025-06-11T16:36:01.520Z",
      "content": "<p>Really appreciate your advice </p>",
      "rawMarkdown": "Really appreciate your advice "
    },
    {
      "id": 3218468,
      "postDate": "2025-06-06T08:01:41.717Z",
      "content": "<p>Absolutely agree! These wild score swings can be so demoralizing — you put in tons of work and the score barely moves. But I guess that’s what makes these challenges a real test of patience and growth.</p>",
      "rawMarkdown": "Absolutely agree! These wild score swings can be so demoralizing — you put in tons of work and the score barely moves. But I guess that’s what makes these challenges a real test of patience and growth."
    },
    {
      "id": 3216981,
      "postDate": "2025-06-04T11:26:55.660Z",
      "content": "<p>Hi!<br>\nThank you so much for your valuable insights on navigating this competition, especially your emphasis on 'simple models that generalize well' and the observation that this is effectively a 'small data challenge' with only ~5100 sequences.<br>\nThis is my first international competition. Considering the points you have mentioned, I'm curious about your perspective on using deep learning models for this competition. Do you think a DL approach would be suitable here, or would it fall into the category of 'complex models with questionable generalization potential' that you advise against? </p>",
      "rawMarkdown": "Hi!\nThank you so much for your valuable insights on navigating this competition, especially your emphasis on 'simple models that generalize well' and the observation that this is effectively a 'small data challenge' with only ~5100 sequences.\nThis is my first international competition. Considering the points you have mentioned, I'm curious about your perspective on using deep learning models for this competition. Do you think a DL approach would be suitable here, or would it fall into the category of 'complex models with questionable generalization potential' that you advise against? ",
      "replies": [
        {
          "id": 3217003,
          "postDate": "2025-06-04T11:57:47.020Z",
          "content": "<p>Of course you can use deep learning - this post is to remind one of the pitfalls of blind blends and very complex approaches that don't often generalise well <a href=\"https://www.kaggle.com/abdulkareemomer\" target=\"_blank\">@abdulkareemomer</a> </p>",
          "rawMarkdown": "Of course you can use deep learning - this post is to remind one of the pitfalls of blind blends and very complex approaches that don't often generalise well @abdulkareemomer ",
          "replies": [
            {
              "id": 3217020,
              "postDate": "2025-06-04T12:27:10.447Z",
              "content": "<p>Thank you for the clarification.</p>",
              "rawMarkdown": "Thank you for the clarification."
            }
          ]
        },
        {
          "id": 3218068,
          "postDate": "2025-06-05T18:40:05.923Z",
          "content": "<p>I'd go for simpler architectures though. From what <a href=\"https://www.kaggle.com/ravi20076\" target=\"_blank\">@ravi20076</a> points out, shakeup can be brutal if your architecture is too fancy which will increase the odds of overfitting the LB</p>",
          "rawMarkdown": "I'd go for simpler architectures though. From what @ravi20076 points out, shakeup can be brutal if your architecture is too fancy which will increase the odds of overfitting the LB"
        }
      ]
    },
    {
      "id": 3214097,
      "postDate": "2025-05-30T23:45:27.483Z",
      "content": "<p>I see some familiar faces on the discussions then I know this comp will have 4500+ participants 💀</p>",
      "rawMarkdown": "I see some familiar faces on the discussions then I know this comp will have 4500+ participants 💀",
      "votes": 2
    },
    {
      "id": 3216622,
      "postDate": "2025-06-03T20:57:56.187Z",
      "content": "<p>Thanks for the insights! First time in a non-playground competition so it was helpful to get a better understanding of this one! Good luck!</p>",
      "rawMarkdown": "Thanks for the insights! First time in a non-playground competition so it was helpful to get a better understanding of this one! Good luck!"
    },
    {
      "id": 3215682,
      "postDate": "2025-06-02T14:42:46.320Z",
      "content": "<p>Thank you for sharing your perspective. :)<br>\nGiven your experience with similar datasets, would you recommend increasing the dataset size through feature engineering techniques? Would it help create a more substantial dataset for training the machine learning model on customized data?</p>",
      "rawMarkdown": "Thank you for sharing your perspective. :)\nGiven your experience with similar datasets, would you recommend increasing the dataset size through feature engineering techniques? Would it help create a more substantial dataset for training the machine learning model on customized data?"
    },
    {
      "id": 3215197,
      "postDate": "2025-06-01T18:44:30.317Z",
      "content": "<p>Helpful insight….for beginners<br>\nthanks for sharing</p>",
      "rawMarkdown": "Helpful insight....for beginners\nthanks for sharing"
    },
    {
      "id": 3214635,
      "postDate": "2025-05-31T23:01:48.240Z",
      "content": "<p>I've also noticed that in most competitions, simple models tend to prevail, which is fascinating.</p>",
      "rawMarkdown": "I've also noticed that in most competitions, simple models tend to prevail, which is fascinating."
    },
    {
      "id": 3220953,
      "postDate": "2025-06-10T07:33:42.347Z",
      "content": "<p>Thank you for your insights and recommendations.</p>",
      "rawMarkdown": "Thank you for your insights and recommendations.",
      "votes": -1
    },
    {
      "id": 3220456,
      "postDate": "2025-06-09T10:47:56.107Z",
      "content": "<p>That was a great and comprehensive analysis, thank you very much.<br>\nA small question, I currently see 8151 unique sequence_ids in the training dataset, while you mentioned about 5100 sequences. Could this difference be due to different versions of the dataset? Or maybe I'm doing something wrong!?</p>",
      "rawMarkdown": "That was a great and comprehensive analysis, thank you very much.\nA small question, I currently see 8151 unique sequence_ids in the training dataset, while you mentioned about 5100 sequences. Could this difference be due to different versions of the dataset? Or maybe I'm doing something wrong!?\n",
      "votes": -1
    },
    {
      "id": 3220158,
      "postDate": "2025-06-08T22:52:24.370Z",
      "content": "<p>Some really great advice here, thanks Ravi.</p>",
      "rawMarkdown": "Some really great advice here, thanks Ravi.",
      "votes": -1
    },
    {
      "id": 3215107,
      "postDate": "2025-06-01T15:39:41.410Z",
      "content": "<p>It’s a very helpful insight for beginners.. Thanks!</p>",
      "rawMarkdown": "It’s a very helpful insight for beginners.. Thanks!",
      "votes": 1,
      "isDeleted": true
    },
    {
      "id": 3243310,
      "postDate": "2025-07-07T02:26:50.537Z",
      "content": "<p>Thanks for your guidance.</p>",
      "rawMarkdown": "Thanks for your guidance.",
      "votes": 1
    },
    {
      "id": 3220839,
      "postDate": "2025-06-10T03:35:04.213Z",
      "content": "<p>Thanks! It's very useful!</p>",
      "rawMarkdown": "Thanks! It's very useful!",
      "votes": 1
    },
    {
      "id": 3220617,
      "postDate": "2025-06-09T15:48:10.473Z",
      "content": "<p>Thanks a lot for your sharing.</p>",
      "rawMarkdown": "Thanks a lot for your sharing.",
      "votes": 1
    },
    {
      "id": 3218969,
      "postDate": "2025-06-07T01:54:36.487Z",
      "content": "<p>good stuff!</p>",
      "rawMarkdown": "good stuff!",
      "votes": 1
    },
    {
      "id": 3218491,
      "postDate": "2025-06-06T08:52:16.107Z",
      "content": "<p>thanks for sharing your knowledge </p>",
      "rawMarkdown": "thanks for sharing your knowledge ",
      "votes": 1
    },
    {
      "id": 3214513,
      "postDate": "2025-05-31T17:25:37.153Z",
      "content": "<p>Thanks, pretty useful tips.</p>",
      "rawMarkdown": "Thanks, pretty useful tips.",
      "votes": 1
    },
    {
      "id": 3214217,
      "postDate": "2025-05-31T05:57:31.073Z",
      "content": "<p>Thanks! It's cool</p>",
      "rawMarkdown": "Thanks! It's cool\n",
      "votes": 1
    }
  ],
  "comments": [
    {
      "id": 3214073,
      "author_name": "greySnow",
      "author_url": "",
      "post_date": "2025-05-30T22:13:50.360000",
      "content": "<blockquote>\n  <blockquote>\n    <p>The dataset appears huge with a 1.2 GB   </p>\n  </blockquote>\n</blockquote>\n<p>'huge'.  <br>\nMeanwhile Geophysical Waveform data: ~500 GB 🤣  <br>\nI wish it really was huge…small data is too shaky, I don't like that…  </p>",
      "votes": 5,
      "replies": [
        {
          "id": 3214196,
          "author_name": "",
          "author_url": "",
          "post_date": "2025-05-31T05:04:49.420000",
          "content": "",
          "votes": -1,
          "replies": [
            {
              "id": 3214203,
              "author_name": "greySnow",
              "author_url": "",
              "post_date": "2025-05-31T05:30:44.870000",
              "content": "<p>Sure, sure, it just made me chuckle.<br>\nI wish I had sposored resources too 🤣</p>",
              "votes": 0,
              "replies": []
            }
          ]
        }
      ]
    },
    {
      "id": 3215577,
      "author_name": "Athar Sayed",
      "author_url": "",
      "post_date": "2025-06-02T12:45:58.197000",
      "content": "<p><a href=\"https://www.kaggle.com/ravi20076\" target=\"_blank\">@ravi20076</a>  one of the problem with this type of competitions is towards the end of competition someone shares a kernel with good public score and lot of participants just blindly fork and submit that code this can lead to shakeups as good chunk of competitors are overfitting rather than solving problem at the hand</p>",
      "votes": 2,
      "replies": []
    },
    {
      "id": 3218840,
      "author_name": "Sourav Basak Shuvo",
      "author_url": "",
      "post_date": "2025-06-06T19:18:22.940000",
      "content": "<p>This is a great set of insights. I completely agree that simplicity often leads to the best solutions, particularly in a competition like this where the data size can be misleading. It’s easy to overcomplicate things, but focusing on feature engineering and straightforward models can work wonders.</p>\n<p>The tip about testing on a dummy train set is great. It’s a small step that can save a lot of time and effort later on.</p>\n<p>Thanks for sharing these thoughtful tips.</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3246735,
      "author_name": "Aristotelis Patsopoulos",
      "author_url": "",
      "post_date": "2025-07-11T12:34:03.610000",
      "content": "<p>I had exactly the same thoughts with you for this competition. But unfortunately I face memory issues even with applying a simple logistic regression model. Any help about that? What are the main steps you follow to handle this? </p>",
      "votes": 0,
      "replies": [
        {
          "id": 3250341,
          "author_name": "",
          "author_url": "",
          "post_date": "2025-07-18T06:15:33.277000",
          "content": "",
          "votes": -1,
          "replies": []
        }
      ]
    },
    {
      "id": 3240806,
      "author_name": "Utkarsh Mavi",
      "author_url": "",
      "post_date": "2025-07-04T08:34:18.900000",
      "content": "<p>Thank you very much for your guidance. I will proceed accordingly and focus on building a strong foundation with simple models and well-thought-out feature engineering.</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 3217427,
      "author_name": "Chris_Shen",
      "author_url": "",
      "post_date": "2025-06-05T02:17:15.573000",
      "content": "<p><a href=\"https://www.kaggle.com/ravi20076\" target=\"_blank\">@ravi20076</a> , very useful advise , thanks for your experience sharing, After reading your article, I know how to start is better!</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3222517,
      "author_name": "Ricardo Pirabed A.A.",
      "author_url": "",
      "post_date": "2025-06-12T08:32:36.687000",
      "content": "<p>Thank you very much for your recommendations. I am sure they will be of great help 😉</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 3221971,
      "author_name": "yousef Elshahat",
      "author_url": "",
      "post_date": "2025-06-11T16:36:01.520000",
      "content": "<p>Really appreciate your advice </p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 3218468,
      "author_name": "Sisyphus",
      "author_url": "",
      "post_date": "2025-06-06T08:01:41.717000",
      "content": "<p>Absolutely agree! These wild score swings can be so demoralizing — you put in tons of work and the score barely moves. But I guess that’s what makes these challenges a real test of patience and growth.</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 3216981,
      "author_name": "Abdulkareem Omer",
      "author_url": "",
      "post_date": "2025-06-04T11:26:55.660000",
      "content": "<p>Hi!<br>\nThank you so much for your valuable insights on navigating this competition, especially your emphasis on 'simple models that generalize well' and the observation that this is effectively a 'small data challenge' with only ~5100 sequences.<br>\nThis is my first international competition. Considering the points you have mentioned, I'm curious about your perspective on using deep learning models for this competition. Do you think a DL approach would be suitable here, or would it fall into the category of 'complex models with questionable generalization potential' that you advise against? </p>",
      "votes": 0,
      "replies": [
        {
          "id": 3217003,
          "author_name": "Ravi Ramakrishnan",
          "author_url": "",
          "post_date": "2025-06-04T11:57:47.020000",
          "content": "<p>Of course you can use deep learning - this post is to remind one of the pitfalls of blind blends and very complex approaches that don't often generalise well <a href=\"https://www.kaggle.com/abdulkareemomer\" target=\"_blank\">@abdulkareemomer</a> </p>",
          "votes": 0,
          "replies": [
            {
              "id": 3217020,
              "author_name": "Abdulkareem Omer",
              "author_url": "",
              "post_date": "2025-06-04T12:27:10.447000",
              "content": "<p>Thank you for the clarification.</p>",
              "votes": 0,
              "replies": []
            }
          ]
        },
        {
          "id": 3218068,
          "author_name": "Victor S",
          "author_url": "",
          "post_date": "2025-06-05T18:40:05.923000",
          "content": "<p>I'd go for simpler architectures though. From what <a href=\"https://www.kaggle.com/ravi20076\" target=\"_blank\">@ravi20076</a> points out, shakeup can be brutal if your architecture is too fancy which will increase the odds of overfitting the LB</p>",
          "votes": 0,
          "replies": []
        }
      ]
    },
    {
      "id": 3214097,
      "author_name": "Tom",
      "author_url": "",
      "post_date": "2025-05-30T23:45:27.483000",
      "content": "<p>I see some familiar faces on the discussions then I know this comp will have 4500+ participants 💀</p>",
      "votes": 2,
      "replies": []
    },
    {
      "id": 3216622,
      "author_name": "Márk Antal Csizmadia",
      "author_url": "",
      "post_date": "2025-06-03T20:57:56.187000",
      "content": "<p>Thanks for the insights! First time in a non-playground competition so it was helpful to get a better understanding of this one! Good luck!</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 3215682,
      "author_name": "Ishita",
      "author_url": "",
      "post_date": "2025-06-02T14:42:46.320000",
      "content": "<p>Thank you for sharing your perspective. :)<br>\nGiven your experience with similar datasets, would you recommend increasing the dataset size through feature engineering techniques? Would it help create a more substantial dataset for training the machine learning model on customized data?</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 3215197,
      "author_name": "Sarah Arshad",
      "author_url": "",
      "post_date": "2025-06-01T18:44:30.317000",
      "content": "<p>Helpful insight….for beginners<br>\nthanks for sharing</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 3214635,
      "author_name": "Michael R",
      "author_url": "",
      "post_date": "2025-05-31T23:01:48.240000",
      "content": "<p>I've also noticed that in most competitions, simple models tend to prevail, which is fascinating.</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 3220953,
      "author_name": "Bilal A. Chaudhry",
      "author_url": "",
      "post_date": "2025-06-10T07:33:42.347000",
      "content": "<p>Thank you for your insights and recommendations.</p>",
      "votes": -1,
      "replies": []
    },
    {
      "id": 3220456,
      "author_name": "Mando",
      "author_url": "",
      "post_date": "2025-06-09T10:47:56.107000",
      "content": "<p>That was a great and comprehensive analysis, thank you very much.<br>\nA small question, I currently see 8151 unique sequence_ids in the training dataset, while you mentioned about 5100 sequences. Could this difference be due to different versions of the dataset? Or maybe I'm doing something wrong!?</p>",
      "votes": -1,
      "replies": []
    },
    {
      "id": 3220158,
      "author_name": "Nick Potter",
      "author_url": "",
      "post_date": "2025-06-08T22:52:24.370000",
      "content": "<p>Some really great advice here, thanks Ravi.</p>",
      "votes": -1,
      "replies": []
    },
    {
      "id": 3215107,
      "author_name": "",
      "author_url": "",
      "post_date": "2025-06-01T15:39:41.410000",
      "content": "<p>It’s a very helpful insight for beginners.. Thanks!</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3243310,
      "author_name": "backpack",
      "author_url": "",
      "post_date": "2025-07-07T02:26:50.537000",
      "content": "<p>Thanks for your guidance.</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3220839,
      "author_name": "Kazukichi",
      "author_url": "",
      "post_date": "2025-06-10T03:35:04.213000",
      "content": "<p>Thanks! It's very useful!</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3220617,
      "author_name": "DriveBeyond",
      "author_url": "",
      "post_date": "2025-06-09T15:48:10.473000",
      "content": "<p>Thanks a lot for your sharing.</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3218969,
      "author_name": "roshan",
      "author_url": "",
      "post_date": "2025-06-07T01:54:36.487000",
      "content": "<p>good stuff!</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3218491,
      "author_name": "raman chaudhary jarodiya",
      "author_url": "",
      "post_date": "2025-06-06T08:52:16.107000",
      "content": "<p>thanks for sharing your knowledge </p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3214513,
      "author_name": "Sandeep M",
      "author_url": "",
      "post_date": "2025-05-31T17:25:37.153000",
      "content": "<p>Thanks, pretty useful tips.</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3214217,
      "author_name": "qdssad",
      "author_url": "",
      "post_date": "2025-05-31T05:57:31.073000",
      "content": "<p>Thanks! It's cool</p>",
      "votes": 1,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "3214048": "Hello all,\n\nI have participated in quite a few tabular challenges lately and have experience of success and failure in these types of assignments across my tryst with these challenges. I wish to chime a few thoughts regarding this competition in line with my participation in past editions of the challenge (PIU and Sleep States) and similar sized dataset challenges too, hoping these points will help a beginner orient himself/ herself well.\n\nPlease feel free to agree/ disagree with these elements as they will surely help the reader orient him/ herself accordingly. \n\n- The dataset appears huge with a 1.2 GB size but we have approx. 5100 sequences of data here in the training set. This translates to an effective data size of 5100 rows, making this a **small data challenge**\n- Past CMI competitions, especially the PIU challenge was known for its shakeups. Single models and very simple approaches prevailed while large and complex ensembles failed - this could be a directive for this competition too\n- The metric is **prone to shakeup** as a few well classified points will alter the score considerably while a few poor classifications could reduce the score considerably. **Be careful to design simple models that generalize well rather than a lot of complex models with questionable generalization potential**\n- This is a code competition with an API - beginners transitioning with the playground competitions may find the API a bit different. Please follow the [standard submission kernel](https://www.kaggle.com/code/sohier/cmi-2025-demo-submission) as a guideline and edit this for starters\n- Remember to **test the prediction values on a dummy train set** before submitting, especially if you are new to this type of competitions - **erroneous submissions are counted in the daily quota**, so be careful and submit correctly \n- **Non-CV backed blends and blind fuses rarely work in such assignments** - stick to optimizing the CV scheme. You have 3 months going ahead and I am sure this competition does not require that long time to complete\n- Usually such competitions will attract a lot of participants and we could witness 4500+ teams at the end of the challenge as well. **A good way to approach such competitions is to set one's goals well and try and realize them as one moves along**. Usually setting easy goals and achieving them all along is better than setting a far sighted and difficult goal that could become difficult to realize.\n- Plan your time in August 2025 now and try and gauge if you could make time for this competition - **this competition will conclude on Sep2, so your time in August is crucial**\n- Start off with simple single models and make way for FE - this is crucial here. We don't need a baroque ensemble here- simple ML models seem to be sufficient if done well. Usually, leaders and toppers focus on FE in such competitions while the rest focus on model training - I am sure one's direction is clear here. \n- Finally, keep **track of your work with any experiment tracking tool.** It could be a simple excel sheet, a tool like W&B, Neptune.ai, MLOps tools like Kedro / MLFlow, etc. Experiment tracking is a good way to orient yourself with regard to ideas that worked and did not work and revisit your work later in the competition. Usually these artefacts are useful while teaming up as well as one could articulate the work done with aplomb.\n- **Save the fitted models and OOF predictions as you move along and keep them handy for later use - this trick will surely help you at the end of the competition when you may want to blend and fuse submissions and models for just an extra bit of alpha**\n\nFinally, have fun - this is a fun-learning filled challenge aimed at making one better at ML models and data wrangling. One learns the best when one enjoys the work done! Try and learn along and improve yourself - the public forums will evolve with time and this is a crucial factor in your final submission. \n\nAll the best for a successful competition and happy learning!\nBest regards,\nRavi R",
    "3214073": ">>The dataset appears huge with a 1.2 GB   \n\n'huge'.  \nMeanwhile Geophysical Waveform data: ~500 GB 🤣  \nI wish it really was huge...small data is too shaky, I don't like that...  ",
    "3215577": "@ravi20076  one of the problem with this type of competitions is towards the end of competition someone shares a kernel with good public score and lot of participants just blindly fork and submit that code this can lead to shakeups as good chunk of competitors are overfitting rather than solving problem at the hand",
    "3218840": "This is a great set of insights. I completely agree that simplicity often leads to the best solutions, particularly in a competition like this where the data size can be misleading. It’s easy to overcomplicate things, but focusing on feature engineering and straightforward models can work wonders.\n\nThe tip about testing on a dummy train set is great. It’s a small step that can save a lot of time and effort later on.\n\nThanks for sharing these thoughtful tips.",
    "3246735": "I had exactly the same thoughts with you for this competition. But unfortunately I face memory issues even with applying a simple logistic regression model. Any help about that? What are the main steps you follow to handle this? ",
    "3240806": "Thank you very much for your guidance. I will proceed accordingly and focus on building a strong foundation with simple models and well-thought-out feature engineering.\n",
    "3217427": "@ravi20076 , very useful advise , thanks for your experience sharing, After reading your article, I know how to start is better!",
    "3222517": "Thank you very much for your recommendations. I am sure they will be of great help 😉",
    "3221971": "Really appreciate your advice ",
    "3218468": "Absolutely agree! These wild score swings can be so demoralizing — you put in tons of work and the score barely moves. But I guess that’s what makes these challenges a real test of patience and growth.",
    "3216981": "Hi!\nThank you so much for your valuable insights on navigating this competition, especially your emphasis on 'simple models that generalize well' and the observation that this is effectively a 'small data challenge' with only ~5100 sequences.\nThis is my first international competition. Considering the points you have mentioned, I'm curious about your perspective on using deep learning models for this competition. Do you think a DL approach would be suitable here, or would it fall into the category of 'complex models with questionable generalization potential' that you advise against? ",
    "3214097": "I see some familiar faces on the discussions then I know this comp will have 4500+ participants 💀",
    "3216622": "Thanks for the insights! First time in a non-playground competition so it was helpful to get a better understanding of this one! Good luck!",
    "3215682": "Thank you for sharing your perspective. :)\nGiven your experience with similar datasets, would you recommend increasing the dataset size through feature engineering techniques? Would it help create a more substantial dataset for training the machine learning model on customized data?",
    "3215197": "Helpful insight....for beginners\nthanks for sharing",
    "3214635": "I've also noticed that in most competitions, simple models tend to prevail, which is fascinating.",
    "3220953": "Thank you for your insights and recommendations.",
    "3220456": "That was a great and comprehensive analysis, thank you very much.\nA small question, I currently see 8151 unique sequence_ids in the training dataset, while you mentioned about 5100 sequences. Could this difference be due to different versions of the dataset? Or maybe I'm doing something wrong!?\n",
    "3220158": "Some really great advice here, thanks Ravi.",
    "3215107": "It’s a very helpful insight for beginners.. Thanks!",
    "3243310": "Thanks for your guidance.",
    "3220839": "Thanks! It's very useful!",
    "3220617": "Thanks a lot for your sharing.",
    "3218969": "good stuff!",
    "3218491": "thanks for sharing your knowledge ",
    "3214513": "Thanks, pretty useful tips.",
    "3214217": "Thanks! It's cool\n"
  }
}