MétaCan
Menu
Back to cohort
Record W2101690519 · doi:10.1109/ests.2007.372112

Graph Trace Analysis Approach to Optimizing Power and Heat Flow for Clustered Computing; An Example of Model Based System of Systems Design and Deployment

2007· article· en· W2101690519 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicSystems Engineering Methodologies and Applications
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsSoftware deploymentComputer scienceDistributed computingDependency (UML)TRACE (psycholinguistics)Engineering design processSystems engineeringSystems designGraphDomain (mathematical analysis)System deploymentData modelingDependency graphSystems modelingSoftware engineeringTheoretical computer scienceEngineering

Abstract

fetched live from OpenAlex

During system of system (SoS) design, many decisions from different engineering disciplines are made and documented. Today, designers increasingly use modeling. For example, they address the issues involved with total cost of ownership by better understanding the interactions of parts and systems. For a large SoS, the labor intense modeling has one potential alternative approach involving the concepts of graph trace analysis (GTA) for distributed processing of integrated system models (ISM). GTA features a wide range of algorithms that flexibly attach to models that stay in their 'engineering domains' in the ISM. A subsystem model for a single domain can be built directly from the engineering design data and then simulated or analyzed. A model using millions of simple objects can be built automatically, including looped and radial systems. Physical dependency linkages between engineering domains can be built directly from reference designators and parts data. Design and deployment of a compute cluster is illustrated by composing an "integrated system model" (ISM) from different engineering domain models, where models from different domains are linked together with dependency iterators from GTA. During early design phases, the ISM of a compute cluster might include a short list of engineering design domains. Later, during deployment, sensors and actuators are included in the ISM and GTA algorithms. A need for open, standard parts data is discussed for design tools used in engineering along with data exchange formats that allow product design data to be reused by other design teams.

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.001
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: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.431
Threshold uncertainty score0.582

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.096
GPT teacher head0.277
Teacher spread0.182 · 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