Advising students in technical projects - recognizing problem scenarios
Bibliographic record
Abstract
In this paper, we consider the advisor’s role during the technical work and the thesis preparation for a student in the final phase of a course of study in an engineering education. We initially claim that there is a marked difference between the learning that takes place in regular course work and the learning ensuing from project work. Concrete differences include that • unlike the a-priori fixed curriculum of regular courses, an important aspect of a project is to define and scientifically formulate the problem itself, in which the student is to be engaged. • projects are carried out individually or in very small groups. For an interesting project, the precise outcome cannot be known in advance. • The flexible and individual nature of each project requires that time must be carefully divided and managed between defining the problem, seeking information, implementing solutions and presenting results. While students work hard during projects and advisors will do their best to support the students’ activities, it is not uncommon that a student fails to meet either his or her own expectations and/or those of the advisor. Occasionally, this is true also of students who perform brilliantly in regular courses. The goal of this paper is to relate the authors’ experiences and investigations into the project advisory process and to provide recommendations for other engineering educators. After an initial discussion of a typical engineering project advisory process, we review a number of representative projects (abstracted and anonymized) and analyze conditions under which a failure to meet or match expectations is likely to arise. This leads us to a small number of scenarios, where a student is likely to under-perform. Common to these scenarios is a lack of balance between the necessary activities in an engineering project. As our main contribution, we investigate and categorize these imbalances leading to the aforementioned scenarios. Finally, we distill suggestions for best project advisory practices.
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.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".