{
  "id": 202729,
  "title": "My Current Learnings From this Competitions !",
  "url": "/competitions/riiid-test-answer-prediction/discussion/202729",
  "author_name": "Athar Sayed",
  "post_date": "2020-12-11T16:28:14.395000",
  "votes": 36,
  "comment_count": 7,
  "views": 0,
  "content": "<ol>\n<li><p>Feature Engineering is Critical and Moreover an optimize way of generating features is also important !</p></li>\n<li><p>Loop Feature Engineering Helps alot to come up with features fast enough and avoid merges ! Hence good ideas is to get comfortable with loops</p></li>\n<li><p><strong>Correctness</strong> of user and content is an important feature , think about ways you can come up with correctness features other than those provided in public kernels(<strong>Note:Use Loops and Dictionaries  Here</strong> ).</p></li>\n<li><p>Rolling and Lags Features will be important , but Our Dataframe needs to be sorted to come up with them ! Moreover it is better to write implementation in Numpy rather than using inbuilt pandas functions ! One Simple Hint is given <a href=\"https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/202714\" target=\"_blank\">here</a></p></li>\n<li><p>Modelling LightGBM works like Magic ! One should Focus on Getting most out of LightGBM and then move onto NN models ! As seen in <strong>M5 Forecasting Accuracy</strong> , Competitions  The <a href=\"https://www.kaggle.com/c/m5-forecasting-accuracy/discussion/163684\" target=\"_blank\">1st Solution</a> , and the <a href=\"https://www.kaggle.com/c/m5-forecasting-accuracy/discussion/163216\" target=\"_blank\">4th Solution</a> , LightGBM fused with robust validation and Feature Engineering can get very high ranks.</p></li>\n<li><p>Rather than using Strong Hyperparameter Tuning and spending alot of time on it , it will be better to do it once or twice ! If we do lot of hyperparameter Tuning it may so happen that Data may overfit on validation set and may not generalize on External Test set unknown to us .</p></li>\n<li><p>Lot of Ensembling and Merges should be avoided to overcome the submission timeout error !</p></li>\n</ol>",
  "messages": [
    {
      "id": 1109404,
      "postDate": "2020-12-11T16:28:14.397Z",
      "content": "<ol>\n<li><p>Feature Engineering is Critical and Moreover an optimize way of generating features is also important !</p></li>\n<li><p>Loop Feature Engineering Helps alot to come up with features fast enough and avoid merges ! Hence good ideas is to get comfortable with loops</p></li>\n<li><p><strong>Correctness</strong> of user and content is an important feature , think about ways you can come up with correctness features other than those provided in public kernels(<strong>Note:Use Loops and Dictionaries  Here</strong> ).</p></li>\n<li><p>Rolling and Lags Features will be important , but Our Dataframe needs to be sorted to come up with them ! Moreover it is better to write implementation in Numpy rather than using inbuilt pandas functions ! One Simple Hint is given <a href=\"https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/202714\" target=\"_blank\">here</a></p></li>\n<li><p>Modelling LightGBM works like Magic ! One should Focus on Getting most out of LightGBM and then move onto NN models ! As seen in <strong>M5 Forecasting Accuracy</strong> , Competitions  The <a href=\"https://www.kaggle.com/c/m5-forecasting-accuracy/discussion/163684\" target=\"_blank\">1st Solution</a> , and the <a href=\"https://www.kaggle.com/c/m5-forecasting-accuracy/discussion/163216\" target=\"_blank\">4th Solution</a> , LightGBM fused with robust validation and Feature Engineering can get very high ranks.</p></li>\n<li><p>Rather than using Strong Hyperparameter Tuning and spending alot of time on it , it will be better to do it once or twice ! If we do lot of hyperparameter Tuning it may so happen that Data may overfit on validation set and may not generalize on External Test set unknown to us .</p></li>\n<li><p>Lot of Ensembling and Merges should be avoided to overcome the submission timeout error !</p></li>\n</ol>",
      "rawMarkdown": "1. Feature Engineering is Critical and Moreover an optimize way of generating features is also important !\n\n2. Loop Feature Engineering Helps alot to come up with features fast enough and avoid merges ! Hence good ideas is to get comfortable with loops\n\n3. **Correctness** of user and content is an important feature , think about ways you can come up with correctness features other than those provided in public kernels(**Note:Use Loops and Dictionaries  Here** ).\n\n4. Rolling and Lags Features will be important , but Our Dataframe needs to be sorted to come up with them ! Moreover it is better to write implementation in Numpy rather than using inbuilt pandas functions ! One Simple Hint is given [here](https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/202714)\n\n5. Modelling LightGBM works like Magic ! One should Focus on Getting most out of LightGBM and then move onto NN models ! As seen in **M5 Forecasting Accuracy** , Competitions  The [1st Solution](https://www.kaggle.com/c/m5-forecasting-accuracy/discussion/163684) , and the [4th Solution](https://www.kaggle.com/c/m5-forecasting-accuracy/discussion/163216) , LightGBM fused with robust validation and Feature Engineering can get very high ranks.\n\n6. Rather than using Strong Hyperparameter Tuning and spending alot of time on it , it will be better to do it once or twice ! If we do lot of hyperparameter Tuning it may so happen that Data may overfit on validation set and may not generalize on External Test set unknown to us .\n\n7. Lot of Ensembling and Merges should be avoided to overcome the submission timeout error !\n\n",
      "votes": 36
    },
    {
      "id": 1118411,
      "postDate": "2020-12-19T03:43:26.393Z",
      "content": "<p>M5 Forecasting Accuracy,aha</p>",
      "rawMarkdown": "M5 Forecasting Accuracy,aha"
    },
    {
      "id": 1115798,
      "postDate": "2020-12-16T15:27:09.600Z",
      "content": "<p>thanks for sharing ! Correctness  is Important！</p>",
      "rawMarkdown": "thanks for sharing ! Correctness  is Important！"
    },
    {
      "id": 1110942,
      "postDate": "2020-12-13T08:17:42.330Z",
      "content": "<p>great insights <a href=\"https://www.kaggle.com/sayedathar11\" target=\"_blank\">@sayedathar11</a> </p>",
      "rawMarkdown": "great insights @sayedathar11 "
    },
    {
      "id": 1121823,
      "postDate": "2020-12-21T23:59:14.010Z",
      "rawMarkdown": "",
      "isDeleted": true
    },
    {
      "id": 1111219,
      "postDate": "2020-12-13T14:35:26.080Z",
      "content": "<p>thank you for sharing</p>",
      "rawMarkdown": "thank you for sharing"
    },
    {
      "id": 1111023,
      "postDate": "2020-12-13T10:03:47.103Z",
      "content": "<p>thanks for sharing !</p>",
      "rawMarkdown": "thanks for sharing !"
    },
    {
      "id": 1109680,
      "postDate": "2020-12-12T00:26:15.660Z",
      "content": "<p>thanks for sharing !</p>",
      "rawMarkdown": "thanks for sharing !"
    }
  ],
  "comments": [
    {
      "id": 1118411,
      "author_name": "zyliang1994",
      "author_url": "",
      "post_date": "2020-12-19T03:43:26.393000",
      "content": "<p>M5 Forecasting Accuracy,aha</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 1115798,
      "author_name": "Jingzhe_Zhu",
      "author_url": "",
      "post_date": "2020-12-16T15:27:09.600000",
      "content": "<p>thanks for sharing ! Correctness  is Important！</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 1110942,
      "author_name": "Ritesh Kumar",
      "author_url": "",
      "post_date": "2020-12-13T08:17:42.330000",
      "content": "<p>great insights <a href=\"https://www.kaggle.com/sayedathar11\" target=\"_blank\">@sayedathar11</a> </p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 1121823,
      "author_name": "",
      "author_url": "",
      "post_date": "2020-12-21T23:59:14.010000",
      "content": "",
      "votes": 0,
      "replies": []
    },
    {
      "id": 1111219,
      "author_name": "Sharlto Cope",
      "author_url": "",
      "post_date": "2020-12-13T14:35:26.080000",
      "content": "<p>thank you for sharing</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 1111023,
      "author_name": "Paul Wang",
      "author_url": "",
      "post_date": "2020-12-13T10:03:47.103000",
      "content": "<p>thanks for sharing !</p>",
      "votes": 0,
      "replies": []
    },
    {
      "id": 1109680,
      "author_name": "Mnka",
      "author_url": "",
      "post_date": "2020-12-12T00:26:15.660000",
      "content": "<p>thanks for sharing !</p>",
      "votes": 0,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "1109404": "1. Feature Engineering is Critical and Moreover an optimize way of generating features is also important !\n\n2. Loop Feature Engineering Helps alot to come up with features fast enough and avoid merges ! Hence good ideas is to get comfortable with loops\n\n3. **Correctness** of user and content is an important feature , think about ways you can come up with correctness features other than those provided in public kernels(**Note:Use Loops and Dictionaries  Here** ).\n\n4. Rolling and Lags Features will be important , but Our Dataframe needs to be sorted to come up with them ! Moreover it is better to write implementation in Numpy rather than using inbuilt pandas functions ! One Simple Hint is given [here](https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/202714)\n\n5. Modelling LightGBM works like Magic ! One should Focus on Getting most out of LightGBM and then move onto NN models ! As seen in **M5 Forecasting Accuracy** , Competitions  The [1st Solution](https://www.kaggle.com/c/m5-forecasting-accuracy/discussion/163684) , and the [4th Solution](https://www.kaggle.com/c/m5-forecasting-accuracy/discussion/163216) , LightGBM fused with robust validation and Feature Engineering can get very high ranks.\n\n6. Rather than using Strong Hyperparameter Tuning and spending alot of time on it , it will be better to do it once or twice ! If we do lot of hyperparameter Tuning it may so happen that Data may overfit on validation set and may not generalize on External Test set unknown to us .\n\n7. Lot of Ensembling and Merges should be avoided to overcome the submission timeout error !\n\n",
    "1118411": "M5 Forecasting Accuracy,aha",
    "1115798": "thanks for sharing ! Correctness  is Important！",
    "1110942": "great insights @sayedathar11 ",
    "1121823": "",
    "1111219": "thank you for sharing",
    "1111023": "thanks for sharing !",
    "1109680": "thanks for sharing !"
  }
}