Aligning expectations - Revision history

WikiSysop: /* The project work */

2026-05-12T08:43:17Z

The project work

← Older revision		Revision as of 10:43, 12 May 2026
Line 134:		Line 134:
	=== The project work ===		=== The project work ===
	In the project all aids are allowed, like books, powerpoints, google, teachers, or knowledge sources. Being overly dependent on AI for your solution is not accepted. Make sure you understand what you are told/read. Uncritical copy/paste is not going to help you or the project. Make references when relevant.<br>		In the project all aids are allowed, like books, powerpoints, google, teachers, or knowledge sources. Being overly dependent on AI for your solution is not accepted. Make sure you understand what you are told/read. Uncritical copy/paste is not going to help you or the project. Make references when relevant.<br>
	"'''All aids'''" does not cover what normally constitutes cheating, like copying other students work or copying from solutions found on the internet or using libraries that solves the ~~entire~~ problem for you.		"'''All aids'''" does not cover what normally constitutes cheating, like copying other students work or copying from solutions found on the internet or using libraries that solves substantial parts of the problem for you.

	The teacher will grade the project work. It consists of 3 parts. The report, the code and the peer evaluation.<br>		The teacher will grade the project work. It consists of 3 parts. The report, the code and the peer evaluation.<br>

WikiSysop: /* How to evaluate the project */

2026-05-12T08:42:09Z

How to evaluate the project

← Older revision		Revision as of 10:42, 12 May 2026
Line 118:		Line 118:
	=== How to evaluate the project ===		=== How to evaluate the project ===
	The projects consists of two very different parts: The report and the program/code. They must be evaluated in different ways, but both evaluations must result in some written text.<br>		The projects consists of two very different parts: The report and the program/code. They must be evaluated in different ways, but both evaluations must result in some written text.<br>
	Here is a [https://teaching.healthtech.dtu.dk/material/~~22113~~/projectevaltemplate.docx template evaluation document], which you can use if you wish.		Here is a [https://teaching.healthtech.dtu.dk/material/22118/projectevaltemplate.docx template evaluation document], which you can use if you wish.
	==== The report ====		==== The report ====
	The report should be evaluated on form and content. It should be understood that the report must be well structured and argued, so somebody not familiar with the subject can understand it.<br>		The report should be evaluated on form and content. It should be understood that the report must be well structured and argued, so somebody not familiar with the subject can understand it.<br>

WikiSysop: /* Content of the project */

2026-05-11T15:36:54Z

Content of the project

← Older revision		Revision as of 17:36, 11 May 2026
Line 65:		Line 65:
	* The program code.		* The program code.
	* Any data files of relevance '''not''' supplied through the course.		* Any data files of relevance '''not''' supplied through the course.
	* A signed version of this [https://teaching.healthtech.dtu.dk/material/~~22113~~/~~ProjectStatement22113~~.pdf statement]. <div style="color:red;display:inline;">DO NOT FORGET</div> It is unfortunate when students fail because they forget a mandatory element.		* A signed version of this [https://teaching.healthtech.dtu.dk/material/22118/ProjectStatement22118.pdf statement]. <div style="color:red;display:inline;">DO NOT FORGET</div> It is unfortunate when students fail because they forget a mandatory element.
	* The teacher must have access to the project repo. Make sure to invite ''peterwadsackett'' or attach a zipped repo when handing in.		* The teacher must have access to the project repo. Make sure to invite ''peterwadsackett'' or attach a zipped repo when handing in.

WikiSysop: /* Content of the project */

2026-02-27T16:13:38Z

Content of the project

← Older revision		Revision as of 18:13, 27 February 2026
Line 66:		Line 66:
	* Any data files of relevance '''not''' supplied through the course.		* Any data files of relevance '''not''' supplied through the course.
	* A signed version of this [https://teaching.healthtech.dtu.dk/material/22113/ProjectStatement22113.pdf statement]. <div style="color:red;display:inline;">DO NOT FORGET</div> It is unfortunate when students fail because they forget a mandatory element.		* A signed version of this [https://teaching.healthtech.dtu.dk/material/22113/ProjectStatement22113.pdf statement]. <div style="color:red;display:inline;">DO NOT FORGET</div> It is unfortunate when students fail because they forget a mandatory element.
			* The teacher must have access to the project repo. Make sure to invite ''peterwadsackett'' or attach a zipped repo when handing in.

	==== The report itself ====		==== The report itself ====

WikiSysop: /* Projects, general information */

2026-02-27T16:08:59Z

Projects, general information

← Older revision		Revision as of 18:08, 27 February 2026
Line 45:		Line 45:
	* Each group will choose a project from the [[Project list]] in the last part of the course. If a group has an idea for a different project, this must be discussed with the teacher to see if it is feasible. Such a "home made" project must be of sufficient complexity, but not too complex either, and have clear goals, so it can be measured if it was failed or not.		* Each group will choose a project from the [[Project list]] in the last part of the course. If a group has an idea for a different project, this must be discussed with the teacher to see if it is feasible. Such a "home made" project must be of sufficient complexity, but not too complex either, and have clear goals, so it can be measured if it was failed or not.
	* A project is estimated to be doable in 50 hours of work - people often use more time.		* A project is estimated to be doable in 50 hours of work - people often use more time.
			* The group must work together using git and GitHub when developing the program. If the report is written in LateX, or other pure text-based format, git could also be used here.
	* The project work consists of two phases; 1) Doing a project - making code and writing report. 2) Individual (not in the group) peer evaluation of another groups project. Thus every project is peer evaluated twice. Both phases are mandatory.		* The project work consists of two phases; 1) Doing a project - making code and writing report. 2) Individual (not in the group) peer evaluation of another groups project. Thus every project is peer evaluated twice. Both phases are mandatory.
	* The teacher will evaluate all projects and peer evaluations. Understand that YOUR evaluation of another groups project is part of YOUR project work, and as such it will be part of YOUR grade.		* The teacher will evaluate all projects and peer evaluations. Understand that YOUR evaluation of another groups project is part of YOUR project work, and as such it will be part of YOUR grade.

WikiSysop: /* Failing the project */

2025-10-17T11:43:04Z

Failing the project

← Older revision		Revision as of 13:43, 17 October 2025
Line 210:		Line 210:
	There are lots of mistakes a student can do; insufficient knowledge of python (syntax and functions), bad performance, repetitive code, missing variables, wrongly iterating loops, missing the right position of sequences etc., but they are not disastrous on the individual level - although they reflect your skill. The problem is when many mistakes/omissions come together and form a mix of the 4 challenges.		There are lots of mistakes a student can do; insufficient knowledge of python (syntax and functions), bad performance, repetitive code, missing variables, wrongly iterating loops, missing the right position of sequences etc., but they are not disastrous on the individual level - although they reflect your skill. The problem is when many mistakes/omissions come together and form a mix of the 4 challenges.

	How to improve: Practice, practice, and then some practice. You can not read it in a book or powerpoint~~, or see the videos again~~. That helps in knowing the syntax and functions of python, but that is not the issue. The issue is training your brain in the analyzing, formulating and executing phases of coherent programming.		How to improve: Practice, practice, and then some practice. You can not read it in a book or powerpoint. That helps in knowing the syntax and functions of python, but that is not the issue. The issue is training your brain in the analyzing, formulating and executing phases of coherent programming.

WikiSysop: /* Failing the course */

2025-10-17T11:41:53Z

Failing the course

← Older revision		Revision as of 13:41, 17 October 2025
Line 187:		Line 187:

	== Failing the course ==		== Failing the course ==
	The ~~course has two parts, which~~ must ~~both be passed~~ in ~~order~~ to ~~pass~~ the course~~: Project and exam~~.<br>		The exercises are mandatory. You must hand-in minimum 10 of the 12. Likewise you must peer-evaluate 10 out of 12 times. You can't peer-evaluate if you do not hand in. Failing to achieve this will make you fail the course - no matter the state of your project.<br>
	~~There are also the weekly~~ exercises ~~and peer evaluations, which are mandatory to hand in for you to be allowed to take the exam.~~		The exercises do not count in passing the course, but consistently doing poorly in exercises is not going to aid the project.
	~~They~~ do not count in passing the course, but consistently doing poorly in exercises is not going to aid
	the project ~~or the exam~~.		=== Failing the project ===
	=== Failing the ~~exam~~ ===		The reasons for failing the project are usually:
	~~This is~~ the ~~most frequent way~~ of ~~failing~~ the ~~course~~. ~~Said~~ in ~~simple words,~~ the ~~exam tests~~ your ~~ability - when faced with~~ a ~~problem~~ - to ~~produce meaningful code~~ that ~~solves the problem~~. As can be ~~seen~~ by the ~~text above, it is not strictly required that~~ the ~~code works. That is just an easy way to measure ability. What '''is''' required, is that~~ the ~~code is meaningful given the problem. Half done, or explaining what you intend is not sufficient~~.		* more than one severe, game changing mistake has been made in the code.
			* severe misunderstandings about the content/purpose of the project.
			* too low quality in the report.
			* too low quality in the code.
			* insufficient contribution in either code or report.
			The first two could somewhat easily be avoided by consulting the teacher.<br>
			For the last reasons... you need to up your game; Take the time to write a decent report - there are resources available on how to do that.<br>
			Insufficient contribution often has an underlying course in insufficient coding skills.<br>
			The code can/must be improved by learning more during the course - study the exercises and the solutions.

	The 4 challenges for failing students are:		The 4 challenges for failing students are:
Line 200:		Line 208:
	* difficulty in making the code coherent - having the grand overview of the method/code.		* difficulty in making the code coherent - having the grand overview of the method/code.

	There are lots of mistakes a student can do ~~at an exam~~; insufficient knowledge of python (syntax and functions), bad performance, repetitive code, missing variables, wrongly iterating loops, missing the right position of sequences etc., but they are not disastrous on the individual level - although they reflect your skill. The problem is when many mistakes/omissions come together and form a mix of the 4 challenges.		There are lots of mistakes a student can do; insufficient knowledge of python (syntax and functions), bad performance, repetitive code, missing variables, wrongly iterating loops, missing the right position of sequences etc., but they are not disastrous on the individual level - although they reflect your skill. The problem is when many mistakes/omissions come together and form a mix of the 4 challenges.

	~~If you have not improved on these 4 points when you are taking an re-exam, the result is quite predictable.<br>~~
	How to improve: Practice, practice, and then some practice. You can not read it in a book or powerpoint, or see the videos again. That helps in knowing the syntax and functions of python, but that is not the issue. The issue is training your brain in the analyzing, formulating and executing phases of coherent programming.		How to improve: Practice, practice, and then some practice. You can not read it in a book or powerpoint, or see the videos again. That helps in knowing the syntax and functions of python, but that is not the issue. The issue is training your brain in the analyzing, formulating and executing phases of coherent programming.

	~~=== Failing the project ===~~
	~~The reasons for failing the project are usually:~~
	* more than one severe, game changing mistake has been made in the code.
	* severe misunderstandings about the content/purpose of the project.
	* too low quality in code and report.
	The first two could somewhat easily be avoided by consulting the teacher. The last... you need to up your game; Take the time to write a decent report - there are resources available on how to do that. The code can/must be improved by learning more during the course - study the exercises and the solutions. A lot of the same reasons for failing the exam also apply here.

WikiSysop: /* Projects, general information */

2025-10-17T11:22:20Z

Projects, general information

← Older revision		Revision as of 13:22, 17 October 2025
Line 42:		Line 42:

	=== Projects, general information ===		=== Projects, general information ===
	* A project is done with two students in each group, no exceptions unless there is an odd number of students, in which case a one (wo)man group is formed. The teacher will form the groups, but will accept already formed groups, if informed in time, see the google sheet found via the ~~announcement~~ at DTU Learn.		* A project is done with two students in each group, no exceptions unless there is an odd number of students, in which case a one (wo)man group is formed. The teacher will form the groups, but will accept already formed groups, if informed in time, see the google sheet found via the Course Overview in Content at DTU Learn.
	* Each group will choose a project from the [[Project list]] in the last part of the course. If a group has an idea for a different project, this must be discussed with the teacher to see if it is feasible. Such a "home made" project must be of sufficient complexity, but not too complex either, and have clear goals, so it can be measured if it was failed or not.		* Each group will choose a project from the [[Project list]] in the last part of the course. If a group has an idea for a different project, this must be discussed with the teacher to see if it is feasible. Such a "home made" project must be of sufficient complexity, but not too complex either, and have clear goals, so it can be measured if it was failed or not.
	* A project is estimated to be doable in 50 hours of work - people often use more time.		* A project is estimated to be doable in 50 hours of work - people often use more time.

WikiSysop: /* Exercises */

2025-10-17T11:21:21Z

Exercises

← Older revision		Revision as of 13:21, 17 October 2025
Line 30:		Line 30:
	* Peer evaluation of exercises are done in the following week on [https://learn.dtu.dk DTU Learn] to be handed in Friday. The evaluations are mandatory.		* Peer evaluation of exercises are done in the following week on [https://learn.dtu.dk DTU Learn] to be handed in Friday. The evaluations are mandatory.
	* At least 10 of 12 evaluations must be handed in on DTU Learn for you to be allowed to take the exam. You can only evaluate if you have handed in exercises.		* At least 10 of 12 evaluations must be handed in on DTU Learn for you to be allowed to take the exam. You can only evaluate if you have handed in exercises.
	* Word or pdf documents are NOT accepted as hand-in - use only simple '''.txt''' or '''.py''' files. Sometimes like with unit test, an entire folder structure should be zipped and uploaded.<br>		* Word or pdf documents are NOT accepted as hand-in - use only simple '''.txt''' or '''.py''' files. Sometimes, like with unit test, an entire folder structure should be zipped and uploaded.<br>
	* Solutions to each week's exercises are published before the next week's lesson on DTU Learn (under Discussions). Can be used as reference for peer evaluation.		* Solutions to each week's exercises are published before the next week's lesson on DTU Learn (under Discussions). Can be used as reference for peer evaluation.
	* Exercises which are handed in after the solutions are published, are voided and will not count, no matter the reason for being late.		* Exercises which are handed in after the solutions are published, are voided and will not count, no matter the reason for being late.

WikiSysop: /* Exercises */

2025-10-17T11:21:02Z

Exercises

← Older revision		Revision as of 13:21, 17 October 2025
Line 30:		Line 30:
	* Peer evaluation of exercises are done in the following week on [https://learn.dtu.dk DTU Learn] to be handed in Friday. The evaluations are mandatory.		* Peer evaluation of exercises are done in the following week on [https://learn.dtu.dk DTU Learn] to be handed in Friday. The evaluations are mandatory.
	* At least 10 of 12 evaluations must be handed in on DTU Learn for you to be allowed to take the exam. You can only evaluate if you have handed in exercises.		* At least 10 of 12 evaluations must be handed in on DTU Learn for you to be allowed to take the exam. You can only evaluate if you have handed in exercises.
	* Word or pdf documents are NOT accepted as hand-in - use only simple '''.txt''' or '''.py''' files.<br>		* Word or pdf documents are NOT accepted as hand-in - use only simple '''.txt''' or '''.py''' files. Sometimes like with unit test, an entire folder structure should be zipped and uploaded.<br>
	* Solutions to each week's exercises are published before the next week's lesson on DTU Learn (under Discussions). Can be used as reference for peer evaluation.		* Solutions to each week's exercises are published before the next week's lesson on DTU Learn (under Discussions). Can be used as reference for peer evaluation.
	* Exercises which are handed in after the solutions are published, are voided and will not count, no matter the reason for being late.		* Exercises which are handed in after the solutions are published, are voided and will not count, no matter the reason for being late.