Skip to content

Tele-AI/TeleBoost

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

1 Commit
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

TeleBoost

A unified post-training framework for diffusion models

Project page TeleBoost arXiv License: Apache 2.0 CPU tests BGPO CVPR 2026 VIPO CVPR 2026

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.

  • πŸŽ›οΈ Multi-paradigm post-training β€” DPO + GRPO
  • πŸ”₯ Memory-efficient DPO β€” ~40% memory cut, ~15Γ— longer context on Wan 14B
  • πŸ†• Six GRPO algorithms β€” DanceGRPO, Flow-GRPO, GRPO-Guard, TempFlow-GRPO, BGPO, VIPO
  • 🧩 Co-located + MPS multi-reward β€” N rewards on actor GPU; wall β‰ˆ max(model)
  • 🎬 Ready-to-use sequence parallel β€” Ulysses SP for long-video training
  • πŸš€ Day-0 BGPO + VIPO (CVPR 2026)

Wan 14B DPO peak GPU memory: Gradient Decoupled DPO cuts memory by ~40% on identical workload and scales to ~15Γ— longer context than standard DPO.

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.

Methods

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.

Quickstart

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.

  • GRPO β€” see INSTALL.md. Set TRAIN_FILE / TEST_FILE / WAN_MODEL_PATH / REWARD_MODEL_PATH, then launch bash recipes/wan_grpo_fsdp/run.sh (for a smoke run, TEST_FILE=$TRAIN_FILE works).
  • DPO β€” see recipes/wan_dpo_teletron/README.md. Build the Dockerfile, export MEGATRON_LM_DIR, then launch bash recipes/wan_dpo_teletron/run.sh.

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.3B

Run tests by executable environment:

pytest --profile=core
pytest --profile=training
pytest --profile=heavy --heavy-lane=wan

The first two profiles do not certify a production checkpoint. See tests/README.md and SUPPORT_MATRIX.md for the exact validation claims.

Documentation map

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

πŸš€ What's new from TeleAI

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).

VIPO β€” Visual Preference Policy Optimization Β Β·Β  GRPO Β Β·Β  CVPR 2026 Β Β·Β  arXiv 2511.18719

Lifts scalar GRPO feedback into structured, pixel-level advantages via a perceptual structuring module that produces spatially-aware advantage maps. See arXiv:2511.18719.

VIPO method overview: standard GRPO uses a scalar advantage; VIPO instead allocates a per-pixel / per-region structured advantage.

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.

BGPO β€” Bayesian-Prior Group Optimization Β Β·Β  GRPO Β Β·Β  CVPR 2026 Β Β·Β  arXiv 2511.18919

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 method overview: RAS (left) computes per-sample trust weights from group rewards and a Bayesian prior; CRT (right) renormalizes rewards against the prior before the next GRPO iteration.

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 + MPS-parallel multi-reward Β Β·Β  GRPO systems

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.

Two complementary throughput optimizations. Left: co-located reward β€” reward workers share the actor GPUs, eliminating the dedicated reward-rank's rollout-idle / training-idle gaps. Right: MPS-parallel multi-reward β€” N reward models compute concurrently on the same GPU via CUDA MPS, with wall-time bounded by the slowest model rather than the sum.

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.

Gradient Decoupled DPO Β Β·Β  DPO systems

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.

Backward-pass timeline of Standard DPO vs Gradient Decoupled DPO. Standard DPO keeps both chosen and rejected branches' full-shape gradients alive simultaneously; Gradient Decoupled DPO reduce-scatters each branch's gradient into the rank's 1/N partition immediately after that branch's backward finishes.

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.)


Layout

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.

Release

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-wan

The 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.

License

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.

Acknowledgments

This project builds on the following upstreams. Full per-package attributions (license texts + redistribution terms) are in NOTICE.

RL training stacks

  • volcengine/verl β€” Apache 2.0. Bytedance's RL training framework; TeleBoost is built as a recipe layer on top.
  • DanceGRPO β€” Apache 2.0. TeleBoost's GRPO-family algorithms are in-house implementations of the method DanceGRPO published (arXiv 2505.07818); the scaffolding builds directly on upstream verl.
  • Tele-AI/TeleTron β€” Apache 2.0. TeleAI's long-context multi-modal training framework; TeleBoost builds on it and adds Gradient Decoupled DPO.

Generation models

  • Wan-Video/Wan2.1 β€” Apache 2.0. Alibaba's Wan2.1 / Wan2.2 video diffusion models, vendored under third_party/wan/ with the upstream LICENSE retained.

Reward models

  • tgxs002/HPSv2 β€” Apache 2.0. Human Preference Score v2.
  • alibaba-pai/VideoCLIP-XL β€” CC-BY-NC-SA-4.0 (non-commercial). Alibaba's video-text alignment model. This repository does not redistribute its code; the videoclip reward loads a copy you place under third_party/VideoCLIP_XL/ yourself.
  • Hritikbansal/videophy β€” MIT. UCLA's video physical-plausibility model.
  • LAION-AI/aesthetic-predictor β€” MIT. LAION's CLIP + linear-head aesthetic predictor.
  • princeton-vl/RAFT β€” BSD-3-Clause. Princeton's optical-flow model, used as a temporal-consistency reward.
  • TencentARC/VideoAlign β€” Apache 2.0. Referenced for reward-model design; not vendored in this repo (pull upstream if you want to train it).

Citation

@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:

  • GRPO algorithms (DanceGRPO, Flow-GRPO, GRPO-Guard, TempFlow-GRPO, BGPO, VIPO) β€” see CITATION.cff.
  • Gradient Decoupled DPO β€” cite the TeleBoost paper above.

About

A Systematic Alignment Framework for High-Fidelity, Controllable, and Robust Video Generation.

Resources

License

Contributing

Security policy

Stars

10 stars

Watchers

1 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages