Papers › Consistency Flow Matching: Defining Straight Flows with Velocity Consistency

Consistency Flow Matching: Defining Straight Flows with Velocity Consistency

2 Jul 2024arXiv:2407.02398archive 2025-07-28

Ling Yang, Zixiang Zhang, Zhilong Zhang, Xingchao Liu, Minkai Xu, Wentao Zhang, Chenlin Meng, Stefano Ermon, Bin Cui

Flow matching (FM) is a general framework for defining probability paths via Ordinary Differential Equations (ODEs) to transform between noise and data samples. Recent approaches attempt to straighten these flow trajectories to generate high-quality samples with fewer function evaluations, typically through iterative rectification methods or optimal transport solutions. In this paper, we introduce Consistency Flow Matching (Consistency-FM), a novel FM method that explicitly enforces self-consistency in the velocity field. Consistency-FM directly defines straight flows starting from different times to the same endpoint, imposing constraints on their velocity values. Additionally, we propose a multi-segment training approach for Consistency-FM to enhance expressiveness, achieving a better trade-off between sampling quality and speed. Preliminary experiments demonstrate that our Consistency-FM significantly improves training efficiency by converging 4.4x faster than consistency models and 1.7x faster than rectified flow models while achieving better generation quality. Our code is available at: https://github.com/YangLing0818/consistency_flow_matching

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 13 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 9 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 8 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 13 samples from 1 repository, 11 ran (2 with no instrument failure; 9 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

yangling0818/consistency_flow_matching officialmentioned in papermentioned on GitHubjaxMITSyntology: 13 samples, 11 ran (9 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

13 samples harvested: 11 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 9 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

8ran · our draft was wrong
1ran; the contract check could not run
2ran
2unverified

Licence: 7 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. For 7 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from yangling0818/consistency_flow_matching. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

yangling0818/consistency_flow_matching official repository 13 samples, 11 ran (9 instrument-failed) · 2 unverified
crop_resize in 16 papers datasets.py ran; the contract check could not run (RAISES) MIT (permissive) here; the stored copy is pointer only · fd14d238ccd5f679 · report fixture: signature image:EagerTensor/3/int, resolution:int/0/int · returned EagerTensor · level recorded 2026-09-26
get_act in 56 papers models/layers.py ran · our draft was wrong MIT (permissive) · db5f935a1d6b4c2c · report fixture: signature config:Config/0/? · returned ReLU · level recorded 2026-09-25
get_data_inverse_scaler in 21 papers datasets.py ran · our draft was wrong MIT (permissive) · 6c419026e778dee2 · report fixture: signature config:SimpleNamespace/0/? · returned function · level recorded 2026-09-22
get_data_scaler in 20 papers datasets.py ran · our draft was wrong MIT (permissive) · 346d2e6cc8b48a5d · report fixture: signature config:SimpleNamespace/0/? · returned function · level recorded 2026-09-22
get_div_fn in 12 papers likelihood.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 0bfcb6b2d940e393 · report fixture: signature fn:callable/0/? · returned function · level recorded 2026-09-26
get_normalization in 25 papers models/normalization.py ran MIT (permissive) · 1b8adb3294e53c6d · report fixture: signature config:Config/0/?, conditional:bool/0/bool · returned type · level recorded 2026-09-25
get_optimizer in 228 papers losses.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 8ff7c24dade9904c · report fixture: signature config:Config/0/?, params:generator/0/? · returned Adam · level recorded 2026-09-24
ncsn_conv1x1 in 21 papers models/layers.py ran MIT (permissive) here; the stored copy is pointer only · 85b2235eb7afaa4f · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int, bias:bool/0/bool, dilation:int/0/int, init_scale:float/0/float, padding:int/0/int · returned Conv2d · level recorded 2026-09-26
optimization_manager in 26 papers losses.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 366bb8c7035a2fc8 · report fixture: signature config:Config/0/? · returned function · level recorded 2026-09-24
pad_t_like_x in 8 papers
census: 2 implementations from 5 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 1, kind float, dtype float32 · arg 2: rank 4, kind float, dtype float32
consistencyfm/torchcfm/conditional_flow_matching.py ran · our draft was wrong MIT (permissive) · 9e320fdaa5a3063f · report fixture: signature t:Tensor/1/float, x:Tensor/4/float · returned Tensor · level recorded 2026-09-22
variance_scaling in 31 papers models/layers.py ran · our draft was wrong MIT (permissive) · 3ac11bfe0ae80195 · report fixture: signature scale:float/0/float, mode:str/0/str, distribution:str/0/str, in_axis:int/0/int, out_axis:int/0/int, dtype:dtype/0/?, device:str/0/str · returned function · level recorded 2026-09-24
classifier_fn_from_tfhub in 10 papers evaluation.py unverified MIT (permissive) here; the stored copy is pointer only · 54a00db9aadf092f · report
load_dataset_stats in 11 papers evaluation.py unverified MIT (permissive) here; the stored copy is pointer only · b45ab263f8440954 · report

Tasks

Image Generation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Consistency Models

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections