lllyasviel / lllyasviel/ControlNet

Openpose sd v1.5 weights different from original sd v1.5 weights

Open
#356 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
34.1k
Forks
3k
PR merge metrics
No merged PRs in 30d

Description

Hi, I downloaded the controlnet weights control_sd15_openpose.pth for openpose sd v1.5 from this site https://huggingface.co/lllyasviel/ControlNet

However, after I extracted the stable diffusion weights from this file, I compared it with the original sd v1.5 weight released in https://huggingface.co/runwayml/stable-diffusion-v1-5

I found the weights for encoding and middle block are the same, but the decoding blocks are different. So I guess it was trained with sd_locked = False? Can you provide the openpose weights in which the original sd is completely locked by any chance?

Furthermore, seems like in HuggingFace diffuser ControlNet implementation, they forcebly merge the extracted pure controlnet weight and the original runwayml/stable-diffusion-v1-5 sd weight together, does this suggest we can also merge this without degrading the generation quality much?

Thanks!!!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the ControlNet and runwayml/stable-diffusion-v1-5 model pages linked in the report and reviewing the extracted weights. Done means determining whether the OpenPose weights were trained with sd_locked=False, documenting or providing fully locked weights if possible, and clarifying whether merging them is supported without significant quality loss.

Written by the indexing model from the issue text.

Assessment

Tech stack
huggingface, python
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.