MétaCan
Menu
Back to cohort
Record W2800866650 · doi:10.1139/tcsme-2005-0011

HIGH-PERFORMANCE MULTI-BODY COLLISION DETECTION FOR THE REAL-TIME CONTROL OF A CTS SYSTEM

2005· article· en· W2800866650 on OpenAlex
Mojtaba Ahmadi, Mustafa Musa Jaber, F. C. Tang

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueTransactions of the Canadian Society for Mechanical Engineering · 2005
Typearticle
Languageen
FieldComputer Science
TopicRobotic Path Planning Algorithms
Canadian institutionsnot available
Fundersnot available
KeywordsCollisionCollision detectionComputationComputer scienceTrajectoryRobotSimulationControl theory (sociology)Relative velocityKinematicsReal-time computingControl (management)AlgorithmArtificial intelligence

Abstract

fetched live from OpenAlex

This paper presents a high performance methodology for the real-time implementation of collision detection on a Captive Trajectory Simulation (CTS) system. The CTS system includes a slow-moving redundant robot manipulator operating inside a wind tunnel environment with transonic conditions. Collisions can occur between robot links or the links and other objects present in the environment. A multi-body dynamic pruning method is proposed based on joint velocity bounds, which can significantly reduce the number of required collision checks without compromising the system’s safety due to its conservative assumptions. A balance is achieved between the accuracy and the speed of computations via the convex subhull subdivision of the objects, which reduces the geometrical details to further decrease the load of computations. Combining the above two strategies results in smaller and more consistent sample times allowing the collision detection to run in real-time as an integral part of a robot with a high speed control loop.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.779
Threshold uncertainty score0.502

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.008
GPT teacher head0.197
Teacher spread0.188 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it