Papers › Global Transport for Fluid Reconstruction with Learned Self-Supervision

Global Transport for Fluid Reconstruction with Learned Self-Supervision

13 Apr 2021CVPR 2021 1arXiv:2104.06031archive 2025-07-28

Erik Franz, Barbara Solenthaler, Nils Thuerey

We propose a novel method to reconstruct volumetric flows from sparse views via a global transport formulation. Instead of obtaining the space-time function of the observations, we reconstruct its motion based on a single initial state. In addition we introduce a learned self-supervision that constrains observations from unseen angles. These visual constraints are coupled via the transport constraints and a differentiable rendering step to arrive at a robust end-to-end reconstruction algorithm. This makes the reconstruction of highly realistic flow motions possible, even from only a single input view. We show with a variety of synthetic and real flows that the proposed global reconstruction of the transport process yields an improved reconstruction of the fluid motion.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 5 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 13 samples from 1 repository, 5 ran (5 with no instrument failure; 0 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

tum-pbs/Global-Flow-Transport officialmentioned in papermentioned on GitHubtfSyntology: 13 samples, 5 ran (0 instrument-failed) · 8 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: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 5 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

5ran · honoured contract
8unverified

Licence: 0 of the 13 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from tum-pbs/Global-Flow-Transport. “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.

tum-pbs/Global-Flow-Transport official repository 13 samples, 5 ran (0 instrument-failed) · 8 unverified
exponential_schedule phitest/render/optimization.py ran · honoured contract fingerprinted MIT (permissive) · dea35f2fb336f071 · report fixture: signature start:float/0/float, iteration:int/0/int, min:float/0/float, max:float/0/float, base:float/0/float, scale:float/0/float, offset:int/0/int · returned float64 · level recorded 2026-09-22
linear_schedule in 26 papers phitest/render/optimization.py ran · honoured contract fingerprinted MIT (permissive) · 62e39ce4ebceebc9 · report fixture: signature start:float/0/float, iteration:int/0/int, min:float/0/float, max:float/0/float, step:float/0/float, offset:int/0/int · returned float64 · level recorded 2026-09-22
logarithmic_decay_schedule phitest/render/optimization.py ran · honoured contract fingerprinted MIT (permissive) · 298556b59501061d · report fixture: signature start:float/0/float, iteration:int/0/int, min:float/0/float, max:float/0/float, base:float/0/float, scale:float/0/float, offset:int/0/int · returned float64 · level recorded 2026-09-22
root_decay_schedule phitest/render/optimization.py ran · honoured contract fingerprinted MIT (permissive) · 9d0acc8ad39ce234 · report fixture: signature start:float/0/float, iteration:int/0/int, min:float/0/float, max:float/0/float, base:float/0/float, scale:float/0/float, offset:int/0/int · returned float64 · level recorded 2026-09-22
scalar_schedule phitest/render/optimization.py ran · honoured contract MIT (permissive) · cf832c4ffbfc957d · report fixture: signature v:dict/0/?, iteration:int/0/int · returned float64 · level recorded 2026-09-22
GridShape phitest/render/optimization.py unverified MIT (permissive) · 601eab27b0ffedb9 · report
Int3 phitest/render/optimization.py unverified MIT (permissive) · b8caec2d42608462 · report
Matrix in 5 papers phitest/render/optimization.py unverified MIT (permissive) · 97a1d0bc12380472 · report
NO_OP phitest/render/optimization.py unverified MIT (permissive) · 69fbf6e35bde397a · report
OptimizationContext phitest/render/optimization.py unverified MIT (permissive) · 152656539723d1f8 · report
Vector2 phitest/render/optimization.py unverified MIT (permissive) · caa6b4a091dcb0d5 · report
Vector3 phitest/render/optimization.py unverified MIT (permissive) · 56d3012c454a0d8f · report
Vector4 phitest/render/optimization.py unverified MIT (permissive) · 758900fa457f8ee5 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Global Transport for Fluid Reconstruction with Learned Self-Supervision (graph method: Global Transport for Fluid Reconstruction with Learned Self-Supervision). 13 bricks; individually on a fixture: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 5 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 8 unverified. The assembly has not been run end-to-end.

  1. OptimizationContext entry · level 0 · unverified · 152656539723d1f8
  2. GridShape helper · level 0 · unverified · 601eab27b0ffedb9
  3. NO_OP helper · level 0 · unverified · 69fbf6e35bde397a
  4. scalar_schedule helper · level 1 · ran · honoured contract · cf832c4ffbfc957d
  5. Int3 helper · level 0 · unverified · b8caec2d42608462
  6. Vector3 helper · level 0 · unverified · 56d3012c454a0d8f
  7. Vector4 helper · level 0 · unverified · 758900fa457f8ee5
  8. exponential_schedule helper · level 1 · ran · honoured contract · dea35f2fb336f071
  9. linear_schedule helper · level 1 · ran · honoured contract · 62e39ce4ebceebc9
  10. logarithmic_decay_schedule helper · level 1 · ran · honoured contract · 298556b59501061d
  11. root_decay_schedule helper · level 1 · ran · honoured contract · 9d0acc8ad39ce234
  12. Vector2 helper · level 0 · unverified · caa6b4a091dcb0d5
  13. Matrix helper · level 0 · unverified · 97a1d0bc12380472

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2104.06031") returns these assemblies with each brick's role and wiring (how to connect).

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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