KDD - Knowledge Discovery in Databases

Downloads

Lecture

1. Prologue - Slides
2. Introduction - Slides
3. Data - Slides
4. Preprocessing - Slides
5. OLAP - Slides
6. Mining Frequent Patterns - Slides
7. Classification - Slides
8. Cluster Analysis - Slides
9. Outlier Analysis - Slides

Exercise

1. Introduction to Python & Pandas - Exercise Sheet × Additional Files - Solution × Additional Files
2. Data Analysis and Preprocessing - Exercise Sheet × Additional Files - Solution × Additional Files
3. Frequent Patterns - Exercise Sheet × Additional Files - Solution × Additional Files
4. Classification - Exercise Sheet × Additional Files - Solution × Additional Files
5. Clustering - Exercise Sheet × Additional Files - Solution × Additional Files

Submission

1. Frequent Patterns - Task Description
2. Classification - Task Description
3. Clustering - Task Description

Summer Semester 2026

• Semester duration: 13 April 2026 – 17 July 2026
• Public holidays:
  • Friday, 1 May 2026
  • Thursday, 14 May 2026
  • Monday, 25 May 2026
  • Thursday, 4 June 2026
• FAU specific holidays (no lectures and exercises):
  • Tuesday, 26 May 2026
  • Friday, 5 June 2026

Setup for Building Lecture Slides Locally

To build these lecture slides locally on your machine you’ll need an up-to-date version of LaTeX such as texlive or MikTex.

Setup for Commiting

We use the framework pre-commit to manage our pre-commit hooks. This simplifies the maintenance of the hooks - especially on heterogeneous systems - but requires an initial installation process of the individual users.

First, the framework itself must be installed. This process is explained on the framework’s website under “Installation”.

The second thing that needs to be done is to install the pre-commit hooks themselves. This can be achieved by running the command pre-commit install in the root directory of this project.

We assume that each commit has been validated with these pre-commit hooks and will not accept pull requests that contain unvalidated commits (the pre-commit hooks are also checked again on the server side by a GitHub action).