Aligning expectations: Difference between revisions
No edit summary |
|||
(5 intermediate revisions by the same user not shown) | |||
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. | ||
The necessary [https://teaching.healthtech.dtu.dk/22113/index.php/Course_preparation tools preparation] can be found here. | |||
== About exercises == | == About exercises == | ||
Line 9: | 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, 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. | |||
== 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 | === 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. | ||
=== Progression of a typical course | === Progression of a typical course day 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. | ||
* 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. | ||
Latest revision as of 11:01, 19 November 2024
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 this unix tutorial and/or this lesson in Unix.
Having a good skill in Python programming is mandatory. A course like 22113/22163 should enable you to participate.
The necessary tools preparation can be found here.
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. 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.
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, 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.
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.
Events
- 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 day in class
- We meet in class at Thursday 13:00.
- I lecture over the powerpoint and your questions.
- We (you, actually) do exercises.
Progression of a typical course day online
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
- Go to Discord (link found at DTU Learn) for the class Thursday 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.