fix: supported extensions in compute_image_statistics method

[yuta-tsuzuki-woven]

Some ML teams are handling image data with uppercase extensions such as .JPG, .PNG.
If there are no negative effects, I would like to support such uppercase extensions in compute_image_statistics method.

---

This change is 

[yuta-tsuzuki-woven]

+@kuanleetri +@chrisochoatri please review it

Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @chrisochoatri and @kuanleetri)

[chrisochoatri]

Reviewable status: 0 of 1 files reviewed, 2 unresolved discussions (waiting on @kuanleetri and @yuta-tsuzuki-woven)

---

dgp/utils/dataset_conversion.py line 75 at r1 (raw file):

    valid_extensions = (
        ".jpg",

nit: do we need .jpeg also?

Code quote:

.jpg"

---

dgp/utils/dataset_conversion.py line 86 at r1 (raw file):

        ".TIFF",
    )
    image_list = list(filter(lambda x: x.endswith(valid_extensions), image_list))

just a question, would it make sense to do something like x.lower().endswith and just keep the lower case extensions?

Code quote:

    image_list = list(filter(lambda x: x.endswith(valid_extensions), image_list))

[yuta-tsuzuki-woven]

@chrisochoatri please next round

Reviewable status: 0 of 1 files reviewed, 2 unresolved discussions (waiting on @chrisochoatri and @kuanleetri)

---

dgp/utils/dataset_conversion.py line 75 at r1 (raw file):

Previously, chrisochoatri (Chris Ochoa) wrote…

nit: do we need .jpeg also?

Thank you! It looks nice.
I added .jpeg.

---

dgp/utils/dataset_conversion.py line 86 at r1 (raw file):

Previously, chrisochoatri (Chris Ochoa) wrote…

just a question, would it make sense to do something like x.lower().endswith and just keep the lower case extensions?

Thank you for your advice. It makes sense.
I added .lower() here and remove uppercase extensions from the list.

[chrisochoatri]

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @kuanleetri)