Papers › Dual Attention Networks for Visual Reference Resolution in Visual Dialog

Dual Attention Networks for Visual Reference Resolution in Visual Dialog

25 Feb 2019IJCNLP 2019 11arXiv:1902.09368archive 2025-07-28

Gi-Cheon Kang, Jaeseo Lim, Byoung-Tak Zhang

Visual dialog (VisDial) is a task which requires an AI agent to answer a series of questions grounded in an image. Unlike in visual question answering (VQA), the series of questions should be able to capture a temporal context from a dialog history and exploit visually-grounded information. A problem called visual reference resolution involves these challenges, requiring the agent to resolve ambiguous references in a given question and find the references in a given image. In this paper, we propose Dual Attention Networks (DAN) for visual reference resolution. DAN consists of two kinds of attention networks, REFER and FIND. Specifically, REFER module learns latent relationships between a given question and a dialog history by employing a self-attention mechanism. FIND module takes image features and reference-aware representations (i.e., the output of REFER module) as input, and performs visual grounding via bottom-up attention mechanism. We qualitatively and quantitatively evaluate our model on VisDial v1.0 and v0.9 datasets, showing that DAN outperforms the previous state-of-the-art model by a significant margin.

PaperPDFConference PDFCodeCode Syntology ran

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 7 code samples harvested from 2 repositories linked to this paper: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 4 samples from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 3 samples from 1 repository, 3 ran (3 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

gicheonkang/DAN-VisDial officialmentioned in papermentioned on GitHubpytorchMITSyntology: 4 samples, 1 ran (0 instrument-failed) · 3 unverified report
phellonchen/DMRM mentioned on GitHubpytorchMITSyntology: 3 samples, 3 ran (0 instrument-failed) · 0 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

7 samples harvested: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 0 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 has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
3ran
3unverified

Licence: 1 of the 7 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. 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.

gicheonkang/DAN-VisDial official repository 4 samples, 1 ran (0 instrument-failed) · 3 unverified
scores_to_ranks utils/eval_utils.py ran MIT (permissive) · 26ec77dabb4db96d · report fixture: signature scores:Tensor/2/float · returned Tensor · level recorded 2026-09-25
create_glove_embedding_init utils/utils.py unverified MIT (permissive) · 40ad7ca583756bff · report
get_gt_ranks utils/eval_utils.py unverified MIT (permissive) · 72d5007cbbf2c295 · report
load_imageid in 5 papers utils/utils.py unverified MIT (permissive) · e90714af510bbb7f · report
phellonchen/DMRM community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
load_folder in 9 papers utils.py ran MIT (permissive) · 8c1252eacab71602 · report fixture: signature folder:str/0/str, suffix:str/0/str · returned list · level recorded 2026-09-25
load_imageid in 5 papers utils.py ran MIT (permissive) · bf90bd27fe08f3a2 · report fixture: signature folder:str/0/str · returned set · level recorded 2026-09-25
pil_loader in 144 papers utils.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · 1df9a5ffd9b38c34 · report fixture: signature path:str/0/str · returned Image · level recorded 2026-09-22

Tasks

AI AgentQuestion AnsweringVisual DialogVisual GroundingVisual Question AnsweringVisual Question Answering (VQA)

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Visual Dialog VisDial v0.9 val DAN MRR 66.38 #2 of 18 Archive leaderboard report
Visual Dialog VisDial v0.9 val DAN Mean Rank 4.04 #2 of 18 Archive leaderboard report
Visual Dialog VisDial v0.9 val DAN R@1 53.33 #2 of 18 Archive leaderboard report
Visual Dialog VisDial v0.9 val DAN R@10 90.38 #2 of 18 Archive leaderboard report
Visual Dialog VisDial v0.9 val DAN R@5 82.42 #2 of 18 Archive leaderboard report
Visual Dialog Visual Dialog v1.0 test-std DAN MRR (x 100) 63.2 #55 of 80 Archive leaderboard report
Visual Dialog Visual Dialog v1.0 test-std DAN Mean 4.3 #55 of 80 Archive leaderboard report
Visual Dialog Visual Dialog v1.0 test-std DAN NDCG (x 100) 57.59 #55 of 80 Archive leaderboard report
Visual Dialog Visual Dialog v1.0 test-std DAN R@1 49.63 #55 of 80 Archive leaderboard report
Visual Dialog Visual Dialog v1.0 test-std DAN R@10 89.35 #55 of 80 Archive leaderboard report
Visual Dialog Visual Dialog v1.0 test-std DAN R@5 79.75 #55 of 80 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.

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