<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[Forex Software — Genetic Selection… the next rabbit hole]]></title>
	<link rel="self" href="https://forexsb.com/forum/feed/atom/topic/10079/" />
	<updated>2026-06-01T10:55:10Z</updated>
	<generator>PunBB</generator>
	<id>https://forexsb.com/forum/topic/10079/genetic-selection-the-next-rabbit-hole/</id>
		<entry>
			<title type="html"><![CDATA[Genetic Selection… the next rabbit hole]]></title>
			<link rel="alternate" href="https://forexsb.com/forum/post/83323/#p83323" />
			<content type="html"><![CDATA[<p>Full disclosure: I got Claude to write this up, because I fancied documenting my failures about as much as you&#039;d expect. The journey&#039;s mine though — promise.</p><p>I wanted to share where I&#039;ve gotten to and ask the people who&#039;ve gone further than me for some pointers.</p><p>Chapter 1 — The textbook pipeline. Built the full walk-forward: In-Sample to generate, Out-of-Sample to filter, a true held-out Forward as the final judge. Multi-asset, multi-timeframe, multiple brokers&#039; data, Monte-Carlo, all of it. The plumbing&#039;s solid — I&#039;ve stress-tested it.</p><p>Chapter 2 — Rich pools don&#039;t translate. I can churn out big, healthy-looking pools: nice IS curves, survive OOS, pass the usual robustness gates. But none of that richness carries into Forward. Every metric I&#039;d rank on (expectancy, R²/linearity, stability ... I (think) I&#039;ve tried them all) shows basically zero correlation with what the strategy actually does forward.</p><p>Chapter 3 — ML didn&#039;t save it. So I did the obvious next thing: build features from the IS/OOS walk-forward behaviour, label by forward outcome, train a model to pick survivors. Same wall. The IS side (IS/OOS degradation etc) just doesn&#039;t carry enough signal about the future. The model can re-rank a useless ranking, but it can&#039;t invent signal that isn&#039;t there.</p><p>Chapter 4 — A genetic-selection wrapper around gen.js. Latest move: I wrapped gen.js in my own GA — breeding strategies generation-to-generation with my own fitness functions, instead of leaning on the built-in search. Lots more control, and some encouraging signs… but I keep bumping into the same questions about what to actually select on, which is why I&#039;m here.</p><p>The questions:</p><p>1. Any IS/OOS metric that actually correlates with forward, not just looks good in backtest?<br />2. Shorter / more recent in-sample windows — do they transfer better for you than long ones?<br />3. Is the real edge in constraining what you generate (skeletons, regime typing, indicator grammar) rather than filtering after?</p><p>Happy to share more on the methodology. Where am I being naive?</p><p>Cheers.<br />Ben</p>]]></content>
			<author>
				<name><![CDATA[begoodall]]></name>
				<uri>https://forexsb.com/forum/user/16312/</uri>
			</author>
			<updated>2026-06-01T10:55:10Z</updated>
			<id>https://forexsb.com/forum/post/83323/#p83323</id>
		</entry>
</feed>
