MétaCan
Menu
Back to cohort

An Approach to Support Human-in-the-Loop Big Data Software Development Projects

2021· article· en· W4206287169 on OpenAlex
Nathalia Nascimento, Paulo Alencar, Donald Cowan

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

Venue2021 IEEE International Conference on Big Data (Big Data) · 2021
Typearticle
Languageen
FieldPsychology
TopicHuman-Automation Interaction and Safety
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsComputer scienceHuman-in-the-loopTask (project management)Software developmentBig dataSoftwareSoftware engineeringSet (abstract data type)Software development processData scienceArtificial intelligenceSystems engineeringEngineeringData miningProgramming language

Abstract

fetched live from OpenAlex

There is a lack of approaches and tools to support the development of projects in which humans and machines (e.g., machine learning algorithms) need to collaborate to achieve a specified goal. Specifically, given a set of software development tasks to develop a project collaboratively, how can these tasks be assigned to humans or machines to perform each task most efficiently and effectively? Such understanding is essential to support new methodologies for developing human-in-the-loop approaches in which machine learning automated procedures assist software developers in achieving their tasks. This paper describes our work in progress towards providing an approach to guide the assignment of tasks in developing human-in-the-loop big data (science) software development projects. The paper provides several contributions, including the provision of (i) a human-in-the-loop approach for the development of big data software development projects; (ii) the application of the approach to two case studies; (iii) a discussion of implications and research opportunities.

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.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Open science, Insufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.564
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0090.002
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0050.003

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.579
GPT teacher head0.463
Teacher spread0.116 · 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