Papers › Temporal Attentive Alignment for Large-Scale Video Domain Adaptation

Temporal Attentive Alignment for Large-Scale Video Domain Adaptation

30 Jul 2019ICCV 2019 10arXiv:1907.12743archive 2025-07-28

Min-Hung Chen, Zsolt Kira, Ghassan AlRegib, Jaekwon Yoo, Ruxin Chen, Jian Zheng

Although various image-based domain adaptation (DA) techniques have been proposed in recent years, domain shift in videos is still not well-explored. Most previous works only evaluate performance on small-scale datasets which are saturated. Therefore, we first propose two large-scale video DA datasets with much larger domain discrepancy: UCF-HMDB_full and Kinetics-Gameplay. Second, we investigate different DA integration methods for videos, and show that simultaneously aligning and learning temporal dynamics achieves effective alignment even without sophisticated DA methods. Finally, we propose Temporal Attentive Adversarial Adaptation Network (TA3N), which explicitly attends to the temporal dynamics using domain discrepancy for more effective domain alignment, achieving state-of-the-art performance on four video DA datasets (e.g. 7.9% accuracy gain over "Source only" from 73.9% to 81.8% on "HMDB --> UCF", and 10.3% gain on "Kinetics --> Gameplay"). The code and data are released at http://github.com/cmhungsteve/TA3N.

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 10 code samples harvested from 2 repositories linked to this paper: 6 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; 3 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 7 samples from 1 repository, 4 ran (1 with no instrument failure; 3 where Syntology's instrument failed); community (archive-listed): 3 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.

No sample is linked to this paper from 2 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

cmhungsteve/TA3N officialmentioned in papermentioned on GitHubpytorchMITSyntology: 7 samples, 4 ran (3 instrument-failed) · 3 unverified report
jonmun/EPIC-KITCHENS-100_UDA_TA3N mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Rescaling Egocentric Vision (arXiv:2006.13256; that paper's own run record: 10 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 3 where Syntology's instrument failed) · 8 unverified); nothing checks that they implement this paper's method. report
mustafa1728/TA3N-Lightning mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Rescaling Egocentric Vision (arXiv:2006.13256; that paper's own run record: 10 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 3 where Syntology's instrument failed) · 8 unverified); nothing checks that they implement this paper's method. report
mustafa1728/TA3N-Lightning-Kitchen_Domain_Adaptation mentioned on GitHubpytorchMITSyntology: 3 samples, 2 ran (0 instrument-failed) · 1 unverified report
olivesgatech/TA3N mentioned on GitHubpytorchMITSyntology: not harvested 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

10 samples harvested: 6 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; 3 where Syntology's instrument failed) · 4 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.

3ran · our draft was wrong
3ran
4unverified

Licence: 0 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. 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.

cmhungsteve/TA3N official repository 7 samples, 4 ran (3 instrument-failed) · 3 unverified
attentive_entropy in 6 papers loss.py ran · our draft was wrong fingerprinted MIT (permissive) · 5dafc748f41191f5 · report fixture: signature pred:Tensor/2/float, pred_domain:Tensor/2/float · returned Tensor · level recorded 2026-09-24
cross_entropy_soft in 6 papers loss.py ran · our draft was wrong fingerprinted MIT (permissive) · b1e8dce608f3f658 · report fixture: signature pred:Tensor/2/float · returned Tensor · level recorded 2026-09-24
dis_MCD in 5 papers loss.py ran · our draft was wrong fingerprinted MIT (permissive) · 0c3c2aa9cf2ac2f0 · report fixture: signature out1:Tensor/2/float, out2:Tensor/2/float · returned Tensor · level recorded 2026-09-24
randSelectBatch utils/utils.py ran fingerprinted MIT (permissive) · 8651bcfb1198f96d · report fixture: signature input:Tensor/2/float, num:int/0/int · returned tuple · level recorded 2026-09-25
convert_c3d_tensor_batch dataset_preparation/video2feature.py unverified MIT (permissive) · b92a3f112f0c080c · report
extract_frame_feature_batch dataset_preparation/video2feature.py unverified MIT (permissive) · 468842eca7cd59de · report
mustafa1728/TA3N-Lightning-Kitchen_Domain_Adaptation community (archive-listed) 3 samples, 2 ran (0 instrument-failed) · 1 unverified
get_aggregated_metrics_from_dict model.py ran MIT (permissive) · 0fb3b659d41d4031 · report fixture: signature input_metric_dict:dict/0/? · returned dict · level recorded 2026-09-24
removeDummy model.py ran MIT (permissive) · 0fb8066818796998 · report fixture: signature attn:Tensor/3/float, out_1:tuple/1/Tensor, out_2:Tensor/2/float, pred_domain:list/1/Tensor, feat:list/1/Tensor, batch_size:int/0/int · returned tuple · level recorded 2026-09-24
get_aggregated_metrics model.py unverified MIT (permissive) · 5fb564b0af4ab527 · report

Tasks

Domain AdaptationUnsupervised Domain Adaptation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Domain Adaptation HMDB --> UCF (full) TA3N Accuracy 81.79 #4 of 4 Archive leaderboard report
Domain Adaptation UCF --> HMDB (full) TA3N Accuracy 78.33 #5 of 5 Archive leaderboard report
Unsupervised Domain Adaptation EPIC-KITCHENS-100 TA3N Average Accuracy 39.9 #3 of 5 Archive leaderboard report
Unsupervised Domain Adaptation HMDB-UCF TA3N Accuracy 90.54 #4 of 6 Archive leaderboard report
Unsupervised Domain Adaptation Jester (Gesture Recognition) TA3N Accuracy 55.5 #3 of 5 Archive leaderboard report
Unsupervised Domain Adaptation UCF-HMDB TA3N Accuracy 81.38 #4 of 6 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