Home › Code › temporal_slice

temporal_slice

Syntologyentry name in harvested 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.

temporal_slice appears in the code Syntology harvested for 11 papers, as 1 distinct code body found in 11 places (a place is one code body under one paper). Of the 11 papers, 0 with a sample that ran: 0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument. 0 of the code bodies carry a behaviour fingerprint.

What this page is not. Routines are grouped here by the exact string of their function or class name. Nothing asserts that two samples named temporal_slice do the same thing, share code, or are comparable; the name is a string, not an identity. Behaviour outputs (what a fingerprinted sample returned on the shared battery) are not in this export and are not shown here; get_code(code_sha256="…") returns this sample's fingerprint on the shared battery, with the battery's shuffled null and lift; not shown on this site (how to connect). "Ran" means executed on a synthesized fixture, not that the code is correct or reproduces a paper.

Samples Syntology

The 1 distinct code body named temporal_slice: 0 ran · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. One tile per status, in the site's fixed vocabulary, each code body counted once:

0ran · honoured contract
0ran · violated contract
0ran · our draft was wrong
0ran; the contract check could not run
0ran
1unverified
0fingerprinted

Licence is a property of each copy, so it is counted per place: 11 of the 11 places are pointer only (Syntology does not serve that copy's text); at 7 of those this paper's copy is under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text (hover the licence cell for why). This site shows no code text for any sample; every row below links to the file in its repository where the record names one.

“Ran” means the sample executed on a synthesized input; it does not mean the output is correct. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “the contract check could not run” (RAISES, DEP_MISSING or TIMEOUT; hover a row's label for which) are failures of Syntology's instrument, not of the code, and those samples did run. The ran count above is every status except unverified, the same rule as each paper page; “with no instrument failure” is honoured, violated and ran with no contract checked. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Papers

11 papers shown of 11, newest first; 11 places in the table. A paper with no recorded date is placed by the month its arXiv id encodes, shown in the Date column as YYYY-MM (from id). One row per place: a paper whose repository defines the name more than once appears more than once, and the same code body held for several papers appears once under each, with the same status. Titles and dates are the archive's archive 2025-07-28 for papers in the archive; 2 papers have no page here and are shown by their id only (arXiv: for an arXiv id; an id from another venue, such as ACL Anthology or AAAI, is named as that venue's id, never as an arXiv id). Status and fingerprint are Syntology's record of each code body; licence is recorded for each place. The File cell ends with the code body's 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.

PaperDateFileStatus SyntologyLicence
Multi-Modality Co-Learning for Efficient Skeleton-based Action Recognition 22 Jul 2024 liujf69/MMCL-Action/feeders/tools.py 2f7f389f0584c97e unverified no licence file found · pointer only
Taylor Videos for Action Recognition 5 Feb 2024 LeiWangR/video-ar/backbone/feeder/tools.py 2f7f389f0584c97e unverified no licence file found · pointer only
Learning Mutual Excitation for Hand-to-Hand and Human-to-Human Interaction Recognition 4 Feb 2024 nkliuyifang/me-gcn/feeders/tools.py 2f7f389f0584c97e unverified no licence file found · pointer only
Navigating Open Set Scenarios for Skeleton-based Action Recognition 11 Dec 2023 kpeng9510/os-sar/feeders/tools.py 2f7f389f0584c97e unverified no licence file found · pointer only
Overcoming Topology Agnosticism: Enhancing Skeleton-Based Action Recognition through Redefined Skeletal Topology Awareness 19 May 2023 zhouyuxuanyx/blockgcn/feeders/tools.py 2f7f389f0584c97e unverified Apache-2.0 (permissive) here; the stored copy is pointer only
Hypergraph Transformer for Skeleton-based Action Recognition 17 Nov 2022 ZhouYuxuanYX/Hypergraph-Transformer-for-Skeleton-based-Action-Recognition/feeders/tools.py 2f7f389f0584c97e unverified Apache-2.0 (permissive) here; the stored copy is pointer only
Hierarchically Decomposed Graph Convolutional Networks for Skeleton-Based Action Recognition 23 Aug 2022 Jho-Yonsei/HD-GCN/feeders/tools.py 2f7f389f0584c97e unverified MIT (permissive) here; the stored copy is pointer only
Spatio-Temporal Tuples Transformer for Skeleton-Based Action Recognition 8 Jan 2022 heleiqiu/sttformer/feeders/tools.py 2f7f389f0584c97e unverified MIT (permissive) here; the stored copy is pointer only
Actional-Structural Graph Convolutional Networks for Skeleton-based Action Recognition 26 Apr 2019 limaosen0/AS-GCN/feeder/tools.py 2f7f389f0584c97e unverified BSD-2-Clause (permissive) here; the stored copy is pointer only
IJCAI id ijcai2022_0511 bruceyo/EGCN/feeder/tools.py 2f7f389f0584c97e unverified BSD-2-Clause (permissive) here; the stored copy is pointer only
id 03697 (not an arXiv id) jerry-wjh/UbH-GCN/feeders/tools.py 2f7f389f0584c97e unverified MIT (permissive) here; the stored copy is pointer only

This site shows no code text; each File cell links to the file on GitHub at the repository's current default branch, which may have changed since the 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 under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text. 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 cell for the reason. Per-sample records for a paper are on its paper page under "Code Syntology ran".

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