| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
English | 中文
TeleBoost is a unified post-training framework for diffusion models, with DPO and GRPO supported. Used internally at TeleAI for diffusion-model alignment.
This public branch is physically Wan-only.
Wan 14B DPO peak memory at 32× 80GB-Hopper GPUs — Decoupled DPO cuts ~40% peak memory on identical workload and scales to ~15× longer context. See the project page linked in the badges above.
| Method | Status | Use case | Path |
|---|---|---|---|
| DPO | ✅ Ready | Preference alignment | recipes/wan_dpo_teletron/ |
| GRPO | ✅ Ready | Reward-based optimization | recipes/wan_grpo_fsdp/ |
| TempFlow-GRPO | ✅ Ready | Noise-aware weighting + trajectory branching (arXiv 2508.04324) | recipes/wan_tempflow_fsdp/ |
| GRPO-Guard | ✅ Ready | Regulated clipping against implicit over-optimization (arXiv 2510.22319); a composable capability, not a standalone recipe | teleboost/algorithms/grpo_guard.py |
| BGPO | ✅ Ready | Bayesian-prior group optimization (CVPR 2026) | recipes/wan_bgpo_fsdp/ |
| VIPO | ✅ Ready | Pixel-weighted dense advantages (CVPR 2026) | recipes/wan_vipo_fsdp/ |
| FSDP backend for DPO | 🚧 Roadmap | Memory-efficient sharding without DeepSpeed-ZeRO | — |
The DPO recipe ships a precision-alignment anchor against the reference standalone-megatron implementation. See recipes/wan_dpo_teletron/README.md.
Pick the recipe that matches your post-training need. The top-level README is the feature overview; the recipe docs contain the commands, environment variables, and dataset expectations needed for a real run.
The reference stack uses Python 3.11, PyTorch 2.9.1, CUDA 12.8, and the exact verl source declared in constraints/upstreams/verl.txt; DPO uses the Megatron-LM revision in constraints/upstreams/megatron-lm.txt. Follow INSTALL.md rather than letting a generic resolver replace the CUDA/PyTorch/Ray stack.
Prepare Wan prompt embeddings after installation:
teleboost-prepare-wan-data \
--input prompts.txt \
--output_dir data/processed \
--wan_model_path /path/to/Wan2.1-T2V-1.3BRun tests by executable environment:
pytest --profile=core
pytest --profile=training
pytest --profile=heavy --heavy-lane=wanThe first two profiles do not certify a production checkpoint. See tests/README.md and SUPPORT_MATRIX.md for the exact validation claims.
| Need | Start here |
|---|---|
| Understand the supported algorithms and system features | This README and SUPPORT_MATRIX.md |
| Install and run GRPO training | INSTALL.md |
| Program inventory and how each recipe launches | recipes/README.md |
| Understand DPO modes, precision alignment, and troubleshooting | recipes/wan_dpo_teletron/README.md |
Four TeleAI contributions ship in this repo: VIPO + BGPO (day-0 GRPO papers), co-located reward + MPS (GRPO systems), and Gradient Decoupled DPO (DPO systems).
Lifts scalar GRPO feedback into structured, pixel-level advantages via a perceptual structuring module that produces spatially-aware advantage maps. See arXiv:2511.18719.
Top — standard Group Relevant Policy Optimization: reward model output collapses into a scalar advantage before policy update. Bottom — VIPO: preference signals are allocated into a structured advantage map, redistributing optimization pressure toward perceptually important regions.
Two levels of optimization grounded in a Bayesian prior: inter-group trust allocation (RAS) and intra-group prior-anchored renormalization (CRT). See arXiv:2511.18919.
BGPO operates at two levels grounded in a Bayesian prior. Left (RAS): group rewards + prior yield per-sample reliability weights → reliability-aware loss ℒ_RAS. Right (CRT): rewards are renormalized against the prior → recalibrated signal driving the next GRPO loss ℒ_CTR.
Co-located reward (workers share actor GPUs) + MPS-parallel multi-reward (N rewards on one GPU via CUDA MPS). Eliminates the idle reward-rank GPU and brings joint wall-time ≈ max(model) instead of sum. On by default in joint mode.
Left: co-located reward shares the actor GPUs, eliminating the reward-rank idle gaps. Right: CUDA MPS — N reward models concurrent on one GPU, wall-time ≈ max(model) instead of sum.
Per-branch backward + immediate reduce-scatter — frees each branch's full-shape gradient before the next backward starts. Mathematically equivalent to single-backward; on Wan 14B DPO at 32× 80GB-Hopper GPUs: ~40% peak memory cut and ~15× longer context.
Per-branch backward + immediate reduce-scatter. Decoupled DPO frees each branch's full-shape tensor before the next backward starts — visibly cutting the peak. (Result figure is at the top of this README.)
teleboost/ the single production Python package programs/ composition root: ProgramSpec binds model family × algorithm × engine × run policy engines/ distributed execution engines (fsdp, teletron/Megatron) training/ neutral training skeleton (core/) + family adapters (families/) algorithms/ algorithm math (grpo, bgpo, vipo, tempflow, grpo_guard, …) models/ Wan models and family semantics (attention, sampling, conversion) reward/ reward contracts, execution, and providers datasets/ datasets, transforms, and Wan data preprocessing cli/ installed command entry points artifacts/ checkpoint artifact conversion config/ patches/ config loading and pinned upstream patches recipes/ declarative configs + launch scripts; teleboost never imports them third_party/ vendored upstream sources (own licenses, excluded from release artifacts) tools/ install / release / smoke / diagnostics scripts (not in the wheel) tests/ core / training / heavy (wan) pytest profiles docs/ figures and architecture docs Dockerfile / makefile / pyproject.toml / requirements.txt build + deps LICENSE / NOTICE / CITATION.cff upstream attributions .github/ CI + CODEOWNERS
Each program launches via recipes/<program>/run.sh; the program inventory lives in recipes/README.md, and the dependency direction / ownership boundaries in docs/target_architecture.md.
Build a public sdist and wheel from the current source boundary:
python -m pip install -c constraints/release.txt -e '.[release]'
python tools/release/build_artifacts.py \
--out-dir /tmp/teleboost-release-wanThe gate stages an allowlisted copy without rewriting it, builds the wheel only from the extracted sdist, validates archive contents and notices, runs strict Twine checks, and performs a clean-install CLI smoke.
Review THIRD_PARTY_PROVENANCE.md, MODEL_AND_DATA_LICENSES.md, and SECURITY.md before publishing or loading external artifacts.
TeleBoost-authored code is Apache 2.0 — see LICENSE. Adapted and vendored code retains its file-level notices and upstream terms; the root package includes the applicable license texts under LICENSES/ and excludes all third_party/ source.
This project builds on the following upstreams. Full per-package attributions (license texts + redistribution terms) are in NOTICE.
RL training stacks
Generation models
Reward models
@article{teleboost2026,
title = {TeleBoost: A Systematic Alignment Framework for High-Fidelity,
Controllable, and Robust Video Generation},
author = {Liang, Yuanzhi and Wu, Xuan'er and Liu, Yirui and Fang, Yijie and
Fan, Yizhen and Hao, Ke and Li, Rui and Liu, Ruiying and Ni, Ziqi and
Yu, Peng and Wang, Yanbo and Huang, Haibin and Weng, Qizhen and
Zhang, Chi and Li, Xuelong},
year = {2026},
}For per-algorithm citations:
| Back | FazBrowse Home | New Git URL |