How many distinct dimensions does your angle really have?
HEC Montréal
Everything you need to type is on one sheet — how to start Python in VS Codium on your platform, how to make a file and run it, the DataFrame basics, and every name from sessions 1 to 13, each with a line showing it in use.
Python Cheatsheet · Session 13 (PDF) · in the repository at
13-…/PYTHON-CHEATSHEET.pdf
One sheet per package, functions explained with pictures: pandas · NumPy · matplotlib · prince · scikit-learn · statsmodels
Print it, or keep it open beside the editor. Nothing on it is examinable; all of it is assumed.
| 00–20 | Reproduce | one result from the paper you read |
| 20–55 | Apply | the method, to your own angle |
| 55–70 | Break | one assumption, deliberately |
| 70–90 | Write, and report | 250 words, then two minutes to the room |
The presenter is drawn at random when your group is called. All three of you prepare.
Everyone pushes at least once. Replace XX with your group number — group 07 uses group-07.
PowerShell’s mkdir creates the intermediate folders already, and rejects -p. The git log is the participation record. It is not a formality.
Take the result the paper rests on, and put it to the test on the database the paper itself uses. There is nothing to unzip — the loader has it.
Paper: Gygli, Haelg, Potrafke & Sturm (2019), The KOF Globalisation Index — revisited, Review of International Organizations 14(3) · data: qmib.load("kof")
A failed reproduction that you diagnose earns full marks. One you do not attempt earns none.
“It did not work” is not a diagnosis. Where did it stop, and what did you check?
core = qmib.load("core")
mine = qmib.load("angle_c_country") # your angle — see your dictionary
df = core.merge(mine, on=["geo", "time"], how="inner")Fit the session’s method on your data, and report what the lecture said to report — in the units of your own variables.
A coefficient without units is not a finding.
Every method in this course rests on something.
Find the assumption this one leans on hardest. Break it deliberately. Record what happened to your answer.
This is the part that carries the marks. A group that shows how its result falls apart understands it; a group that only shows it holding does not yet know.
250 words in your submissions folder:
And the standing rule: one LLM output you identified as wrong, and how you established that.
git add groups/A2026/group-XX/session-13
git commit -m "Session 13 practice — group XX"
git push -u origin group-XXDeliverable. A dimension-reduction of your project’s indicators: the scree plot, the number retained with its justification, the loadings interpreted, and a note on what you are not entitled to call the components.
And everywhere in this course: an association described in causal language.
| One number | with its units and its uncertainty |
| One assumption | the one you broke, and what happened |
| One limit | what you cannot claim from this |
Listen for traceable evidence, not confidence of delivery.
The QMIB Lab has a knowledge check on what you have just done: warin.ca/qmib-labs
Optional, never a prerequisite for the next lecture, and never marked for correctness. A completed report counts because attempting it is the engagement being measured — it is one of the three routes to the participation mark.
What is required before the next session: the article, its Dataverse package, and the self-check. That is the pre-session deck, not this.
MATH60033A · Session 13 practice · Thierry Warin, PhD · HEC Montréal