Difference between revisions of "BCH441 Oral Test instructions"
m (→Instructions) |
m (→Instructions) |
||
| Line 19: | Line 19: | ||
Approximately (but still to be refined) ...: | Approximately (but still to be refined) ...: | ||
| − | + | ===== Scheduling ===== | |
| − | + | {{Smallvspace}} | |
| − | + | Oral tests will be scheduled between Monday, November 16 and Friday, November 27. , between 17:00 and 20:00. | |
| − | |||
| − | |||
| + | I will randomly assign test-slots, half an hour each, between 17:00 and 20:00 beginning about a week after the drop-date and inform students by eMail. | ||
| + | |||
| + | If you have a conflict on your scheduled test date, you are welcome to find someone to swap with; both of you must contact me by e-mail at least two days ahead of the first exam scheduled for either of you. (One e-mail with a CC will do). | ||
| + | |||
| + | {{Smallvspace}} | ||
| + | |||
| + | ===== Preparations ===== | ||
| + | {{Smallvspace}} | ||
| + | In the test, we will discuss aspects of your chosen Integrator Unit, and you will have opportunity to demonstrate your understanding of the material. This is not a memorize-and-recall type of test, so studying for it in the conventional sense will probably not be useful. To prepare: make sure you understand the concepts, the computational aspects, the R code, the results, and how to interpret the results. Questions that have led to productive discussion in the past included: whether all steps are necessary, whether there are ways to improve the workflow, whether the results match your expectations and how those expectations are justified etc. I'm looking for your ability to analyze, evaluate and synthesize. Since the test is cumulative, we may also discuss aspects of your previously submitted units and their resp. prerequisites. | ||
| + | |||
| + | The required work must have been submitted on the Student Wiki by midnight of the day before the exam. | ||
| + | |||
| + | |||
| + | {{Smallvspace}} | ||
| + | |||
| + | ===== The Test ===== | ||
| + | {{Smallvspace}} | ||
| + | You must be present alone in a room with a stable internet connection, and connect from the computer that you normally use to work on the assignments. Be prepared to be able to share your screen so we can look into some of your project files. (You may want to consider what windows you have open and what is on your desktop etc.) No other computer may be on in the room and your cell-phone must be switched off. You cannot wear headphones for the test. | ||
| + | |||
| + | Call in to the Zoom conference link you received with your scheduling eMail exactly at your scheduled time. | ||
| + | |||
| + | If you are late, but less then 15 minutes late, you will lose a proportional amount of marks, up to 50%. If you are more than 15 minutes late, I will treat this as a no-show. | ||
| + | |||
| + | Expect that you will be asked to write a few lines of code. Prepare your computer, have an R-Studio session open, and have the ABC-units project loaded and initialized. <small>(Please be advised that you may lose up to 100% of marks if we can't evaluate '''your''' code on '''your''' machine where it was written.)</small> | ||
| + | |||
| + | Recording ... | ||
| + | |||
| + | {{Smallvspace}} | ||
| + | |||
| + | ===== Marking ===== | ||
| + | {{Smallvspace}} | ||
| + | (Rubrics ...) | ||
| + | |||
| + | |||
| + | {{Smallvspace}} | ||
| + | |||
| + | ===== Things that might go wrong ===== | ||
| + | |||
| + | {{Smallvspace}} | ||
| + | |||
| + | If you did not finish your preparations in time ... (documentation policy, marks deducted) | ||
| + | |||
| + | If you miss your test you will receive zero marks. If you have a documented, acceptable reason for missing the test (according to Faculty policies), we will attempt to find a make up slot. It is unlikely that this will be possible before the last day to submit term work. In that case, the mark of zero will become part of your course grade, and you need to petition the Faculty for an alternative evaluation. | ||
| + | |||
| + | {{Smallvspace}} | ||
====Notes==== | ====Notes==== | ||
Revision as of 09:05, 3 October 2020
Oral Test instructions
Contents
Instructions
Coming soon.
Approximately (but still to be refined) ...:
Scheduling
Oral tests will be scheduled between Monday, November 16 and Friday, November 27. , between 17:00 and 20:00.
I will randomly assign test-slots, half an hour each, between 17:00 and 20:00 beginning about a week after the drop-date and inform students by eMail.
If you have a conflict on your scheduled test date, you are welcome to find someone to swap with; both of you must contact me by e-mail at least two days ahead of the first exam scheduled for either of you. (One e-mail with a CC will do).
Preparations
In the test, we will discuss aspects of your chosen Integrator Unit, and you will have opportunity to demonstrate your understanding of the material. This is not a memorize-and-recall type of test, so studying for it in the conventional sense will probably not be useful. To prepare: make sure you understand the concepts, the computational aspects, the R code, the results, and how to interpret the results. Questions that have led to productive discussion in the past included: whether all steps are necessary, whether there are ways to improve the workflow, whether the results match your expectations and how those expectations are justified etc. I'm looking for your ability to analyze, evaluate and synthesize. Since the test is cumulative, we may also discuss aspects of your previously submitted units and their resp. prerequisites.
The required work must have been submitted on the Student Wiki by midnight of the day before the exam.
The Test
You must be present alone in a room with a stable internet connection, and connect from the computer that you normally use to work on the assignments. Be prepared to be able to share your screen so we can look into some of your project files. (You may want to consider what windows you have open and what is on your desktop etc.) No other computer may be on in the room and your cell-phone must be switched off. You cannot wear headphones for the test.
Call in to the Zoom conference link you received with your scheduling eMail exactly at your scheduled time.
If you are late, but less then 15 minutes late, you will lose a proportional amount of marks, up to 50%. If you are more than 15 minutes late, I will treat this as a no-show.
Expect that you will be asked to write a few lines of code. Prepare your computer, have an R-Studio session open, and have the ABC-units project loaded and initialized. (Please be advised that you may lose up to 100% of marks if we can't evaluate your code on your machine where it was written.)
Recording ...
Marking
(Rubrics ...)
Things that might go wrong
If you did not finish your preparations in time ... (documentation policy, marks deducted)
If you miss your test you will receive zero marks. If you have a documented, acceptable reason for missing the test (according to Faculty policies), we will attempt to find a make up slot. It is unlikely that this will be possible before the last day to submit term work. In that case, the mark of zero will become part of your course grade, and you need to petition the Faculty for an alternative evaluation.
Notes
