lllyasviel / lllyasviel/ControlNet
Annotator Resolution: when it's a good idea to move it from the "512" base position?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.1k
- Forks
- 3k
- PR merge metrics
- No merged PRs in 30d
Description
- When is 512 the best resolution?
- In what cases is it reasonable to make it smaller?
- In what cases is it reasonable to make it larger?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies no file, test, or entry point; begin by locating the project's annotator-resolution guidance and relevant examples. Done means documenting when 512 is appropriate and when smaller or larger resolutions are reasonable, with enough context for users to apply the guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100