Home › Code › get_lidar_in_image_fov

get_lidar_in_image_fov

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.

get_lidar_in_image_fov appears in the code Syntology harvested for 5 papers, as 2 distinct code bodies found in 5 places (a place is one code body under one paper). Of the 5 papers, 5 with a sample that ran: 0 with a run with no instrument failure, 5 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 get_lidar_in_image_fov 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 2 distinct code bodies named get_lidar_in_image_fov: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 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
2ran · our draft was wrong
0ran; the contract check could not run
0ran
0unverified
0fingerprinted

Licence is a property of each copy, so it is counted per place: 1 of the 5 places is pointer only (Syntology does not serve that copy's text). 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

5 papers shown of 5, newest first; 5 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. 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
Sparse Fuse Dense: Towards High Quality 3D Detection with Depth Completion 18 Mar 2022 LittlePey/SFD/kitti_object.py 47397a2377a470c7 ran · our draft was wrong Apache-2.0 (permissive)
Cooperative Perception for 3D Object Detection in Driving Scenarios using Infrastructure Sensors 18 Dec 2019 eduardohenriquearnold/coop-3dod-infra/lib/dataset/kitti_object.py 47397a2377a470c7 ran · our draft was wrong BSD-2-Clause (permissive)
BLVD: Building A Large-scale 5D Semantics Benchmark for Autonomous Driving 15 Mar 2019 VCCIV/BLVD/utils.py d070e0ebc13c8b39 ran · our draft was wrong no licence file found · pointer only
Modeling Local Geometric Structure of 3D Point Clouds using Geo-CNN 19 Nov 2018 voidrank/Geo-CNN/kitti/kitti_object.py 47397a2377a470c7 ran · our draft was wrong Apache-2.0 (permissive)
Frustum PointNets for 3D Object Detection from RGB-D Data 22 Nov 2017 Veincore/f-pointnet/infer/prep_data_infer.py 47397a2377a470c7 ran · our draft was wrong Apache-2.0 (permissive)

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