{
  "id": 161434,
  "title": "Very few things learned",
  "url": "/competitions/jigsaw-multilingual-toxic-comment-classification/discussion/161434",
  "author_name": "",
  "post_date": "2020-06-24T21:58:29.492809300Z",
  "votes": 7,
  "comment_count": 1,
  "views": 0,
  "content": "<p>After finishing the <a href=\"https://www.kaggle.com/c/tweet-sentiment-extraction\"><strong>Tweet Sentiment Extraction</strong></a> competition (and learning a ton about NLP and TPUs), I have decided to enter this competition over the last few days of its timeline. This wasn't very wise of me and I should have entered earlier. That being said, here are the few things I have learned: </p>\n\n<ul>\n<li>There are many BERT language flavors: <a href=\"https://huggingface.co/transformers/model_doc/flaubert.html\">FlauBERT</a>, <a href=\"https://github.com/stefan-it/turkish-bert\">BERTurk</a>, <a href=\"https://github.com/dccuchile/beto\">BETO</a>, and so on.</li>\n<li><a href=\"https://huggingface.co/transformers/model_doc/xlmroberta.html\"><strong>XLM-RoBERTa</strong></a> performs very well on multi-lingual/cross-lingual datasets</li>\n<li>Working with <strong>TPUs</strong> is (still) hard!</li>\n<li><strong>Public LB validation</strong> is a thing, especially when the test dataset is different to the train dataset and the public/private split is random (thus making LB probing viable)</li>\n<li><strong>Post-processing</strong> seems to be one of the winning strategies in a lot of top solutions. I should learn how to do it better and spot those patterns if any. </li>\n</ul>\n\n<p>That's it, time to do some computer vision now. ;)</p>",
  "messages": [
    {
      "id": "900538",
      "postDate": "06/24/2020 21:58:29",
      "content": "<p>After finishing the <a href=\"https://www.kaggle.com/c/tweet-sentiment-extraction\"><strong>Tweet Sentiment Extraction</strong></a> competition (and learning a ton about NLP and TPUs), I have decided to enter this competition over the last few days of its timeline. This wasn't very wise of me and I should have entered earlier. That being said, here are the few things I have learned: </p>\n\n<ul>\n<li>There are many BERT language flavors: <a href=\"https://huggingface.co/transformers/model_doc/flaubert.html\">FlauBERT</a>, <a href=\"https://github.com/stefan-it/turkish-bert\">BERTurk</a>, <a href=\"https://github.com/dccuchile/beto\">BETO</a>, and so on.</li>\n<li><a href=\"https://huggingface.co/transformers/model_doc/xlmroberta.html\"><strong>XLM-RoBERTa</strong></a> performs very well on multi-lingual/cross-lingual datasets</li>\n<li>Working with <strong>TPUs</strong> is (still) hard!</li>\n<li><strong>Public LB validation</strong> is a thing, especially when the test dataset is different to the train dataset and the public/private split is random (thus making LB probing viable)</li>\n<li><strong>Post-processing</strong> seems to be one of the winning strategies in a lot of top solutions. I should learn how to do it better and spot those patterns if any. </li>\n</ul>\n\n<p>That's it, time to do some computer vision now. ;)</p>",
      "rawMarkdown": "After finishing the [**Tweet Sentiment Extraction**](https://www.kaggle.com/c/tweet-sentiment-extraction) competition (and learning a ton about NLP and TPUs), I have decided to enter this competition over the last few days of its timeline. This wasn't very wise of me and I should have entered earlier. That being said, here are the few things I have learned: \n\n\n- There are many BERT language flavors: [FlauBERT](https://huggingface.co/transformers/model_doc/flaubert.html), [BERTurk](https://github.com/stefan-it/turkish-bert), [BETO](https://github.com/dccuchile/beto), and so on.\n- [**XLM-RoBERTa**](https://huggingface.co/transformers/model_doc/xlmroberta.html) performs very well on multi-lingual/cross-lingual datasets\n- Working with **TPUs** is (still) hard!\n- **Public LB validation** is a thing, especially when the test dataset is different to the train dataset and the public/private split is random (thus making LB probing viable)\n- **Post-processing** seems to be one of the winning strategies in a lot of top solutions. I should learn how to do it better and spot those patterns if any. \n\nThat's it, time to do some computer vision now. ;)",
      "votes": null
    },
    {
      "id": "912468",
      "postDate": "07/02/2020 13:48:46",
      "content": "<p>that doesnt sound like a few things. getting creative is a skill that one can learn w/ time, e.g. the 1st place's finetuning on the public LB. next step is to practice these bullet-points as the one thing I have learnt over the course of a few years of self-education is that learning theory w/ no practice is vain.</p>\n\n<p>I have learnt to try many ideas as this is a very engineering discipline, like physics 😊 </p>",
      "rawMarkdown": "that doesnt sound like a few things. getting creative is a skill that one can learn w/ time, e.g. the 1st place's finetuning on the public LB. next step is to practice these bullet-points as the one thing I have learnt over the course of a few years of self-education is that learning theory w/ no practice is vain.\n\nI have learnt to try many ideas as this is a very engineering discipline, like physics 😊",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 912468,
      "author_name": "dronych",
      "author_url": "",
      "post_date": "07/02/2020 13:48:46",
      "content": "<p>that doesnt sound like a few things. getting creative is a skill that one can learn w/ time, e.g. the 1st place's finetuning on the public LB. next step is to practice these bullet-points as the one thing I have learnt over the course of a few years of self-education is that learning theory w/ no practice is vain.</p>\n\n<p>I have learnt to try many ideas as this is a very engineering discipline, like physics 😊 </p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "900538": "After finishing the [**Tweet Sentiment Extraction**](https://www.kaggle.com/c/tweet-sentiment-extraction) competition (and learning a ton about NLP and TPUs), I have decided to enter this competition over the last few days of its timeline. This wasn't very wise of me and I should have entered earlier. That being said, here are the few things I have learned: \n\n\n- There are many BERT language flavors: [FlauBERT](https://huggingface.co/transformers/model_doc/flaubert.html), [BERTurk](https://github.com/stefan-it/turkish-bert), [BETO](https://github.com/dccuchile/beto), and so on.\n- [**XLM-RoBERTa**](https://huggingface.co/transformers/model_doc/xlmroberta.html) performs very well on multi-lingual/cross-lingual datasets\n- Working with **TPUs** is (still) hard!\n- **Public LB validation** is a thing, especially when the test dataset is different to the train dataset and the public/private split is random (thus making LB probing viable)\n- **Post-processing** seems to be one of the winning strategies in a lot of top solutions. I should learn how to do it better and spot those patterns if any. \n\nThat's it, time to do some computer vision now. ;)",
    "912468": "that doesnt sound like a few things. getting creative is a skill that one can learn w/ time, e.g. the 1st place's finetuning on the public LB. next step is to practice these bullet-points as the one thing I have learnt over the course of a few years of self-education is that learning theory w/ no practice is vain.\n\nI have learnt to try many ideas as this is a very engineering discipline, like physics 😊"
  },
  "source": "meta"
}