From 34f68fc171f206e75df4f63c78d64e12b702ecc9 Mon Sep 17 00:00:00 2001 From: Gerasimos Chourdakis Date: Mon, 12 Oct 2026 20:27:41 +0200 Subject: [PATCH 1/6] Update orga slides for WT2627 --- 00_organization/challenge_intro_slides.md | 55 +++++++------ 00_organization/course_intro_slides.md | 79 +++++++++++-------- .../organizational_remarks_week8_slides.md | 22 ++---- 00_organization/rse_basics_slides.md | 36 +++++++-- 00_organization/topic_overview_demo.md | 3 + timetable.md | 1 + 6 files changed, 119 insertions(+), 77 deletions(-) diff --git a/00_organization/challenge_intro_slides.md b/00_organization/challenge_intro_slides.md index 465e335b..e3767cbb 100644 --- a/00_organization/challenge_intro_slides.md +++ b/00_organization/challenge_intro_slides.md @@ -37,7 +37,7 @@ slideOptions: -# Your Challenge: Contribute to Real Simulation Software +# Challenge: Contribute to real simulation software --- @@ -51,17 +51,17 @@ slideOptions: ## Timeline -- Pick a software (till **Oct 22**, evening) -- **Step 1**: Present the software: how you got it, what are main features, some tutorials you did, ... (**Nov 5**) -- **Step 2**: Present *"RSE infrastructure"* of the software: Which CI / documentation / building / git workflow ... does it use? How do contributions work? (**Dec 17**) -- Suggest contribution (**Dec 17**) -- **Step 3**: Present the contribution (**Feb 4**) +1. Pick a simulation software project +2. **Presentation 1**: How you got the software, what are main features, some tutorials you did, ... +3. **Presentation 2**: *"RSE infrastructure"* of the software:
Which CI / documentation / building / git workflow ... does it use? How do contributions work? +4. Suggest contribution +5. **Presentation 3**: Your contribution --- ## Grading -Challenge / exercises / other = 45% / 50% / 5% +Challenge / exercises / engagement = 45% / 50% / 5% The challenge part: @@ -75,9 +75,9 @@ The challenge part: --- -## Example Contributions +## Example contributions -1. Ported several demo cases ([see one](https://github.com/FEniCS/dolfinx/pull/2508)) from FEniCS to [FEniCSx](https://fenicsproject.org/): difficulty *"outstanding"* +1. Ported several demo cases ([see one](https://github.com/FEniCS/dolfinx/pull/2508)) from FEniCS to [FEniCSx](https://fenicsproject.org/): difficulty *"outstanding"* (before widespread AI assistance) 2. [Improved website search](https://github.com/MakieOrg/Makie.jl/pull/2474) of [Makie](https://makie.org/website/): difficulty *"good"* 3. [Solved a simple good first issue](https://github.com/pymor/pymor/pull/1898) in [pyMOR](https://pymor.org/): difficulty *"ok"* @@ -85,7 +85,7 @@ The challenge part: --- -## Which Software to Pick? +## Which software to pick? - Something in the simulation universe (this includes equation solvers, meshing, scientific visualization, (AI), ...) - Truly open source, all development in public @@ -108,16 +108,16 @@ The challenge part: - [Firedrake](https://www.firedrakeproject.org/): FEM library in Python - [LAMMPS](https://www.lammps.org/): MD simulator - [MercuryDPM](https://www.mercurydpm.org/home): particle code -- [Nalu-Wind](https://github.com/Exawind/nalu-wind): CFD solver for wind farms +- [MFEM](https://mfem.org/): FEM library in C++ +- [NeoFOAM](https://exasim-project.com/NeoFOAM/) +- [Kynema-UGF](https://github.com/kynema/kynema-ugf): CFD solver for wind farms - [Palabos](https://palabos.unige.ch/): Lattice Boltzmann method solver --- ## Suggestions II -- [OpenFAST](https://www.nrel.gov/wind/nwtc/openfast.html): Multi-fidelity wind turbine simulation tool - [PETSc](https://petsc.org/): LA library -- [preCICE](https://precice.org/): Coupling library (Stuttgart) - [pyiron](https://pyiron.org/): Workflow manager in Python - [pyMOR](https://pymor.org/): MOR library in Python - [pyLife](https://pylife.readthedocs.io/en/stable/): fatigue of mechanical components in Python @@ -125,12 +125,23 @@ The challenge part: - [SUNDIALS](https://computing.llnl.gov/projects/sundials): Nonlinear solvers, ODEs - [TRILINOS](https://trilinos.github.io/): Collection of scientific software libraries, mainly solvers - [VisIt](https://visit-dav.github.io/visit-website/index.html): Scientific visualization software -- more projects in [xSDK](https://xsdk.info/packages/), [NumFOCUS](https://numfocus.org/sponsored-projects), or [HiRSE Code Promotion](https://www.helmholtz-hirse.de/promo.html) +- more projects in [NumFOCUS](https://numfocus.org/sponsored-projects) or [HiRSE Code Promotion](https://www.helmholtz-hirse.de/promo.html) - **Or your suggestion** (also agent-based or discrete event simulation software) --- -## What Happens if Maintainers do not React in Time? +## The Challenge: Advice + +- Pick something from your background +- Don't choose based on the programming language +- Start early, persist with questions, iterate quickly +- Start with something clear, extend with a second contribution +- Contact us early in case of trouble +- Make reviews easy for maintainers (will return to this) + +--- + +## What happens if maintainers do not react? - Give them time, contact early - Not your fault @@ -138,17 +149,17 @@ The challenge part: --- -## How to Submit my Choice? +## How to submit my choice? -- [https://gitlab-sim.informatik.uni-stuttgart.de/simulation-software-engineering-wite2526/challenge](https://gitlab-sim.informatik.uni-stuttgart.de/simulation-software-engineering-wite2526/challenge) -- Comment in [issue #1](https://gitlab-sim.informatik.uni-stuttgart.de/simulation-software-engineering-wite2526/challenge/-/issues/1) till **22nd of October** (next Wednesday) evening (no FCFS) +- Challenge repository (see `timetable.md`) +- Comment in `work item #1` till next Wednesday evening (no FCFS) - Priority list with at least three choices -- If **not** on our suggestion list, write short paragraph what the software does and give links +- If **not** on our suggestion list, motivate and give links - Add pre-knowledge that you have in the field. For example, if you pick pyMOR, you should know already what MOR is. --- -## Role of Advisor +## Role of advisor - Felix, Frédéric, Serge, or Gerasimos - Use, for example, exercise blocks and time before and after lectures for discussions @@ -169,8 +180,8 @@ The challenge part: - Submit a report for each step - 1-2 pages (2500-5000 chars) -- Written in markdown -- Submission via a merge request to the [GitLab challenge repo](https://gitlab-sim.informatik.uni-stuttgart.de/simulation-software-engineering-wite2526/challenge) +- Written in Markdown +- Submission via a merge request to the GitLab challenge repo - Add links, instructions, ... should work like a compact summary for everybody in the end - Will be visible to everybody in SSE group - We will prepare templates diff --git a/00_organization/course_intro_slides.md b/00_organization/course_intro_slides.md index 67d5fc2b..039c3974 100644 --- a/00_organization/course_intro_slides.md +++ b/00_organization/course_intro_slides.md @@ -41,38 +41,43 @@ slideOptions: --- -## The Lecturers +## Involved people -- Gerasimos (Chourdakis) [`@MakisH`](https://github.com/MakisH) -- Frédéric (Simonis) [`@fsimonis`](https://github.com/fsimonis) -- Felix (Neubauer) [`@Logende`](https://github.com/Logende) -- On leave this year: Benjamin (Uekermann) [`@uekerman`](https://github.com/uekerman) +- Gerasimos Chourdakis - [`@MakisH`](https://github.com/MakisH) +- Frédéric Simonis - [`@fsimonis`](https://github.com/fsimonis) +- Felix Neubauer - [`@Logende`](https://github.com/Logende) +- Serge Kotchourko - [`@kotserge`](https://github.com/kotserge) -Additional challenge advisors: - -- Serge Kotchourko [`@kotserge`](https://github.com/kotserge) +--- -SSE Hall of Fame: +## Involved people (2) -- Alexander (Jaust) [`@ajaust`](https://github.com/ajaust) -- Ishaan (Desai) [`@IshaanDesai`](https://github.com/IshaanDesai) +- On leave this year: Benjamin Uekermann - [`@uekerman`](https://github.com/uekerman) +- SSE Hall of Fame: + - Alexander Jaust - [`@ajaust`](https://github.com/ajaust) + - Ishaan Desai - [`@IshaanDesai`](https://github.com/IshaanDesai) --- -## The Idea & Learning Goals +## Learning goals -- No (advanced) programming course - Learn about all the other things you need to develop research / simulation software (to become a *"Research Software Engineer"*): - continuous integration, virtualization, building & packaging, documentation, ... -- Focus on tools for C++ and Python -- More than a *"3-days software carpentry workshop on Python and Git"* + continuous integration, containers, building & packaging, documentation, ... - Learn how to contribute to large-scale open-source simulation software projects - Learn which important simulation software packages exist and how to use them --- -## Building Blocks +## Specific angle + +- No (advanced) programming course (for C++ and Python) +- More than a *"3-days software carpentry workshop on Python and Git"* +- Focus on simulation software + +--- + +## Building blocks Two parallel branches: @@ -90,7 +95,7 @@ Two parallel branches: ## Prerequisites: Skills - Basic programming (Python, C++) -- Basic software development skills (bash, Git, md, ...) +- Basic software development skills (CLI, Git, Markdown, ...) - Some simulation background - SimTech, COMMAS students: no issue - CS, SE: ideally through Numerical Fundamentals (NumGL) and Fundamentals of Scientific Computing (WissRech) @@ -108,15 +113,15 @@ Two parallel branches: ## Material -- Great open-source book to recap: Irving, Hertweck, Johnston, Ostblom, Wickham, and Wilson: [Research Software Engineering with Python](https://third-bit.com/py-rse/) -- All our material is on [https://github.com/Simulation-Software-Engineering](https://github.com/Simulation-Software-Engineering) +- Great open-source book to recap: Irving, Hertweck, Johnston, Ostblom, Wickham, and Wilson:
[Research Software Engineering with Python](https://third-bit.com/py-rse/) +- All our material is on GitHub:
[https://github.com/Simulation-Software-Engineering](https://github.com/Simulation-Software-Engineering) - Mainly markdown ... use your favorite tool to render (simply GitHub viewer, [GWDG Hedgedoc](https://pad.gwdg.de/), [stuvus Hedgedoc](https://pad.stuvus.de/), [pandoc](https://pandoc.org/), [PDFs generated in CI](https://github.com/Simulation-Software-Engineering/Lecture-Material/actions/workflows/create-pdfs-from-markdown.yml), [Marp example](https://github.com/uekerman/sse-marp-example), ...) - We rework the material as the semester goes. - We give links to docs, videos, blog posts, podcasts, ... --- -## Contribute to the Material +## Contribute to the material - You, no joke :see_no_evil: ([many students already contributed](https://github.com/Simulation-Software-Engineering/Lecture-Material/graphs/contributors)) - Typos, broken links, ... @@ -133,11 +138,15 @@ Two parallel branches: - Also changes RSE rapidly - Even more important: having a good overview of technology and being able to **read** code (what we teach in this course) -- If you use generative AI for your exercises or your challenge: **mandatory** to make this transparent (which parts of your code, how, ...) +- If you use generative AI for your exercises or your challenge: **mandatory** to make this transparent (where, how, ...) - It is important, experiment! But also build a firm understanding of the basics of technology! --- +## Goal: Learn + +--- + ## Chapters 1. Version Control @@ -145,7 +154,7 @@ Two parallel branches: 3. Building and Packaging 4. Documentation 5. Testing and Continuous Integration -6. Miscellaneous +6. Miscellaneous: Publishing, Licenses, ... --- @@ -157,15 +166,18 @@ Two parallel branches: - Contribute something small (but not trivial) to a large-scale open-source simulation software (*"good first issue"*) - Examples: feature, tutorial, documentation, new packaging, bugfix, ... -- Run through complete cycle (issue, discussion, PR, review, merge) +- Run through the complete cycle (issue, discussion, PR, review, merge) -### Timeline +--- + +## The Challenge: Timeline - Pick a software project to contribute to -- **Step 1**: Present the software: how you got it, what are main features, some tutorials you did, ... -- **Step 2**: Present *"RSE infrastructure"* of the software: Which CI / documentation / building / git workflow ... does it use? How do contributions work? -- Suggest contribution -- **Step 3**: Present the contribution +- **Step 1**: Present the software: how you got it, what are the main features, some tutorials you did, ... +- **Step 2**: Present *"RSE infrastructure"* of the software: Which CI / documentation / building / git workflow ... does it use? How do contributions work? Is there a GenAI policy? +- Suggest a contribution +- **Step 3**: Present your contribution + --- @@ -178,13 +190,18 @@ See [GitHub: timetable.md](https://github.com/Simulation-Software-Engineering/Le ## Examination - *"Course accompanying examination"*: no exam, but continuous examination (more like a lab course or a seminar) -- Attendance is mandatory - We look at: - Challenge (reports, presentations, contribution; more in the afternoon) (45%) - Exercises (not every detail, but *"outstanding"* / *"good"* / *"ok"* / *"not enough"* ) (50%) - - Other (e.g. contributions to lecture material, ...) (5%) + - Engagement (e.g., contributions to lecture material, ...) (5%) - *"good"* everywhere leads to 1.0. - We give (brief) feedback after every exercise. +- This year: Adding 3x short multiple-choice exams (optional, engagement points if all passed) + +--- + +## Examination logistics + - You will need to register yourself to the *"exam"* on C@MPUS. - Last in: The deadline to pick a software - Last out: Once you handed in the first report diff --git a/00_organization/organizational_remarks_week8_slides.md b/00_organization/organizational_remarks_week8_slides.md index 98f01e6a..7f8f746f 100644 --- a/00_organization/organizational_remarks_week8_slides.md +++ b/00_organization/organizational_remarks_week8_slides.md @@ -33,26 +33,18 @@ slideOptions: } -# Organizational Things Week 8 +# Organizational remarks --- -## Time Table +## Exam registration - - -## Exam Registration - -- You have to register for the exam node on C@MPUS (we cannot do this for you) +- You have to register for the exam node on C@MPUS
(we cannot do this for you) - The deadline should be very soon --- -## Challenge First Report: MR Feedback +## Challenge first report: MR feedback - Try to write good MR titles and descriptions - Resolve threads when comments are answered, done, or dropped @@ -63,14 +55,12 @@ td { --- -## Challenge Contribution +## Challenge contribution - Please open an issue in the Challenge repo explaining what you want to work on in the contribution. We will then use these issues to further discuss the progress of the contribution. Provide links to issues, pull requests etc. - Remember the deadline for opening the issue (see timetable) - - If you open earlier, you get feedback earlier - - Latest feedback from supervisors: first course week after Christmas + - If you open earlier, you get feedback earlier (till early January) - Title of issue: "Contribution to SOFTWARE by USERNAME" - Tag your supervisor in description - Get in touch with maintainers early (through official channels) - Discuss before you start developing - diff --git a/00_organization/rse_basics_slides.md b/00_organization/rse_basics_slides.md index 4a07991e..ee084781 100644 --- a/00_organization/rse_basics_slides.md +++ b/00_organization/rse_basics_slides.md @@ -36,13 +36,18 @@ slideOptions: --- -## Starting Points +## Starting ooints - [DORA declaration](https://sfdora.org/) in 2012: reshape how research impact should be assessed underlining importance of software > For the purposes of research assessment, consider the value and impact of all research outputs (including datasets and software) in addition to research publications ... - [UK survey in 2014](https://zenodo.org/record/1183562): 7 out of 10 researchers could not conduct research without software. + +--- + +## First steps and clear need + - DFG funding calls on research software in 2016 & 2019 & [2022](https://www.dfg.de/en/news/news-topics/announcements-proposals/2022/info-wissenschaft-22-85) - [Nationale Forschungsdaten Infrastruktur, NFDI](https://www.nfdi.de/?lang=en) since 2020 - Lack of careers for software developers in academia @@ -50,7 +55,7 @@ slideOptions: --- -## RSE Movement +## RSE movement ... academic software developers needed a name: **Research Software Engineers** @@ -59,8 +64,14 @@ slideOptions: > A Research Software Engineer (RSE) combines professional software engineering expertise with an intimate understanding of research. -- *"Movement"* started in the UK, first UK RSE conference in 2016 -- First conferences in Germany and the Netherlands in 2019 ([deRSE 2026](https://events.hifis.net/event/2945/) is in Stuttgart, March 3-5) +*"Movement"* started in the UK, first UK RSE conference in 2016 + +--- + +## The RSE movement in Germany + +- First conferences in Germany and the Netherlands in 2019 +- [deRSE 2026](https://events.hifis.net/event/2945/) was in Stuttgart, 2027 in Dortmund - [First de-RSE position paper](https://f1000research.com/articles/9-295/v2) in 2020, [several working groups](https://de-rse.org/en/working_groups.html) - [Learning and teaching RSE](https://de-rse.org/learn-and-teach/), [foundational competencies](https://de-rse.org/blog/2024/10/08/identifying-the-foundational-competencies-of-an-RSE-en.html) - [Why be an RSE?](https://researchit.blogs.bristol.ac.uk/2021/10/14/international-rse-day-why-be-an-rse/) Interesting and novel projects, technical freedom, RSEs come from varied backgrounds, development for social good @@ -69,8 +80,6 @@ slideOptions: ## How is Simulation Software Engineering different from RSE? -> Why is the name of the course SSE and not RSE? - - Difference is not so big actually. - Simulation research depends on software by definition (even less a *"by-product"* than for research in Chemistry, Biology, ...). - Already prototypes are so complicated today that one (wo)man hero PhD projects are no longer feasible. --> Learn how to work with / contribute to community software. @@ -81,9 +90,20 @@ slideOptions: ## Do I need this in Industry? - Yes. Research also happens in industry. -- All things we learn (Git, packaging, CI/CD, virtualization, documentation, ...) is also highly relevant for non-research software. +- All topics we discuss also apply to non-research software. - Companies use (more and more) the same workflows and tools. - It is not just about coding. It is about collaborative work. -- Open-source development excellent door opener for industry. +- Open-source development is excellent door opener for industry. - Some companies use open-source software and need to make contributions. - Some companies develop their software as open-source software. + +--- + +## How can I start contributing to open-source? + +- Fix something that annoys you. +- Support programs: + - [Outreachy](https://www.outreachy.org/) + - [Google Summer of Code](https://summerofcode.withgoogle.com/) +- Do your thesis on an open-source project 😉 +- Do the SSE challenge! diff --git a/00_organization/topic_overview_demo.md b/00_organization/topic_overview_demo.md index f15051c7..18084210 100644 --- a/00_organization/topic_overview_demo.md +++ b/00_organization/topic_overview_demo.md @@ -28,3 +28,6 @@ - LGPL3 license - semantic versioning scheme - [distribution published on DaRUS](https://darus.uni-stuttgart.de/dataset.xhtml?persistentId=doi:10.18419/darus-4167) +- Contributors: + - Many contributors in the [core](https://github.com/precice/precice), [tutorials](https://github.com/precice/tutorials), and more repositories. + - Participated in the [Google Summer of Code 2026](https://precice.org/community-contribute-open-projects.html) - Maybe interesting to apply. diff --git a/timetable.md b/timetable.md index c1b2498d..7de3aab7 100644 --- a/timetable.md +++ b/timetable.md @@ -43,6 +43,7 @@ This timetable is for the winter term 2026-27. Resources: - [Challenge respository](https://gitlab-sim.informatik.uni-stuttgart.de/simulation-software-engineering-wite2627/challenge) +- [Register for the Challenge](https://gitlab-sim.informatik.uni-stuttgart.de/simulation-software-engineering-wite2627/challenge/-/work_items/1) ## Week 1 From 65b2846743d4344c50e9232b939d2cbeaf00ec6e Mon Sep 17 00:00:00 2001 From: Gerasimos Chourdakis Date: Tue, 13 Oct 2026 13:22:21 +0200 Subject: [PATCH 2/6] Fix typo --- timetable.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/timetable.md b/timetable.md index 7de3aab7..218ff8c9 100644 --- a/timetable.md +++ b/timetable.md @@ -24,9 +24,9 @@ | [10](#week-10) | 16.12. | 🎉 | Student presentations: Challenge - step 2 | | | | | 🎉 | Student presentations: Challenge - step 2 | | | | | ⚠️ | **Deadline:** Suggest a Challenge contribution | | -| - | 23.12. | 🎄 | _Christmasn break_ | | -| - | 30.12. | 🎄 | _Christmasn break_ | | -| - | 06.01. | 🎄 | _Christmasn break_ | | +| - | 23.12. | 🎄 | _Christmas break_ | | +| - | 30.12. | 🎄 | _Christmas break_ | | +| - | 06.01. | 🎄 | _Christmas break_ | | | [11](#week-11) | 13.01. | 🧑‍🏫 | Intro testing, testing in Python | Felix | | | | 💻️ | Testing in Python | Felix | | [12](#week-12) | 20.01. | 🧑‍🏫 | Markup, Pandoc, website gener. | Felix | From ac8e8f56f97c180aa2cf52423bce2f0da29a8109 Mon Sep 17 00:00:00 2001 From: Gerasimos Chourdakis Date: Tue, 13 Oct 2026 17:04:05 +0200 Subject: [PATCH 3/6] Adjust timetable --- 00_organization/course_intro_slides.md | 16 +++++++++++++--- timetable.md | 18 ++++++++++++------ 2 files changed, 25 insertions(+), 9 deletions(-) diff --git a/00_organization/course_intro_slides.md b/00_organization/course_intro_slides.md index 039c3974..eb04404d 100644 --- a/00_organization/course_intro_slides.md +++ b/00_organization/course_intro_slides.md @@ -140,6 +140,7 @@ Two parallel branches: - Even more important: having a good overview of technology and being able to **read** code (what we teach in this course) - If you use generative AI for your exercises or your challenge: **mandatory** to make this transparent (where, how, ...) - It is important, experiment! But also build a firm understanding of the basics of technology! +- **Not allowed:** GenAI for communication (reports/exercise PR descriptions). --- @@ -192,7 +193,7 @@ See [GitHub: timetable.md](https://github.com/Simulation-Software-Engineering/Le - *"Course accompanying examination"*: no exam, but continuous examination (more like a lab course or a seminar) - We look at: - Challenge (reports, presentations, contribution; more in the afternoon) (45%) - - Exercises (not every detail, but *"outstanding"* / *"good"* / *"ok"* / *"not enough"* ) (50%) + - Exercises (pass/fail) + interim assessments on the course topics (25%+25%) - Engagement (e.g., contributions to lecture material, ...) (5%) - *"good"* everywhere leads to 1.0. - We give (brief) feedback after every exercise. @@ -200,9 +201,18 @@ See [GitHub: timetable.md](https://github.com/Simulation-Software-Engineering/Le --- +## Examination details + +- Challenge: Must pass every step. +- Exercises: Collect points +- Feedback on exercises: pass/fail +- On each presentation week (morning slot): a few (primarily closed-form) understanding questions + +--- + ## Examination logistics -- You will need to register yourself to the *"exam"* on C@MPUS. +- You will need to register yourself for the *"exam"* on C@MPUS. - Last in: The deadline to pick a software - Last out: Once you handed in the first report @@ -210,7 +220,7 @@ See [GitHub: timetable.md](https://github.com/Simulation-Software-Engineering/Le ## GitLab Account -- Please write a mail till tonight to Gerasimos. +- Please write an email until tonight to Gerasimos. - [gerasimos.chourdakis@ipvs.uni-stuttgart.de](mailto:gerasimos.chourdakis@ipvs.uni-stuttgart.de) - Email subject: "GitLab account SSE course" - State your **name** and preferred **email-address** diff --git a/timetable.md b/timetable.md index 218ff8c9..e8c5a9e9 100644 --- a/timetable.md +++ b/timetable.md @@ -9,7 +9,8 @@ | | | ⚠️ | **Deadline:** Register for the Challenge | | | [3](#week-3) | 28.10. | 🧑‍🏫 | Virtualization and containers | Gerasimos | | | | 💻️ | Containers | Gerasimos | -| [4](#week-4) | 04.11. | 🎉 | Student presentations: Challenge - step 1 | | +| [4](#week-4) | 04.11. | ✏️ | Interim assessment 1 | | +| | | 🎉 | Student presentations: Challenge - step 1 | | | | | 🎉 | Student presentations: Challenge - step 1 | | | [5](#week-5) | 11.11. | 🧑‍🏫 | Intro packaging, Python packaging | Felix | | | | 💻️ | Python packaging | Felix | @@ -21,7 +22,8 @@ | | | 💻️ | CPack | Frédéric | | [9](#week-9) | 09.12. | 🧑‍🏫 | Technical writing | Gerasimos | | | | 💻️ | Code review | Gerasimos | -| [10](#week-10) | 16.12. | 🎉 | Student presentations: Challenge - step 2 | | +| [10](#week-10) | 16.12. | ✏️ | Interim assessment 2 | | +| | | 🎉 | Student presentations: Challenge - step 2 | | | | | 🎉 | Student presentations: Challenge - step 2 | | | | | ⚠️ | **Deadline:** Suggest a Challenge contribution | | | - | 23.12. | 🎄 | _Christmas break_ | | @@ -35,7 +37,8 @@ | | | 💻️ | GitHub Actions | Felix | | [14](#week-14) | 03.02. | 🧑‍🏫 | Boost.Test and CTest | Frédéric | | | | 💻️ | Boost.Test and CTest | Frédéric | -| [15](#week-15) | 10.02. | 🎉 | Student presentations: Challenge - step 3 | | +| [15](#week-15) | 10.02. | ✏️ | Interim assessment 3 | | +| | | 🎉 | Student presentations: Challenge - step 3 | | | | | 🎉 | Student presentations: Challenge - step 3 | | This timetable is for the winter term 2026-27. @@ -90,9 +93,10 @@ Chapter 2: Virtualization and Containers ## Week 4 -Student presentations +Interim assessment 1 and student presentations 1 - Morning: + - Assessment on the topics of weeks 1, 2, 3. - The Challenge, step one, presentations - Afternoon: - The Challenge, step one, presentations @@ -149,9 +153,10 @@ Chapter 4: Documentation - Technical Writing, Code Review ## Week 10 -Student presentations +Interim assessment 2 and student presentations 2 - Morning: + - Assessment on the topics of weeks 5, 6, 7, 8, 9. - The Challenge, step two, presentations - Afternoon: - The Challenge, step two, presentations @@ -208,9 +213,10 @@ Chapter 5: Testing and Continuous Integration - Boost.Test and CTest ## Week 15 -Student presentations +Interim assessment 3 and student presentations 3 - Morning: + - Assessment on the topics of weeks 11, 12, 13, 14. - The Challenge, step three, presentations - Afternoon: - The Challenge, step three, presentations From 6b07bb45ff06bdf6175670d54818a197003c7d28 Mon Sep 17 00:00:00 2001 From: Gerasimos Chourdakis Date: Tue, 13 Oct 2026 17:05:52 +0200 Subject: [PATCH 4/6] Fix typo --- 00_organization/rse_basics_slides.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/00_organization/rse_basics_slides.md b/00_organization/rse_basics_slides.md index ee084781..613b535a 100644 --- a/00_organization/rse_basics_slides.md +++ b/00_organization/rse_basics_slides.md @@ -36,7 +36,7 @@ slideOptions: --- -## Starting ooints +## Starting points - [DORA declaration](https://sfdora.org/) in 2012: reshape how research impact should be assessed underlining importance of software From 13cf3ed2209868a11af5babf09b9f6c81c204e3b Mon Sep 17 00:00:00 2001 From: Gerasimos Chourdakis Date: Tue, 13 Oct 2026 17:11:37 +0200 Subject: [PATCH 5/6] Fix indentation --- 00_organization/course_intro_slides.md | 4 ++-- 00_organization/rse_basics_slides.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/00_organization/course_intro_slides.md b/00_organization/course_intro_slides.md index eb04404d..86b81db0 100644 --- a/00_organization/course_intro_slides.md +++ b/00_organization/course_intro_slides.md @@ -54,8 +54,8 @@ slideOptions: - On leave this year: Benjamin Uekermann - [`@uekerman`](https://github.com/uekerman) - SSE Hall of Fame: - - Alexander Jaust - [`@ajaust`](https://github.com/ajaust) - - Ishaan Desai - [`@IshaanDesai`](https://github.com/IshaanDesai) + - Alexander Jaust - [`@ajaust`](https://github.com/ajaust) + - Ishaan Desai - [`@IshaanDesai`](https://github.com/IshaanDesai) --- diff --git a/00_organization/rse_basics_slides.md b/00_organization/rse_basics_slides.md index 613b535a..f28a092a 100644 --- a/00_organization/rse_basics_slides.md +++ b/00_organization/rse_basics_slides.md @@ -103,7 +103,7 @@ slideOptions: - Fix something that annoys you. - Support programs: - - [Outreachy](https://www.outreachy.org/) - - [Google Summer of Code](https://summerofcode.withgoogle.com/) + - [Outreachy](https://www.outreachy.org/) + - [Google Summer of Code](https://summerofcode.withgoogle.com/) - Do your thesis on an open-source project 😉 - Do the SSE challenge! From c5c446249e01527912416bb5d5e22f382b98d5a3 Mon Sep 17 00:00:00 2001 From: Gerasimos Chourdakis Date: Tue, 13 Oct 2026 18:21:29 +0200 Subject: [PATCH 6/6] Revert changes regarding attendance and residue of optional --- 00_organization/course_intro_slides.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/00_organization/course_intro_slides.md b/00_organization/course_intro_slides.md index 86b81db0..71250fca 100644 --- a/00_organization/course_intro_slides.md +++ b/00_organization/course_intro_slides.md @@ -191,13 +191,13 @@ See [GitHub: timetable.md](https://github.com/Simulation-Software-Engineering/Le ## Examination - *"Course accompanying examination"*: no exam, but continuous examination (more like a lab course or a seminar) +- Attendance is mandatory - We look at: - Challenge (reports, presentations, contribution; more in the afternoon) (45%) - Exercises (pass/fail) + interim assessments on the course topics (25%+25%) - Engagement (e.g., contributions to lecture material, ...) (5%) - *"good"* everywhere leads to 1.0. - We give (brief) feedback after every exercise. -- This year: Adding 3x short multiple-choice exams (optional, engagement points if all passed) ---