MétaCan
Menu
Back to cohort
Record W2151504680 · doi:10.1504/ijise.2010.030744

Stochastic cycle time analysis in robotic cells

2010· article· en· W2151504680 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

VenueInternational Journal of Industrial and Systems Engineering · 2010
Typearticle
Languageen
FieldEngineering
TopicScheduling and Optimization Algorithms
Canadian institutionsToronto Metropolitan University
Fundersnot available
KeywordsRobotComputer scienceParametric statisticsCellular manufacturingGraphReal-time computingSimulationEngineeringArtificial intelligenceMathematical optimizationMathematicsTheoretical computer science

Abstract

fetched live from OpenAlex

The purpose of this study is to analyse the cycle time in a single part type robotic cell. The robotic cell is made up of several machines and a single gripper robot that loads, unloads the machines and moves the part between machines. The cell can be classified into flow- and open-shops based on the part sequence and robot move. When number of machine is increased, the cycle time analysis in a robotic cell can lead to an NP-complete problem, which remains a challenge in existing literature. In addition, the problem complication rise by having stochastic processing time in the cell. In this study, we have developed a formula for decrease (increase) structure that part processing sequence is based on decrease (increase) order of manufacturing process time. This leads to a virtual robotic cell, which its machines are virtually arranged in order of processing time regardless of their physical location. In addition, using flow-graph concept, a model is developed to calculate the cycle time of a robotic cell where the part processing time element is stochastic. This model provides parametric results for expected value of and variance of the cycle time, which can be used for evaluating the productivity of the scenarios.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.116
Threshold uncertainty score0.366

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.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.010
GPT teacher head0.208
Teacher spread0.197 · 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