MétaCan
Menu
Back to cohort
Record W4320493463 · doi:10.3390/drones7020127

Towards a Quantitative Approach for Determining DAA System Risk Ratio

2023· article· en· W4320493463 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueDrones · 2023
Typearticle
Languageen
FieldEngineering
TopicAir Traffic Management and Optimization
Canadian institutionsNational Research Council Canada
Fundersnot available
KeywordsComputer scienceAviationRulemakingSystems engineeringAeronauticsRisk analysis (engineering)Operations researchEngineeringAerospace engineeringBusiness

Abstract

fetched live from OpenAlex

Specific Operations Risk Assessment (SORA) is a methodology developed by the Joint Authority on Rulemaking for Unmanned Systems (JARUS) for safely conducting and evaluating Remotely Piloted Aircraft Systems (RPAS) operations in specific airspace. Many regulators, including Transport Canada (TC), the civilian aviation authority in Canada, have adopted the SORA approach to guide RPAS operators in their applications for Beyond Visual Line of Sight (BVLOS) flight. Although the qualitative approach on how to assess the performance of a Detect and Avoid (DAA) system is outlined in the SORA, a quantitative and agreed-upon approach, on how to ensure that the specific DAA system meets the required Risk Ratio criteria, has yet to be established. This paper proposes a practical approach to determining the Risk Ratio, considering sensor performance, RPA maneuvering characteristics, and airspace specifics. The developed approach relies on publicly available modelling frameworks and airspace models. Illustrative examples of applying the method to determine the Risk Ratio of specific DAA systems are presented in the paper along with a discussion on the challenges of implementing SORA into BVLOS regulations for RPAS.

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.918
Threshold uncertainty score0.317

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.0000.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.024
GPT teacher head0.238
Teacher spread0.214 · 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