MétaCan
Menu
Back to cohort
Record W4386175527 · doi:10.1080/09544828.2023.2249216

How much workload is a ‘good’ workload for human beings to meet the deadline: human capacity zone and workload equilibrium

2023· article· en· W4386175527 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Engineering Design · 2023
Typearticle
Languageen
FieldNeuroscience
TopicMind wandering and attention
Canadian institutionsConcordia University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsWorkloadComputer scienceOperations researchSimulationOperations managementEngineeringOperating system

Abstract

fetched live from OpenAlex

When given a ‘good’ workload, human participants can efficiently complete the assigned task within the time limit, while they may fail to complete it due to low efficiency when given a ‘bad’ workload. The objective of this research is to investigate how much workload is considered ‘good’ for individuals to meet a deadline and successfully complete the assigned task. High work efficiency can be achieved by manipulating workload assignments and assigning them to different individuals at the appropriate time. We have defined the range of this ‘good’ workload as the capacity zone, which should be supported by necessary interventions from computers or human instructors. The capacity zone represents the area between the two workload equilibrium points, whose position and shape are influenced by factors such as mental capacity, maximum efficiency, and stress limit. Our analysis and simulation results indicate that humans are only capable of effectively completing a large amount of workload assignment by the deadline when working within their capacity zone. Therefore, this research aims to enhance overall work efficiency by customising workload allocation strategies based on different individuals' capacity zone and providing timely intervention when they are working beyond their capacity zone.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.116
Threshold uncertainty score0.808

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.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.085
GPT teacher head0.280
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