Open Debugging: Bring Your Own Problem
Workshop 33 - Winter Semester 2026-27
Overview
Collaborative troubleshooting across R, Python, Git, and document workflows.
Got a model that won't converge, a Git merge conflict you can't resolve, an R script that produces unexpected results, or a LaTeX document throwing obscure errors? This open debugging session is an informal, collaborative clinic where CRC members can bring their current technical challenges and work through them together with peers and the Project S team.
How It Works
- Bring Your Own Problem: Bring whatever is currently blocking your analysis, coding, or publishing workflow.
- Collaborative Problem Solving: Work through problems together with peers and experienced developers/statisticians.
- Cross-Domain Expertise: Help available across R, Python, Julia, Git/GitHub/GitLab, LaTeX, and data processing tools.
- Learn from Others' Hurdles: Even if you don't have a specific issue, join to see common traps, debugging strategies, and helpful workflow tricks.
Common Topics
- R and package errors (
tidyverse,lme4,brms,ggplot2) - Python environment, package, and script issues
- Git merge conflicts, rebasing questions, and repository management
- Reproducibility and workflow automation hurdles
- LaTeX formatting, bibliography errors, and compilation failures
Session Details
- Date: 20 January 2027
- Time: 14:00 - 15:30
- Location: House of Prominence, Attic (Top floor), Luxemburger Str. 299, Cologne
- Speaker: TBC
Related CRC 1252 Workshops
- Workshop 19: Let's Rant: Open Debugging — First open debugging session from Winter 2025-26
- Workshop 21: Version Control I: Getting Started with Git — Git fundamentals
- Workshop 27: lme4 Model Criticism — Troubleshooting mixed-effects models