Wandb guide

[AK391]

Opening a WIP PR that fixes: https://github.com/gradio-app/gradio/issues/1759

Guide on how to integrate with Weights and Biases

[abidlabs]

Moving to draft status for now -- let us know when you want a review @AK391!

[AK391]

@abidlabs should be ready for review now, also will be sending this to the wandb team in slack to go over and to see if they want to use the wandb organization https://huggingface.co/wandb on HF to adding gradio demos made through following this guide

[abidlabs]

Hey @AK391, I moved the Guide to the proper location in the repo, so that it would be visible when building locally. However, the Guide's formatting looks all messed up to me:

http://localhost:8000/Gradio_and_Wandb_Integration/

Something's off about the Markdown syntax. Is the Guide looking fine for you locally? Let me know if you need any help setting up the website locally

[AK391]

@abidlabs formatting issue should be fixed now, guide locally looks like this

[abidlabs]

@AK391 I'm still seeing a lot of broken formatting and jumbled text in the body of the blog post. For example, see this paragraph where the markdown isn't rendering right:

Are you seeing this on your end?

[AK391]

@abidlabs thanks, should be fixed now

[abidlabs]

Thanks @AK391 the Guide is loading for me now! However, I'm still confused by this Guide for several reasons:

• There's way too much code. I think we should avoid writing the code that's already in the colab notebook.
• It seems like we're showing how to use wandb for experiment tracking, but not really showing how to embed a Gradio demo in the wandb report (using the Interface.integrate() or Blocks.integrate() functions).
• It would be nice to have a "final" colab notebook with all of the jojogan, gradio, and wandb code in one place that we link to at the end

[AK391]

@abidlabs thanks for the review made most of the updates, will look into adding a final notebook to add to the end

[abidlabs]

Thanks @AK391 this looks much better.

I'm still seeing some weird things, though. For example, all of this "@markdown" in the code. Is this supposed to be here?

And some code not being formatted as code, like here:

I can make a pass through the Guide tomorrow and clean up these formatting issues.

Would you be able put together a "final" colab notebook with all of the jojogan, gradio, and wandb code in one place that we could link to?

[AK391]

@abidlabs thanks for checking @markdown is actually from the original colab notebook https://colab.research.google.com/github/mchong6/JoJoGAN/blob/main/stylize.ipynb from the jojogan repo, it renders panels like this to interact with rather than running the code cell but I will remove it from the guide as its confusing

[abidlabs]

Sounds good, we're pretty close I think -- just let me know when you want me to review again.

[AK391]

@abidlabs final colab is ready https://colab.research.google.com/drive/1Xq7YLsE3CNqGjcmfj5hiwGXCnYY3anrm?usp=sharing, one issue when using blocks and then integrate, works fine but when using interface and integrate I get this error

AttributeError                            Traceback (most recent call last)
<ipython-input-14-2371ac6ca7c4> in <module>()
----> 1 demo.integrate(wandb=wandb)

AttributeError: 'tuple' object has no attribute 'integrate'

[AK391]

@abidlabs thanks, issue should be resolved now, updated colab and the code block in the guide

[AK391]

@abidlabs following up on this, should be ready for review

[abidlabs]

Sounds good, will take a look today!

[abidlabs]

Thanks for making all of the edits, @AK391, looks good to me :)

I made some tweaks to shorten things up and I think maybe the code can be shortened even more, but it's a good guide for now!

I'll go ahead and merge it in after the CI runs