<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[Forex Software — FSB v4.2.0.3 unstable - beta tests]]></title>
		<link>https://forexsb.com/forum/topic/77/fsb-v4203-unstable-beta-tests/</link>
		<atom:link href="https://forexsb.com/forum/feed/rss/topic/77/" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in FSB v4.2.0.3 unstable - beta tests.]]></description>
		<lastBuildDate>Thu, 19 Apr 2007 17:40:24 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/379/#p379</link>
			<description><![CDATA[<p>The v4.2.0.3-2 unstable is published (with small corrections) as&nbsp; FSB v4.2.2.0.</p>]]></description>
			<author><![CDATA[null@example.com (Popov)]]></author>
			<pubDate>Thu, 19 Apr 2007 17:40:24 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/379/#p379</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/376/#p376</link>
			<description><![CDATA[<p>Sounds good.<br />But dont be discouraged by all this - I still think even with all that, that it has a great potential, just need to put accuracy as a priority - the rest will follow.</p>]]></description>
			<author><![CDATA[null@example.com (DannyBens)]]></author>
			<pubDate>Thu, 19 Apr 2007 16:39:59 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/376/#p376</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/375/#p375</link>
			<description><![CDATA[<p>So, I thing to mark them as dangerous and to publish this v4.2.0.3-2 as final.</p><p>I&#039;ve put a link to the &quot;Safety First&quot; forum on the website&#039;s front page&nbsp; and also I thing to make a direct link to it from the program.</p><p>We have to explain all dangerous aspects to the unexperienced users.</p>]]></description>
			<author><![CDATA[null@example.com (Popov)]]></author>
			<pubDate>Thu, 19 Apr 2007 15:52:32 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/375/#p375</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/374/#p374</link>
			<description><![CDATA[<p>Yes, I think you should mark these for demo. People seem to be counting on them now, so its best if they know the status and not be overly optimistic about their systems.</p><p>- If the exit has passed (open price of next bar is higher than the PT or lower than the SL) then you exit at open (overshoot)<br />- If both levels reached at the next bar, you assume the worst and mark this as a loss, since you have no way of knowing for sure which one hit first.<br />- If no level was reached on the next bar, you continue the logic to the following bar</p>]]></description>
			<author><![CDATA[null@example.com (DannyBens)]]></author>
			<pubDate>Thu, 19 Apr 2007 15:42:30 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/374/#p374</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/372/#p372</link>
			<description><![CDATA[<p><em>Stop at the next bar</em> is a solution except in the case when the levels have been passed. <br />- If the exit (stop or limit) is not reached in the current bar - the problem is transfered to the next bar (if both levels are in both side of the open price)<br />- if a level has been passed - where to close?&nbsp; It seems - the opening price is the best place.</p><p>And lot to do if the user set Stop Limit +-5 pips? The deep scan cannot help us here, except a tick scan!</p><p>This situation has to be changed as soon as possible! The fastest is to mark the &quot;Stop Limit&quot; and &quot;Take Profit&quot; as &quot;For demo only!!!&quot; like Fibonacci.</p>]]></description>
			<author><![CDATA[null@example.com (Popov)]]></author>
			<pubDate>Thu, 19 Apr 2007 15:20:36 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/372/#p372</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/371/#p371</link>
			<description><![CDATA[<p>You are correct. The best solution is to look into a deeper time frame, to figure out the execution order.<br />But, the current implementation, not only that it is not safe, it is completely misleading.</p><p>I know, it is nice to have many beginner strategy writers come to this forum and share their 5-minute get rich strategy, and get all excited about something that will never work in real life, but I believe there should be a different approach here.</p><p>Accuracy of backtesting should come first. Nice GUI, fancy indicators and other bells, are nice but are only a secondary priority. Always.</p><p>So, to answer your question - I think that stop/limit exits cannot be removed from FSB - these are the basic exit rules and must stay there.</p><p>One solution that is possible (without deep scan) is to do the following:<br />1. Assume the worst possible execution order<br />2. Apply stops at next bar only.</p><p>This means that once you enter the trade, it stays &quot;naked&quot; until the next bar, then, the next bar has a logic of:<br />&nbsp; &nbsp; if not SellAtStop then SellAtLimit</p><p>Which means, if the next bar hits both limit and stop orders, it is considered a loss since you have no way of knowing which one hit first.</p><p>Of course, if you plan on doing a deep scan sometimes soon, I wouldnt bother working on this logic, since it has its own inaccuracies - only in this inaccuracy case, it is a pessimistic inaccuracy rather than an optimistic one, so if a user will be able to make a working strategy, there is more chance it will actually work in real life.</p>]]></description>
			<author><![CDATA[null@example.com (DannyBens)]]></author>
			<pubDate>Thu, 19 Apr 2007 14:51:34 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/371/#p371</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/370/#p370</link>
			<description><![CDATA[<p>The problem of <em>Stop Limit</em> is coming from the interpolating algorithm&#039;s inability to find the right order of exit prices (in the same bar). <br />This problem can be fixed with an in-deep scanner (lower periods searching).</p><p>Do you know other solution?<br />Or, to mark the indicator as unsafe! (Remove it from FSB!!)</p><p>The same logic is used in the derivative indicators: <em>Stop Loss</em> and <em>Take Profit</em></p><p>The <em>Stop Limit</em> in older versions before 2.4.0.3-2 send unlimited exit order. In most cases this is not problem, but is possible the position to be closed/reversed earlier by the opposite signal.</p><p>Example:<br />&nbsp; buy at: 1.0100<br />&nbsp; Stop Limit: +-50</p><p>if the position has been closed at 1.0140 (by an opposite entry signal), the exit orders are not canceled. FSB will cancel it when the market touch the exit price (FSB cancels an exit order when there is no open position). </p><p>If the position has been reversed at 1.0110&nbsp; FSB sends buy exit orders at 1.0160/1.0060<br />The problem is coming&nbsp; when the market reaches the nearest exit 1.0150 (from the initial position) and we are short, but we have a sell exit order?!? I think FSB calculates this situation correctly, but I&#039;m not so sure.</p><p>The new version sends valid to the end of the period orders. And if there is reversing before the exit FSB simply sends the new exit orders.</p><p>We need more tests to be sure that the new logic works well!</p><p>This does not cover the closing in the same bar problem!</p><p>edit:<br />The exit logic does not average the exit levels (if the position&#039;s amount has been changed).<br />FSB is very strict to the exit signals. It cannot increase, reduce or reverse the existing position. An exit signal is &quot;exit&quot; - close all the open lots.</p>]]></description>
			<author><![CDATA[null@example.com (Popov)]]></author>
			<pubDate>Thu, 19 Apr 2007 14:03:34 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/370/#p370</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/367/#p367</link>
			<description><![CDATA[<p>Popov - can you specify a little more about &quot;logic improved&quot; for the stop and limit?<br />This is one of the biggest achilles heels in FSB, and I believe this is causing the euphoria in this forum that suddenly everybody is a successful system builder.</p>]]></description>
			<author><![CDATA[null@example.com (DannyBens)]]></author>
			<pubDate>Thu, 19 Apr 2007 12:44:48 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/367/#p367</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/345/#p345</link>
			<description><![CDATA[<p>Can the optimization function have an option to optimize over a certain period, aim is to get a strategy with a as straight line upward as possible.</p>]]></description>
			<author><![CDATA[null@example.com (Melvin Lau)]]></author>
			<pubDate>Wed, 18 Apr 2007 06:50:05 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/345/#p345</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/342/#p342</link>
			<description><![CDATA[<p>FSB v2.4.0.3 - 2 Unstable, released on 2007-04-18</p><p>Changes with Forex Strategy Builder 2.4.0.3 - 2 Unstable</p><p>&nbsp; * More symbols - added<br />&nbsp; * Take Profit - logic improved<br />&nbsp; * Stop Loss - logic improved<br />&nbsp; * Stop Limit - logic improved<br />&nbsp; * Trailing Stop -&nbsp; logic improved<br />&nbsp; * Close logic conditions - only when the &quot;Closing point of the position&quot; is &quot;Bar Closing&quot;</p>]]></description>
			<author><![CDATA[null@example.com (Popov)]]></author>
			<pubDate>Tue, 17 Apr 2007 23:42:58 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/342/#p342</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/333/#p333</link>
			<description><![CDATA[<p>Melvin is right.</p><p>We need some kind of warning when are doing something unusual (unsafe). <br />-- zero swap<br />-- zero spread<br />-- Manual operating with &quot;Use prev. bar value&quot;<br />-- some non-logical indicators (if any)!<br />...</p>]]></description>
			<author><![CDATA[null@example.com (ccjuce)]]></author>
			<pubDate>Tue, 17 Apr 2007 19:15:37 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/333/#p333</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/332/#p332</link>
			<description><![CDATA[<p>What is this 0 pips spread in the Stable and 4 in Unstable?!? <br />The spread and the swap values are of your choice.&nbsp; When you save your strategy with 0/0 spread/swap it will be loaded next time with the same values. <br />I think the default values are 4/1. But of course you can override your default strategy (New.xml) with other numbers.</p><p>Be careful!!</p>]]></description>
			<author><![CDATA[null@example.com (Jar Jar)]]></author>
			<pubDate>Tue, 17 Apr 2007 18:30:05 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/332/#p332</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/331/#p331</link>
			<description><![CDATA[<p>Now I know why the optimizer behave this way, for the stable version, it do charge any cost for Spread &amp; Swap whereas in the unstable version it is 4 pips for Spread and 1 for Swap Numbers. [ Maybe the user have to be warn to include cost of transaction in the attempt to come up with wining strategy, else it don&#039;t work in real trading)</p><p>No wonder it was so easy to make money using the stable version. I was &quot;making&quot; in excess of 70K pips for EURUSD M1 in 20 days</p><p>But still FSB is the easiest way for a novice like me who don&#039;t fully under what spread &amp; swap number are, to come up with a wining forex strategy.</p><p>For USDCHF Daily it make 34,670 pips over ~30 yrs averaging&nbsp; 1,100 pips per year and the profit line is a straight line up. Using risk managing technique ( a feature I had earlier requested) I am sure it could grow to a much higher number than this.</p><br /><p><strong>Forex Strategy Builder V 2.4.0.3-1 Unstable</strong><br />Strategy name: <strong>Daily_30K_AllCurrency</strong><br />Exported on: 4/18/2007 2:00:48 AM</p><p>Market: USDCHF 1 Day<br />Spread: 4 pips<br />Swap Number: 1 pip</p><p>Balance: <strong>34670</strong> pips<br />Minimum account: -17 pips<br />Maximum drawdown: 589 pips<br />Time in position: 44 %</p>]]></description>
			<author><![CDATA[null@example.com (Melvin Lau)]]></author>
			<pubDate>Tue, 17 Apr 2007 18:20:16 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/331/#p331</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/329/#p329</link>
			<description><![CDATA[<p>The optimizer uses no liner, random algorithm to find the extreme value. You have to try several times. This algorithm can reach maximum optimization for minimum time, but it may not succeed in the first try. </p><p>The best usage of optimizer is to start it 2-3 times. After that if the values are near to the limits adjust it and try again 2-3 times.</p><p>If the result is not so good, you have to start from the initial values (cancel the optimization and again).</p><p>You can test the strategy for curve fitting by changing the parameters one by one a little bit up and down. If there is a significant change of the performance the strategy is over-optimised.</p>]]></description>
			<author><![CDATA[null@example.com (Popov)]]></author>
			<pubDate>Tue, 17 Apr 2007 15:20:32 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/329/#p329</guid>
		</item>
		<item>
			<title><![CDATA[Re: FSB v4.2.0.3 unstable - beta tests]]></title>
			<link>https://forexsb.com/forum/post/326/#p326</link>
			<description><![CDATA[<p>he optimizing function in the unstable did not perform like that in the stable function, it fail to find the optinum value the stable function found.</p><p>When I tranfer the strategy file from the stable version to the unstable version, the unstable version gave the same result. Hence I have to conclude that the is some issue with the coding of the optimizing function in the unstable function.</p>]]></description>
			<author><![CDATA[null@example.com (Melvin Lau)]]></author>
			<pubDate>Tue, 17 Apr 2007 14:14:38 +0000</pubDate>
			<guid>https://forexsb.com/forum/post/326/#p326</guid>
		</item>
	</channel>
</rss>
