Blessing 2 - page 219

 

Hello chicagorob,you set AutoCal true or fasle on usdjpy, eurgbp, and eurchf,thanks

 
ChicagoRob:
You said my settings crashed in 2007, but I just ran a backtest and it passed,

but only on the H4 chart and not H1(which was great in '08/'09).

Rob

Will retest. I am using FXDD MT4 for back testing. Could this be the difference. don't understand why but have seen this issue reaised before. I am also using FXDD for live trading...

 
haojzh:
Hello chicagorob,you set AutoCal true or fasle on usdjpy, eurgbp, and eurchf,thanks

AutoCal = false on all pairs

 
seank:
Will retest. I am using FXDD MT4 for back testing. Could this be the difference. don't understand why but have seen this issue reaised before. I am also using FXDD for live trading...

It might make a difference. When I researched on proper methods for

backtesting, I read that the terminal should never be used for forward

testing, or live trading. IOW, charts should never be loaded, since they

will disrupt the data history. Only using the tester keeps the data clean

from one test to the next.

Rob

 
ChicagoRob:
It might make a difference. When I researched on proper methods for

backtesting, I read that the terminal should never be used for forward

testing, or live trading. IOW, charts should never be loaded, since they

will disrupt the data history. Only using the tester keeps the data clean

from one test to the next.

Rob

You can always keep the data 100% clean by enabling windows firewall and blocking all communication to terminal.exe

Deleting the account which has been suggested in everything I've read screws up account details.

 
engreric:
You can always keep the data 100% clean by enabling windows firewall and blocking all communication to terminal.exe Deleting the account which has been suggested in everything I've read screws up account details.

Excelent ....

Here's a suggestion. Can we post or put somewhere our collective data ?

so we're all using the same data.

And based on your knowledge we write up the simple things to do like using windows firewall and so on ...

I waste alot of time with inconsistencies o nthe back test. sometimes going in circles. I am ready to settup at terminal "fixed" for backtesting. We could devide up the test (at least for me as it takes time to optimize).

sean

 

Blessing 3

All,

I'm about 75% complete with programming Blessing 3. I've been combing the threads checking suggestions and the one suggestion I like is a trailing stop.

I've watched backtests and have seen the basket go positive and then turn right around and go negative for a while. I believe that once the basket is in profit, it should not be allowed to go negative again but that's just me.

The new menu will be more user friendly however, I seem to have cluttered it up a bit with indicator programming features and I don't like that. I want everyone to have a chance to backtest and forward test this new product but sometimes too many options will create problems. So, what I have done is to cut and paste the proposed menu selectable items below. If you have to ask what an item is, it's probably not required as a menu selectable item, right? Instead of garbaging up this thread, throw me your thoughts via email to support@jtatoday.com on what you think the menu should be like. Keep in mind that a trailing stop feature has yet to be added so that may end up as a menu selectable item as well. Here it is:

extern string TradeComment = "Blessing";

extern int StopTradeBalance = 5000;

extern bool IBFXmicro = false; // set to true for IBFX micro "penny a pip"

extern bool UseMM = true; // Money Management

extern double LAF = 1.0; // Adjusts MM base lot for large accounts

extern double lot = 0.01; // Starting lots if Money Management is off

extern double Portion = 1.0; // Portion of account you want to trade on this pair

extern double MaxDDPercent = 50; // Percent of portion for max drawdown level.

extern double Multiplier = 1.4; // Multiplier on each level

extern int MaxTrades = 99; // Maximum number of trades to place(stops placing orders when reaches MaxTrades)

extern int BreakEvenTrade = 12; // Close All level , when reaches this level, doesn't wait for TP to be hit

extern bool BollingerStochEntry = true; // if false, uses simple MA for entry

extern int BollPeriod = 15; // Period for Bollinger

extern double BollDistance = 13; // Up/Down spread

extern double BollDeviation = 2.0; // Standard deviation multiplier for channel

extern int BuySellStochZone = 20; // Determines Overbought and Oversold Zones

extern int MAPeriod = 100; // Period of MA

extern bool UsePowerOutSL = false;// Transmits a SL in case of internet loss

extern bool AutoCal = false; // Auto calculation of TakeProfit and Grid size;

extern double GAF = 1.0; // Widens/Squishes Grid on increments/decrements of .1

Happy Trading

v/r

 
engreric:
I've been characterizing performance on backtesting by the max levels being reached and the frequency of all the levels, and then looking at the monthly averages for these. If you characterize it this way, then it doesn't matter as much what the risk and betting settings are.

Backtesting and Optimization in Metatrader 4 - Expert Advisor Programming

 

Changes to Blessing

All,

I'm about complete with the programming of Blessing 3. It offers all the same features as 2 but the menu is cleaned up. Here are some other changes:

Easier to use menu, items make sense

A Bollinger Band confirmed with Stoch entry feature

User selectable BB settings with one Stoch setting selectable

MA still available for use. Turn off the BBStoch is all you need to do.

Power Out Stop Loss still available

Auto Calculation of grid still available

Grid Adjustment Feature still available

A new Maximize Profit Feature that does the following

Sets a Trailing Profit Stop based on percent of basket profit potential

Moves the Take Profit to garner larger profits should the pair "run"

TP moves a set number of times based on user input

Profits can be taken on the Trailing Profit stop or TP point

Can be turned off to use Blessing to Take Profit at the TP point

The new menu with explainations is below:

extern string TradeComment = "Blessing";

extern int StopTradeBalance = 5000;

extern bool IBFXmicro = false; // set to true for IBFX micro "penny a pip"

extern bool UseMM = true; // Money Management

extern double LAF = 1.0; // Adjusts MM base lot for large accounts

extern double lot = 0.01; // Starting lots if Money Management is off

extern double Portion = 1.0; // Portion of account you want to trade on this pair

extern double MaxDDPercent = 50; // Percent of portion for max drawdown level.

extern double Multiplier = 1.4; // Multiplier on each level

extern int MaxTrades = 99; // Maximum number of trades to place (stops placing orders when reaches MaxTrades)

extern int BreakEvenTrade = 12; // Close All level , when reaches this level, doesn't wait for TP to be hit

extern bool MaximizeProfit = true; // Turns on TP move and Profit Trailing Stop Feature

extern double ProfitSet = 60; // Locks in Profit at this percent of Total Profit Potential

extern double MoveTP = 15; // Moves TP this amount in pips

extern int TotalMoves = 3; // Number of times you want TP to move before stopping movement

extern bool BollingerStochEntry = true; // if false, uses simple MA for entry

extern int BollPeriod = 15; // Period for Bollinger

extern double BollDistance = 13; // Up/Down spread

extern double BollDeviation = 2.0; // Standard deviation multiplier for channel

extern int BuySellStochZone = 20; // Determines Overbought and Oversold Zones

extern int MAPeriod = 100; // Period of MA

extern bool UsePowerOutSL = false;// Transmits a SL in case of internet loss

extern bool AutoCal = false;// Auto calculation of TakeProfit and Grid size;

extern doubleGAF = 1.0; // Widens/Squishes Grid on increments/decrements of .1

Blessing 3 will be out shortly. I am running through prelimnary testing to ensure all features are operating as planned.

Happy Trading

v/r

 

A fine job, indeed, Jeff. Looking forward to getting Blessing 3 dialed-in.

The trailing profit stop is especially interesting.

Rob

Reason: