Exercise Rework

[dominik-probst]

For the Summer semester of 2024, we are planning an overhaul of our exercise modules. The objective is to create two new types of exercises from the existing ones:

1. In-Person Exercises: The in-person exercises are (likely) going to be designed in such a way that they do not require any prior preparation from the students (aside from reviewing the lecture material), as the tasks will be progressively worked on together. There will be two categories of in-person exercises, alternating more or less:

• Data Science Experiments: Leveraging our existing database, we will use Python libraries in a hands-on setting to analyze the data and unearth knowledge. This practical approach aims to complement the lecture material and offer a glimpse into the life of a data scientist.
• Theoretical Tasks on Methods: We have already dealt with theoretical tasks related to methods like A Priori and FP-Growth in the last semester, similar to what one might find in an exam. These will continue to be part of the in-person exercises and will be expanded to include new tasks (for instance, on classification).

2. Implementation Exercises: The implementation exercises will be done as pure homework by the students. These will largely reflect the previous exercise sheets where methods were implemented step by step by hand. They will be enhanced to allow for automatic "correction" using Otter-Grader. Students who invest the effort to implement the tasks on their own and achieve a certain percentage of the points will gain access to a small bonus exam.

[dominik-probst]

The first part of the new exercises was completed on time for the start of the semester and has been merged into main (#80).

There has been a minor change regarding the implementation exercises - now called submissions: Contrary to the original plan, these will not be assessed using Otter-Grader, but through GitHub Classrooms. This offers the advantage that students receive immediate feedback on their submissions. Furthermore, it obviates the need for us to run the submissions locally, as they are executed and evaluated directly on GitHub (via GitHub Action).

[dominik-probst]

All Done (Final commit: 1c151849c6cd5b4b8edb47132ecdb57e922a8bde)