Developing Planetary Rover Traction Systems
Bibliographic record
Abstract
Surface mobility will be a critical aspect of any robotic or manned planetary surface mission. The Lunar and Martian surfaces have a wide variety of terrain types, from wideranging plains to steep mountainous regions; from rock-infested boulder fields to soft sand. Prospecting rovers must have the ability to climb steep slopes and traverse soft, deep sand, while ISRU-specific rovers require high levels of traction to accomplish land-forming tasks. Whereas their terrestrial counterparts generally rely on rubber pneumatic tires, rubber tracks, or segmented steel tracks to provide high levels of traction in extreme terrain, environmental conditions and mass constraints preclude the use of these traction devices for space exploration applications. At Argo/ODG, alternative technologies are being developed in an effort to provide planetary rovers with high levels of traction while surviving the extreme environmental conditions. The metallic track developed by Argo/ODG shares characteristics of both the heavyduty steel segmented track and the high performance, lightweight rubber track used more commonly in the power-sports industry. In addition to traction characteristics, consideration was given to reliability, durability, failure modes, and efficiency over different terrain. Testing in soft, fine-grained sand has shown that the metallic track is able to produce high levels of traction, while more qualitative testing in rocky and steep terrain has shown the metallic tracks to be reliable and durable. For scenarios in which mass constraints are more severe, and very high traction levels are not required, a lightweight compliant metal wheel may provide a better compromise between traction, mass, and simplicity. Using some of the techniques and technologies that arose from track development, a simple, lightweight compliant wheel was designed for the Juno Rover. Prototyping and testing is scheduled for summer/fall of 2010 to characterize its performance against both the baseline rubber pneumatic tire and the metallic tracks.
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 machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.005 | 0.003 |
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 source (direct Gemma or distilled Codex), 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".