MétaCan
Menu
Back to cohort
Record W1985418137 · doi:10.5539/jmr.v4n4p114

Balking and Re-service in a Vacation Queue with Batch Arrival and Two Types of Heterogeneous Service

2012· article· en· W1985418137 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Mathematics Research · 2012
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicAdvanced Queuing Theory Analysis
Canadian institutionsnot available
Fundersnot available
KeywordsService (business)QueueType of serviceService systemComputer scienceOperations researchService level objectiveComputer networkMathematicsService designBusinessService delivery frameworkMarketing

Abstract

fetched live from OpenAlex

In this paper we have considered a single server queue with customers or units arriving in groups or batches in a system providing two types of general heterogeneous service. The server provides type 1 or type 2 services on a first come first served basis. At the beginning of a service, a customer has the option to choose either type 1 or type 2 service. Also we added the concept of balking and re-service in this study. Balking is a kind of customer behavior. If a batch on arrival for service is reluctant or refuses to join the system for some reasons is said to balk. Once a service is completed the customer may leave the system or he has the option to demand re-service for the same service taken. Further as soon as service of any type gets completed, the server may take vacation or continue staying at the system even if the system is empty. For this model we have derived the steady state queue size distribution at random epoch and some particular cases have been developed and compared with known results.

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.003
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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.443
Threshold uncertainty score0.255

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.065
GPT teacher head0.350
Teacher spread0.285 · 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