Bibliographic record
Abstract
The International Space Station (ISS) is the largest space program that has ever been undertaken on the basis of international cooperation (United States, Russia, Japan, Canada and Europe). Europe is responsible for two key station elements, which are the Attached Pressurized Module (APM) - Columbus and the Automated Transfer Vehicle (ATV). The purpose of this paper is to give an overview about the Columbus operations concept for performing the ground and flight control tasks assigned to the Columbus Control Center (Col-CC). DLRs German Space Operations Center (GSOC) will provide facilities and manpower to the International Space Station Program within the framework of the European Space Agencys Columbus project. The Col -CC is the main control centre for Columbus and will receive all system downlink telemetry, uplink all system commands and is the source/destination for all system file transfers to/from the Columbus. The so called Columbus Flight Control Team has been designated in order to address the operations Preparation and Planning Support, operations Execution (including Activation and Checkout during Flight 1-E), Increment-Preparation and Post-Operations Evaluation activities, which are needed to conduct safe, sustained and efficient Columbus mission operations during its orbital life. Also this article provides the Col-CC mission description, objectives, constraints and an overview of the mission phases, interfaces to other centers, organizations and communications networks and a description of the operations interfaces. A description of the specified Columbus software systems environment, showing the onboard data management and the interface between flight subsystems (e.g. Communication and Data Management Subsystems) like data acquisition and distribution, telecommunication support, data management environment for applications in support of system and mission management is also given.
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.002 | 0.004 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.004 |
| Science and technology studies | 0.004 | 0.001 |
| Scholarly communication | 0.007 | 0.005 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.473 | 0.220 |
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".