Papers › Non-Promise Version of Unique Sink Orientations
Non-Promise Version of Unique Sink Orientations
Tiago Oliveira Marques
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.
A unique sink orientation (USO) is an orientation of the edges of a hypercube such that each face has a unique sink. Many optimization problems like linear programs reduce to USOs, in the sense that each vertex corresponds to a possible solution, and the global sink corresponds to the optimal solution. People have been studying intensively the problem of find the sink of a USO using vertex evaluations, i.e., queries which return the orientation of the edges around a vertex. This problem is a so called promise problem, as it assumes that the orientation it receives is a USO. In this paper, we analyze a non-promise version of the USO problem, in which we try to either find a sink or an efficiently verifiable violation of the USO property. This problem is worth investigating, because some problems which reduce to USO are also promise problems (and so we can also define a non-promise version for them), and it would be interesting to discover where USO lies in the hierarchy of subclasses of TFNPᵈᵗ, and for this a total search problem is required (which is the case for the non-promise version). We adapt many known properties and algorithms from the promise version to the non-promise one, including known algorithms for small dimensions and lower and upper bounds, like the Fibonacci Seesaw Algorithm. Furthermore, we present an efficient resolution proof of the problem, which shows it is in the search complexity class PLSᵈᵗ (although this fact was already known via reductions). Finally, although initially the only allowed violations consist of $2$ vertices, we generalize them to more vertices, and provide a full categorization of violations with $4$ vertices, showing that they are also efficiently verifiable.
Code
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
Not run by Syntology. Nothing on this page verifies that the listed code works.
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