That's a very good idea!

I second to Togr! There should be a way to select a base parameter which prevails. Now there's only the equity or highest profit and it overrides all the other limitations.

Thanks Togr for bringing and reminding me of this.

Hi Mr Popov,
how do you think about this.

You can use a fitness function, it will be a combination of some parameters.

for example.

A strategy is good if
a) drawdown is low
b) the equitycurve is good
c) the symetry is good
d) the percentence of trades in ISS and OSS is nerarly the same

Strategy fitness= (attribute a * faktor1) + (attribute b * faktor2) + (attribute c * faktor3) + (attribute d * faktor4)

In the generationprocess you generate a list of found strategies.
For example you produce 100 strategies in the list and sort this list for this fitniss criterium.

If you found more than 100 strategies you throw out the strategies with bad fitniss.

You can say the optimizer reject strategies with fitnesslevel < X

You can use some configurable limitations for the process.
for example.

mintrades =300, maxtrades=600
minsymetry=30%
equtiycurve (you can take criterium from FSB)

thomas

Any ideas how can easily provide nightly build of FSB Pro.

I'll have several months vacation from my main work and will concentrate on FSB Pro development.
I'll be probably able to publish new features every several days, but standard update process is too cumbersome. I also do not to embarrass regular users with very frequent updates with small added value.

Uploading somewhere update file and a post in forum will be enough I think. Any ideas?

I think it will be one of the most important modifications '' fitness thing'' , But and tell me if iam wrong it will depends on when the fitness function will be applied is it applied before finding the top strategies or it will be done after finding the top strategies and at that time it will be some sort of indexing and sorting of top strategies

fantastic , so adding a new  strategy to top will not limited to one criteria which is to exceeds the previous higher strategy returns in the top list but instead it will be a portfolio of fitness criteria s including profits

nice addition

I want to make better update system for FSB Pro. Something like Chrome and Firefox.

Program to check for updates at startup.
If there is a new update, to download the new files.

There are two variants here:
1. To download installer and to run it at next startup.
2. To download files. To extract and replace them silently.

This will be next my task.

My guess is  that the optimizer is the weak point of the FSB.

My proposal is to use a genetic optimizer with settable parameters.(population size, max generations, fitness functions, etc) , and most important , a WFA (walk forward analyser) module.
FSB generates too many "good strategies" that are very difficult to verify without having a method of measuring their robustness (WFE). I mean the old principles of Robert Pardo.
There are many examples of WFO / WFA / CWFA applications, but I think the best is the one implemented by Wouter Oosthuizen in GWFO and then in TradeStation.He is the one who made many years ago CASB (Computer Assisted Strategy Builder) for Easy Language.
In my opinion, FSB + good WFA module = best product on the market.

Where's LTF function in position opening and closing slots?

Indicator window/tab/sheet should close not only with the arrow and ok/cancel buttons, but when click is made outside of its boundaries.

100% agree with that.
The biggest issue I see now is that we have to go to Editor Page in order to edit a trading strategy.
I'm considering redesign of the Trader Page:

Connection panel will go to the left and Strategy panel will go to the middle.
I'll introduce a Quick Edit button in the center of the menu.
The Quick Edit function will stop trading and disconnect current connections. It will allow also clicking on the slots and showing options Dialog Panel on the left side (like in Editor).
When we finish with the editing, a Reconnect button will allow recovering of the previous trader state.

Lets say the original time frame is 1 hour and we set "Bar Opening" with time frame - 4 hours.

1H Period        4H Period 
Bar Opening      Entry Level
10:00 - 1.34        1.34
11:00 - 1.38        1.34
12:00 - 1.40        1.34
13:00 - 1.37        1.34
14:00 - 1.35        1.35
15:00 - 1.34        1.35
16:00 - 1.32        1.35
17:00 - 1.28        1.35

We see that the entry level will remain the same for 4 bars.

The problem: "Bar Opening" entry may differ for the opening price of the original time frame. How we'll enter on such a price?

Every indicator has a property ExecutionTime.

namespace ForexStrategyBuilder.Infrastructure.Enums
{
    /// <summary>
    /// The type of the time execution indicator.
    /// It is used with the indicators, which set opening / closing position price.
    /// </summary>
    public enum ExecutionTime
    {
        DuringTheBar,   // The opening / closing price can be everywhere in the bar.
        AtBarOpening,   // The opening / closing price is at the beginning of the bar.
        AtBarClosing,   // The opening / closing price is at the end of the bar.
        CloseAndReverse // For the close and reverse logic.
    }
}

This property is set to "ExecutionTime.AtBarOpening" for "Bar Opening" indicator. It says to the backtester that it has to open a position exactly at the opening price. This will fool the backtester for a  LTF "Bar Opening".

If we remove that parameter from the indicator, most of the bars will become "Ambiguous" because the backters will have to interpolate the bar in searching of the entry price.

This problem is even bigger for the Closing Slot.

We know that Closing Logic Conditions have OR logic. So even one satisfied condition has to close the position. If we use LTF Bar Closing, such exit may appear on a price that is out of the bar range... How to deal with such a case?

...

I think the simplest solution is Krog or other developer to convert WTF indicators to the new format. He may call them LTF to differ from the old ones.

Bar Opening and Bar Closing are indicators as the others.

For example MA also has  ExecutionTime set in the following way:

            if (period == 1 && shift == 0)
            {
                if (price == BasePrice.Open)
                    IndParam.ExecutionTime = ExecutionTime.AtBarOpening;
                else if (price == BasePrice.Close)
                    IndParam.ExecutionTime = ExecutionTime.AtBarClosing;
            }

Also Day Closing, Day Closing 2, Week Closing, Trailing Stop, Stop Loss, Take Profit, Stop Limit, Entry Hour, Exit Hour...

The LTF and Symbol functions for Logical Conditions slots are implemented in the core of Backtester and Trader. Indicators are not changed in any way and this make the feature rigid and bug proof.

...

I can allow LTF, Signal Shift and Signal Repeat for Opening and Closing slots by deleting a single line of code. (Line No 199)

There is no problem with implementation. The functionality is available for all slots. I simply hide it for Opening and Closing Slots because it may not work as expected.