diffusers VS gradio

I'm missing something about the random factor, from the sample code from https://github.com/huggingface/diffusers/blob/main/README.md

Hey people, I noticed that combining these two methods in a single forward pass increases the controllability of the generation quite a bit. I was kind of puzzled that sometimes ControlNet yielded better results than T2IAdapter for some cases, and sometimes it was the other way around, so I decided to test both at the same time, and results were quite nice. Some visuals and more motivation here: https://github.com/huggingface/diffusers/issues/5847 And it was already merged here: https://github.com/huggingface/diffusers/pull/5869

Open Parti Prompts: The better way to evaluate diffusion models (repo)

You have disabled the safety checker for by passing `safety_checker=None`. Ensure that you abide to the conditions of the Stable Diffusion license and do not expose unfiltered results in services or applications open to the public. Both the diffusers team and Hugging Face strongly recommend to keep the safety filter enabled in all public facing circumstances, disabling it only for use-cases that involve analyzing network behavior or auditing its results. For more information, please have a look at https://github.com/huggingface/diffusers/pull/254 .

For developers, TensorRT support also exists for the diffusers library via community pipelines. [1] It's limited, but if you're only supporting a subset of features, it can help.

In general, these insane speed boosts comes at the cost of bleeding edge features.

[1] https://github.com/huggingface/diffusers/blob/28e8d1f6ec82a6...

I was training sdxl UNET base model, with the diffusers library, which was going great until around step 210k when the weights suddenly turned back to their original values and stayed that way. I also tried with the ema version, which didn't change at all. I also looked at the tensor's weight values directly which confirmed my suspicions.

Merging LoRAs is essentially taking a weighted average of the LoRA adapter weights. It's more common in other UIs.

diffusers is working on a PR for it: https://github.com/huggingface/diffusers/pull/4473

There's also that library all the AI models started using that gives you a public URL to share. After researching it: https://www.gradio.app/ is the link.

It's used specifically for making simple UIs for machine learning apps. But I guess technically you could use it for anything.

What is the business model for https://www.taipy.io/, https://streamlit.io/, or https://www.gradio.app/? These are nice tools - but how will the sponsoring businesses support themselves? I didn't see any mention of enterprise plans, etc. Is the answer simply that "we've not announced our revenue model yet"? What should one expect?

Repo : https://github.com/gradio-app/gradio

There's TensorFlow.js for running machine learning on JavaScript, but personally, I'd prefer using the Python Gradio package, which is designed for creating UIs for machine learning inference demos.

I found an issue on gradio github but looks like it's closed so I am not sure if it's still a common issue or only I am facing it due to certain settings/absence of a fix. ( https://github.com/gradio-app/gradio/issues/3060 )

I disagree hard with this – for instance I've recently needed to dig into the code for the Gradio library, and when PRs are like https://github.com/gradio-app/gradio/pull/3300 (and the merge commit's message is what it is) it's hard to understand why some decisions have been made when doing `git annotate` later on.

Gradio for a ui that your commanderGPT can visit and use

gradio is documented, it doesn't seem very complex, it would be something like moving this block under the other one. i think it's ui_extra_networks.py, the file you are looking to edit. (if you do it make a copy to restore when you go to update)

Gradio did have an issue for a while where your URL was guessable, so unless you had a password it was pretty easy to find, but as far as I know they've increased the complexity so much that it's no longer an issue.

My script wouldn't work on the langchain because it was literally made within the gradio "docs builder" script that afaik was made specifically for their website (repo)