Winter 2019 CMPUT 428/615 Lab and TA policies
TA contact information
Name: Bernard Llanos
Email: llanos@ualberta.ca
I will answer emails at least within 24 h.
All questions that may be of interest to other students should be posted to the eClass discussion forum.
(Otherwise, I will quote the relevant portions of emails on the discussion forum, and provide an answer there.)
Office hours:
For short discussions, you can usually find me in CSC 2-65,
around 9:30 - 11:30 and 2:30 - 5:30, except for Thursday mornings and Friday afternoons.
No appointment necessary, but I might be out when you drop by.
If you need to have a long discussion, if you want to be certain to reach me,
or if you need to discuss anything private or requiring traceability (e.g. marking concerns),
then contact me by email to set up an appointment.
Lab grading
- The week after each lab session, you will both submit your work on eClass,
and present it to me (i.e. give a demo —no slides or formal presentation required)
and answer some questions verbally.
I will ask you to show/explain pieces of your code, in addition to asking you to run it, to check its output.
- If you complete the lab in the same session as it is introduced,
you can present it to me then as well, after I have finished seeing demos that are due that week.
- Labs submitted late, and lab demos given late, will not be given marks,
but I will give feedback on them. Late demos include arriving at or after the end of the lab session.
If you are late, you should ensure that you understand the content of the lab,
but then focus on getting ahead on the next lab.
- If you have a reason for submitting and/or demoing a lab late,
contact the instructor and I by email to request an exemption.
- The late policy is not intended to be harsh.
Submitting an incomplete lab on time will get you most of the marks.
- Everyone must demo by the end of the second lab session of the week, but,
ideally, people will distribute themselves so that neither lab sessions is too full.
Guidelines for lab submissions
- Basic instructions are in the course calendar.
- Your submission should be your own work (i.e. no groupwork).
- All code must run in the lab environment, or must include any extra components required to run it.
- Your program must make it clear what is going on. (This is will also help you with debugging.) For example:
- For optical flow, any video output must play at a rate which gives the viewer time to look at the flow vectors.
- For graphical output wherein multiple things are being shown in one image, please add labels.
- Include documentation describing what code to run for each exercise in the lab assignment, and how to run it,
if it is not obvious.
About me
- Don't hesitate to ask me to speak louder; I tend to be too quiet.
- More generally, I (and the course) will benefit from any feedback you share with me.
- You are welcome to visit CSC 2-65 to see what research projects are underway in my supervisor's group.