{
  "id": 417292,
  "title": "Question to Competition hosts",
  "url": "/competitions/vesuvius-challenge-ink-detection/discussion/417292",
  "author_name": "",
  "post_date": "2023-06-15T05:20:45.153852300Z",
  "votes": 5,
  "comment_count": 3,
  "views": 0,
  "content": "<p>I have two questions to the hosts of the competitions. </p>\n<p>The first one is why was the validation fragment rotated in the test set.  I fortunately recognized it was rotated and unrotated it for predictions, but I am sure there were many people that got bad lb scores because they were unaware that it was rotated.  If rotation augmentation was not used during training, scores could easily be .1-.2 lower than they should have been.  I feel like data should be presented during evaluation in the same format as they were in the training set.</p>\n<p>Also, why was the public and private lb fragment a part of the same fragment?  I felt like the strategy for this competition was to overfit as much as possible to the public lb because the public lb contained the closest data to the private lb.  I feel like you may have gotten models that generalized better if 15% of one of the training fragments was taken and used as the public lb.  This way the best models would have to generalize to unseen data.</p>",
  "messages": [
    {
      "id": "2303133",
      "postDate": "06/15/2023 05:20:45",
      "content": "<p>I have two questions to the hosts of the competitions. </p>\n<p>The first one is why was the validation fragment rotated in the test set.  I fortunately recognized it was rotated and unrotated it for predictions, but I am sure there were many people that got bad lb scores because they were unaware that it was rotated.  If rotation augmentation was not used during training, scores could easily be .1-.2 lower than they should have been.  I feel like data should be presented during evaluation in the same format as they were in the training set.</p>\n<p>Also, why was the public and private lb fragment a part of the same fragment?  I felt like the strategy for this competition was to overfit as much as possible to the public lb because the public lb contained the closest data to the private lb.  I feel like you may have gotten models that generalized better if 15% of one of the training fragments was taken and used as the public lb.  This way the best models would have to generalize to unseen data.</p>",
      "rawMarkdown": "I have two questions to the hosts of the competitions. \n\nThe first one is why was the validation fragment rotated in the test set.  I fortunately recognized it was rotated and unrotated it for predictions, but I am sure there were many people that got bad lb scores because they were unaware that it was rotated.  If rotation augmentation was not used during training, scores could easily be .1-.2 lower than they should have been.  I feel like data should be presented during evaluation in the same format as they were in the training set.\n\nAlso, why was the public and private lb fragment a part of the same fragment?  I felt like the strategy for this competition was to overfit as much as possible to the public lb because the public lb contained the closest data to the private lb.  I feel like you may have gotten models that generalized better if 15% of one of the training fragments was taken and used as the public lb.  This way the best models would have to generalize to unseen data.",
      "votes": null
    },
    {
      "id": "2303326",
      "postDate": "06/15/2023 08:36:43",
      "content": "<p>I think it is a really bad idea that they give the test samples 90° rotated. Applying the methods to the full scroll you will know the orientation of the text.<br>\nWe used rotations as test time augmentation because it was mentioned in one discussion but only using the 90° rotated scans would probably have further improved our result. I think chumajin reported an improvement of 0.16 between normal and 90° rotated input.<br>\nImho the organizers should evaluate the algorithms on the normal data and 90° rotated to make it really fair. Otherwise that is also just test set overfitting.</p>",
      "rawMarkdown": "I think it is a really bad idea that they give the test samples 90° rotated. Applying the methods to the full scroll you will know the orientation of the text.\nWe used rotations as test time augmentation because it was mentioned in one discussion but only using the 90° rotated scans would probably have further improved our result. I think chumajin reported an improvement of 0.16 between normal and 90° rotated input.\nImho the organizers should evaluate the algorithms on the normal data and 90° rotated to make it really fair. Otherwise that is also just test set overfitting.",
      "votes": null
    },
    {
      "id": "2303332",
      "postDate": "06/15/2023 08:43:32",
      "content": "<p>Our team got little worse results when adding rotation TTA during inference. (we applied rotate90's augmentation during training)<br>\nOur model will probably perform the same whether the fragment is rotated or not, but we can improve the generalization performance by applying augmentations.</p>",
      "rawMarkdown": "Our team got little worse results when adding rotation TTA during inference. (we applied rotate90's augmentation during training)\nOur model will probably perform the same whether the fragment is rotated or not, but we can improve the generalization performance by applying augmentations.",
      "votes": null
    },
    {
      "id": "2303557",
      "postDate": "06/15/2023 10:53:45",
      "content": "<p><a href=\"https://www.kaggle.com/petersk20\" target=\"_blank\">@petersk20</a>,<br>\nHow did you get the validation fragment? Was it made public after final evaluation? I think it would be worth if competion hosts make it public togather with ground truth data, after the competition is finished.</p>",
      "rawMarkdown": "petersk20,\nHow did you get the validation fragment? Was it made public after final evaluation? I think it would be worth if competion hosts make it public togather with ground truth data, after the competition is finished.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 2303326,
      "author_name": "yankir",
      "author_url": "",
      "post_date": "06/15/2023 08:36:43",
      "content": "<p>I think it is a really bad idea that they give the test samples 90° rotated. Applying the methods to the full scroll you will know the orientation of the text.<br>\nWe used rotations as test time augmentation because it was mentioned in one discussion but only using the 90° rotated scans would probably have further improved our result. I think chumajin reported an improvement of 0.16 between normal and 90° rotated input.<br>\nImho the organizers should evaluate the algorithms on the normal data and 90° rotated to make it really fair. Otherwise that is also just test set overfitting.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 2303332,
      "author_name": "tattaka",
      "author_url": "",
      "post_date": "06/15/2023 08:43:32",
      "content": "<p>Our team got little worse results when adding rotation TTA during inference. (we applied rotate90's augmentation during training)<br>\nOur model will probably perform the same whether the fragment is rotated or not, but we can improve the generalization performance by applying augmentations.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 2303557,
      "author_name": "yurikreinin",
      "author_url": "",
      "post_date": "06/15/2023 10:53:45",
      "content": "<p><a href=\"https://www.kaggle.com/petersk20\" target=\"_blank\">@petersk20</a>,<br>\nHow did you get the validation fragment? Was it made public after final evaluation? I think it would be worth if competion hosts make it public togather with ground truth data, after the competition is finished.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "2303133": "I have two questions to the hosts of the competitions. \n\nThe first one is why was the validation fragment rotated in the test set.  I fortunately recognized it was rotated and unrotated it for predictions, but I am sure there were many people that got bad lb scores because they were unaware that it was rotated.  If rotation augmentation was not used during training, scores could easily be .1-.2 lower than they should have been.  I feel like data should be presented during evaluation in the same format as they were in the training set.\n\nAlso, why was the public and private lb fragment a part of the same fragment?  I felt like the strategy for this competition was to overfit as much as possible to the public lb because the public lb contained the closest data to the private lb.  I feel like you may have gotten models that generalized better if 15% of one of the training fragments was taken and used as the public lb.  This way the best models would have to generalize to unseen data.",
    "2303326": "I think it is a really bad idea that they give the test samples 90° rotated. Applying the methods to the full scroll you will know the orientation of the text.\nWe used rotations as test time augmentation because it was mentioned in one discussion but only using the 90° rotated scans would probably have further improved our result. I think chumajin reported an improvement of 0.16 between normal and 90° rotated input.\nImho the organizers should evaluate the algorithms on the normal data and 90° rotated to make it really fair. Otherwise that is also just test set overfitting.",
    "2303332": "Our team got little worse results when adding rotation TTA during inference. (we applied rotate90's augmentation during training)\nOur model will probably perform the same whether the fragment is rotated or not, but we can improve the generalization performance by applying augmentations.",
    "2303557": "petersk20,\nHow did you get the validation fragment? Was it made public after final evaluation? I think it would be worth if competion hosts make it public togather with ground truth data, after the competition is finished."
  },
  "source": "meta"
}