Papers › Boundaries for quantum advantage with single photons and loop-based time-bin interferometers

Boundaries for quantum advantage with single photons and loop-based time-bin interferometers

25 Nov 2024arXiv:2411.16873links table onlyarchive 2025-07-28

Samo Novák, David D. Roberts, Alexander Makarovskiy, Raúl García-Patrón, William R. Clements

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Loop-based boson samplers interfere photons in the time degree of freedom using a sequence of delay lines. Since they require few hardware components while also allowing for long-range entanglement, they are strong candidates for demonstrating quantum advantage beyond the reach of classical emulation. We propose a method to exploit this loop-based structure to more efficiently classically sample from such systems. Our algorithm exploits a causal-cone argument to decompose the circuit into smaller effective components that can each be simulated sequentially by calling a state vector simulator as a subroutine. To quantify the complexity of our approach, we develop a new lattice path formalism that allows us to efficiently characterize the state space that must be tracked during the simulation. In addition, we develop a heuristic method that allows us to predict the expected average and worst-case memory requirements of running these simulations. We use these methods to compare the simulation complexity of different families of loop-based interferometers, allowing us to quantify the potential for quantum advantage of single-photon Boson Sampling in loop-based architectures.

PaperPDFCodeCode Syntology ran

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

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2411.16873")

Code

Syntology Ran 5 of 6 code samples harvested from 1 repository linked to this paper; 1 has no recorded run. Of those that ran: 2 ran · honoured contract; 1 ran · violated contract; 2 ran · fixture could not drive it.

By repository: official repository: 6 samples from 1 repository, 5 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

orcacomputing/loop-progressive-simulator officialmentioned in papermentioned on GitHub 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

6 samples harvested; 5 ran; 2 honoured the contract we drafted; 1 has no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

2ran · honoured contract
1ran · violated contract
2ran · fixture could not drive it
1unverified

Licence: 0 of the 6 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 orcacomputing/loop-progressive-simulator. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

arg_int_or_var orcacomputing/loop-progressive-simulator/shell_utilities/run_experiment_families.py official repository ran · honoured contract fingerprinted Apache-2.0 (permissive) · c5148c34aab732e8 · report
arg_sym_tuple_range_or_ellipsis orcacomputing/loop-progressive-simulator/shell_utilities/run_experiment_families.py official repository ran · honoured contract fingerprinted Apache-2.0 (permissive) · 5cb09c220028d4f6 · report
check_commute orcacomputing/loop-progressive-simulator/loop_progressive_simulator/bscircuits.py official repository ran · violated contract fingerprinted Apache-2.0 (permissive) · d5f600fcd8a8eb34 · report
commute_multiple_forward orcacomputing/loop-progressive-simulator/loop_progressive_simulator/bscircuits.py official repository ran · fixture could not drive it Apache-2.0 (permissive) · ee4c0661b33b2808 · report
commute_pos_forward orcacomputing/loop-progressive-simulator/loop_progressive_simulator/bscircuits.py official repository ran · fixture could not drive it Apache-2.0 (permissive) · 9c89caee45939fa9 · report
arg_range orcacomputing/loop-progressive-simulator/shell_utilities/run_experiment_families.py official repository unverified Apache-2.0 (permissive) · c5f60ba0c7513642 · report

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