• There will be no group work in the first tutorial.
  • Over the next few weeks, you will be divided into groups by instructors and will work on smaller exercises during tutorial sessions.
  • Later, you will form teams on your own and work on a project (both during and outside of tutorial sessions).
  • This document covers group work in the first part of the semester; when working on the group project, you will have freedom to organize your work within the team according to your own judgment.

Objectives and grading

Objectives

  • Practice teamwork
  • Get to know your classmates better
  • Exchange experiences with classmates, learn new approaches from them, clarify misunderstandings, or formulate questions unclear to the whole group

Involve all group members

  • All group members should understand the submitted solution and be able to solve similar exercises independently.
  • It is better to solve a smaller part of the assignment so that all group members understand it than to solve a larger part where one person does the work and nobody learns anything.

Grading

  • We will evaluate both the submitted solution and how well you collaborated.
  • Usually all group members receive the same points, but if necessary, we can add or subtract points for individual members.

Roles in a group

During group assignments, you will have assigned specific roles within your team:

  • One team member has the role of driver, following the practice of pair programming. The driver is the only one who edits the notebook and runs the code, while others advise.
  • One team member has the role of scribe. The scribe records a log of the team’s collaboration progress.
  • One team member has the role of chair. The chair oversees team cooperation, ensuring all team members participate and their questions and suggestions are considered by others.
  • All group members, including those mentioned above, participate in solving the tasks (reading assignments, discussing possible solutions, finding appropriate resources, searching for errors, explaining to other team members as needed, etc.).
  • Teams with two members have only the driver and scribe roles assigned.
  • If not all team members are present, redistribute roles according to circumstances.

Submission

At the end of the group session, the driver submits two documents to Moodle on behalf of the entire group:

  • The notebook with your solutions (ipynb format)
  • The log (pdf format)

In the log, include

  • team members and their roles
  • any special circumstances (e.g., if technical problems occurred)
  • a brief comment on the progress: any problems encountered while solving the tasks, any interesting discussions in the group
  • you may mention if there were problems with some members (they arrived late or refused to participate reasonably) or if someone was particularly supportive of the team

Tutorial class

  • The list of groups and assigned roles will be published before the class via Moodle, please look it up.
  • Each group will occupy a block of computers next to each other in room I-H6. The driver sits in the middle, but others also turn on their computers.
  • Tasks and a log template can be found in Moodle.
  • The Jupyter notebook with the solved task is edited by the driver via Google Colab and can be shared with other group members.
  • The log is edited by the scribe and shared with other group members.
  • Individual group members can thus have both documents open on their computer, but only the driver modifies and runs the notebook.
  • Suggested code snippets and similar content can be shared in a special section of the log (scratch), where everyone writes. The rest of the log is handled by the scribe.
  • At the end of the session, the driver downloads the notebook (.ipynb) and log (.pdf) and submits them in Moodle. Before submission, verify that you have the correct group members in Moodle and resolve any discrepancies with the instructor before submitting.

Absence

  • If you cannot attend the tutorial class with a group task, contact B. Zigo, preferably at least 24 hours in advance so that we can take it into account when forming the groups.
  • If you have serious reasons for missing the class, we may allow you to make up this activity in another way.