MétaCan
Menu
Back to cohort
Record W2738422289

CHOPIN: Methods and Results of the Fourth Global Trajectory Optimization Competition

2010· article· en· W2738422289 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJAXA Repository (JAXA) · 2010
Typearticle
Languageen
FieldEngineering
TopicSpacecraft Dynamics and Control
Canadian institutionsnot available
Fundersnot available
KeywordsTrajectoryCompetition (biology)Trajectory optimizationComputer scienceMathematicsEconomicsMathematical optimizationOptimal control
DOInot available

Abstract

fetched live from OpenAlex

In the Winter of 2009, the CHOPIN (Canada, HOlland, jaPan orbit Investigator Network) team of the Japan Aerospace Exploration Agency (JAXA) participated in the fourth Global Trajectory Optimization Competition (GTOC4). This time, the objective was driven by the question: "How to maximize the relevance of a rendezvous mission to a given NEA by visiting the largest set of intermediate asteroids?" For the competition, the spacecraft had to be launched from Earth with a hyperbolic excess velocity of up to 4 km/s. Then, using electric propulsion, the spacecraft had to flyby a maximum number of asteroids from a given list and rendezvous with a last one within 10 years. The mission was constrained to have a launch window between 2015 and 2025, and the spacecraft wet mass was assumed to be 1000 kg, with a spacecraft specific impulse of 3000 s and a thrust level constrained to 0.135 N. Finally, each asteroid could only be visited once. The performance index to be maximized was the number of asteroids and the final mass of the spacecraft. In this paper, we go over the methods used, results obtained and lessons learned.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.625
Threshold uncertainty score0.430

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.003
GPT teacher head0.224
Teacher spread0.220 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it