Course Description and Goals:

Statistical learning is a field that teaches students how to analyze and interpret data by applying statistical methods and machine learning algorithms to uncover patterns, make predictions, and gain insights from data. The syllabus includes:

• Statistical and machine learning methods, including linear and polynomial regression, logistic regression, and linear discriminant analysis.

• Model validation techniques such as cross-validation and bootstrap, model selection, and regularization methods (ridge and lasso).

• Nonlinear models, splines, and generalized additive models.

• Tree-based methods, including random forests and boosting.

• Support-vector machines and an introduction to causal inference.

• Unsupervised learning methods such as principal components analysis and clustering (k-means and hierarchical).

Examination Format: Report and Presentation (obligatory to receive participaation certificate)

General Information University: University of Duisburg-Essen

• Learning Platform: Moodle (Link: https://lehre.moodle.uni-due.de/course/view.php?id=1986)

• Hybrid Format: Yes, the course includes both in-person and online sessions via Zoom

• Study Program and Level: Master’s/PhD students

• Weekly Hours: The event consists of three block sessions (lecture with tutorial sessions) with two additional dates for tutorials:

• First session: 02.04. (9:00–14:00)

• Following sessions: 03.04. & 04.04. (9:00–17:00)

• Online session: 07.04.

• Final lecture: 25.04. (9:00–14:00)

• Language: German or English (depending on student preference)

Further information, including locations, and Zoom links, can be found on our homepage: Statistical Learning SS 25

Related Posts

How To: Open Science

How To: Open Science

Tired of Recreating someone else’s work? - How Open Science can accelerate research and overcome reinvention

Have you ever found papers on algorithms but their implementation is missing? Found an interesting analysis but there is no way to check the results, as you don’t have access to the data they were derived from? Ever thought you had a great idea for a project, just to find out a year later that you are not the only research group following that specific idea? Not having access to other people’s code, data, metrics or even their plans for research projects often leads to unnecessary delays and scientific redundancies. There is an easy solution to overcome (almost) all of these issues. It’s called Open Science! What is Open Science? The UNESCO defines Open Science as a construct of “movements and practices aiming to make multilingual scientific knowledge openly available, accessible and reusable for everyone, to increase scientific collaborations and sharing of information for the benefits of science and society, and to open the processes of scientific knowledge creation, evaluation and communication to societal actors […]”. To ensure that everyone has access to scientific knowledge and infrastructure, Open Science focuses on four main concepts.

Read More
Announcement - Call for participation

Announcement - Call for participation

Update (June 24, 2024)

The call for participation is now open! Read more

Upcoming!

The Data Literacy Center Rhine-Rhur is issuing a call for participation in its “rent-an-expert” project! This is a great opportunity for PhD students and early postdocs who are working on research projects that involve data science, artificial intelligence, high performance computing and simulation, to get free support from our expert consultants.

Support can take the form of short- or long-term consulting, depending on the needs of the project. More info will be available shortly!

Read More
Documentation From User Experience

Documentation From User Experience

This post is a condensed version of a talk at our Data Compentcy College

If you regularly use scientific software written by others, or tried to replicate interesting research that relies on software, you have probably also invested weeks of work to solve a software problem or even given up on a software because of missing documentation. Finding a project that might be the solution to your problem and then failing to run the code is frustrating. Being unable to run a project you have built yourself years ago is even worse. Having experienced all those setbacks myself in the past I want to use this post to channel that frustration to fuel solutions for better documentation for our current and future projects.

Read More