Skip to content

Code presentation improvements: Bayesian ML, Gaussian Distribution - #154

Merged
fonsp merged 6 commits into
mainfrom
code-presentation-improvements-22-aug-2025
Aug 25, 2025
Merged

Code presentation improvements: Bayesian ML, Gaussian Distribution#154
fonsp merged 6 commits into
mainfrom
code-presentation-improvements-22-aug-2025

Conversation

@fonsp

@fonsp fonsp commented Aug 22, 2025

Copy link
Copy Markdown
Member

Working on:

  • Gaussian Distribution (code changes, but not 100% happy with this one yet, because the example is not so spectacular. We should think of a new example together.)
  • Probability Theory (no big changes)
  • Bayesian ML 🌟 This one is completely restructured with more visible code, results, structure etc.

@fonsp
fonsp marked this pull request as ready for review August 22, 2025 15:53
@fonsp
fonsp requested a review from bertdv August 22, 2025 15:53
@fonsp fonsp mentioned this pull request Aug 22, 2025
13 tasks
@fonsp fonsp changed the title Code presentation improvements Code presentation improvements: Bayesian ML, Gaussian Distribution Aug 22, 2025
@bertdv

bertdv commented Aug 25, 2025

Copy link
Copy Markdown
Collaborator

Generally, I think it is a great update! Well done and thanks. Some specific issues for discussion on Bayesian ML Lecture (for each issue I added a screenshot of what I saw):

  • Please move the optional slide on KL divergence to a mini. In general, important background materials that hinder the narrative of the lecture should preferably be moved to minis. In this case, teh KL divergence is important and I lke to refer to it from mulitple lecrtures, therefore I dont like it as an optional slide in the BML lecture.

  • I prefer not to see any using package in the middle of the lecture notes. Can we move all using packages to the Appendix cell? Also, (optionally) perhaps use sliders in one of the graphs to change alpha and beta.

Screenshot 2025-08-25 at 10 29 18

-[ ] I am happy with showing code per default for model specification, but I rather not interrupt the narrative to show other code, such as how many samples, and numerical values of the outcomes (BTW the outcomes should be 1's and 0's, not TRUE and FALSE, since we coded head as 1).

Screenshot 2025-08-25 at 10 34 22 Screenshot 2025-08-25 at 10 35 22
  • I don't like to show numerical values for outcomes and inference results per default, especially for vectors. Perhaps we can make the below a "click for ..."-box instead? After inference, I like to show the results immediately by a graph.
Screenshot 2025-08-25 at 10 37 43
  • This is the graph we should show as results, immediately after inference:
Screenshot 2025-08-25 at 10 40 36
  • same here. Let's show the graph, but not the numerical evidences. Numerical values of evidence are also not important, it's about the comparison to evidence for another model.
Screenshot 2025-08-25 at 10 41 52

**In short, I like what you have done very much, but I suggest the following for Code examples:

  1. show code of model specification (and optionally refer to the equations in the lecture).
  2. show code for inference procedure as optional: "Click for code of inference procedure"
  3. show inference results in a graph (usually for the posterior). Ideally, with a slider to play.**

@fonsp
fonsp merged commit 0fc98aa into main Aug 25, 2025
1 check failed
@fonsp
fonsp deleted the code-presentation-improvements-22-aug-2025 branch August 25, 2025 14:16
@fonsp

fonsp commented Aug 25, 2025

Copy link
Copy Markdown
Member Author

I implemented the changes from our call, merging this 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants