MétaCan
Menu
Back to cohort
Record W2068214349 · doi:10.1155/2014/169097

Scheduling of Changes in Complex Engineering Design Process via Genetic Algorithm and Elementary Effects Method

2014· article· en· W2068214349 on OpenAlex
Yuliang Li, Wei Zhao, Yongsheng Ma, Lichen Hu

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

VenueAdvances in Mechanical Engineering · 2014
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicProduct Development and Customization
Canadian institutionsUniversity of Alberta
FundersNational Natural Science Foundation of China
KeywordsComputer scienceCritical path methodScheduleEngineering design processScheduling (production processes)Mathematical optimizationGenetic algorithmDependency (UML)HeuristicProcess (computing)AlgorithmIndustrial engineeringEngineeringMachine learningSystems engineeringArtificial intelligenceMathematics

Abstract

fetched live from OpenAlex

Engineering design changes constantly occur in a complex engineering design process. Designers have to put an appropriate procedure in place to handle these changes in order to realize successful product development in a timely and cost-effective manner. When many change propagation paths are present, selection of the best change evolution paths and distribution of change results to downstream tasks become critical to the progress management of the project. In this paper, based on the available change propagation simulation algorithm, a global sensitivity analysis method known as elementary effects (EE) is employed to rank the importance of each potential propagation path with those involved design dependencies in the process. Further, an EE-based heuristic design dependency encoding method is applied to the genetic algorithm which is then adopted to schedule the change updating process. Finally, the optimal results obtained by the complete search and the heuristic dependency encoding methods are compared to illustrate the improvements and effectiveness of the latter method.

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.496
Threshold uncertainty score0.737

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.007
GPT teacher head0.227
Teacher spread0.221 · 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