<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[Forex Software — Calling Geektrader!!]]></title>
		<link>https://forexsb.com/forum/topic/7786/calling-geektrader/</link>
		<atom:link href="https://forexsb.com/forum/feed/rss/topic/7786/" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Calling Geektrader!!.]]></description>
		<lastBuildDate>Tue, 09 Apr 2019 21:57:11 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Calling Geektrader!!]]></title>
			<link>https://forexsb.com/forum/post/55064/#p55064</link>
			<description><![CDATA[<p>Hi Geek, </p><p>I was doing some reading on the forum and saw you mention a new strategy you have or creating hundreds of EA Studio strategies and putting them live knowing that 60% or so will fail but playing the numbers game. </p><p>I’d love to further discuss this with you as I for one have taken the approach of generating millions of strategies with very strict criteria (performing Almost as well in 20%oos, as well as across at least 5/20 markets). <br />I have only been using this approach for a month or so so I cannot come to any definitive conclusions as to how well this works. </p><p>I have loved reading you posts in the ‘success stories’ thread about your approach on massive amounts of backtesting data as well as multi market testing.<br />However I am a bit confused as these two approaches of yours seem to contradict one another in the way that the timeframe you mentioned you built 100 strategies to use seemed very short. I may be wrong however. </p><p>I have taken your approach of as much backtesting data I can get my hands on and bought myself a Threadripper <img src="https://forexsb.com/forum/img/smilies/smile.png" width="15" height="15" alt="smile" /></p>]]></description>
			<author><![CDATA[null@example.com (Michael1)]]></author>
			<pubDate>Tue, 09 Apr 2019 21:57:11 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/55064/#p55064</guid>
		</item>
	</channel>
</rss>
