Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Community Pipeline] Modified Cross-Attention - Structured Diffusion Guidance for Compositional T2I synthesis #878

Closed
apolinario opened this issue Oct 17, 2022 · 8 comments
Assignees
Labels
community-examples hacktoberfest stale Issues that haven't received updates

Comments

@apolinario
Copy link
Collaborator

apolinario commented Oct 17, 2022

Intro

Community Pipelines are introduced in diffusers==0.4.0 with the idea of allowing the community to quickly add, integrate, and share their custom pipelines on top of diffusers.

You can find a guide about Community Pipelines here. You can also find all the community examples under examples/community/. If you have questions about the Community Pipelines feature, please head to the parent issue.

Idea: Modified cross-attention mechanism

This pipeline aims to implement this paper to Stable Diffusion, improving interpretability of the prompts. Some results of the paper Training-Free Structured Diffusion Guidance for Compositional Text-to-Image Synthesis:
image

@apolinario apolinario changed the title ]C [Community Pipeline] Modified Cross-Attention - Structured Diffusion Guidance for Compositional T2I synthesis Oct 17, 2022
@apolinario apolinario added help wanted Extra attention is needed good first issue Good for newcomers community-examples hacktoberfest and removed help wanted Extra attention is needed labels Oct 17, 2022
@20RitikSingh
Copy link

I want to work on this.

@apolinario
Copy link
Collaborator Author

apolinario commented Oct 17, 2022

Awesome @20RitikSingh! Feel free to share your progress and ask if you find any challenges

@keturn
Copy link
Contributor

keturn commented Oct 18, 2022

This is a super interesting paper! Note that there is a reference implementation included in the .zip of "supplementary material" on the paper submission. Also note that implementation is not released under the Apache License, so I don't know if 🤗 can accept a PR that includes it. It might be safer to do a clean-room implementation from only the description in the text of the paper.

[I Am Not A Lawyer and I Am Not Your Lawyer, but the paper's authors are obligated to remain anonymous until the end of the ICLR 2023 review period, so they might have a hard time speaking up for themselves right now.]

If you do choose to use the code from the supplementary material, you may need to swap some things around to make it better fit diffusers instead of ldm.

@patrickvonplaten
Copy link
Contributor

Also cc @patil-suraj here FYI

@patil-suraj
Copy link
Contributor

Interesting!

@20RitikSingh , let us know you need any help or have any questions, happy to help :)

@patil-suraj patil-suraj self-assigned this Oct 26, 2022
@shunk031
Copy link

Hi, I have built a pipeline with diffusers based on the reference implementation. Here is my implementation of the Structured Diffusion Guidance: https://github.com/shunk031/training-free-structured-diffusion-guidance.

However, I am not confident in my implementation because some parts of the published implementation are missing (e.g., sampler; a new argument, skip, has been added, but the details of this argument are not clear). Also, my implementation assumes batch size = 1, so it does not support multiple batch sizes. My implementation seems to have a bug with this limitation as well. Thank you.

@keturn
Copy link
Contributor

keturn commented Dec 17, 2022

The paper has been submitted as https://arxiv.org/abs/2212.05032 and is no longer anonymous! https://weixi-feng.github.io/structure-diffusion-guidance/

MIT licensed code by @weixi-feng at https://github.com/weixi-feng/Structured-Diffusion-Guidance

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread.

Please note that issues that do not follow the contributing guidelines are likely to be ignored.

@github-actions github-actions bot added the stale Issues that haven't received updates label Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-examples hacktoberfest stale Issues that haven't received updates
Projects
None yet
Development

No branches or pull requests

6 participants