thu-ml/Causal-Forcing - Open Source PR Review Scorecard

[ICML 2026] Official codebase for "Causal Forcing: Autoregressive Diffusion Distillation Done Right for High-Quality Real-Time Interactive Video Generation" & Causal Forcing++

C-Rank Grade: B (Solid) - 45/100

External PR Merge Rate: 50%

Response Time: <1h

First Timer Success: -

Frequently Asked Questions

Is thu-ml/Causal-Forcing welcoming to first-time open-source contributors?

thu-ml/Causal-Forcing has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in thu-ml/Causal-Forcing respond to incoming external pull requests in approximately 0.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 45.2 C-Rank™ score (B Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 45.2 places thu-ml/Causal-Forcing in the B tier.

What is the external contributor pull request merge rate for thu-ml/Causal-Forcing?

The external contributor pull request merge rate for thu-ml/Causal-Forcing is 50.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in thu-ml/Causal-Forcing?

thu-ml/Causal-Forcing currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

thu-ml
thu-ml/Causal-ForcingB•Solid999
GitHub
Back to Explorer
thu-ml

thu-ml/Causal-Forcing

999
InactiveB•Solid(45/100)Low Sample (<20 PRs)Python

[ICML 2026] Official codebase for "Causal Forcing: Autoregressive Diffusion Distillation Done Right for High-Quality Real-Time Interactive Video Generation" & Causal Forcing++

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in thu-ml/Causal-Forcing. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in thu-ml/Causal-Forcing focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
50.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
50.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe50/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for thu-ml/Causal-Forcing
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/thu-ml/Causal-Forcing)](https://getmerged.abhishekco.de/thu-ml/Causal-Forcing?utm_source=github&utm_medium=badge)

Active Good First Issues (2)

View on GitHub

I am working on an action-controlled Wan2.2 TI2V (Image-to-Video) model. When converting the model from bidirectional flow to an autoregressive teacher for distillation, I encountered the following issue: Training predictions: Look normal and reasonable. Inference results: Are significantly worse, with poor quality. I have attached the following for reference: Training prediction samples train_pred_step_001300.mp4 Inference output samples: ar_VID_20251229_164739_147_slice_295_back_180_step_001300.mp4 Training loss curves What could be causing this discrepancy between training and inference quality?

📅 Opened Jun 5, 2026💬 7 comments
Quality: 80/100Contribute

This is truly a remarkable piece of work! Many thanks to the author for open-sourcing it. I have a question about the critic loss computation. From my understanding, the student predicts $x_0$ using the generator's scheduler (denoted as scheduler_stu). Then scheduler_stu is used to add noise, and the resulting noisy sample is passed to the fake/real teachers. However, the teachers use a scheduler with a different shift value from the student's scheduler to predict $x_0$ from pred_flow. After that, the code converts $x_0$ back to pred_flow again using the generator's scheduler. I am wondering why the critic loss is not computed directly from the teacher's original output (pred_flow). Instead, pred_flow is first transformed to $x_0$ and then converted back using a different shift setting. Is this intentional, or could it be a bug? file path model/dmd.py _, pred_fake_image = self.fake_score( noisy_image_or_video=noisy_generated_image, # !!!!!!!!!!!!!!!!! conditional_dict=con

📅 Opened May 6, 2026💬 5 comments
Quality: 70/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for thu-ml/Causal-Forcing

When evaluating whether to contribute to thu-ml/Causal-Forcing, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of thu-ml/Causal-Forcing acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to thu-ml/Causal-Forcing

01

Is thu-ml/Causal-Forcing welcoming to first-time open-source contributors?

thu-ml/Causal-Forcing has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 45.2 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 45.2 places thu-ml/Causal-Forcing in the Solid tier.

04

What is the external contributor pull request merge rate for thu-ml/Causal-Forcing?

The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in thu-ml/Causal-Forcing?

Yes, thu-ml/Causal-Forcing currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for thu-ml/Causal-Forcing are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.