A colleague needs more than your code to reproduce a return or risk estimate. The dataset, package versions, configuration and random seed can all affect the result. This lesson records those inputs and checks a run from clean state. A virtual environment isolates packages; Git identifies the code revision.
Learning objectives. By the end of this note you should be able to identify the ingredients of a reproducible run, inspect versions and explain why a fixed seed is necessary but insufficient.
In this lesson
- Record the computational contract
- One command, clean state
- A seed is only one run input
Before you start
The full lesson, with worked examples and exercise solutions, is for members.
Read the full lessonNew to SelfMadeQuant.com? See membership options or browse the Python and Data Primer syllabus.