modelscope / modelscope/DiffSynth-Studio
details about the training of zimage_turbo_training_adapter
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.1k
- Forks
- 1.3k
- Avg merge
- 13h 12m
- Merged PRs (30d)
- 45
Description
Thank you for your tremendous contributions to the community. I have a question regarding the de-distillation LoRA strategy described in the repository. To enable fine-tuning of the few-step distilled model (zimage-turbo), the approach first generates a synthetic dataset using the distilled model itself, and then trains a de-distillation LoRA on this data. My specific question is: when training this de-distillation LoRA, is the optimization objective simply the standard flow matching loss (i.e., corrupting clean samples with noise to obtain noisy states and predicting the velocity), or does it employ distillation-specific losses?
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 does not name a training file or test. Start by locating the repository’s zimage_turbo de-distillation LoRA training entry point and its loss construction, then compare them with the flow-matching and distillation documentation. Done means documenting whether the objective is standard flow matching or includes additional distillation-specific terms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100