<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Statistical-Arbitrage on Jonathan Franklin</title><link>https://jonnie.github.io/tags/statistical-arbitrage/</link><description>Recent content in Statistical-Arbitrage on Jonathan Franklin</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 30 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jonnie.github.io/tags/statistical-arbitrage/index.xml" rel="self" type="application/rss+xml"/><item><title>Statistical Arbitrage Strategy</title><link>https://jonnie.github.io/work/statistical-arbitrage-strategy/</link><pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate><guid>https://jonnie.github.io/work/statistical-arbitrage-strategy/</guid><description>&lt;h2 id="problem"&gt;Problem&lt;/h2&gt;&#10;&lt;p&gt;Pricesearcher wanted to research statistical arbitrage as another strategy for its FX/CFD trading operation. The approach measures a pair&amp;rsquo;s spread as a z-score, enters when it moves away from its recent range, and seeks an exit as it reverts. The difficult part is assessing whether that relationship persists, how execution and risk settings affect the result, and what happens when several setups share an account.&lt;/p&gt;&#10;&lt;h2 id="architecture"&gt;Architecture&lt;/h2&gt;&#10;&lt;p&gt;Research workflows load and resample bar data, rank pairs and feed backtesting tools. Scheduled AWS services run the signal engine against the &lt;a href="https://jonnie.github.io/work/mt5-ohlcv-pipeline/"&gt;S3 bar lake&lt;/a&gt;, while an on-demand service uses the same engine for historical inputs. MQL5 and Python engines execute configured setups, with trade-level reporting and Slack monitoring closing the review loop.&lt;/p&gt;</description></item></channel></rss>