by **TakisGen** » Fri Jun 21, 2013 6:55 am

I do not believe what you have done to the strategy optimizer.

I used to backtest 20 pairs in a range of 4 years with the previous version, without any problem!

Now, after the update, i cannot backtest more than 7 months for 7 instruments.

So, i tried the help files where i found about the sdk optimizer.

I thought things would be better there, but are worst as i was prompted for first, second and third price source.

Is there something i do not understand with my 136 iq?

One, cannot figure out the correct parameters when he has to combine the output of more than two backtests in complex strategies.

Just to give you an idea of what i am talking about:

--local I={"EUR/USD, USD/JPY, GBP/USD, USD/CHF, EUR/CHF, AUD/USD, USD/CAD, NZD/USD, EUR/GBP, EUR/JPY, GBP/JPY, CHF/JPY, GBP/CHF, EUR/AUD, EUR/CAD, AUD/CAD, AUD/JPY, CAD/JPY, NZD/JPY, GBP/CAD, GBP/NZD, GBP/AUD, AUD/NZD"}

local I={"USD/JPY", "EUR/JPY", "GBP/JPY", "CHF/JPY", "AUD/JPY", "CAD/JPY", "NZD/JPY"}

table.sort(I)

strategy.parameters:addString ("Instruments", "Instruments", "", table.concat(I,","))

strategy.parameters:addInteger ("updateTF", "Update TF index", "1=m1 2=m5 3=m15 4=m30 5=H1 6=H2 7=H3 8=H4 9=H6 10=H8 11=D1 12=W1 13=M1", 0,0,13);

strategy.parameters:addInteger ("workingTF", "Working TF index", "1=m1 2=m5 3=m15 4=m30 5=H1 6=H2 7=H3 8=H4 9=H6 10=H8 11=D1 12=W1 13=M1", 8,1,13);

strategy.parameters:addInteger ("TradeYear", "Trade Year", "", 0);

strategy.parameters:addInteger ("TradeMonth", "Trade Month", "", 0, 0, 12);

strategy.parameters:addInteger ("Agent", "Agent", "", 1);

strategy.parameters:addString ("Currency", "Currency", "", "JPY");

This WAS running! the multi frame version WAS running too!