Aligning expectations - Revision history

WikiSysop: /* About the exam */

2024-11-19T10:01:12Z

About the exam

← Older revision		Revision as of 12:01, 19 November 2024
Line 10:		Line 10:

	== About the exam ==		== About the exam ==
	The course is graded as pass/fail based on the exam, but participating in the exam requires a sufficient number of qualified hand-ins. The exam itself is a multiple-choice exam lasting 2 hours. There are 72 questions. Answering 60% correct will make you pass. There are no negative points - answering wrong does not count down.		The course is graded as pass/fail based on the exam, but participating in the exam requires a sufficient number of qualified hand-ins, see previous paragraph. The exam itself is a multiple-choice exam lasting 2 hours. There are 72 questions. Answering 60% correct will make you pass. There are no negative points - answering wrong does not count down.

	Being familiar with the curriculum, i.e. the powerpoints, should enable you to to pass. Re-exams are 4 hours written examinations, where you have to write the code that will solve 2-3 problems based on the curriculum. No open internet at any exam.		Being familiar with the curriculum, i.e. the powerpoints, should enable you to to pass. Re-exams are 4 hours written examinations, where you have to write the code that will solve 2-3 problems based on the curriculum. No open internet at any exam.

WikiSysop: /* About the exam */

2024-11-19T09:59:22Z

About the exam

← Older revision		Revision as of 11:59, 19 November 2024
Line 10:		Line 10:

	== About the exam ==		== About the exam ==
	The course is graded as pass/fail based on the exam. The exam itself is a multiple-choice exam lasting 2 hours. Being familiar with the curriculum, i.e. the powerpoints, should enable you to to pass. Re-exams are 4 hours written examinations, where you have to write the code that will solve 2-3 problems based on the curriculum. No open internet at any exam.		The course is graded as pass/fail based on the exam, but participating in the exam requires a sufficient number of qualified hand-ins. The exam itself is a multiple-choice exam lasting 2 hours. There are 72 questions. Answering 60% correct will make you pass. There are no negative points - answering wrong does not count down.

			Being familiar with the curriculum, i.e. the powerpoints, should enable you to to pass. Re-exams are 4 hours written examinations, where you have to write the code that will solve 2-3 problems based on the curriculum. No open internet at any exam.

	== Weekly schedule ==		== Weekly schedule ==

WikiSysop: /* Prerequisite knowledge */

2024-09-02T17:36:41Z

Prerequisite knowledge

← Older revision		Revision as of 19:36, 2 September 2024
Line 3:		Line 3:
	Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and/or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix].<br>		Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and/or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix].<br>
	Having a good skill in Python programming is mandatory. A course like [http://teaching.healthtech.dtu.dk/22113 22113/22163] should enable you to participate.		Having a good skill in Python programming is mandatory. A course like [http://teaching.healthtech.dtu.dk/22113 22113/22163] should enable you to participate.
			The necessary [https://teaching.healthtech.dtu.dk/22113/index.php/Course_preparation tools preparation] can be found here.

	== About exercises ==		== About exercises ==

WikiSysop: /* Prerequisite knowledge */

2024-08-20T10:05:12Z

Prerequisite knowledge

← Older revision		Revision as of 12:05, 20 August 2024
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	== Prerequisite knowledge ==		== Prerequisite knowledge ==
	Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix].<br>		Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and/or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix].<br>
	Having a good skill in Python programming is mandatory. A course like [http://teaching.healthtech.dtu.dk/22113 22113/22163] should enable you to participate.		Having a good skill in Python programming is mandatory. A course like [http://teaching.healthtech.dtu.dk/22113 22113/22163] should enable you to participate.

WikiSysop: /* Weekly schedule */

2024-03-06T11:36:48Z

Weekly schedule

← Older revision		Revision as of 13:36, 6 March 2024
Line 12:		Line 12:

	== Weekly schedule ==		== Weekly schedule ==
	Prepare for a new lecture, see the [[programme]]. There will be powerpoints, video lectures for later reference, and sometimes extra material. There are no TA's.		Prepare for a new lecture, see the [[programme]]. There will be powerpoints, video lectures for later reference, and sometimes extra material. There are no TA's.<br>
			'''Events'''<br>
			* Thursday: Solutions to previous weeks exercises will have been published at DTU Learn, Discussions forum.
			* Sunday (deadline; midnight) you do the peer evaluation of previous weeks exercises.
			* Wednesday (deadline; midnight) you upload the exercises for this week.

	=== Progression of a typical course ~~week~~ in class ===		=== Progression of a typical course day in class ===
	* We meet in class at Thursday 13:00.		* We meet in class at Thursday 13:00.
	* I lecture over the powerpoint and your questions.		* I lecture over the powerpoint and your questions.
	* We (you, actually) do exercises.		* We (you, actually) do exercises.
	* Thursday: Solutions to previous weeks exercises will have been published at DTU Learn, Discussions forum.
	* Sunday (deadline; midnight) you do the peer evaluation of previous weeks exercises.
	* Wednesday (deadline; midnight) you upload the exercises for this week.

	=== Progression of a typical course ~~week~~ online ===		=== Progression of a typical course day online ===
	Online teaching will only happen in case of force majeure. Do NOT expect this.		Online teaching will only happen in case of force majeure. Do NOT expect this.
	* Watch lecture videos '''before''' the module starts Thursday at 13.00		* Watch lecture videos '''before''' the module starts Thursday at 13.00
Line 28:		Line 29:
	* We start out with questions and preparation for the week, followed by walkthrough of last weeks exercises.		* We start out with questions and preparation for the week, followed by walkthrough of last weeks exercises.
	* The remaining time is used for doing exercises and asking questions/getting help.		* The remaining time is used for doing exercises and asking questions/getting help.
	* Thursday: Solutions to previous weeks exercises will have been published at DTU Learn, Discussions forum.
	* Sunday (deadline; midnight) you do the peer evaluation of previous weeks exercises.
	* Wednesday (deadline; midnight) you upload the exercises for this week.

WikiSysop: /* Progression of a typical course week online */

2024-03-06T11:34:51Z

Progression of a typical course week online

← Older revision		Revision as of 13:34, 6 March 2024
Line 23:		Line 23:

	=== Progression of a typical course week online ===		=== Progression of a typical course week online ===
	Online teaching will only happen in case of force majeure.		Online teaching will only happen in case of force majeure. Do NOT expect this.
	* Watch lecture videos '''before''' the module starts Thursday at 13.00		* Watch lecture videos '''before''' the module starts Thursday at 13.00
	* Go to Discord (link found at DTU Learn) for the class Thursday at 13:00.		* Go to Discord (link found at DTU Learn) for the class Thursday at 13:00.

WikiSysop at 11:33, 6 March 2024

2024-03-06T11:33:59Z

← Older revision		Revision as of 13:33, 6 March 2024
Line 1:		Line 1:
			__NOTOC__
	== Prerequisite knowledge ==		== Prerequisite knowledge ==
	Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix].<br>		Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix].<br>
Line 4:		Line 5:

	== About exercises ==		== About exercises ==
	There will be weekly exercises, which have to be handed in after 7 days on DTU Learn and peer evaluated the week after~~. A link to DTU Learn can also be found on DTU Inside for the course~~. You can only peer evaluate if you have handed in, and at you must have at least 11 out of 13 '''acceptable''' (by the teacher) hand-ins and evaluations to participate in the exam. The ~~course~~ is ~~graded as pass/fail based on~~ the ~~exam~~.		There will be weekly exercises, which have to be handed in after 7 days on DTU Learn and peer evaluated the week after. You can only peer evaluate if you have handed in, and at you must have at least 11 out of 13 '''acceptable''' (by the teacher) hand-ins and evaluations to participate in the exam.
			The hand-in must be runnable code, when the exercise is making programs. Sometimes you are asked to evaluate different methods, then text or pdf can be added to the hand-in.

	The ~~hand~~-~~in must be runnable code~~, ~~when~~ the ~~exercise is making programs~~. ~~Sometimes you~~ are ~~asked to evaluate different methods~~, ~~then text or pdf can be added~~ to the ~~hand~~-in.		== About the exam ==
			The course is graded as pass/fail based on the exam. The exam itself is a multiple-choice exam lasting 2 hours. Being familiar with the curriculum, i.e. the powerpoints, should enable you to to pass. Re-exams are 4 hours written examinations, where you have to write the code that will solve 2-3 problems based on the curriculum. No open internet at any exam.

			== Weekly schedule ==
			Prepare for a new lecture, see the [[programme]]. There will be powerpoints, video lectures for later reference, and sometimes extra material. There are no TA's.

	== Progression of a typical course week in class ==		=== Progression of a typical course week in class ===
	~~We will have normal class based teaching. Online only in case of force majeure.~~		* We meet in class at Thursday 13:00.
	~~There are videos for each lesson, which can be used as later reference.<br>~~
	~~'''Class based'''<br>~~
	* We meet in class at ~~Monday~~ 13:00.
	* I lecture over the powerpoint and your questions.		* I lecture over the powerpoint and your questions.
	* We (you, actually) do exercises.		* We (you, actually) do exercises.
	~~'''Online'''<br>~~		* Thursday: Solutions to previous weeks exercises will have been published at DTU Learn, Discussions forum.
	* ~~Watch lecture videos '''before''' the module starts Monday at 13.00~~		* Sunday (deadline; midnight) you do the peer evaluation of previous weeks exercises.
	* Go to Discord (link found at DTU Learn) for the class Monday at 13:00.		* Wednesday (deadline; midnight) you upload the exercises for this week.
	* We start out with questions and preparation for the week, followed by walkthrough of last weeks exercises.
	* The remaining time is used for doing exercises and asking questions/getting help. There will be no TA's.
	~~'''Common for both'''<br>~~
	* Monday: Solutions to previous weeks exercises will have been published at DTU Learn, Discussions forum.
	* ~~Friday~~ (deadline; midnight) you do the peer evaluation of previous weeks exercises.
	* ~~Sunday~~ (deadline; midnight) you upload the exercises for this week.

	== Progression of a typical course week online ==		=== Progression of a typical course week online ===
	Online teaching will only happen in case of force majeure.		Online teaching will only happen in case of force majeure.
	~~There are videos for each lesson, which can be used as later reference.<br>~~		* Watch lecture videos '''before''' the module starts Thursday at 13.00
	~~'''Class based'''<br>~~		* Go to Discord (link found at DTU Learn) for the class Thursday at 13:00.
	* We meet in class at Monday 13:00.
	* I lecture over the powerpoint and your questions.
	* We (you, actually) do exercises.
	~~'''Online'''<br>~~
	* Watch lecture videos '''before''' the module starts ~~Monday~~ at 13.00
	* Go to Discord (link found at DTU Learn) for the class ~~Monday~~ at 13:00.
	* We start out with questions and preparation for the week, followed by walkthrough of last weeks exercises.		* We start out with questions and preparation for the week, followed by walkthrough of last weeks exercises.
	* The remaining time is used for doing exercises and asking questions/getting help~~. There will be no TA's~~.		* The remaining time is used for doing exercises and asking questions/getting help.
	~~'''Common for both'''<br>~~		* Thursday: Solutions to previous weeks exercises will have been published at DTU Learn, Discussions forum.
	* ~~Monday~~: Solutions to previous weeks exercises will have been published at DTU Learn, Discussions forum.		* Sunday (deadline; midnight) you do the peer evaluation of previous weeks exercises.
	* ~~Friday~~ (deadline; midnight) you do the peer evaluation of previous weeks exercises.		* Wednesday (deadline; midnight) you upload the exercises for this week.
	* ~~Sunday~~ (deadline; midnight) you upload the exercises for this week.

WikiSysop: /* Progression of a typical course week */

2024-03-06T11:19:34Z

Progression of a typical course week

@@ Line 8: / Line 8: @@
 The hand-in must be runnable code, when the exercise is making programs. Sometimes you are asked to evaluate different methods, then text or pdf can be added to the hand-in.
-== Progression of a typical course week ==
+== Progression of a typical course week in class ==
 We will have normal class based teaching. Online only in case of force majeure.
 There are videos for each lesson, which can be used as later reference.<br>
 '''Class based'''<br>

WikiSysop: Created page with "== Prerequisite knowledge == Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix].
Having a good skill in Python progr..."

2024-03-06T11:15:51Z

Created page with "== Prerequisite knowledge == Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix]. Having a good skill in Python progr..."

New page

== Prerequisite knowledge ==
Being comfortable with using the Unix shell and being able to navigate the file system is '''required'''. No help will be forthcoming on the subject on a basic level, only advanced Unix tools and concepts will be discussed and that only as a side note. Consult [http://teaching.healthtech.dtu.dk/unix this unix tutorial] and or this [https://teaching.healthtech.dtu.dk/22113/index.php/Unix lesson in Unix]. 
Having a good skill in Python programming is mandatory. A course like [http://teaching.healthtech.dtu.dk/22113 22113/22163] should enable you to participate.

== About exercises ==
There will be weekly exercises, which have to be handed in after 7 days on DTU Learn and peer evaluated the week after. A link to DTU Learn can also be found on DTU Inside for the course. You can only peer evaluate if you have handed in, and at you must have at least 11 out of 13 '''acceptable''' (by the teacher) hand-ins and evaluations to participate in the exam. The course is graded as pass/fail based on the exam.

The hand-in must be runnable code, when the exercise is making programs. Sometimes you are asked to evaluate different methods, then text or pdf can be added to the hand-in.

== Progression of a typical course week ==
We will have normal class based teaching. Online only in case of force majeure.
There are videos for each lesson, which can be used as later reference. 
'''Class based''' 
* We meet in class at Monday 13:00.
* I lecture over the powerpoint and your questions.
* We (you, actually) do exercises.
'''Online''' 
* Watch lecture videos '''before''' the module starts Monday at 13.00
* Go to Discord (link found at DTU Learn) for the class Monday at 13:00.
* We start out with questions and preparation for the week, followed by walkthrough of last weeks exercises.
* The remaining time is used for doing exercises and asking questions/getting help. There will be no TA's.
'''Common for both''' 
* Monday: Solutions to previous weeks exercises will have been published at DTU Learn, Discussions forum.
* Friday (deadline; midnight) you do the peer evaluation of previous weeks exercises.
* Sunday (deadline; midnight) you upload the exercises for this week.