Papers › Dual Transfer Learning for Event-based End-task Prediction via Pluggable Event to...

Dual Transfer Learning for Event-based End-task Prediction via Pluggable Event to Image Translation

4 Sep 2021ICCV 2021 10arXiv:2109.01801archive 2025-07-28

Lin Wang, Yujeong Chae, Kuk-Jin Yoon

Event cameras are novel sensors that perceive the per-pixel intensity changes and output asynchronous event streams with high dynamic range and less motion blur. It has been shown that events alone can be used for end-task learning, e.g., semantic segmentation, based on encoder-decoder-like networks. However, as events are sparse and mostly reflect edge information, it is difficult to recover original details merely relying on the decoder. Moreover, most methods resort to pixel-wise loss alone for supervision, which might be insufficient to fully exploit the visual details from sparse events, thus leading to less optimal performance. In this paper, we propose a simple yet flexible two-stream framework named Dual Transfer Learning (DTL) to effectively enhance the performance on the end-tasks without adding extra inference cost. The proposed approach consists of three parts: event to end-task learning (EEL) branch, event to image translation (EIT) branch, and transfer learning (TL) module that simultaneously explores the feature-level affinity information and pixel-level knowledge from the EIT branch to improve the EEL branch. This simple yet novel method leads to strong representation learning from events and is evidenced by the significant performance boost on the end-tasks such as semantic segmentation and depth estimation.

PaperPDFConference PDFCodeCode 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 1 repository linked to this paper: 7 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 10 samples from 1 repository, 7 ran (5 with no instrument failure; 2 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.

addisonwang2013/dtl officialmentioned in papermentioned on GitHubpytorchMITSyntology: 10 samples, 7 ran (2 instrument-failed) · 3 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: 7 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 2 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.

2ran · our draft was wrong
5ran
3unverified

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 addisonwang2013/dtl. “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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

addisonwang2013/dtl official repository 10 samples, 7 ran (2 instrument-failed) · 3 unverified
EITConv modeling/deeplab_dtl.py ran fingerprinted MIT (permissive) · 9660609a6d6cbf98 · report fixture: returned EITConv · level recorded 2026-09-22
build_aspp in 10 papers modeling/deeplab_dtl.py ran · our draft was wrong MIT (permissive) · 39265c6363db075a · report fixture: signature backbone:str/0/str, output_stride:int/0/int, BatchNorm:callable/0/? · returned ASPP_EIT · level recorded 2026-09-22
conv3x3 in 1,376 papers backbone/drn.py ran · our draft was wrong MIT (permissive) · 0e722c9ff0920473 · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int, padding:int/0/int, dilation:int/0/int · returned Conv2d · level recorded 2026-09-22
conv_bn in 88 papers backbone/mobilenet.py ran MIT (permissive) · 8cf426bba4e98da5 · report fixture: signature inp:int/0/int, oup:int/0/int, stride:int/0/int, BatchNorm:callable/0/? · returned Sequential · level recorded 2026-09-25
decode_segmap in 7 papers visualize.py ran MIT (permissive) · d50d152c6a2002ce · report fixture: signature temp:ndarray/2/int · returned ndarray · level recorded 2026-09-25
fixed_padding in 28 papers backbone/mobilenet.py ran fingerprinted MIT (permissive) · b34c12741c44b60c · report fixture: signature inputs:Tensor/4/float, kernel_size:int/0/int, dilation:int/0/int · returned Tensor · level recorded 2026-09-25
xception in 13 papers backbone/xception_new.py ran MIT (permissive) · fd487be36b369be6 · report fixture: signature pretrained:bool/0/bool, BatchNorm:callable/0/? · returned Xception · level recorded 2026-09-26
ASPP_EIT modeling/deeplab_dtl.py unverified MIT (permissive) · 40529a28fb8f1e37 · report
ASPP_Fusion modeling/deeplab_dtl.py unverified MIT (permissive) · 15fc6f001d543fef · report
DeepLab_Dual_V2 modeling/deeplab_dtl.py unverified MIT (permissive) · 2db744a03f84a236 · report

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 Dual Transfer Learning (graph method: Dual Transfer Learning). 21 bricks; individually on a fixture: 12 ran (of which 6 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 1 violated, 6 with no contract checked; 4 where Syntology's instrument failed) · 9 unverified. The assembly has not been run end-to-end.

  1. DeepLab_Dual_V2 entry · level 0 · unverified · 2db744a03f84a236
  2. EITConv model · level 1 · ran · 9660609a6d6cbf98
  3. SynchronizedBatchNorm2d helper · level 1 · ran · e6f91e80712a76dd
  4. build_aspp helper · level 1 · ran · our draft was wrong · 39265c6363db075a
  5. build_backbone helper · level 1 · ran · our draft was wrong · 8157861ceb8eb470
  6. build_decoder helper · level 1 · ran · our draft was wrong · 23ce2fc66128ad4c
  7. build_im_recon_decoder helper · level 1 · ran · our draft was wrong · 5e5f8123e17483ef
  8. _SynchronizedBatchNorm helper · level 1 · ran · 9f557ce8389a603f
  9. ASPP helper · level 0 · unverified · fced7a51f0af7316
  10. ASPP_EIT helper · level 0 · unverified · 40529a28fb8f1e37
  11. ASPP_Fusion helper · level 0 · unverified · 15fc6f001d543fef
  12. ASPP_Nodropout helper · level 0 · unverified · 89524076ef47e188
  13. Decoder helper · level 0 · unverified · f5402b45ac78ab62
  14. Decoder_DTL helper · level 0 · unverified · 6dad7760a37b19c3
  15. Decoder_Nodropout helper · level 0 · unverified · d12c50019a4b5875
  16. SyncMaster helper · level 1 · ran · 93f1be24e0653bc8
  17. _sum_ft helper · level 1 · ran · violated contract · 3151cee68a1020dc
  18. _unsqueeze_ft helper · level 1 · ran · honoured contract · 1efd43bcf31727c0
  19. _ASPPModule helper · level 0 · unverified · 5e90ce39dc46a1c4
  20. FutureResult helper · level 1 · ran · 9e8c636cac1d847f
  21. SlavePipe helper · level 1 · ran · e75aa93b78286d50

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

Tasks

DecoderDepth EstimationEvent-based Object SegmentationRepresentation LearningSemantic SegmentationTransfer LearningTranslation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Event-based Object Segmentation MVSEC-SEG DTL mIoU 0.33 #4 of 8 Archive leaderboard report
Event-based Object Segmentation RGBE-SEG DTL mIoU 0.29 #5 of 8 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