SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2002.06289 · 2020

3D Dynamic Scene Graphs: Actionable Spatial Perception with Places, Objects, and Humans

arXiv · PDF · Open in the Atlas

Code that ran

1 of 4 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 1 has no contract verdict; 0 failures of our instrument; 3 no recorded run), measured 2026-11-21; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2002.06289.json · badge: /api/ran/2002.06289.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
MIT-SPARK/Kimera-VIO-Evaluation community (classifier label)
classifier basis not recorded on the link
1 ran · 3 no recorded run
FunctionStatusWhere it lives
get_pipeline_times Ran
ran on a synthesized input
MIT-SPARK/Kimera-VIO-Evaluation/plotting_tools/display_timing.py
code served (permissive licence) · get_code("b34d6ebc2acb186d")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import os
import numpy as np
import tempfile
import shutil

# Create temporary directory structure for testing
temp_dir = tempfile.mkdtemp()

# Create pipeline directories and timing files
pipeline_names = ['pipeline_1', 'pipeline_2']

for pipeline_name in pipeline_names:
    output_dir = os.path.join(temp_dir, pipeline_name, 'output')
    os.makedirs(output_dir, exist_ok=True)
    
    # Create a timing file with keyframe_ids and timing data
    timing_file = os.path.join(output_dir, 'output_timingVIO.txt')
    with open(timing_file, 'w') as f:
        # Write sample timing data: keyframe_id and various timing columns
        f.write("0 10.5 20.1 30.2\n")
        f.write("1 11.3 21.0 31.5\n")
        f.write("2 12.1 22.5 32.0\n")
        f.write("3 10.9 21.8 30.7\n")

results_folder = temp_dir
time_column_idx = 1  # Column index for timing information (0-indexed, so 1 is the second column)

ARGS = {
    'results_folder': results_folder,
    'pipeline_names': pipeline_names,
    'time_column_idx': time_column_idx
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple — a tuple output has no array shape of its own; none is stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
find_submissions Not yet run
unverified (harvested, no recorded run)
MIT-SPARK/Kimera-VIO-Evaluation/evaluation/go_seek_evaluation.py
code served (permissive licence) · get_code("7877d692dc622ad3")
How it ran

no invocation recorded.

find_submissions Not yet run
unverified (harvested, no recorded run)
MIT-SPARK/Kimera-VIO-Evaluation/evaluation/uHumans_evaluation.py
code served (permissive licence) · get_code("3d95f1c3d29f54c2")
How it ran

no invocation recorded.

write_yaml_params Not yet run
unverified (harvested, no recorded run)
MIT-SPARK/Kimera-VIO-Evaluation/evaluation/regression_tests.py
code served (permissive licence) · get_code("092fb93f1a94ce62")
How it ran

no invocation recorded.

Also present in other papers' code

Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 4 are also present in other papers whose code we hold (4 with at least one paper dated earlier, 0 the same month, 0 later) and 0 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

FunctionAlso present inEarliest-datedOthers named
find_submissions 1 other paper
1 dated earlier
1910.02490 (2019-10)
Kimera: an Open-Source Library for Real-Time Metric-Semantic Localization and Mapping
find_submissions 1 other paper
1 dated earlier
1910.02490 (2019-10)
Kimera: an Open-Source Library for Real-Time Metric-Semantic Localization and Mapping
get_pipeline_times 1 other paper
1 dated earlier
1910.02490 (2019-10)
Kimera: an Open-Source Library for Real-Time Metric-Semantic Localization and Mapping
write_yaml_params 1 other paper
1 dated earlier
1910.02490 (2019-10)
Kimera: an Open-Source Library for Real-Time Metric-Semantic Localization and Mapping

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-21.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

We present a unified representation for actionable spatial perception: 3D Dynamic Scene Graphs. Scene graphs are directed graphs where nodes represent entities in the scene (e.g. objects, walls, rooms), and edges represent relations (e.g. inclusion, adjacency) among nodes. Dynamic scene graphs (DSGs) extend this notion to represent dynamic scenes with moving agents (e.g. humans, robots), and to include actionable information that supports planning and decision-making (e.g. spatio-temporal relations, topology at different levels of abstraction). Our second contribution is to provide the first fully automatic Spatial PerceptIon eNgine(SPIN) to build a DSG from visual-inertial data. We integrate state-of-the-art techniques for object and human detection and pose estimation, and we describe how to robustly infer object, robot, and human nodes in crowded scenes. To the best of our knowledge, this is the first paper that reconciles visual-inertial SLAM and dense human mesh tracking. Moreover, we provide algorithms to obtain hierarchical representations of indoor environments (e.g. places, structures, rooms) and their relations. Our third contribution is to demonstrate the proposed spatial perception engine in a photo-realistic Unity-based simulator, where we assess its robustness and expressiveness. Finally, we discuss the implications of our proposal on modern robotics applications. 3D Dynamic Scene Graphs can have a profound impact on planning and decision-making, human-robot interaction, long-term autonomy, and scene prediction. A video abstract is available at https://youtu.be/SWbofjhyPzI

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2002.06289")
get_code_for_paper("2002.06289")
have("2002.06289")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2002.06289.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2002.06289.svg)](https://syntology.ai/paper/2002.06289)

Connect an agent — have() is free.