Skip to content

Knowledge Centre · Start here

Introduction to the series

The field notes are a technical curriculum in systematic trading, from the first test of an idea to a strategy running with real money. Claims rest on public data and primary research, and figures come with their code.

Audience

Who the notes are for

We write for engineers, analysts and students who plan to research and run systematic strategies themselves. We assume you are comfortable with Python and pandas, with basic statistics and probability, and with the material of a first course in finance: returns, portfolios, leverage and the Sharpe ratio.

The notes are not an introduction to investing and contain no trade ideas. If Python or basic statistics are new to you, learn those first. Everything here is general, and a technique that suits one portfolio can be wrong for another.

Tracks

Five tracks, one reading path

Each track answers one question a working trader faces. On the map each note is a star and each track a constellation, and the lines trace the reading path from this introduction, the fixed point.

A map of the field notes as a night sky: the Introduction is the fixed star, each track is a constellation, and the lines follow the reading path. Use the arrow keys to move from star to star. The same notes are listed in full below.

The curriculum as a night sky: each note a star on its track’s orbit about this introduction, the reading path drawn as the lines. The same notes are listed by track below.

Foundations

Which ideas deserve to be traded, and how should they be tested?

Research infrastructure

What runs a backtest, and how do you keep thousands of them reproducible?

Portfolio construction and risk

How large should each position and each strategy be, and what limits the downside?

Execution

What does trading cost, and how do you measure and reduce it?

Production operations

Once real money is at stake, how do you know the system is doing what the research said it would?

Reading path

The reading path

Later notes assume the earlier ones unless their prerequisites say otherwise.

  1. FoundationsMarket anomaliesWhich return sources have held up, and why do most published ones fade?
  2. FoundationsData for systematic tradingWhat has to be true of the data before a backtest can be believed?
  3. FoundationsIndicators and the 200-day moving averageHow do you turn an idea into a rule, and test it without look-ahead or hidden costs?
  4. Research infrastructureQuantConnect and LEANWhat engine runs one algorithm in backtest and live, and what must you check before trusting it?
  5. Research infrastructureRunning backtests at scaleHow do you run thousands of backtests and still trust the results?
  6. Portfolio construction and riskVolatility targetingHow large should a position be?
  7. Portfolio construction and riskBuilding strategies from componentsHow do you build a strategy from parts that can be tested and replaced separately?
  8. Portfolio construction and riskCombining strategies into one bookHow much capital should each strategy get, and what happens when strategies trade the same instruments?
  9. ExecutionTWAP, slicing and jitterWhat does a trade really cost, and how do you measure it?
  10. Production operationsGoing liveHow does a tested strategy become one that trades real money, and how is it stopped or rolled back?
  11. Production operationsMonitoring a live bookWhat should be checked every trading day once real money is at stake?
  12. Production operationsAlerting that people act onWhich conditions deserve to interrupt someone, and how do you keep alerts trusted?
  13. Production operationsLive versus backtest reconciliationWhy do live results differ from the simulation, and when does the difference matter?

Shortcuts

Inside a note

What to look for

Abstract and key takeaways
The first screen of every note states the argument and its conclusions. If the takeaways are familiar, skip to the sections that are not.
Before you start
The background each note assumes, and the notes it builds on.
Notation
Symbols mean the same thing in every note; the table below is the reference.
Code listings
Python with pandas and NumPy, labelled with the file each listing comes from. Where a listing produced a number, it ran on the public data or the simulator named beside it, so you can reproduce the figure.
Interactive labs
Each lab’s caption suggests experiments. Change one setting at a time, and predict the result before you look.
Step-by-step figures
Each note’s key argument is a figure that builds up as you read its numbered steps. Without script, or with reduced motion, it shows its final state and the steps read as ordinary text.
Evidence and caveats
Results come with their limits: the sample, the sensitivity to parameters, and the conditions under which a technique fails.
References
Primary sources, cited where they are used and listed at the end with a DOI or a link.

Standards

How the notes are written

  • Claims about markets rest on public data or primary research, and the source is named where the claim is made.
  • Signals use only data available at the time, and costs are modelled rather than assumed away.
  • Failures, decay and weak periods are reported alongside what worked.
  • Every figure built from data can be reproduced from the code shown with it.
  • The notes describe published methods, not the rules or parameters of our strategies.

Notation used throughout

rₜsimple return over period t (daily unless stated)
Pₜprice or total-return index at the close of t
wₜexposure held over period t, decided at the close of t − 1
σ, σ̂ₜannualised volatility; its forecast made with data up to t − 1
SRSharpe ratio: mean excess return over its standard deviation, annualised
Tlength of a sample in years; N the number of trials or slices; n the number of observations
bpbasis point, 0.01%

The series

How it grows

Notes are cited by title, and their addresses do not change. New notes take their place on the reading path as they are published.

Begin with Market anomalies →