Papers › Human-Aware Vision-and-Language Navigation: Bridging Simulation to Reality with...

Human-Aware Vision-and-Language Navigation: Bridging Simulation to Reality with Dynamic Human Interactions

27 Jun 2024arXiv:2406.19236archive 2025-07-28

Heng Li, Minghan Li, Zhi-Qi Cheng, Yifei Dong, Yuxuan Zhou, Jun-Yan He, Qi Dai, Teruko Mitamura, Alexander G. Hauptmann

Vision-and-Language Navigation (VLN) aims to develop embodied agents that navigate based on human instructions. However, current VLN frameworks often rely on static environments and optimal expert supervision, limiting their real-world applicability. To address this, we introduce Human-Aware Vision-and-Language Navigation (HA-VLN), extending traditional VLN by incorporating dynamic human activities and relaxing key assumptions. We propose the Human-Aware 3D (HA3D) simulator, which combines dynamic human activities with the Matterport3D dataset, and the Human-Aware Room-to-Room (HA-R2R) dataset, extending R2R with human activity descriptions. To tackle HA-VLN challenges, we present the Expert-Supervised Cross-Modal (VLN-CM) and Non-Expert-Supervised Decision Transformer (VLN-DT) agents, utilizing cross-modal fusion and diverse training strategies for effective navigation in dynamic human environments. A comprehensive evaluation, including metrics considering human activities, and systematic analysis of HA-VLN's unique challenges, underscores the need for further research to enhance HA-VLN agents' real-world robustness and adaptability. Ultimately, this work provides benchmarks and insights for future research on embodied AI and Sim2Real transfer, paving the way for more realistic and applicable VLN systems in human-populated environments.

PaperPDFCodeCode 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 10 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 4 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: 8 samples from 1 repository, 7 ran (1 with no instrument failure; 6 where Syntology's instrument failed); found in paper text by Syntology: 2 samples from 1 repository, 2 ran (2 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

lpercc/ha3d_simulator officialmentioned in papermentioned on GitHubpytorchSyntology: 8 samples, 7 ran (6 instrument-failed) · 1 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

10 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 6 where Syntology's instrument failed) · 1 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.

4ran · our draft was wrong
2ran; the contract check could not run
3ran
1unverified

Licence: 10 of the 10 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

lpercc/ha3d_simulator official repository 8 samples, 7 ran (6 instrument-failed) · 1 unverified
compute in 13 papers human-viewpoint_annotation/GUI.py ran · our draft was wrong no licence file found · pointer only · da343e316b1e1233 · report fixture: signature posData:list/1/Tensor, averageArea:int/0/int · returned tuple · level recorded 2026-09-24
getRotation src/render/renderer.py ran; the contract check could not run (DEP_MISSING) no licence file found · pointer only · c0a6c9ca8a2e54b8 · report fixture: signature theta:float/0/float · returned MagicMock · level recorded 2026-09-24
getRotation src/render/rendermdm.py ran; the contract check could not run (DEP_MISSING) no licence file found · pointer only · 02200133f4a15ecf · report fixture: signature theta:float/0/float · returned ndarray · level recorded 2026-09-24
locationTypeDic HA3DSim.py ran · our draft was wrong no licence file found · pointer only · 1f3d937a2c0d07f8 · report fixture: signature location:Location/0/? · returned dict · level recorded 2026-09-24
navigableLocationsTypeDic HA3DSim.py ran · our draft was wrong no licence file found · pointer only · 8d66151ac83216bc · report fixture: signature navigableLocations:list/1/Location · returned list · level recorded 2026-09-24
renderFrames src/render/rendermdm.py ran no licence file found · pointer only · 9c4b4864491fd086 · report fixture: returned list · level recorded 2026-09-24
stateToDic HA3DSim.py ran · our draft was wrong no licence file found · pointer only · f95217d6e5b8f7e6 · report fixture: signature state:State/0/? · returned dict · level recorded 2026-09-24
computeRel src/render/rendermdm.py unverified no licence file found · pointer only · 69b68e12100d16b4 · report
peteanderson80/Matterport3DSimulator found in paper text by Syntology 2 samples, 2 ran (0 instrument-failed) · 0 unverified
AttnDecoderLSTM tasks/R2R/model.py ran licence not identified · pointer only · 3bf5245a56c56be1 · report fixture: signature action:Tensor/2/int, feature:Tensor/2/float, h_0:Tensor/2/float, c_0:Tensor/2/float, ctx:Tensor/3/float, ctx_mask:Tensor/2/bool · returned tuple · level recorded 2026-09-24
SoftDotAttention tasks/R2R/model.py ran · metamorphic tier: deterministic licence not identified · pointer only · fcb4c7f24c6fdfb4 · report fixture: signature h:Tensor/2/float, context:Tensor/3/float, mask:NoneType/0/? · returned tuple · level recorded 2026-09-22

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 Expert-Supervised Cross-Modal (VLN-CM) agent (graph method: Expert-Supervised Cross-Modal (VLN-CM) agent). 2 bricks; individually on a fixture: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

  1. AttnDecoderLSTM entry · level 1 · ran · 3bf5245a56c56be1
  2. SoftDotAttention model · level 1 · ran · fcb4c7f24c6fdfb4

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="2406.19236") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

NavigateVision and Language Navigation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformer

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