{
  "id": 394433,
  "title": "Extra digit(s) on leaderboard score??",
  "url": "/competitions/asl-signs/discussion/394433",
  "author_name": "",
  "post_date": "2023-03-13T14:14:39.080235400Z",
  "votes": null,
  "comment_count": 1,
  "views": 0,
  "content": "<p>Hi all,</p>\n<p>As submissions are really close to each other, it would be nice if the leaderboard could show one (or two?) extra significant digits. It won't be much fun if at the end, the top XXX all show the same number.</p>\n<p>In addition, maybe you could add an extra criterion to push for low-resource solutions, e.g., when the difference between private scores is below a certain 'noise' threshold, rank according to FLOPS or parameters in submitted model?</p>\n<p>That would probably spice up the competition a bit?</p>",
  "messages": [
    {
      "id": "2179991",
      "postDate": "03/13/2023 14:14:39",
      "content": "<p>Hi all,</p>\n<p>As submissions are really close to each other, it would be nice if the leaderboard could show one (or two?) extra significant digits. It won't be much fun if at the end, the top XXX all show the same number.</p>\n<p>In addition, maybe you could add an extra criterion to push for low-resource solutions, e.g., when the difference between private scores is below a certain 'noise' threshold, rank according to FLOPS or parameters in submitted model?</p>\n<p>That would probably spice up the competition a bit?</p>",
      "rawMarkdown": "Hi all,\n\nAs submissions are really close to each other, it would be nice if the leaderboard could show one (or two?) extra significant digits. It won't be much fun if at the end, the top XXX all show the same number.\n\nIn addition, maybe you could add an extra criterion to push for low-resource solutions, e.g., when the difference between private scores is below a certain 'noise' threshold, rank according to FLOPS or parameters in submitted model?\n\nThat would probably spice up the competition a bit?",
      "votes": null
    },
    {
      "id": "2183149",
      "postDate": "03/15/2023 13:47:21",
      "content": "<p>In most Kaggle competitions the public leaderboard only shows a limited amount of digits, to prevent overfitting.<br>\nAfter the private leaderboard is finalized, the full score (e.g. 6 digits after comma) is shown.</p>",
      "rawMarkdown": "In most Kaggle competitions the public leaderboard only shows a limited amount of digits, to prevent overfitting.\nAfter the private leaderboard is finalized, the full score (e.g. 6 digits after comma) is shown.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 2183149,
      "author_name": "jcerpentier",
      "author_url": "",
      "post_date": "03/15/2023 13:47:21",
      "content": "<p>In most Kaggle competitions the public leaderboard only shows a limited amount of digits, to prevent overfitting.<br>\nAfter the private leaderboard is finalized, the full score (e.g. 6 digits after comma) is shown.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "2179991": "Hi all,\n\nAs submissions are really close to each other, it would be nice if the leaderboard could show one (or two?) extra significant digits. It won't be much fun if at the end, the top XXX all show the same number.\n\nIn addition, maybe you could add an extra criterion to push for low-resource solutions, e.g., when the difference between private scores is below a certain 'noise' threshold, rank according to FLOPS or parameters in submitted model?\n\nThat would probably spice up the competition a bit?",
    "2183149": "In most Kaggle competitions the public leaderboard only shows a limited amount of digits, to prevent overfitting.\nAfter the private leaderboard is finalized, the full score (e.g. 6 digits after comma) is shown."
  },
  "source": "meta"
}