thu-ml / thu-ml/Causal-Forcing

Awesome work!

Open
#7 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
969
Forks
55
PR merge metrics
No merged PRs in 30d

Description

Self Forcing fixed the mistake in CausVid’s DMD stage, while Causal Forcing fixed the mistake in the ODE-initialization stage of both CausVid and Self Forcing. In my view, Causal Forcing deserves to stand alongside CausVid and Self Forcing—they together form the evolutionary lineage of AR-Diffusion distillation: CausVid $\rightarrow$ Self Forcing $\rightarrow$ Causal Forcing. Salute!

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 is an appreciation message describing the lineage from CausVid to Self Forcing to Causal Forcing. It names no files, tests, or entry points, and does not specify a code or documentation change or a completion criterion.

Written by the indexing model from the issue text.

Assessment

Domain
ai, machine-learning
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
5/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.