Reflect on Day 3

Author: richelbilderbeek

evaluations/20260423_day_3/README.md

@@ -21,37 +21,79 @@
 
 - good
 - good
-- Richèl's sessions had a good pace, the rest were way too fast with too little time for exercises and too little time for breaks.
+- Richèl's sessions had a good pace,
+  the rest were way too fast with too little time for exercises
+  and too little time for breaks.
 - more practice
 - good
 - Good, did well balancing levels across a large group
-- I like the way that Richèl is teaching. He makes the concepts clear and you can follow his instructions and learn. However, I cannot follow the class when Bjorn is teaching, I feel very lost.
+- I like the way that Richèl is teaching.
+  He makes the concepts clear and you can follow his instructions and learn.
+  However, I cannot follow the class when Bjorn is teaching, I feel very lost.
 - The overall pace was OK
 - Pace seems to be OK, it's probably me who is slower than the pace :)
 - A bit uneven. I think more time is needed
 - OK
 
-
 ### [Future topics](future_topics.txt)
 
 - We did not even get to practice what is already in the course properly
 - GNNs
-- More information about how analyze big data such as genomic or transcriptomic data.
-- More examples on how to run Python codes as batch jobs. More about finding modules
+- More information about how analyze big data such as genomic
+  or transcriptomic data.
+- More examples on how to run Python codes as batch jobs.
+  More about finding modules
 - USPEX
 
-
 ### [Other comments](comments.txt)
 
-- more cases, like, an oom killed job , how to seff it and solve the issue to run it properly
-- Use Richèl's teaching style for all topics. Keep the amount of content in the course as it is, but spread it over 5 days instead of 4 days. There's simply way too much to go through, way to many potential technical difficulties that take time, and way too little time to do exercises to actually absorb all the content and enjoy the learning process. And I would suggest that the course on how to connect and work in an HPC environment be moved to before this course during the same semester, so that people don't have to deal with having to learn that at the same time. Right now the "Online training events for new users: NAISS Introduction training days" course is after this course during the semester, which makes little sense considering that its contents should be a prerequisite for this course.
+- more cases, like, an oom killed job,
+  how to seff it and solve the issue to run it properly
+- Use Richèl's teaching style for all topics.
+  Keep the amount of content in the course as it is,
+  but spread it over 5 days instead of 4 days.
+  There's simply way too much to go through,
+  way to many potential technical difficulties that take time,
+  and way too little time to do exercises to actually absorb
+  all the content and enjoy the learning process.
+  And I would suggest that the course on how to connect and work
+  in an HPC environment be moved to before this course during the same semester,
+  so that people don't have to deal with having to learn that at the same time.
+  Right now the "Online training events for new users:
+  NAISS Introduction training days" course is after this course during
+  the semester, which makes little sense considering that its contents
+  should be a prerequisite for this course.
 - Where should we improve? materials, exercises, and structure
-- For me personally, the time spent interacting with the cluster and getting familiarised was the most useful. This is personaly though an I'm not sure whether this would be the case across the board.
-- Today (day3), the topics were more of what I expected from an Introduction to Python and Using Python in an HPC environment course. The morning session about pandas, matplotlib and seaborn was interesting, as well as the big data with python. I will probably use Dask in the future so it was a good explanation of how Dask works. I still don't understand the time spent talking about bash and sending jobs. We could use that time learning and using common python packages in an HPC cluster.
-- It think that we need more documentation about Dardel. Also, we need more hands-ons and demonstrations.
-- I feel some exercises are not in "step-by-step" format that makes difficult to complete it.
-- I think there is very little material on the pandas/matplotlib/seaborn part and would like there to be more so I can redo it later myself. This just tells you were to go look for the info and that could be put in a box at the bottom. I am not fond of the way Richel teaches (sorry - he is very nice). I prefer to have more theory and material to read and then also show some demos. Maybe if there was more time for this course. I really think you should have it a full week.
-- At first I didn't understand why we need to learn about batch since most people use IDEs now but I realized that batch is also part of HPC and that there may be some people who still submit jobs to batch and doesn't just work in jupyter
+- For me personally, the time spent interacting with the cluster and
+  getting familiarised was the most useful.
+  This is personaly though an I'm not sure whether this would be the case
+  across the board.
+- Today (day3), the topics were more of what I expected from an
+  Introduction to Python and Using Python in an HPC environment course.
+  The morning session about pandas, matplotlib and seaborn was interesting,
+  as well as the big data with python.
+  I will probably use Dask in the future
+  so it was a good explanation of how Dask works.
+  I still don't understand the time spent talking about bash and sending jobs.
+  We could use that time learning and using common python packages
+  in an HPC cluster.
+- It think that we need more documentation about Dardel.
+  Also, we need more hands-ons and demonstrations.
+- I feel some exercises are not in "step-by-step" format
+  that makes difficult to complete it.
+- I think there is very little material on the pandas/matplotlib/seaborn part
+  and would like there to be more so I can redo it later myself.
+  This just tells you were to go look for the info and
+  that could be put in a box at the bottom.
+  I am not fond of the way Richel teaches (sorry - he is very nice).
+  I prefer to have more theory and material to read and
+  then also show some demos.
+  Maybe if there was more time for this course.
+  I really think you should have it a full week.
+- At first I didn't understand why we need to learn about batch
+  since most people use IDEs now but I realized that batch
+  is also part of HPC and that there may be some people who still submit jobs
+  to batch and doesn't just work in jupyter
 
 ## [Any other feedback](any_other_feedback.csv)
 

evaluations/20260423_day_3/analyse.R

@@ -182,21 +182,14 @@ ggplot2::ggplot(
 
 ggplot2::ggsave(filename = "average_confidences_per_question.png", width = 7, height = 7)
 
-
-t_sessions_taught <- unique(t_tidy$question)
+success_score <- mean(t_tidy$answer) / 5.0
+readr::write_lines(x = success_score, "success_score.txt")
 
 # Cut out sessions if needed
-#t_sessions_taught <- stringr::str_subset(t_sessions_taught, "Pandas|Seaborn|matplotlib")
+t_sessions_taught <- stringr::str_subset(t_sessions_taught, "Pandas|Seaborn|matplotlib")
 
 testthat::expect_true(all(t_sessions_taught %in% t_tidy$question))
 
 confidences_on_taught_sessions <- t_tidy |> dplyr::filter(question %in% t_sessions_taught)
 success_score <- mean(confidences_on_taught_sessions$answer) / 5.0
-readr::write_lines(x = success_score, "success_score.txt")
-
-
-
-
-
-
-
+readr::write_lines(x = success_score, "success_score_richel.txt")

evaluations/20260423_day_3/success_score_richel.txt

@@ -0,0 +1 @@
+0.66

evaluations/all_courses_so_far/README.md

@@ -95,4 +95,3 @@
 A wordcloud of all the words in the comments.
 
 ![Wordcloud](wordcloud.png)
-