Changed code that converts tensors to PIL images in the write_your_own_pipeline notebook

[jere357]

What does this PR do?

Some weeks ago i had a PR merged on the notebooks repo. It had some changes to the write_your_own_pipeline notebook, but the hf docs builder bot has overwritten the changes in this commit

you can check the commit history

To me it seems that changing the notebooks on the notebooks repo does nothing, because you have to change to "source code" here in these markdown files. [citation required] If this is the case maybe this should be mentioned in the notebooks repo readme.md so it's clear.

The actual code changes

Hello, this PR rewrites two cells in the write_your_own_pipeline diffusers notebook.
It changes the code that converts the output tensor to a PIL image to run a bit faster. It uses squeeze on the tensor and then runs all possible operations on the GPU before transferring the tensor to the CPU and creating the PIL Image.

You can find the code i used to benchmark my changes in this colab , I'm unsure if this kind of benchmarking code is the "proper" way to do it

I think it's generally good pytorch practice to do as many things on the GPU before transferring things to the CPU

Feel free to discuss this change and maybe find an even faster way to write this code 🤗

Fixes # (issue)

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• Did you read the contributor guideline?
• Did you read our philosophy doc (important for complex PRs)?
• Was this discussed/approved via a Github issue or the forum? Please add a link to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

@patrickvonplaten - Patrick has reviewed the PR that was merged 3 weeks ago, maybe you remember this PR, the changes aren't visible in the notebooks. I'm not sure where exactly i have to change my code for it to be visible both in the notebooks and in the docs files on the website

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

[HuggingFaceDocBuilderDev]

The documentation is not available anymore as the PR was closed or merged.

[sayakpaul]

@jere357 it's the other way around i.e., when you add [[open-in-colab]] in a markdown documentation, the doc builder automatically pushes the notebook version from it.

@stevhliu can shed more light.

[stevhliu]

Hi! The notebooks in the notebooks repo are all generated from the docs by the doc-builder when we add [[open-in-colab]] to it. Thanks for your feedback though, and I'll make a mention of it in the README.md! 😄