MétaCan
Menu
Back to cohort
Record W1958190125 · doi:10.24908/pceea.v0i0.5769

EVALUATION OF INDIVIDUAL MEMBERS IN ENGINEERING DESIGN TEAMS

2015· article· en· W1958190125 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.
venuePublished in a venue whose home country is Canada.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueProceedings of the Canadian Engineering Education Association (CEEA) · 2015
Typearticle
Languageen
FieldEngineering
TopicEngineering Education and Curriculum Development
Canadian institutionsUniversity of New Brunswick
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsFormative assessmentPeer evaluationPsychologyTeam compositionTeamworkAccreditationTeam effectivenessEngineering educationPeer feedbackTask (project management)CurriculumMedical educationWork (physics)Mathematics educationEngineeringHigher educationSocial psychologyPedagogyOperations managementEngineering managementManagementPolitical scienceMedicine

Abstract

fetched live from OpenAlex

The curriculum of accredited engineering programs in Canada must culminate with a significant design experience where students must demonstrate an ability to work in teams. The determination of individual grades for work products submitted by a team is however a challenging task. To deter students from free riding on the efforts of their teammates, every team member should not simply receive the same grade. Individual grades in the senior process design course at the University of New Brunswick are determined by first assigning a team grade to team deliverables and then adjusting each team member’s grade up or down using a multiplier. The value of the multiplier is based on peer and mentor evaluations and on the level of participation of the student in course activities. The peer ratings collected in 2014-2015 are generally higher than the mentor ratings, likely because of peer pressures to give high ratings. The bias is greatly reduced however when the evaluations are normalized by dividing the rating for each student by the team average. Because of this bias, the mentor evaluations should complement the peer ratings when providing formative feedback to students and determining individual team member grades.

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.002
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.318
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.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.019
GPT teacher head0.225
Teacher spread0.206 · 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