Bibliographic record
Abstract
Recent nanosatellite programs and studies of nanosatellites for operational missions have highlighted challenges that are unique to this spacecraft category. While each small satellite class has peculiar design challenges, nanosatellite development challenges are compounded by the unique niche that nanosatellites occupy and the current perception of hardware maturity levels available to support nanosatellite spacecraft. Recent experimental successes with microsatellite systems are allowing such spacecraft to rapidly move toward operational systems. This has produced a false perception that the same small, high TRL operational components and subsystems used in microsatellites will transition easily into the smaller nanosatellite designs. At the same time advances in the sophistication of CubeSat missions and academic programs have increased the expectation of the mission utility that should be possible with nanosatellites. This paper focuses on the unique design challenges of high mission utility nanosatellite programs and the current state of component and subsystem hardware available to meet the unique nanosatellite design constraints. Addressing these challenges in coming years will enable this class of spacecraft to become a viable and healthy part of the aerospace industry, and as a secondary payload improve the launch options and reduced cost commensurate with operationally responsive space (ORS) solutions.
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.003 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.002 |
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".