---
# System prepended metadata

title: Debugging course - internal hackmd

---

# Debugging course - internal hackmd

- [x] finalizing days+times + topics + instructors ==ALL==
- [x] course webpage ==JR+TP==
- [x] registration form ==EG==
- [ ] course materials pages ==ALL==
- [x] Tools: zoom + hackMD ==EG==
- [x] advertise to ==EG==
    - [x] triton users, 
    - [x] guilds, 
    - [x] data agents, 
    - [x] fcci, 
    - [x] departments
    - [x] scicomp announcements
    - [x] MS teams
- [ ] page under aalto.fi if we want big numbers ==EG==
- [ ] twitter if we want big numbers ==EG==
- [x] update motd ==EG==
- [ ] email to participants before easter ==EG==
- [x] email to registered participants one day before first event ==??==


## Outline

Q1: are 3 hours too much? too little? please discuss
  - JR: 1 - 1.5 hours for the lecture part, rest for bigger exercises, hands on support 
  - SÄ: 3 hours is a comfortable afternoon session; let's see what the contents would be
  - TP: Most of the work will be (I expect) getting comfortable with the debugging tools, so I personally expect at most 1 hour of "lecture", and rather 2 hours of hands-on exercises.
 
Q2: do we have all languages / instructors?
  - We have Python, C/C++ and Matlab
  - Possibly Julia, no direct confirmation 
      - TP: Luca confirmed this or am I wrong?
  - R missing, no material and no instructor
      - TP: Simo offered to do this (if I'm not mistaken)
  - If there is a need for the short BASH debugging intro, I can handle one (=Ivan). Got quite a bit of material for the topic over the last years.

Q3: will it be streamed (e.g. twitch) or is it that there will be live interaction with the participants?
  - JR: I would like recording to exist
  - TP: I don't mind a recording, even though I expect that most actual use will come from zoom/hackmd questions, potentially even with screen sharing, which I would definitely not record.

Q4: hybrid?
  - What are the current restrictions for the dates?
  - TP: I guess we are completely open. Personally I prefer remote.

Q5: how many participants do you want to reach?
  - JR: Not expecting large numbers, but the material (and videos?) would be useful to have
  - TP: I would expect quite some for python and potentially matlab. Probably less for C/Julia. No idea about R, since we haven't gotten a lot of R questions in garage I don't expect many.
 
Q6: pre-requisites? pre-assignments?
  - JR: Know the language and use it for work.
  - TP: Know basics of the language, a few language concepts will be introduced. 


## Agenda

- Wed 20/April/2022 12:00-15:00 Debugging with python (**Simppa, Thomas**)
- Thu 21/April/2022 12:00-15:00 Debugging with Matlab (**Thomas, ???**)
- Fri 22/April/2022 12:00-15:00 Debugging with C/C++ (**Jarno, Simppa**)
- Mon 25/April/2022 12:00-15:00 Debugging with Julia (**Luca, Jarno**)
- Tue 26/April/2022 12:00-15:00 Debugging with R (**Simo, ???**)


## Coordination

Enrico can take care of registration + zoom + communication.

## Internal email list
simppa.akaslompolo@aalto.fi, thomas.pfau@aalto.fi, jarno.rantaharju@aalto.fi, luca.ferranti@aalto.fi, simo.tuomisto@aalto.fi



## Email before the course starts

Hello!

you are receiving this email because you have registered for one or more days of "How to debug code 2022". https://scicomp.aalto.fi/training/scip/debugging-2022/ which will start tomorrow 20/April.

Here some important details:

- The course will happen fully online at: https://aalto.zoom.us/j/69608324491
- Time(zone!): we start at 12:00 sharp (EEST, Helsinki timezone), please connect few minutes before that.
- Please check that the prerequisites are satisfied: https://github.com/AaltoSciComp/debugging (they are different for each day/language)
- Asynchronous chat during the course: https://hackmd.io/@AaltoSciComp/Debug2022
- Although you have registered only for some of the days/languages listed, you are welcome to join any of the days/languages. Connection details are the same for all days.
- We do not provide credits or certificates with this course
- We might not be able to record this course, so please do not count on recordings.
- We will email you a reminder before each day and an end-of-the-course survey. If your plans have changed and you do not want to receive these emails anymore, please ask to be removed by contacting scip@aalto.fi

See you tomorrow and have a great day!
Aalto Scientific Computing

## Email to triton users

Hello everyone!

Spring is here (can you tell?) and we would like you to join us for two great practical courses organized by Aalto Scientific Computing.

**1) 20-26/April: How to debug code** 
Do you need to code to get your research work done? Then you must have debugged your code at least once. Do you just print debug statements? There are better ways that will save you lots of time! Come join us to learn some of the more advanced tools and how they can save you lots of time.   Each day is dedicated to one programming language: Python, MATLAB, C/C++, Julia, R. Each day is independent so you can join only the days relevant to you:

Registration and infos at: https://scicomp.aalto.fi/training/scip/debugging-2022/

**2) 25/April - 9/May: Software design for scientific computing**
Getting your code to be doing what you want it to do is only the first step of the journey to truly great software. In this course we set you on a path to thinking about the design of your code: how to make it obvious what the code does, that it is correct, efficient and elegant. Please note: limited amount of places available on a first-come-first-served basis.

Registration and infos at: https://scicomp.aalto.fi/training/scip/software-design-2022/

Other courses in May and June are listed at https://scicomp.aalto.fi/training/

