Datasets:

Spawning

/

PD12M

like 121

Follow

Spawning 32

Yes, that's definitely ok with us. We do plan to update the dataset as people use source.plus to flag items. It might make sense for us to set up a way to sync the repos when that happens.

Thank you so much!

I will update this thread when the upload is complete.

@jordancmeyer I have completed the upload here:
https://huggingface.co/datasets/sayakpaul/pd12m-full

The estimated number of rows is 10,778,260.

The following command was used to download the dataset:

img2dataset --url_list pd12m_full.parquet --input_format "parquet" \
 --url_col "url" --caption_col "caption" --output_format webdataset \
   --number_sample_per_shard=5000 --skip_reencode=True \
   --output_folder s3://diffusion-datasets/pd12m \
    --processes_count 16 --thread_count 64 \
     --resize_mode no \
       --enable_wandb True

WandB logs: https://wandb.ai/sayakpaul/img2dataset/runs/b8hmd5v1.

I am now working on adding a sample dataloader script with webdataset in the repository.

I think it could be nice to host the dataset under the hf.co/Spawning org. If so, I can reach out to the Hub team internally to make that happen. Let me know :)

@sayakpaul This is awesome, thanks for pulling this together! I had some questions on the count of records - the wandb logs looks like there were several large spikes of failures. I'm curious, do you have any insight into those failures? I want to be certain the reason for the missing records aren't due to any issues with the parquets/urls/files.

It would be awesome to move this under the Spawning org! That would be very much appreciated!

Umm, I currently I don’t have a solid insight honestly. What I could do is try to see if the URLs were logged with the downloaded sharded and then use them to get a list of the URLs that weren’t downloaded and inspect manually.

I will get back here.

Thanks for the kind words!

@sayakpaul That would be very helpful. We can make a task to follow up on the missing images as well. The wandb logs show sudden spikes of errors, which could be consistent with short network outages. I didn't want to jump to conclusions if you had a better idea, but that makes sense to me.

I just wanted to make sure we hadn't missed any potential issues in our verification process. Either way, confirming the cause would be helpful. Thanks again!

Thanks once again, @padge , for being so welcoming!

The wandb logs show sudden spikes of errors, which could be consistent with short network outages. I didn't want to jump to conclusions if you had a better idea, but that makes sense to me.

I think it's almost likely because of network-related issues, which can be hard to prevent. I am still running an entire iteration through the downloaded shards to get the list of the successful URLs. After that, my plan is to obtain the URLs that weren't downloaded and inspect them.

If all goes well, we should be able to download those and still prepare shards out of them. Does this sound like a plan?

Regardless, I will keep this thread updated.

@sayakpaul I totally understand. That sounds perfect, thanks for following up!