{
  "id": 154519,
  "title": "Preprocessed jpegs to 224x224 png",
  "url": "/competitions/siim-isic-melanoma-classification/discussion/154519",
  "author_name": "",
  "post_date": "2020-05-28T18:13:29.189303800Z",
  "votes": 12,
  "comment_count": 4,
  "views": 0,
  "content": "<p>Hello,</p>\n\n<p>As can be seen here: <a href=\"https://www.kaggle.com/c/siim-isic-melanoma-classification/discussion/154281\">https://www.kaggle.com/c/siim-isic-melanoma-classification/discussion/154281</a> loading images in a Kaggle kernel from the jpeg files is too slow. So you currently have a few options:</p>\n\n<ul>\n<li>Use tfrecords instead with tensorflow/keras and TPU as per some public notebooks.</li>\n<li>Do it on your own local/cloud hardware</li>\n<li>Preprocess all images to make smaller files that don't take long to load in a kaggle kernel. </li>\n</ul>\n\n<p>So I've down the preprocess for my own baseline. *<em>The published dataset (s</em>*o if you also use 224x224 you don't need to run the notebook again !):\n<a href=\"https://www.kaggle.com/arroqc/siic-isic-224x224-images\">https://www.kaggle.com/arroqc/siic-isic-224x224-images</a></p>\n\n<p>Here is the very simple notebook that created it: \n<a href=\"https://www.kaggle.com/arroqc/siim-isic-preprocessing-jpeg-notebook\">https://www.kaggle.com/arroqc/siim-isic-preprocessing-jpeg-notebook</a></p>",
  "messages": [
    {
      "id": "865591",
      "postDate": "05/28/2020 18:13:29",
      "content": "<p>Hello,</p>\n\n<p>As can be seen here: <a href=\"https://www.kaggle.com/c/siim-isic-melanoma-classification/discussion/154281\">https://www.kaggle.com/c/siim-isic-melanoma-classification/discussion/154281</a> loading images in a Kaggle kernel from the jpeg files is too slow. So you currently have a few options:</p>\n\n<ul>\n<li>Use tfrecords instead with tensorflow/keras and TPU as per some public notebooks.</li>\n<li>Do it on your own local/cloud hardware</li>\n<li>Preprocess all images to make smaller files that don't take long to load in a kaggle kernel. </li>\n</ul>\n\n<p>So I've down the preprocess for my own baseline. *<em>The published dataset (s</em>*o if you also use 224x224 you don't need to run the notebook again !):\n<a href=\"https://www.kaggle.com/arroqc/siic-isic-224x224-images\">https://www.kaggle.com/arroqc/siic-isic-224x224-images</a></p>\n\n<p>Here is the very simple notebook that created it: \n<a href=\"https://www.kaggle.com/arroqc/siim-isic-preprocessing-jpeg-notebook\">https://www.kaggle.com/arroqc/siim-isic-preprocessing-jpeg-notebook</a></p>",
      "rawMarkdown": "Hello,\n\nAs can be seen here: https://www.kaggle.com/c/siim-isic-melanoma-classification/discussion/154281 loading images in a Kaggle kernel from the jpeg files is too slow. So you currently have a few options:\n\n* Use tfrecords instead with tensorflow/keras and TPU as per some public notebooks.\n* Do it on your own local/cloud hardware\n* Preprocess all images to make smaller files that don't take long to load in a kaggle kernel. \n\n\n\nSo I've down the preprocess for my own baseline. **The published dataset (s**o if you also use 224x224 you don't need to run the notebook again !):\nhttps://www.kaggle.com/arroqc/siic-isic-224x224-images\n\n Here is the very simple notebook that created it: \nhttps://www.kaggle.com/arroqc/siim-isic-preprocessing-jpeg-notebook",
      "votes": null
    },
    {
      "id": "865606",
      "postDate": "05/28/2020 18:23:08",
      "content": "<p>Thank you for this Arnaud! Cant wait to see your kernel!</p>",
      "rawMarkdown": "Thank you for this Arnaud! Cant wait to see your kernel!",
      "votes": null
    },
    {
      "id": "915416",
      "postDate": "07/04/2020 18:01:06",
      "content": "<p>I recently joined the competition. The raw images take so long to load. My epochs time increased 3 times. So I decided to investigate further. Quite alarming that reading a batch of Raw images is 3 times slower on Kaggle then on My Laptop (6 core i5 and ssd). </p>\n\n<p><img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1807042%2Fa9281eef0e9ad2f566803c4c0639c50c%2Fbatchsize64.svg?generation=1593885494697955&amp;alt=media\" alt=\"\"></p>",
      "rawMarkdown": "I recently joined the competition. The raw images take so long to load. My epochs time increased 3 times. So I decided to investigate further. Quite alarming that reading a batch of Raw images is 3 times slower on Kaggle then on My Laptop (6 core i5 and ssd). \n\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1807042%2Fa9281eef0e9ad2f566803c4c0639c50c%2Fbatchsize64.svg?generation=1593885494697955&amp;alt=media)",
      "votes": null
    },
    {
      "id": "915539",
      "postDate": "07/04/2020 20:05:07",
      "content": "<p>Yes, the raw images are as large as 4000x3000. I don't recommend using raw images. You should use a folder of resized JPEGs or resized TFRecords.</p>",
      "rawMarkdown": "Yes, the raw images are as large as 4000x3000. I don't recommend using raw images. You should use a folder of resized JPEGs or resized TFRecords.",
      "votes": null
    },
    {
      "id": "916205",
      "postDate": "07/05/2020 13:22:52",
      "content": "<p><a href=\"/cdeotte\">@cdeotte</a> I am using your TFrecords dataset. Thanks a lot. </p>",
      "rawMarkdown": "cdeotte I am using your TFrecords dataset. Thanks a lot.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 865606,
      "author_name": "yannmajewski",
      "author_url": "",
      "post_date": "05/28/2020 18:23:08",
      "content": "<p>Thank you for this Arnaud! Cant wait to see your kernel!</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 915416,
      "author_name": "spideysloth",
      "author_url": "",
      "post_date": "07/04/2020 18:01:06",
      "content": "<p>I recently joined the competition. The raw images take so long to load. My epochs time increased 3 times. So I decided to investigate further. Quite alarming that reading a batch of Raw images is 3 times slower on Kaggle then on My Laptop (6 core i5 and ssd). </p>\n\n<p><img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1807042%2Fa9281eef0e9ad2f566803c4c0639c50c%2Fbatchsize64.svg?generation=1593885494697955&amp;alt=media\" alt=\"\"></p>",
      "votes": null,
      "replies": [
        {
          "id": 915539,
          "author_name": "cdeotte",
          "author_url": "",
          "post_date": "07/04/2020 20:05:07",
          "content": "<p>Yes, the raw images are as large as 4000x3000. I don't recommend using raw images. You should use a folder of resized JPEGs or resized TFRecords.</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 916205,
          "author_name": "spideysloth",
          "author_url": "",
          "post_date": "07/05/2020 13:22:52",
          "content": "<p><a href=\"/cdeotte\">@cdeotte</a> I am using your TFrecords dataset. Thanks a lot. </p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "865591": "Hello,\n\nAs can be seen here: https://www.kaggle.com/c/siim-isic-melanoma-classification/discussion/154281 loading images in a Kaggle kernel from the jpeg files is too slow. So you currently have a few options:\n\n* Use tfrecords instead with tensorflow/keras and TPU as per some public notebooks.\n* Do it on your own local/cloud hardware\n* Preprocess all images to make smaller files that don't take long to load in a kaggle kernel. \n\n\n\nSo I've down the preprocess for my own baseline. **The published dataset (s**o if you also use 224x224 you don't need to run the notebook again !):\nhttps://www.kaggle.com/arroqc/siic-isic-224x224-images\n\n Here is the very simple notebook that created it: \nhttps://www.kaggle.com/arroqc/siim-isic-preprocessing-jpeg-notebook",
    "865606": "Thank you for this Arnaud! Cant wait to see your kernel!",
    "915416": "I recently joined the competition. The raw images take so long to load. My epochs time increased 3 times. So I decided to investigate further. Quite alarming that reading a batch of Raw images is 3 times slower on Kaggle then on My Laptop (6 core i5 and ssd). \n\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1807042%2Fa9281eef0e9ad2f566803c4c0639c50c%2Fbatchsize64.svg?generation=1593885494697955&amp;alt=media)",
    "915539": "Yes, the raw images are as large as 4000x3000. I don't recommend using raw images. You should use a folder of resized JPEGs or resized TFRecords.",
    "916205": "cdeotte I am using your TFrecords dataset. Thanks a lot."
  },
  "source": "meta"
}