Papers › GET: Group Event Transformer for Event-Based Vision

GET: Group Event Transformer for Event-Based Vision

4 Oct 2023ICCV 2023 1arXiv:2310.02642archive 2025-07-28

Yansong Peng, Yueyi Zhang, Zhiwei Xiong, Xiaoyan Sun, Feng Wu

Event cameras are a type of novel neuromorphic sen-sor that has been gaining increasing attention. Existing event-based backbones mainly rely on image-based designs to extract spatial information within the image transformed from events, overlooking important event properties like time and polarity. To address this issue, we propose a novel Group-based vision Transformer backbone for Event-based vision, called Group Event Transformer (GET), which de-couples temporal-polarity information from spatial infor-mation throughout the feature extraction process. Specifi-cally, we first propose a new event representation for GET, named Group Token, which groups asynchronous events based on their timestamps and polarities. Then, GET ap-plies the Event Dual Self-Attention block, and Group Token Aggregation module to facilitate effective feature commu-nication and integration in both the spatial and temporal-polarity domains. After that, GET can be integrated with different downstream tasks by connecting it with vari-ous heads. We evaluate our method on four event-based classification datasets (Cifar10-DVS, N-MNIST, N-CARS, and DVS128Gesture) and two event-based object detection datasets (1Mpx and Gen1), and the results demonstrate that GET outperforms other state-of-the-art methods. The code is available at https://github.com/Peterande/GET-Group-Event-Transformer.

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 11 code samples harvested from 1 repository linked to this paper: 8 ran (of which 6 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 0 violated, 7 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: 11 samples from 1 repository, 8 ran (8 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 1 of its repositories that Syntology harvested for other papers:

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.

peterande/get-group-event-transformer officialmentioned in papermentioned on GitHubpytorchSyntology: 11 samples, 8 ran (0 instrument-failed) · 3 unverified report
qiwang233/dailydvs-200 mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to DailyDVS-200: A Comprehensive Benchmark Dataset for Event-Based Action Recognition (arXiv:2407.05106; that paper's own run record: 9 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; 2 where Syntology's instrument failed) · 6 unverified); nothing checks that they implement this paper's method. 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

11 samples harvested: 8 ran (of which 6 constructed an object rather than computing a result; 8 with no instrument failure: 1 honoured, 0 violated, 7 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
7ran
3unverified

Licence: 11 of the 11 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 peterande/get-group-event-transformer. “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 4 samples that ran, the graph records a signature this page does not show, each row saying why in its tooltip: for 3, 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; for 1, an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.

peterande/get-group-event-transformer official repository 11 samples, 8 ran (0 instrument-failed) · 3 unverified
GTA models/GET.py ran no licence file found · pointer only · c2279fab0aabbfd0 · report fixture: returned GTA · level recorded 2026-09-22
GTE models/GET.py ran fingerprinted no licence file found · pointer only · 2f3cd08e6aa447a5 · report fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-24
GroupAttention models/GET.py ran no licence file found · pointer only · bdaae63b59ddf52e · report fixture: returned GroupAttention · level recorded 2026-09-22
Group_Mlp models/GET.py ran no licence file found · pointer only · 234ea7e4f3885cbe · report fixture: returned Group_Mlp · level recorded 2026-09-22
OGConv models/GET.py ran fingerprinted no licence file found · pointer only · 9854f8b1756dbbec · report fixture: returned OGConv · level recorded 2026-09-22
Pool in 8 papers models/GET.py ran fingerprinted no licence file found · pointer only · fcdc2941985e03e5 · report fixture: returned Pool · level recorded 2026-09-22
WindowAttention in 50 papers models/GET.py ran no licence file found · pointer only · 4b0f05c87c76da57 · report fixture: returned WindowAttention · level recorded 2026-09-22
load_checkpoint in 277 papers models/GET.py ran · honoured contract no licence file found · pointer only · f54ea09cb6cccd68 · report fixture: returned float · level recorded 2026-09-22
BasicLayer in 56 papers models/GET.py unverified no licence file found · pointer only · 0fe62915b9760ef0 · report
EDSABlock models/GET.py unverified no licence file found · pointer only · a9e73877468fa6e7 · report
GET models/GET.py unverified no licence file found · pointer only · 0f01118c51363bf3 · 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 Group Event Transformer (GET) (graph method: Group Event Transformer (GET)). 16 bricks; individually on a fixture: 13 ran (of which 7 constructed an object rather than computing a result; 10 with no instrument failure: 1 honoured, 0 violated, 9 with no contract checked; 3 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

  1. GET entry · level 0 · unverified · 0f01118c51363bf3
  2. BasicLayer model · level 0 · unverified · 0fe62915b9760ef0
  3. GTA model · level 1 · ran · c2279fab0aabbfd0
  4. GTE model · level 1 · ran · 2f3cd08e6aa447a5
  5. LayerNormFP32 helper · level 1 · ran · 6d0ff69e341e91b6
  6. load_checkpoint helper · level 1 · ran · honoured contract · f54ea09cb6cccd68
  7. EDSABlock model · level 0 · unverified · a9e73877468fa6e7
  8. window_partition helper · level 2 · ran; the contract check could not run · 144d10b49baeb8a6
  9. OGConv model · level 1 · ran · 9854f8b1756dbbec
  10. Pool helper · level 1 · ran · fcdc2941985e03e5
  11. Group_Mlp model · level 1 · ran · 234ea7e4f3885cbe
  12. GroupAttention model · level 1 · ran · bdaae63b59ddf52e
  13. WindowAttention model · level 1 · ran · 4b0f05c87c76da57
  14. window_reverse helper · level 1 · ran · our draft was wrong · 61bf152e6a42a184
  15. LinearFP32 helper · level 1 · ran · ef982aba178be7dd
  16. custom_normalize helper · level 1 · ran · our draft was wrong · 4e2c8a04e709451b

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

Tasks

ClassificationEvent-based visionObject Detectionobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Classification N-CARS GET Accuracy (%) 96.7 #2 of 6 Archive leaderboard report
Classification N-CARS GET Architecture Transformer #2 of 6 Archive leaderboard report
Classification N-CARS GET Params (M) 4.5 #2 of 6 Archive leaderboard report
Classification N-CARS GET Representation Token #2 of 6 Archive leaderboard report
Object Detection GEN1 Detection GET-T Params 21.9 #2 of 11 Archive leaderboard report
Object Detection GEN1 Detection GET-T mAP 47.9 #2 of 11 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.

Methods

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

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