# 4-day workshop planning: Python
## Materials page
- https://github.com/UPPMAX/R-python-julia-matlab-HPC/
- https://uppmax.github.io/R-python-julia-matlab-HPC/

#### DECIDED Python schedule

[How this schedule was created, including discussion points](https://github.com/UPPMAX/R-python-julia-matlab-HPC/tree/main/lesson_plans/202401022_richel#suggestion).

Time |Topic |Teacher
-----------|------------------------------------------------------|-------
09:00-09:45|First login |BB + PO+ RB + RP
09:45-10:00|Break |.
10:00-10:10|Syllabus BB, RB, |RP
10:10-10:20|Python in general BB, RB |RP
10:20-10:50|Load modules and run BB, RB |RP
10:50-11:05|Break |.
11:05-11:35|Packages 30/30 |RB
11:35-12:00|Isolated environments (ML, venv, conda) 25/60 mins |RB
12:00-13:00|Lunch |.
13:00-13:35|Isolated environments (ML, venv, conda) 35/60 mins |RB
13:35-14:05|Batch 30/30 mins |BB
14:05-14:20|Break |.
14:20-14:40|GPU |BB
14:40-15:10|Simultaneous session 30/30 mins |BB * RB * RP
15:10-15:25|Break |.
15:25-16:00|Parallel and multithreaded functions |PO
16:00-16:15|Summary and evaluation |RB

Simultaneous session:
- Kebnekaise: Jupyter, by BB
- Rackham: Interactive session and Jupyter, by RB
- LUNARC, by RP

- [DECISION] We all agree on this schedule :+1:

Discussion points:

- For this schedules, breaks were scheduled first, so that
(1) schedule is simple, and (2) all session lengths are 45 or 60 mins.
However, assuming all durations are correct (!), some sessions will be
cut by a break. Is that acceptable?
- If yes: no problemo
- No: where should the breaks be instead? Who makes a new schedule?
- I picked to discuss batch (by BB) from 13:35-14:05,
over having a break at 14:00 and having a 5 minute session
with a schedule like below. Agreed?

Time |Topic |Teacher
-----------|------------------------------------------------------|-------
13:35-14:00|Batch 25/30 mins |BB
14:00-14:15|Break |.
14:15-14:20|Batch 5/30 mins |BB

- R: There is no time for evaluation at the end. I feel 10 minutes
is enough and the time is worth it. I suggest to add it.
- Pro: helps us improve the course, shows we care about our learners' opinion
- Con: takes time away
- Vote:
- Yes:
- No:
- If evaluation, suggest questions on confidence,
see [here](https://github.com/UPPMAX/uppmax_intro_day_1/tree/main/evaluations/20240827)
- Pro: useful to asses stronger/weaker sessions of the course
- Con: maybe must use a standard evaluation form, needs teachers to formulate
their lesson goals
- Vote:
- Yes:
- No: