lllyasviel / lllyasviel/ControlNet

Weird training results

Open
#206 4 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, thank you for your great work.
I hava a question for the ControlNet training

I am just trying to train ControlNet with canny edge condition using OpenImage Dataset to reproduce or mimic your traning scheme. I preserve all training setting with the tutorial you gave us. However, the results is so weird like below and that was not recovered even after many training iterations.

Did you have a experience like me during training? or is there any opinion to this phenomenon?
I just want to get some opinion or intuition about this from you.

Thank you.

The prompt is fixed by "a high-quality, detailed, and professional image"

**Input**
![gs-011025_e-000000_b-044100_control](https://user-images.githubusercontent.com/32098205/222352032-0cb52537-9360-482c-a38a-03f73fdb302f.png)

**Ourput**
![gs-011025_e-000000_b-044100_samples_cfg_scale_9 00](https://user-images.githubusercontent.com/32098205/222352212-d5124d7d-9b95-45b2-b017-bef0cd9853aa.png)

**Recon**
![gs-011025_e-000000_b-044100_reconstruction](https://user-images.githubusercontent.com/32098205/222352271-471f1f09-7dc4-4440-ab7a-f3e54d63d344.png)

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

The issue mentions ControlNet training with canny-edge conditioning on the OpenImage Dataset, but provides no files, commands, tests, or specific configuration to inspect. Start by comparing the tutorial settings with the reported training setup and the Input, Output, and Recon images; done requires identifying a concrete cause or reproducible defect and documenting the findings.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.