{
  "id": 137029,
  "title": "CutMix/MixUp is **Not** All You Need?",
  "url": "/competitions/bengaliai-cv19/discussion/137029",
  "author_name": "",
  "post_date": "2020-03-18T22:09:39.891242Z",
  "votes": 9,
  "comment_count": 9,
  "views": 0,
  "content": "<p>I'm very surprised at the big shake and I don't still understand why I got this place.</p>\n\n<p>I suppose one of reasons why <a href=\"https://www.kaggle.com/c/bengaliai-cv19/discussion/136815\">I got 10th place by very simple solution</a> is using RandomErasing <strong>but not using CutMix/MixUp</strong>.</p>\n\n<p>I think these two are effective in making unseen combinations of components, but <strong>not effective in disentangling interdependence of components in seen graphemes.</strong></p>\n\n<p>What do you think about this?</p>",
  "messages": [
    {
      "id": "778955",
      "postDate": "03/18/2020 22:09:39",
      "content": "<p>I'm very surprised at the big shake and I don't still understand why I got this place.</p>\n\n<p>I suppose one of reasons why <a href=\"https://www.kaggle.com/c/bengaliai-cv19/discussion/136815\">I got 10th place by very simple solution</a> is using RandomErasing <strong>but not using CutMix/MixUp</strong>.</p>\n\n<p>I think these two are effective in making unseen combinations of components, but <strong>not effective in disentangling interdependence of components in seen graphemes.</strong></p>\n\n<p>What do you think about this?</p>",
      "rawMarkdown": "I'm very surprised at the big shake and I don't still understand why I got this place.\n\nI suppose one of reasons why [I got 10th place by very simple solution](https://www.kaggle.com/c/bengaliai-cv19/discussion/136815) is using RandomErasing **but not using CutMix/MixUp**.\n\nI think these two are effective in making unseen combinations of components, but **not effective in disentangling interdependence of components in seen graphemes.**\n\nWhat do you think about this?",
      "votes": null
    },
    {
      "id": "779153",
      "postDate": "03/19/2020 04:13:51",
      "content": "<p>Late sub\n||pucblic|private|\n|---| --- | --- |\n|cutmix|0.9876  |0.9246|\n|no cutmix|0.9830|0.9201|</p>\n\n<p>The score goes down without cutmix in my model.😓 </p>",
      "rawMarkdown": "Late sub\n||pucblic|private|\n|---| --- | --- |\n|cutmix|0.9876  |0.9246|\n|no cutmix|0.9830|0.9201|\n\nThe score goes down without cutmix in my model.😓",
      "votes": null
    },
    {
      "id": "779260",
      "postDate": "03/19/2020 06:42:55",
      "content": "<p>Thanks for sharing your result!</p>\n\n<p>Did you use a simple mask augmentation such as CutOut/RandomErasing?</p>",
      "rawMarkdown": "Thanks for sharing your result!\n\nDid you use a simple mask augmentation such as CutOut/RandomErasing?",
      "votes": null
    },
    {
      "id": "779272",
      "postDate": "03/19/2020 06:56:03",
      "content": "<p>Yes, I use shiftscalerotate and CutOut. \nMaybe, My model only classify seen grapheme and cutmix can be ​​effective for seen grapheme.</p>",
      "rawMarkdown": "Yes, I use shiftscalerotate and CutOut. \nMaybe, My model only classify seen grapheme and cutmix can be ​​effective for seen grapheme.",
      "votes": null
    },
    {
      "id": "779288",
      "postDate": "03/19/2020 07:06:23",
      "content": "<p>This is quite interesting results. Thanks for sharing it!\nMaybe the secret sause appears when we combine random erasing and se average pooling block..?</p>",
      "rawMarkdown": "This is quite interesting results. Thanks for sharing it!\nMaybe the secret sause appears when we combine random erasing and se average pooling block..?",
      "votes": null
    },
    {
      "id": "779316",
      "postDate": "03/19/2020 07:48:29",
      "content": "<p>Hmm..., it is interesting.\nAs <a href=\"/kyoshioka47\">@kyoshioka47</a> says, it is important to use not only RandomErasing but component-wise spatial weighted average pooling like sSE-Pooling ?</p>\n\n<p><a href=\"/d1348k\">@d1348k</a> , how about a pooling layer in your model ?</p>",
      "rawMarkdown": "Hmm..., it is interesting.\nAs @kyoshioka47 says, it is important to use not only RandomErasing but component-wise spatial weighted average pooling like sSE-Pooling ?\n\n@d1348k , how about a pooling layer in your model ?",
      "votes": null
    },
    {
      "id": "779320",
      "postDate": "03/19/2020 07:49:01",
      "content": "<p>I did raise <a href=\"https://www.kaggle.com/c/bengaliai-cv19/discussion/126557\">some questions about the use of CutMix</a>. While I do think it does help, I also think it has to be applied more thoughtfully than at random. People have been sharing CAM-CutMix which IMHO is a really interesting approach to tackle this and not do it purely at random.</p>",
      "rawMarkdown": "I did raise [some questions about the use of CutMix](https://www.kaggle.com/c/bengaliai-cv19/discussion/126557). While I do think it does help, I also think it has to be applied more thoughtfully than at random. People have been sharing CAM-CutMix which IMHO is a really interesting approach to tackle this and not do it purely at random.",
      "votes": null
    },
    {
      "id": "779366",
      "postDate": "03/19/2020 09:09:51",
      "content": "<p>My model use GeM. Here is my head.</p>\n\n<p><img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1977801%2Fd0138e5d3169deeaee7ecf80404c33cf%2FBengalai_head.png?generation=1584608889278316&amp;alt=media\" alt=\"\"></p>",
      "rawMarkdown": "My model use GeM. Here is my head.\n\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1977801%2Fd0138e5d3169deeaee7ecf80404c33cf%2FBengalai_head.png?generation=1584608889278316&amp;alt=media)",
      "votes": null
    },
    {
      "id": "779555",
      "postDate": "03/19/2020 13:23:26",
      "content": "<p>Thanks. Your model seems to have component-wise necks before pooling layer 🤔 Hmm...</p>",
      "rawMarkdown": "Thanks. Your model seems to have component-wise necks before pooling layer 🤔 Hmm...",
      "votes": null
    },
    {
      "id": "779563",
      "postDate": "03/19/2020 13:30:04",
      "content": "<p>Thanks! That post is helpful for me to understand the risk of using CutMix roughly.</p>",
      "rawMarkdown": "Thanks! That post is helpful for me to understand the risk of using CutMix roughly.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 779153,
      "author_name": "d1348k",
      "author_url": "",
      "post_date": "03/19/2020 04:13:51",
      "content": "<p>Late sub\n||pucblic|private|\n|---| --- | --- |\n|cutmix|0.9876  |0.9246|\n|no cutmix|0.9830|0.9201|</p>\n\n<p>The score goes down without cutmix in my model.😓 </p>",
      "votes": null,
      "replies": [
        {
          "id": 779260,
          "author_name": "ttahara",
          "author_url": "",
          "post_date": "03/19/2020 06:42:55",
          "content": "<p>Thanks for sharing your result!</p>\n\n<p>Did you use a simple mask augmentation such as CutOut/RandomErasing?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 779272,
          "author_name": "d1348k",
          "author_url": "",
          "post_date": "03/19/2020 06:56:03",
          "content": "<p>Yes, I use shiftscalerotate and CutOut. \nMaybe, My model only classify seen grapheme and cutmix can be ​​effective for seen grapheme.</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 779288,
          "author_name": "kyoshioka47",
          "author_url": "",
          "post_date": "03/19/2020 07:06:23",
          "content": "<p>This is quite interesting results. Thanks for sharing it!\nMaybe the secret sause appears when we combine random erasing and se average pooling block..?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 779316,
          "author_name": "ttahara",
          "author_url": "",
          "post_date": "03/19/2020 07:48:29",
          "content": "<p>Hmm..., it is interesting.\nAs <a href=\"/kyoshioka47\">@kyoshioka47</a> says, it is important to use not only RandomErasing but component-wise spatial weighted average pooling like sSE-Pooling ?</p>\n\n<p><a href=\"/d1348k\">@d1348k</a> , how about a pooling layer in your model ?</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 779366,
          "author_name": "d1348k",
          "author_url": "",
          "post_date": "03/19/2020 09:09:51",
          "content": "<p>My model use GeM. Here is my head.</p>\n\n<p><img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1977801%2Fd0138e5d3169deeaee7ecf80404c33cf%2FBengalai_head.png?generation=1584608889278316&amp;alt=media\" alt=\"\"></p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 779555,
          "author_name": "ttahara",
          "author_url": "",
          "post_date": "03/19/2020 13:23:26",
          "content": "<p>Thanks. Your model seems to have component-wise necks before pooling layer 🤔 Hmm...</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 779320,
      "author_name": "maxlenormand",
      "author_url": "",
      "post_date": "03/19/2020 07:49:01",
      "content": "<p>I did raise <a href=\"https://www.kaggle.com/c/bengaliai-cv19/discussion/126557\">some questions about the use of CutMix</a>. While I do think it does help, I also think it has to be applied more thoughtfully than at random. People have been sharing CAM-CutMix which IMHO is a really interesting approach to tackle this and not do it purely at random.</p>",
      "votes": null,
      "replies": [
        {
          "id": 779563,
          "author_name": "ttahara",
          "author_url": "",
          "post_date": "03/19/2020 13:30:04",
          "content": "<p>Thanks! That post is helpful for me to understand the risk of using CutMix roughly.</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "778955": "I'm very surprised at the big shake and I don't still understand why I got this place.\n\nI suppose one of reasons why [I got 10th place by very simple solution](https://www.kaggle.com/c/bengaliai-cv19/discussion/136815) is using RandomErasing **but not using CutMix/MixUp**.\n\nI think these two are effective in making unseen combinations of components, but **not effective in disentangling interdependence of components in seen graphemes.**\n\nWhat do you think about this?",
    "779153": "Late sub\n||pucblic|private|\n|---| --- | --- |\n|cutmix|0.9876  |0.9246|\n|no cutmix|0.9830|0.9201|\n\nThe score goes down without cutmix in my model.😓",
    "779260": "Thanks for sharing your result!\n\nDid you use a simple mask augmentation such as CutOut/RandomErasing?",
    "779272": "Yes, I use shiftscalerotate and CutOut. \nMaybe, My model only classify seen grapheme and cutmix can be ​​effective for seen grapheme.",
    "779288": "This is quite interesting results. Thanks for sharing it!\nMaybe the secret sause appears when we combine random erasing and se average pooling block..?",
    "779316": "Hmm..., it is interesting.\nAs @kyoshioka47 says, it is important to use not only RandomErasing but component-wise spatial weighted average pooling like sSE-Pooling ?\n\n@d1348k , how about a pooling layer in your model ?",
    "779320": "I did raise [some questions about the use of CutMix](https://www.kaggle.com/c/bengaliai-cv19/discussion/126557). While I do think it does help, I also think it has to be applied more thoughtfully than at random. People have been sharing CAM-CutMix which IMHO is a really interesting approach to tackle this and not do it purely at random.",
    "779366": "My model use GeM. Here is my head.\n\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1977801%2Fd0138e5d3169deeaee7ecf80404c33cf%2FBengalai_head.png?generation=1584608889278316&amp;alt=media)",
    "779555": "Thanks. Your model seems to have component-wise necks before pooling layer 🤔 Hmm...",
    "779563": "Thanks! That post is helpful for me to understand the risk of using CutMix roughly."
  },
  "source": "meta"
}