Development, analysis, and implications of open-source simulations of remotely piloted aircraft.
Bibliographic record
Abstract
In recent years, the use of Remotely Piloted Aircraft (RPAs) for diverse purposes has increased exponentially. As a consequence, the uncertainty created by situations turning into a threat for civilians has led to more restrictive regulations from national administrations such as Transport Canada. Their purpose is to safely integrate RPAs in the current airspace used for piloted aviation by evaluating Sense and Avoid (SAA) strategies and close encounters. The difficulty falls on having to rely on simulated environments because of the risk to the human pilot in the piloted aircraft. In the first part of this research, the technical difficulties associated with the development and study of RPA computer models are discussed. It explores the rationale behind using Open-Source Software (OSS) platforms for simulating RPAs as well as the challenges associated with interacting with OSS at graduate student level. A set of recommendations is proposed as the solution to improve the graduate student experience with OSS. In the second part, particular challenges related to the design of OSS computer models are addressed. Based on: (1) the differences and similarities between piloted and RPA flight simulators and (2) existing Verification and Validation (V&V) approaches, a validation method is presented as a solution to the subject of developing fixed-wing RPAs in OSS environments. This method is used to design two flight dynamics models with SAA applications. The first computer model is presented in tutorial format as a case study for the validation procedure whereas the second computer model is specific for testing SAA strategies. In the last part, one of the designed RPAs is integrated into a computer environment with a representative general aircraft. From the simulated encounters, a diving avoidance manoeuvre on the RPA is developed. This performance is observed to analyze the consequences to the airspace. The implications of this research are seen from three perspectives: (1) the OSS challenges in graduate school are wide-spread across disciplines, (2) the proposed validation procedure is adaptable to fit any computer model and simulation scenario, and (3) the simulated OSS framework with an RPA computer model has served for testing preliminary SAA methods with close encounters with manned aircraft.
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.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.002 | 0.004 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".