Notice bibliographique
Résumé
At GSOC, we start developing a concept for a modular and flexible ground system.Applying a service oriented architecture and using standardized interfaces, such a system will help to support upcoming missions of all kinds, especially in the context of the increasing amount of small satellites.Such a system will offer complete new ways to organize space operations in form of distributed operations.Also dedicated setups for special mission phases will become much easier as the system is designed to be dynamically deployed or changed.Providing the opportunity to access the system not only from within the control center allows using the experts wherever they are located and reduces the need to double such resources. I. IntroductionSpaceflight is changing, and with it spacecraft operations does.The number of launched spacecrafts is significantly increasing; space-crafts are getting smaller and cheaper.While we were used to have one large satellite for a special purpose, nowadays there are formations and fleets of similar or equal satellites.Small groups of students at universities build experimental cube-sats and find rather economical possibilities to launch them.Start-Up companies use satellites on a trial-and-error basis with short lifetimes.Dysfunctional objects deorbit and they are replaced rapidly by the next generation.All these developments have a strong impact to the ground system used for such missions.With the more easy and low-priced possibilities to bring an instrument into orbit, the ground system to control such an instrument is demanded to be inexpensive as well.Furthermore, the rapid developments and shortened production-and launchcycles require much more flexible ways to set up and configure the ground segments.In addition, with satellites being operated by smaller teams, groups or companies, it is essential for them to have direct access to their spacesegment out of these groups -that is they will not establish an additional dedicated ground operations team.Consequently operations will no longer be necessarily confined to one single dedicated control-centers such as ours at Oberpfaffenhofen.However, even if all those boundary conditions do change, the tasks to be fulfilled to successfully operate a space mission stay the same.Orbit and attitude still need to be controlled.Activities on board still need to be planned and initiated.Ground stations still need to be connected to the mission control instance, contacts still need to be scheduled, and space-links still need to be established.Telemetry data still needs to be received and analyzed.And last not least, payload data still need to be received, processed and delivered.At the Germans Space Operation Center (GSOC) we are convinced to have the proper tools to carry out all such tasks.Developed throughout a heritage of 50 years from its founding and with more than 70 missions -from all areas of space-flight -operated at GSOC, we have a rich portfolio of expertize, experience and tools.Now it is up to us, to make this treasure available to customers in an environment rapidly changing as outlined above. II. Determining the GoalsBeing aware of the ongoing and upcoming changes described above, the future requirements were collected in two ways.First, the business-unit development group of our institution made a survey with GSOC customers, representing the various kinds of satellite operators.Second, the personnel in charge at GSOC to carry out satellite operations was asked to provide some kind of wish-list, how their daily work could be improved.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,002 | 0,002 |
| Méta-épidémiologie (sens strict) | 0,001 | 0,001 |
| Méta-épidémiologie (sens large) | 0,001 | 0,001 |
| Bibliométrie | 0,001 | 0,001 |
| Études des sciences et des technologies | 0,001 | 0,002 |
| Communication savante | 0,003 | 0,006 |
| Science ouverte | 0,002 | 0,005 |
| Intégrité de la recherche | 0,002 | 0,003 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,008 | 0,005 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».