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

DESIGN DAYS BOOT CAMP: ENHANCING STUDENT MOTIVATION TO START THINKING IN ENGINEERING DESIGN TERMS IN THE FIRST YEAR

2018· article· en· W2885679389 on OpenAlex
Igor Ivkovic, Thomas L. Willett, Matthew Borland, Maud Gorbet

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.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueProceedings of the Canadian Engineering Education Association (CEEA) · 2018
Typearticle
Languageen
FieldEngineering
TopicBiomedical and Engineering Education
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsEngineering design processTerm (time)Process (computing)Minor (academic)Engineering educationComputer scienceDesign thinkingMathematics educationIterative designDesign educationDesign processEngineering managementWork in processEngineeringPsychologyHuman–computer interactionOperations managementMechanical engineering

Abstract

fetched live from OpenAlex

Abstract – Engineering design is a core aspect of engineering education. Students might not appreciate the importance of engineering design early on, especially in the first term of their academic study. In this paper, we propose an approach for motivating students to think early about engineering design, namely at the start of their first academic term. The approach entails organizing an immersive design boot camp –“Design Days” – that replaces lectures for the first two days of the term. During the two days, students are divided into randomly assigned teams, and provided specifications to work on a design challenge. As part of the challenge, students are incentivized to fully understand the problem before attempting to solve it, instructed to follow a design process and apply iterative design, and asked to document their design and its rationale. The proposed method was successfully applied in Fall 2016. The approach will be applied again in Fall 2017 with minor modifications based on student feedback.

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: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.732
Threshold uncertainty score0.854

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
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.010
GPT teacher head0.201
Teacher spread0.191 · 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