Papers › TALoS: Enhancing Semantic Scene Completion via Test-time Adaptation on the Line of Sight
TALoS: Enhancing Semantic Scene Completion via Test-time Adaptation on the Line of Sight
Hyun-Kurl Jang, Jihun Kim, Hyeokjun Kweon, Kuk-Jin Yoon
Semantic Scene Completion (SSC) aims to perform geometric completion and semantic segmentation simultaneously. Despite the promising results achieved by existing studies, the inherently ill-posed nature of the task presents significant challenges in diverse driving scenarios. This paper introduces TALoS, a novel test-time adaptation approach for SSC that excavates the information available in driving environments. Specifically, we focus on that observations made at a certain moment can serve as Ground Truth (GT) for scene completion at another moment. Given the characteristics of the LiDAR sensor, an observation of an object at a certain location confirms both 1) the occupation of that location and 2) the absence of obstacles along the line of sight from the LiDAR to that point. TALoS utilizes these observations to obtain self-supervision about occupancy and emptiness, guiding the model to adapt to the scene in test time. In a similar manner, we aggregate reliable SSC predictions among multiple moments and leverage them as semantic pseudo-GT for adaptation. Further, to leverage future observations that are not accessible at the current time, we present a dual optimization scheme using the model in which the update is delayed until the future observation is available. Evaluations on the SemanticKITTI validation and test sets demonstrate that TALoS significantly improves the performance of the pre-trained SSC model. Our code is available at https://github.com/blue-531/TALoS.
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):
get_harvested_code_for_paper(arxiv_id="2410.15674")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2410.15674", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2410.15674")
Code
Syntology 17 code samples harvested from 1 repository linked to this paper: 14 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 2 violated, 2 with no contract checked; 8 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 6 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: official repository: 17 samples from 1 repository, 14 ran (6 with no instrument failure; 8 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. 3 of the 14 samples that ran have no recorded date.
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
17 samples harvested: 14 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 2 violated, 2 with no contract checked; 8 where Syntology's instrument failed) · 3 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.
Licence: 17 of the 17 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 blue-531/talos. “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.
f3d8ca81e8d0ee0c · report
fixture: signature label:Tensor/1/int · returned Tensor · level recorded 2026-09-26 3f9a651be8d4082c · report
fixture: signature x:Tensor/5/float · returned tuple · level recorded 2026-09-26 3d6928be33f7d1bb · report
fixture: signature points:ndarray/2/float, pose0:ndarray/2/float, pose:ndarray/2/float · returned ndarray · level recorded 2026-09-26 261283216054e8b0 · report
fixture: signature semkittiyaml:dict/0/? · returned tuple · level recorded, date not recorded 03a862c1bc4bb8d4 · report
fixture: signature semkittiyaml:dict/0/? · returned ndarray · level recorded, date not recorded census: 5 implementations from 7 papers, 5 distinct outputs across 5 buckets, one shared input per bucket this sample: bucket 3 of 5, arg 1: rank 2, kind int, dtype int64 · arg 2: rank 2, kind int, dtype int64 utils/lovasz_losses.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only ·
d94639b28b2134ff · report
fixture: signature preds:ndarray/2/int, labels:ndarray/2/int, C:int/0/int, EMPTY:float/0/float, ignore:NoneType/0/?, per_image:bool/0/bool · returned ndarray · level recorded 2026-09-22 1211530cd527bd0b · report
fixture: signature preds:ndarray/3/int, labels:ndarray/3/int, EMPTY:float/0/float, ignore:int/0/int, per_image:bool/0/bool · returned float · level recorded 2026-09-22 e85b5d21dc5b8382 · report
fixture: signature gt_sorted:Tensor/1/int · returned Tensor · level recorded 2026-09-22 1ff14b65ece70b32 · report
fixture: signature x:Tensor/5/float, proposure:Tensor/2/int · returned tuple · level recorded 2026-09-26 936c2117da625a10 · report
fixture: signature x:Tensor/5/float · returned tuple · level recorded 2026-09-26 c134fed586d67760 · report
fixture: signature cls:callable/0/?, name:NoneType/0/? · returned type · level recorded 2026-09-26 06a0e2786c57fc38 · report
fixture: signature cls:callable/0/?, name:str/0/str · returned type · level recorded 2026-09-26 9416a0d63c5a653a · report
fixture: signature cls:callable/0/?, name:str/0/str · returned type · level recorded 2026-09-26 ae0ede157bf07297 · report
fixture: signature input_label:Tensor/2/int · returned Tensor · level recorded, date not recorded 0a96d3b0c027f68e · report
237978845d0ee378 · report
dc3115f6b6438996 · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| 3D Semantic Scene Completion | SemanticKITTI | TALoS | mIoU | 37.9 | #1 of 20 | Archive leaderboard | report |
Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.
Methods
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