MétaCan
Menu
Back to cohort
Record W4285252923 · doi:10.5267/j.jpm.2022.4.002

A precedence constrained flow shop scheduling problem with transportation time, breakdown times, and weighted jobs

2022· article· en· W4285252923 on OpenAlexvenueno aff
M. Thangaraj, T. Jayanth Kumar, KR. Nandan

Bibliographic record

VenueJournal of Project Management · 2022
Typearticle
Languageen
FieldEngineering
TopicScheduling and Optimization Algorithms
Canadian institutionsnot available
Fundersnot available
KeywordsSuccessor cardinalFlow shop schedulingComputer scienceJob shop schedulingJob shopMathematical optimizationScheduling (production processes)Operations researchIndustrial engineeringScheduleMathematicsEngineering

Abstract

fetched live from OpenAlex

Job precedence can often be seen in various manufacturing process scenarios. For instance, in the context of flow shop scheduling, certain jobs must be processed before a specific job may be executed. Formally, this scenario is known as precedence constraint, which influences the optimal job sequence. Because of this practical significance, in this study, a two-machine flow shop scheduling problem in which transportation times, breakdown time, and weighted jobs are considered. In addition to that, an ordered precedence constraint is considered that ensures a successor job cannot start on any machine before its predecessor job has been done on all machines. This is the first study that deals with flow shop scheduling problems with transportation times, breakdown time, job weights, and precedence constraints altogether, to the best of the author’s knowledge. To solve this problem, a simple and efficient solution methodology is developed that assures optimal or near-optimal solutions effectively. The developed algorithm is tested on various test instances and results are reported, which will be useful for future comparative studies.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.002
Version: metacan-v3-hybrid-931329e0061cValidation 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: none
Teacher disagreement score0.005
Threshold uncertainty score0.010

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.002
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.002
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0020.001
Insufficient payload (model declined to judge)0.0030.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.006
GPT teacher head0.200
Teacher spread0.195 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations3
Published2022
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Project ManagementSame topicScheduling and Optimization AlgorithmsFrench-language works237,207