Menu

Options

Bookmark Thread

First Page First Unread Last Page Last Post

Print Thread

Similar Threads

Grid - New indicator that replaces chart grid 60 replies

Grid (not grid system) or horizontal lines indicator 6 replies

100% win grid EA 45 replies

Grid, Burst Grid, Grid Risk and Grid Profit 1 reply

Double Time Grid and Pip Grid 0 replies

Attachments: 100% Win Math Grid Ea
Exit Attachments

100% Win Math Grid Ea

This my first thread that I followed to the last page. It was an intersting journey. I saw the improvements Mr. Viper tried to make, he did his best but death trade seems unavoidable. Yes, if one babysits and manages this EA, you can come out profitable but seeing huge DD and emotional distress (fear of death trade lingering over head possibility) not worth it.

I think its time to let this one go and start a new project to develop a new EA that is based on realities of market (non martingale/grids) which is "price action" momentum support resistance etc (the fundamentals) these are realities of this market that can never go wrong if we can code this using slick parameters.

It's my advise to the sincere ones, to try making an EA based on price action and in thread we will be coming up with the ideas as how we perceive price action and what parameters can be utilized...ie: if S/R broken, is it with momentum? measuring moment speed of pips movement, indicating demand is heavy therefore enter etc etc..such parameters we humans know and coders know how EA's communicate to our mt4, so lets put to use this brilliant man's talent to achieve the great use eh? why waste time on a loser. cliche, cut short loss, let winners run.

I wish i was a coder, knowing price action in market, I would certainly have build a close-to holy grail EA by now.

thank you all for participating in the battle, let the new journey begin...
Quoting GoodBoy
This my first thread that I followed to the last page. It was an intersting journey. I saw the improvements Mr. Viper tried to make, he did his best but death trade seems unavoidable. Yes, if one babysits and manages this EA, you can come out profitable but seeing huge DD and emotional distress (fear of death trade lingering over head possibility) not worth it.

I think its time to let this one go and start a new project to develop a new EA that is based on realities of market (non martingale/grids) which is "price action" momentum support resistance...
My friend,
I think that's the beauty of such forum, you can start a new thread without even bothering writing a comment in other threads, and eventually ppl will come and share.

On my side, the Grid journey is definitely not done and I will keep publishing updates on what I do here.

I identified a set of another 5 set-up that would result in a Break-even position while breaking Level3, meaning there would be no need to keep adding positions for these but simply close at beak-even and start a new grid upon BE .... eventually letting run the winning ones.

So is there still some unexplored potential ... I believe yes, whether or not it will lead to an interesting path.

Wael, from my I saw, there might be some value in trailing from Level2 on 2 specific set-up just to prevent simply Breaking-even.

I will post the few set-up I investigates tomorrow night or a little later (I'm in between flights and was checking on potential updates).

PS: yes, closing @BE means only the broker made good $$ on the spread and not us .... you know what .... this is something you have to live with if you decide to use a grid strategy .... and yes ppl can keep saying this is crap (as I read in few places) but hey ... thanks for the eye opener and pass your way.

Xmph.
Hello , i found this ea very help full. First of all congrats for the creator.

Can any one make this ea to work in stealth mode with max spread option??

If it is already created please let me know.

Thankyou.
Quoting rajchumar
Hello , i found this ea very help full. First of all congrats for the creator.

Can any one make this ea to work in stealth mode with max spread option??

If it is already created please let me know.

Thankyou.
Yes this has already been created. look for version 2.62 should have all the options u need.
Quoting xmph
See my code below (implementing my vision of the trailing as specify in the few lines of code comments). I do not know where this would go in VT code considering I recoded everything for myself. However, I believe my variables are self-explanatory.

Now Trailling is one thing if you are seeking a quick exit after a Straight price action from Level 1 to 3 .... Is this STILL profitable if that happens after multiple swings ?

Answering this allows to start investigating the different incomplete exit strategies. I would appreciate some ppl to provide...

Thanks a lot for that,

i've been trying for almost 5 days right now to insert the code into viper EA but constantly having errors and im not getting even close.

I think the feature is very important, it reduces risk a lot.

and it could be triggered after break even scenarios in other break even scenarios.

Is it possible you can help the 2.62 to have the option to trail?

that would be great.

Thanks,

W
Quoting wael117
Is it possible you can help the 2.62 to have the option to trail?
W
It is unlikely. I do not want to spend the time looking at, and understanding, someone else's code considering I do trade only with my own programming.

X.
Wael,

If you can describe what you want clearly, in logical terms (when A is true AND B is true, then do this), I will code it. I can't make promises on turn around time but I will try to get to it without too much delay.

You should be able to use the total set take profit for this as well. I can add a way to define it in pips instead of dollars if people think that is more useful.

Viper

Quoting wael117
Thanks a lot for that,

i've been trying for almost 5 days right now to insert the code into viper EA but constantly having errors and im not getting even close.

I think the feature is very important, it reduces risk a lot.

and it could be triggered after break even scenarios in other break even scenarios.

Is it possible you can help the 2.62 to have the option to trail?

that would be great.

Thanks,

W
Quoting tradingviper
Wael,

If you can describe what you want clearly, in logical terms (when A is true AND B is true, then do this), I will code it. I can't make promises on turn around time but I will try to get to it without too much delay.
Viper
Here is my trailing code:
1) Initiate trailing if first three orders hit successively Lvl1, Lvl2 and Lvl3.
2) @Lvl3, initiate trailing by defining a new SL (for every open orders) at Lvl2+increment/2 (for a long, -increment/2 for a short). This is Initial Trailing SL (ITSL). Other pending orders should be killed.
3) At every tick, compare the pips difference in between Lvl3 and Bid (or Ask), if difference is superior than [current SL - (ITSL)], then update SL (take care of minimum SL imposed by broker) with respect to the difference.

Trailing from Lvl2+increment/2 guarantees that you leave some space for price action happening after Lvl3 is reached. If you start trailing at Lvl3 directly .... you will almost always hit your SL in within few ticks.

OF NOTE: from the backtesting I did, trailing this way always cut the normal approach profit, while preventing only few drawdown. However, it diminish a lot the risk and as such, it is a personal choice. I do trail that way ;-)

By Default: Do not update the SL with the minimum SL imposed by the broker. This would defeat the purpose of leave some living space for price action. See my code, I believe this is the right approach.

Here is an improved code for the Trailing. It handles occasion where SL is below the minimum requirements of the broker.

I think there is a small bug somewhere as I saw some weird behavior. I'm on it.

In the main program:
Inserted Code
int start()
  {

// TRAILLING
if (TrailingStop){TrailOrder(); if (OrdersTotal() == 0){TrailingStop=false;Initiate = true;} return(0);}
The following code is to start trailling at mid-Lvl2/Lvl3
Inserted Code
// MinSL stores the minimal deviation for the StopLoss.
   double MinSL = (MarketInfo(Symbol(), MODE_STOPLEVEL)+MarketInfo(Symbol(), MODE_SPREAD))*Point;
   // SLPrice will store the Long or Short StopLoss price.
   double SLPrice;

if (Straight3 == 0 || Straight3 == 3)
      {
         
         for(i=total-1;i>=0;i--)
         {
            OrderSelect(i, SELECT_BY_POS);
            if (OrderType() == OP_BUY)
            {
               SLPrice = thisAsk()- MinSL;
               
               if (GridLevelSetUp[1][LevelBuy2] + GridLevelSetUp[0][GridSpace]/2 < SLPrice)
               {SLPrice = GridLevelSetUp[1][LevelBuy2] + GridLevelSetUp[0][GridSpace]/2;}
               
               InitialTrailingSL = SLPrice;
               
               RefreshRates();OrderModify(OrderTicket(),OrderOpenPrice(),SLPrice,0,0,Green);
            }
            else
            { 
               SLPrice = thisBid()+MinSL;
               
               if (GridLevelSetUp[2][LevelSell2] - GridLevelSetUp[0][GridSpace]/2 > SLPrice)
               {SLPrice = GridLevelSetUp[2][LevelSell2] - GridLevelSetUp[0][GridSpace]/2;}
               
               InitialTrailingSL = SLPrice;
               RefreshRates();OrderModify(OrderTicket(),OrderOpenPrice(),SLPrice ,0,0,Green);
            }
         }
         TrailingStop = true;
         return (true);
The following code is to keep trailing seemingly to as much price action moves in the trailing direction after Lvl3.
Inserted Code
void TrailOrder()
{
   double PriceMovement = 0;
   double InitialSL = 0;
   int i=0;
   
   // MinSL stores the minimal deviation for the StopLoss.
   double MinSL = (MarketInfo(Symbol(), MODE_STOPLEVEL)+MarketInfo(Symbol(), MODE_SPREAD))*Point;
   // SLPrice will store the Long or Short StopLoss price.
   double SLPrice;
   
   int cnt,total;
   total  = OrdersTotal();
   
   
   
   if(TrailingStop)
   {        
            
/*
   THIS LOOP WILL HELP UPDATING THE STOPlOSS IN ORDER TO TRAIL FROM MID-LEVEL 2, BASED ON THE MOVEMENTS SINCE LEVEL 3
*/
      for(i=total-1;i>=0;i--)
      {
         OrderSelect(i, SELECT_BY_POS);
         if (OrderType() == OP_BUY)
         {
/*
   We check if there is anything to Trail by comparing the point movement from Level 3 with current SL.
   
*/
            PriceMovement = MathAbs(thisAsk()-GridLevelSetUp[1][LevelBuy3]);
            InitialSL = InitialTrailingSL;
            
            SLPrice = thisAsk() - MinSL;
            
            if ( InitialSL +  PriceMovement > OrderStopLoss())
            {
               if (InitialSL+PriceMovement < SLPrice)
               {SLPrice = InitialSL+PriceMovement;}
               else if (InitialSL+PriceMovement > SLPrice && SLPrice > OrderStopLoss())
               {OrderModify(OrderTicket(),OrderOpenPrice(),SLPrice,0,0,Green);}
            }
         }
         else if (OrderType() == OP_SELL)
         {            
            PriceMovement = MathAbs(GridLevelSetUp[2][LevelSell3]-thisBid());
            InitialSL = InitialTrailingSL;
            
            SLPrice = thisBid()+MinSL;
            
            if ( InitialSL -  PriceMovement < OrderStopLoss())
            {
               if (InitialSL-PriceMovement > SLPrice)
               {SLPrice = InitialSL-PriceMovement;}
               else if (InitialSL-PriceMovement < SLPrice && SLPrice < OrderStopLoss())
               {OrderModify(OrderTicket(),OrderOpenPrice(),SLPrice,0,0,Green);}
            }
         }
      }
   }
}
Quoting tradingviper
Wael,
I will code it. I can't make promises on turn around time but I will try to get to it without too much delay.
Viper
hello Viper, I'm glad to see you are still around here.
Are you still trying to improve on the solution ?

I did not had the time to post the scenarios I've been working on. However, there is many things that can be done and which makes sense from the math point of view.

Whether or not these are what FF mentionned earlier, I will be posting my updates as I validates them (but I lacked spare-time these last few weeks).

Xmph.
Quoting tradingviper
Wael,

If you can describe what you want clearly, in logical terms (when A is true AND B is true, then do this), I will code it. I can't make promises on turn around time but I will try to get to it without too much delay.

You should be able to use the total set take profit for this as well. I can add a way to define it in pips instead of dollars if people think that is more useful.

Viper

Hello Viper,

Thank you so much for taking my request,

i have been trading your EA on demos and live accounts ( on and off)

result has been very spectacular with a couple of Modifications from my end, where i tried to limit the DD and the death trade as much as possible but again there are many times that i see a death trade formation starting to pile up on my account and i start to act manually in order to minimize the damage on my account

I will explain the modification that i am requesting on the EA


The whole basic idea is to trail after hitting next increment in order to protect from hitting 1,2,3,x increment and then reversing.

For Example

If we have 3 Level Gird

we need the following functions which is the trailing stop.

Lets say market is Bullish,

Level 1 is triggered, No action

Level 2 is triggered, No action

Level 3 is triggered - Trailing stop starts by "X" pips, Now the X pips can be a number that is modified by the user.

Also the level of which the trailing stop can be triggered is modified by the user.

For example if i use 5 level grid, I can select to activate the Trailing Stop Function starting from any where starting from the 1st level to the 5th level.

Now this is here where it is simply the market goes B1, B2, B3,..BX

in the case where the market goes B1, B2 and then reverses to S1,S2,Sx...

We can initiate the trailing stop by number of pips from break even in profit value or in pips value.

Basically the lower you initiate your trailing stop the less you are prone to start hitting reversal with trailing stop and so on.

Why do i beleive this can work, i have been running many of my tests lately with TP, levels where i make my EA setup a 3-5 grid level but setup my TP level couple of pips either before the 2nd or 3rd grid level initiate, with the right setup you can have very good long term result, some of my back tests run from 2005 on tick data and no death trade on 0.5% risk level on entry. with a combination of multiple currencies the account can double yearly.

Now with the trailing stop feature this would allow it to run longer in profits not worrying about the TP. which i think would be better modification for this setup. and quiet necessary


Another example

let me explain my point behind a 3 grid level with 10 pips increments each.

Now there are many times that the the grid reached 3rd level on the buy side and hit 4 pips away from the TP level and then reversed to the hit S1 & S2

now if we have 5 pips Trailing STOP. the market will exit B3 with +1 pip, B2 with 11+ pips and B1 with 21+ pips, and then the next grid will initiate, the second grid will hit S1,S2,S3

and this is in the scenario that i activate the trailing only when it reaches 3rd level, where with this function we can minimize the grid levels below 20 and feel kind of safer from the retracement or reversal of the pair.

Moreover, Please if possible as you mentioned that you change the TP from dollar value to pips value,

With $ value it is perfect when you are using fixed lots, but when you're using Money management with time then you have to change the TP every time. Doesn't make a lot of difference on the live account, but on back testing makes quiet a difference.

Thanks a lot viper, and please if you have any questions or comments on the method behind this I'll be more than happy to discuss and clarify.

and thanks XMPH for your input as well.

Thanks to both, been very helpful. Please take your time there is no rush into this. I am even expecting a bigger surprise than just my recommendation function here.

Once again i am not sure about how will this method work in terms if it reverses for example if we start trailing from B3, but then it hits B1,B2 then S1,S2,SX, we need the first function first and then to test this on forward and back testing to see the results.

Thanks again viper very appreciated.
I've been very busy on some other projects, but I check in every now and then. I am still interested in improving this EA, if possible. I don't have time, however, to entertain every persons whim. When I check in, if something seems interesting, I consider adding it.

I appreciate your help and inputs.

Viper

Quoting xmph
hello Viper, I'm glad to see you are still around here.
Are you still trying to improve on the solution ?

I did not had the time to post the scenarios I've been working on. However, there is many things that can be done and which makes sense from the math point of view.

Whether or not these are what FF mentionned earlier, I will be posting my updates as I validates them (but I lacked spare-time these last few weeks).

Xmph.
Let me spend a little time looking at your post and I may need to respond with questions... Let me see what I can do...

Viper

Quoting wael117
Hello Viper,

Thank you so much for taking my request,

i have been trading your EA on demos and live accounts ( on and off)

result has been very spectacular with a couple of Modifications from my end, where i tried to limit the DD and the death trade as much as possible but again there are many times that i see a death trade formation starting to pile up on my account and i start to act manually in order to minimize the damage on my account

I will explain the modification that i am requesting on the EA


The whole basic idea is to trail...
Thank you for your inputs. I will take a look at them as well... if they are very different from WAEL's, we may need to reach a consensus so it can be implemented one, optimal way...

Viper

Quoting xmph
Here is my trailing code:
1) Initiate trailing if first three orders hit successively Lvl1, Lvl2 and Lvl3.
2) @Lvl3, initiate trailing by defining a new SL (for every open orders) at Lvl2+increment/2 (for a long, -increment/2 for a short). This is Initial Trailing SL (ITSL). Other pending orders should be killed.
3) At every tick, compare the pips difference in between Lvl3 and Bid (or Ask), if difference is superior than [current SL - (ITSL)], then update SL (take care of minimum SL imposed by broker) with respect to the difference.

Trailing...
You know X, it's not bad code to look at... ;-)

Viper

Quoting xmph
It is unlikely. I do not want to spend the time looking at, and understanding, someone else's code considering I do trade only with my own programming.

X.
Quoting xmph

I think there is a small bug somewhere as I saw some weird behavior. I'm on it.
Here is my mistake
Change
Inserted Code
if ( InitialSL +  PriceMovement > OrderStopLoss())
            {
               if (InitialSL+PriceMovement < SLPrice)
               {SLPrice = InitialSL+PriceMovement;}
               else if (InitialSL+PriceMovement > SLPrice && SLPrice > OrderStopLoss())
               {OrderModify(OrderTicket(),OrderOpenPrice(),SLPrice,0,0,Green);}
            }
by
if ( InitialSL + PriceMovement > OrderStopLoss())
{
if (InitialSL+PriceMovement < SLPrice)
{SLPrice = InitialSL+PriceMovement;OrderModify(OrderTicket(),OrderOpenPrice(),SLPrice,0,0,Green);
}
else if (InitialSL+PriceMovement > SLPrice && SLPrice > OrderStopLoss())
{OrderModify(OrderTicket(),OrderOpenPrice(),SLPrice,0,0,Green);}
}

HTH
Quoting tradingviper
You know X, it's not bad code to look at... ;-)

Viper
Agreed, but I'm the "my money, my code, my mistake if it failed" type of guy ;-)
and considering I have little time and I do use my code on live accounts (once ready) .... then it makes sense for me to just spend as much time as I can on my code.

Now, do not misunderstand me ... I do look into your and other's code ... but implementing new concept is a different story as IF (and I mean really if) there is a bug that does not belong to the new implementation, but to the original code, and that it takes 2 days to realize that ... then it's a 2days I'd prefer to spend on my code ;-)

This is a personal opinion. What I like to do though is share my experience, my code (if other find it useful) and my "improvement" eventually.

x.
Quoting wael117

I will explain the modification that i am requesting on the EA
Wael,
I backtested from march 20 2010 till april 28 2010 with the trailing (in the way I mentionned).

I ran one grid/day at 8am, spacing 150 pips - 5digits

Over 15 1-2-3 consecutive hits, the trailing helped me only once ! Rest of the time, it simply prevent the traditional run to take TP.

To maximize the trailing, I realize that it's better to start trailing on the New bar after Lvl3 is hit, on a 5min chart (I know it defeat the purpose of the no-time frame EA).

So you "pay" a lot for security.
I do not see the advantage of a 10 spacing increment with trailing considering you pay a 2/3 up to 5 pip spread, and I do not understand trailing 5pips increment.

Wael, could you provide screenshots of cases where it's usefull and the respective grid-set-up. I can do the same thing.

X.
Quoting xmph
Wael,
I backtested from march 20 2010 till april 28 2010 with the trailing (in the way I mentionned).

I ran one grid/day at 8am, spacing 150 pips - 5digits

Over 15 1-2-3 consecutive hits, the trailing helped me only once ! Rest of the time, it simply prevent the traditional run to take TP.

To maximize the trailing, I realize that it's better to start trailing on the New bar after Lvl3 is hit, on a 5min chart (I know it defeat the purpose of the no-time frame EA).

So you "pay" a lot for security.
I do not see the advantage of a 10 spacing...
Hello X,

OK you can see the other screen shots that i have put earlier, these are some of many situations where i have been stuck due to the fact that the price level almost reached the TP but didn't hit due to the fact it was 5-8 pips away,

In the example i just provided a 10 pip increment levels, but on live accounts i never had the guts to go that low, in fact i do not set a increment level. i find that the ATR increment is much more adaptable to all situations. although sometimes u might get stuck into positions that would get you in a start of a death trade situation, but still it is manageable if you are monitoring it. but as we all know we just cannot be there for it 24/5 and this is the reason i started diverting into setting a take profit for the whole cycle and looking into the option for trailing stop.

Now basically the way i trade this is that i go for the set gird TP then get stuck in a full 3 grid level, of course this cuts down a lot from my profitability, but in the end of the day i am 10x safer than being stuck in a grid for a couple of days or several weeks just compiling more and more trades, especially with how the markets was the last 10 days. i got positions on demos that have been piling up for the pat 8 days now, i would have been much safer.

I am not expecting a major change in the result in terms of risk as where you can put you set a Take profit or put a trailing stop, but i think the trailing stop would make it much profitable and safer now depending on where and how you deploy it. thats why i would prefer to have the function that i can set the trailing stop at any level i want.

my optimum setup is 3 levels, but i ran a couple of tests on 5- 10 grid levels and the result that i got was very interesting, now just needed to have something very safe, in order to run something like that on a live account + the broker as well (which is not the issue here).

VIPER, i do not mind we can start with any of both versions either X or mine, even x already has his code setup, if this is easier to implement that would be a good start for all of us, where we can setup and test, my only request is that we would have as much possiblities in the input/setup section in order for us to do more testing with different input and setup values and share the results. and once again thanks X for the code and your input..

Thanks Viper & X,

Seriously looking forward to this!!!
Good work guys.. keep it up
Quoting tradingviper
Thank you for your inputs. I will take a look at them as well... if they are very different from WAEL's, we may need to reach a consensus so it can be implemented one, optimal way...
Viper
Viper and Wael,
In addition to taking a scenario-based approach, I'm still investigating a Math_mitigation based on Strong Support/Resistance.

The interest of Strong Sup/Res as I see it is that you more or less predict these ones for ... let's say a last-2weeks or month Sup/Res. What I'm trying to put together is to consider these as BreakEven objective if we've been oscillating for some time.

Thus, instead of keeping the pattern of the grid, I would modify the grid to simply BE@Sup/Res. Yes one would loose time, and as well loose money by not making profits ... but this might be something good if it is triggered only few times, and save a blown-up ... considering the rest of the time is just taking profit.

As I'm not exactly sure how I want this to work, I throw my ideas .... so what do you think of it ?
2 traders viewing now