MétaCan
Menu
Back to cohort
Record W2790675559 · doi:10.1109/tem.2018.2797223

A Cuckoo Search Algorithm to Solve Transfer Line Balancing Problems With Different Cutting Conditions

2018· article· en· W2790675559 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

VenueIEEE Transactions on Engineering Management · 2018
Typearticle
Languageen
FieldEngineering
TopicAssembly Line Balancing Optimization
Canadian institutionsUniversity of Windsor
Fundersnot available
KeywordsCuckoo searchComputer scienceCuckooLine (geometry)AlgorithmMathematical optimizationMathematics

Abstract

fetched live from OpenAlex

An automated transfer line balancing problem is investigated in this paper. The line produces a complex part at a high volume, such as cylinder heads, and incorporates identical machines that can be operated under different cutting conditions. The selection of cutting conditions significantly influences productivity and the cost of the transfer line. The production of cylinder heads requires machining different operations within a given takt time and satisfying precedence, inclusion, and exclusion relationships. The operations are located on different faces of the cylinder head and are processed by different cutting tools. The line balancing problem is studied to identify the optimal cutting conditions, number of machines and tools, and machining sequence of operations. The objective is to design a balanced transfer line at a minimum machining and tooling cost, and also with minimum nonproductive time. The problem is represented by a goal-programming model and solved for small transfer line configurations through linearization. An improved cuckoo search algorithm via Levy flight is developed to solve large-scale instances. Results of the cuckoo algorithm are promising since it reached optimal and close-to-optimal solutions to small problems and surpassed the results of a random local search approach for instances of medium and large problems.

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 categoriesMeta-epidemiology (narrow)
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.907
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
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.206
Teacher spread0.199 · 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