MétaCan
Menu
Back to cohort
Record W2325068193 · doi:10.2514/6.2005-5612

Theory and Application of the Power Tools Suite (PTS) for General Orbital EPS Applications

2005· article· en· W2325068193 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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venue3rd International Energy Conversion Engineering Conference · 2005
Typearticle
Languageen
FieldEngineering
TopicSpacecraft Design and Technology
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsSuiteComputer scienceSizingSatellitePower (physics)Battery (electricity)Photovoltaic systemVoltageRadiator (engine cooling)Aerospace engineeringConstant (computer programming)SimulationElectrical engineeringEngineeringPhysics

Abstract

fetched live from OpenAlex

The P ower Tools Suite (PTS) is being used to calculate various Electric Power System (EPS) sizing studies and also to provide detailed transient analysis for various given orbital satellite missions. Greater accuracy is now being demanded in these EPS simulati ons to not only reduce the satellite weight, but to also accurately predict the battery, solar array, load, and radiator power responses immediately after liftoff, during ascent, during the mission phase, and at end -of -life. The PTS code provides detailed subsystem models to accurately calculate all of the EPS system parameters, and predict future EPS mission behavior. Improvements recently made to the tools suite include several user -defined solar array and battery models, additional solar array wings, a s well as constant power and constant current load subsystems. Iterative numerical techniques are used during each time -step of the calculation to insure accurate and stabilized EPS currents and voltages, even at and near the maximum power point of the so lar array. The presentation will include descriptions of the various EPS subsystem models, and comparisons of PTS model results to data and various proposed missions.

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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.943
Threshold uncertainty score0.419

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.006
GPT teacher head0.200
Teacher spread0.194 · 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