Repository navigation
Description
Model/Pipeline/Scheduler description
Proposes adding a new scheduler to diffusers: a parallel-in-time τ-leaping sampler for absorbing discrete diffusion, based on Accelerating Discrete Diffusion Models with Parallel-In-Time Sampling (arXiv:2607.00773).
The paper contributes a sampling algorithm (not a model architecture or training method) for discrete diffusion: it parallelizes the τ-leaping sampler for absorbing discrete diffusion formulated as a Continuous-Time Markov Chain (CTMC). Using the continuous-time stochastic-integral form of τ-leaping combined with Picard iteration, it achieves parallel-in-time acceleration, reducing per-sample NFE complexity from O(d·log S) to O(log(d·log S)·log d). It reports 7–9× runtime speedup on synthetic distributions and 1.45–1.86× (with 50% fewer NFE) on image/text tasks on a single GPU.
What blocks a clean implementation
- No τ-leaping / CTMC infrastructure exists. A repo-wide search returns zero hits for
tau-leap/τ-leap,CTMC,absorbing, orD3PM. The paper's contribution is accelerating τ-leaping — but the base τ-leaping sampler it speeds up is not implemented anywhere in the repo. - The existing discrete schedulers use a different paradigm.
scheduling_amused.py,scheduling_vq_diffusion.py, andscheduling_block_refinement.py(LLaDA2) sample via masked / multinomial / Gumbel schemes. None expose a CTMC rate matrix or a τ-leaping step that the parallel-in-time method could hook into. - No natural call site, and no scoped slice was identified. No selection rationale named a host module. A new
scheduling_tau_leaping*.pywould be freestanding — none of the AMuSED / VQ-Diffusion / LLaDA2 pipelines would call it. - No benchmark/eval path to consume as a lighter slice.
benchmarks/targets continuous models (Flux, SDXL, LTX, Wan) for latency/memory and reports no discrete-generation NFE/quality metrics. There is no released discrete-diffusion artifact the existing eval path can ingest.
Suggested scope spike
Prototype τ-leaping + Picard iteration on a synthetic absorbing-state CTMC (or against a discrete-diffusion checkpoint that already has a diffusers loader), and benchmark NFE/runtime against diffusers' existing masked discrete schedulers (AMuSED, LLaDA2 BlockRefinement). Confirm a real call site exists before committing to a full scheduler integration.
Why this is an Issue rather than a PR
The paper's contribution is a parallel-in-time τ-leaping sampler for absorbing discrete diffusion (CTMC), but diffusers has no τ-leaping/CTMC/absorbing infrastructure to parallelize — its discrete schedulers (AMuSED, VQ-Diffusion, LLaDA2) all use masked/multinomial/Gumbel sampling instead. No selection rationale named a call site, so there is no scoped slice that drops into existing code; a new τ-leaping scheduler would be freestanding and called by nothing. This needs a team decision before building: does the team want absorbing discrete diffusion / τ-leaping support at all (current discrete support is limited to masked-generation text via LLaDA2 and image via AMuSED)? Would we add a standalone τ-leaping scheduler, or retrofit it into an existing discrete pipeline that would need rewiring? Which absorbing-discrete-diffusion checkpoint would exercise it, and is there a loader path in diffusers today?
Open source status
- The model implementation is available.
- The model weights are available (Only relevant if addition is not a scheduler).
Provide useful links for the implementation
- Paper: Accelerating Discrete Diffusion Models with Parallel-In-Time Sampling (arXiv:2607.00773)
- No reference code repository surfaced in the paper, recommendation envelope, or arxiv abstract page — worth confirming whether the authors have an open release before investing in adoption.
- Authors: no GitHub usernames surfaced.
Drafted by Outrider — paper: arXiv:2607.00773.
Discovery context
Confidence: moderate (Remyx relevance 0.65)
Research interest: (pin-arxiv)
License & code availability
🟡 No code repository surfaced — couldn't fetch a LICENSE to evaluate. Worth confirming the paper has an open release before investing in adoption.
- Code / model: no repository or model URL surfaced in the paper, recommendation envelope, or arxiv abstract page.
- License:
(none detected)(class:no-code-link, compat: 0.30)
Reopen this Issue if you want Outrider to revisit this paper later. While it stays closed, the orchestrator will not re-recommend the same paper.
Opened by the Remyx Recommendation orchestrator. Pre-flight routed this paper to Issue before the coding agent ran.
Activity
smellslikeml commentedon Jul 3, 2026
@remyx-ai[bot] LEAD — autoresearch loop decision.
Hypothesis (outer agent): diffusers ships a rich scheduler abstraction (DDIM, DPM-Solver, Euler, etc.) with configurable step counts and sampling loops, making a parallel-in-time sampling acceleration for discrete diffusion directly integrable as a new scheduler or sampling-mode modifier — this aligns perfectly with the library's stated focus on model efficiency and inference acceleration, and does not require growing a new axis (no trainer, no reward model, no eval harness needed). Prior cycles all produced LEADs on IP-Adapter/pruning/fairness edges; this paper targets the scheduler core, a previously unexplored axis with clean architectural fit.
Rationale: hypothesis: diffusers' scheduler abstraction enables direct integration of parallel-in-time τ-leaping for absorbing discrete diffusion — observed: the issue body demonstrates via repo-wide search that zero τ-leaping/CTMC/absorbing/D3PM infrastructure exists; all existing discrete schedulers (AMuSED, VQ-Diffusion, LLaDA2) use masked/multinomial/Gumbel paradigms with no CTMC rate matrix; a new scheduler would be freestanding and called by nothing; no benchmark path exists for discrete-generation NFE/quality metrics — conclusion: LEAD, because the paper cannot land as-is but the scope spike names a concrete, architecturally-grounded experiment using existing modules
Research LEAD (architecturally-viable experiment surfaced by preflight):
The paper itself doesn't fit, but the experiment above uses existing target modules — this is a labeled engineering lead worth queueing, distinct from a REJECT.
remyx-ai commentedon Jul 3, 2026
This cycle's decision aligns with your summary, resulting in a LEAD (an
issue_opened_preflightstatus).Based on the telemetry for run
fc346640-ea7b-4c92-aea5-e52604ea2522:arXiv:2607.00773v1).preflight_decision: ISSUE, opening smellslikeml/diffusers#17. This confirms your rationale: a direct pull request was not viable.scheduling_amused.py,scheduling_block_refinement.py) use incompatible paradigms.selection_proposed_call_siteisnull. No viable call site for a direct integration was found, which prompted theISSUEdecision and the experimental "LEAD" you outlined.