Activity logs

Updates in red were inserted on 3/19/2026, and apply only to the second half of the semester.

A significant component of your grade for COMP560 will be determined by your activity log. Your activity log is a private Teams channel in which the only participants are you and the instructors. Please create your own activity log in our Team when you begin working on the project. Guidance:

• Please name your activity log channel “Your Name activity log” e.g. “John MacCormick activity log”. Make sure it is a private channel and give access to the three instructors.
• The activity log should record essentially everything you do for the project. This includes time you spend:
  • reading background materials, literature and documentation;
  • writing code, debugging, conducting experiments, producing results;
  • writing reports, papers, presentations, posters etc.;
  • attending meetings or working with other students;
  • any other activity related to the project.
• Because a significant component of your grade is determined by effort rather than achievement, you should be assiduous in logging your activity. The instructors will be able to give you favorable grade for effort only if your activity log makes it obvious that you have been spending at least 107 hours per week working on our project.
• It is suggested you post at least one message to your activity log on every day on which you spend time working on our project. Each message should be a few sentences describing your activity (aim for, say, 50 words – but more is better!).
  • Example: In some particular week you spend the following time working on COMP560: 3 hours on Monday, one hour on Wednesday to attend our weekly evening meeting, 4 hours on Thursday, and 4 hours on Saturday. Then you should post four separate activity log messages describing your activities on Monday, Wednesday, Thursday, and Saturday.
• If you post fewer than two messages per week, you will likely receive a failing grade unless there is very strong alternative evidence of your effort on the project (e.g. substantial commits to our code repository, or concrete achievements such as research reports).