MétaCan
Menu
Back to cohort
Record W2090701678 · doi:10.1115/1.2406099

Model-based Rapid Redesign Using Decomposition Patterns

2006· article· en· W2090701678 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

VenueJournal of Mechanical Design · 2006
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicProduct Development and Customization
Canadian institutionsUniversity of New BrunswickUniversity of Toronto
Fundersnot available
KeywordsExpeditingComputer scienceDesign structure matrixProcess (computing)DecompositionSelection (genetic algorithm)Industrial engineeringAgile manufacturingAgile software developmentSystems engineeringEngineeringArtificial intelligenceSoftware engineering

Abstract

fetched live from OpenAlex

This paper presents a pattern-based decomposition methodology for rapid redesign to support design customization in agile manufacturing of evolutionary products. The methodology has three functional phases. The first phase, called design dependency analysis, systematizes and reorganizes the intrinsic coupling structure of a given existing design model that is represented using the design dependency matrix. The second phase, called redesign partitioning analysis, generates alternative redesign pattern solutions to form a solution selection space through a three-stage procedure. The third phase, called pattern selection analysis, finds an optimal redesign pattern solution that entails the least potential redesign effort (in the subsequent solution process). Each pattern solution identifies and delimits the portions of the design model that need to be recomputed, thus expediting the redesign solution process. In such a way, one can treat the recomputation of the entire model, which is a conventional and computation-expensive solution approach, only as the last resort to solve the redesign problem given. An example redesign problem is used for the methodology illustration.

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.897
Threshold uncertainty score0.517

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.001
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.042
GPT teacher head0.246
Teacher spread0.204 · 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