Trapping System: Grid | Page 133 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Trapping System: Tunnel Martingale 476 replies

Grid - New indicator that replaces chart grid 60 replies

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

Trapping System: Way to Fully-Automated Trading System 47 replies

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

Attachments: Trapping System: Grid
Exit Attachments

Trapping System: Grid

  • #2,641
  • Dec 4, 2015 7:43am Dec 4, 2015 7:43am
Quoting yogasampurno
What do you think caused it guys?
May be the Beige Book release?

I seem the events you indicated are all red news, so we wouldn't trade.
  • #2,642
  • Dec 4, 2015 1:16pm Dec 4, 2015 1:16pm
This week I left EA on to see what would happen

The V1.8 survived one better than the other I have another test that is running V1.7 that collapsed completely

so an interesting week

Attached Image


I do Good I feel GoodI do Bad I feel Bad
  • #2,643
  • Dec 4, 2015 2:38pm Dec 4, 2015 2:38pm
Quoting radityo.ardi
{quote} It is something worth to try, but we need to work on the details. What I can do is to apply the logic in the timerange. If it is outside, you'll have to manage it manually. OR we can put a button over there for EA to close only the profit orders and refill the previously closed orders with new Limit orders.
Yes, this is what I am thinking of these days. Please remind the accumulative profit need to be managed. If not, it will take longer time to end the current cycle, in many cases, this is not what we want to see.
  • #2,644
  • Dec 4, 2015 4:37pm Dec 4, 2015 4:37pm
Quoting Offshore
This week I left EA on to see what would happen The V1.8 survived one better than the other I have another test that is running V1.7 that collapsed completely so an interesting week {image}
v1.7 limit or stop? What trading window are you using?
  • #2,645
  • Dec 4, 2015 8:13pm Dec 4, 2015 8:13pm

loser loser loser.....

Attached Image (click to enlarge)
Click to Enlarge Name: Screenshot1.png Size: 22 KB


This was tricky, deep down then going up.... stop mode hit tp but still got negetive profit.

But i found a solution.....see you in next month Mr.NFP
No one wants to be defeated~
  • #2,646
  • Dec 5, 2015 12:55am Dec 5, 2015 12:55am
Quoting jonirrenicus
loser loser loser..... {image} This was tricky, deep down then going up.... stop mode hit tp but still got negetive profit. But i found a solution.....see you in next month Mr.NFP
What's the solution? Interested to know. I saw your screenshot where 2 orders with almost same price, slippage? May i know when to turn on EA? And whats the grid interval? Whats the current price interval? Possible to share the set file?
  • #2,647
  • Dec 5, 2015 10:31am Dec 5, 2015 10:31am
Quoting yogasampurno
I did some backtests using GTLimit v.18 and its set file for EURUSD. Data is from histdata and I shifted it to GMT+2 because Robo's Marketwatch is GMT+2. It went well except some dates as in excel file attached. On those dates the account blew and I tried to figure it out events that caused it. However, I don't know what is the culprit for 14-15 Jan. What do you think caused it guys? {file} {image}
Just for your information, HistData, for Singapore Time, I need to shift to +13 hours. There's no time conversion mechanism, so we should count the timezone our own compared to the EST time recorded in HistData time.
I've had a hard time to understand the Strategy Tester date-time mechanism. If you run it in the Strategy Tester, EA will only consider it as local time.

14-15 Jan, no idea.
If you ask me to code/fix your EA... it's probably not for free...
  • #2,648
  • Dec 5, 2015 10:34am Dec 5, 2015 10:34am
Quoting happytrade38
Hi radityo, I have an idea to start the stop order with either v.17 or v.18. Time to trade will be london/new york open or few minutes before red news. Let say i start with 3 buy stop and 3 sell stop orders with 100 grid points. Unfortunately, the price up open 1 buy stop then price retrace back and open a sell order, ranging condition continues till no more pending orders either buy or stop. In this case, account will be in float loss by about 60pips. Will leave this float alone. Then we repeat the above process on next day london/new york open...
Your magic number must be same. It can't be anything else. I've tested both v1.7 and v1.8, the magic number mechanism still work. Even a few weeks ago I wanted to set 2 different strategy on the same account, it was behaving the same like yours, even worse. The account sets Active (IN time range) open the order, but then it closes all orders. Then I realized the magic number was still same.
If you ask me to code/fix your EA... it's probably not for free...
  • #2,649
  • Dec 5, 2015 10:38am Dec 5, 2015 10:38am
Quoting polomine
{quote} Yes, this is what I am thinking of these days. Please remind the accumulative profit need to be managed. If not, it will take longer time to end the current cycle, in many cases, this is not what we want to see.
Please wait...
I've been thinking of another strategy applied to STOP mode. I think it'll print money like anything like last time I've set up for STOP. I just need to proof it, put the code in, and test it.

But I can't tell you guys as of now, since it still needs to be proven first before I present to you guys.
If you ask me to code/fix your EA... it's probably not for free...
  • #2,650
  • Dec 5, 2015 1:15pm Dec 5, 2015 1:15pm
Quoting radityo.ardi
{quote} Your magic number must be same. It can't be anything else. I've tested both v1.7 and v1.8, the magic number mechanism still work. Even a few weeks ago I wanted to set 2 different strategy on the same account, it was behaving the same like yours, even worse. The account sets Active (IN time range) open the order, but then it closes all orders. Then I realized the magic number was still same.
Hi,
Now I am testing all strategies in one account with different magic numbers.
1. EU session with STOP orders , set file GTS_EU1_LIVEFIX, magic # 1111, 7GMT-9GMT,
2. London session (after 3 from opening): using Limit orders set file GTL_EU2 , magic#2222, i.e. 11GMT to 14GMT;
3. US session using STOP orders, set file GTS_US_LIVEFIX, magic#3333, from 12GMT-14GMT
4. Quite time LIMIT orders set file GTL_EU2 , set file magic#4444 from 17GMT-22GMT;

Let me see how all strategy works in one account
  • #2,651
  • Dec 5, 2015 2:58pm Dec 5, 2015 2:58pm
It's very important that all of us are running different kind of forward testing, so we can explore the entire scope of options with stop and limit orders!
  • #2,652
  • Dec 5, 2015 4:57pm Dec 5, 2015 4:57pm
Quoting radityo.ardi
{quote} Your magic number must be same. It can't be anything else. I've tested both v1.7 and v1.8, the magic number mechanism still work. Even a few weeks ago I wanted to set 2 different strategy on the same account, it was behaving the same like yours, even worse. The account sets Active (IN time range) open the order, but then it closes all orders. Then I realized the magic number was still same.
Let me test again this week. Let say i have 2 eurusd charts with 2 EA with different magic number, i would like to close all orders in2 charts no matter opened by EA1 or EA2 if TP$. Possible to do this? Or each EA only responsible for the order opened that EA created? Thanks.
  • #2,653
  • Dec 5, 2015 8:24pm Dec 5, 2015 8:24pm
Quoting happytrade38
{quote} Let me test again this week. Let say i have 2 eurusd charts with 2 EA with different magic number, i would like to close all orders in2 charts no matter opened by EA1 or EA2 if TP$. Possible to do this? Or each EA only responsible for the order opened that EA created? Thanks.
Each EA attached is only responsible for their magic number. When you click force close all, it'll only close the orders created by it.
If you ask me to code/fix your EA... it's probably not for free...
  • #2,654
  • Dec 6, 2015 9:01am Dec 6, 2015 9:01am
Quoting radityo.ardi
{quote} Just for your information, HistData, for Singapore Time, I need to shift to +13 hours. There's no time conversion mechanism, so we should count the timezone our own compared to the EST time recorded in HistData time. I've had a hard time to understand the Strategy Tester date-time mechanism. If you run it in the Strategy Tester, EA will only consider it as local time.
Yup, i'm aware of it. Thats why I use this
Attached Image
. I have compared the trade lists between backtest and live account on november, they have similar time and price on their orders.
But now, after I did the same backtest, the result is different, will try local time tomorrow.

Quoting radityo.ardi
{quote}14-15 Jan, no idea.
Ah, found why the account blew. I used the new set file (v.1.8) that has 100 Grid Step and Close Type : Target Based or Min Profit Open Orders.
After I tried the old set file (from v1.7) the account survive.
  • #2,655
  • Dec 6, 2015 10:42am Dec 6, 2015 10:42am
Quoting yogasampurno
{quote} Yup, i'm aware of it. Thats why I use this {image}. I have compared the trade lists between backtest and live account on november, they have similar time and price on their orders. But now, after I did the same backtest, the result is different, will try local time tomorrow.
Hmmm... I'm not sure as well how to do it with backtest.
Last time I checked, no matter you change the set config to GMT, Local or Server time, it always do this logic:
GMT Time = Local Time = Server Time.
So, if I set time start at 03:00 with GMT, it will start at 03:00 based on the history. It will also start at 03:00 if I set to Local Time, or Server Time. So, be watch out with this bug in Strategy Tester. Though I feel that my MT4 is updated to the latest, but this bug still exist.

Quoting yogasampurno
{quote} Ah, found why the account blew. I used the new set file (v.1.8) that has 100 Grid Step and Close Type : Target Based or Min Profit Open Orders. After I tried the old set file (from v1.7) the account survive.
Then you need to check which version of EA you are using? Because v1.7 and v1.8 there's a differences in the set file. You can't mix running v1.8 EA with v1.7 set file, or vice versa.
If you ask me to code/fix your EA... it's probably not for free...
  • #2,656
  • Dec 6, 2015 10:45am Dec 6, 2015 10:45am
I'll release v1.9 tomorrow. It has a few bug fixes, including the one for Max Cycle.

I think I can't wait to start v2.0 development with massive enhancements!
If you ask me to code/fix your EA... it's probably not for free...
  • #2,657
  • Edited 12:59pm Dec 6, 2015 11:55am | Edited 12:59pm
Quoting radityo.ardi
I'll release v1.9 tomorrow. It has a few bug fixes, including the one for Max Cycle. I think I can't wait to start v2.0 development with massive enhancements!
Finally I'm back home!
Ahah we all can't wait for the developments! This EA is kind of magic!
(but I know we are all waiting to hear the "money printing idea" that you had ahah!)

Live with the 2 Litims settings already posted and feeling so gooood... (I took off the Stop set file from Live and back it to Demo because i feel is more stable using Limits, need to work more on it, well on news is working well)
The key is to use the EA with no greed! Little daily steps are more then enough! If there are signs that the market could be a storm (red news) just pass the day...No problem...

Next week I will also start a new Demo on EURGBP (same trade windows that EURUSD, 18:00 -> 22:00 GMT) with the aggressive set file, due that EURGBP has lower volatility... I'm also starting considering other pair, my "without greed" (and a fast back test) approach suggested to me this plan:

GBPUSD - 20:00 GMT - 1 cycle only:
Lots Multiplier = 0.00007 (I thought would be better use 0.0001 but GBPUSD moves wider and using tight grid I prefer user a little lot size)
Target Multiplier = 0.005 (0.5%)
Grid Step (points) = 40
Current price interval (points) = 30
Closure logic = "Target based or Middle point"
Middle Point Range (points) = 30 (this is thought because i'm planning to use v1.8 and it doesn't have that loved bug that consider the "middle point" all the "middle area" so I put the "Middle Point Range" to the same size of the "Current Price Interval". It should recreate that "area". So it should work like v1.7 that it doesn't need to back exactly in the middle point but is enough that the price come back just a point in the middle area)
Middle Point Activation (Order Count) = 2
Cycle Counter = 1 (1 cycle for day)

I hope that I explained it "understandable". If yes I would also ask to you: to recreate the v1.7 "Middle Point" bug I could (like explained before) use a wider "Middle Point Range" but also use the closure logic "Target Based or Min Profit Open Orders" and set the counter "Min Open Profit Orders" = 2 right?

I'm also searching other pairs to use this "1 cycle for day approch"...
Will update the results of the tests...

Have a nice week to all here!

EDIT: for the GBPUSD the start time was 20:00 GMT -> I wrote 21:00 because i'm GMT +1. Corrected... And also added GBPJPY with identical approach (1 Limit Cycle)
  • #2,658
  • Dec 6, 2015 11:04pm Dec 6, 2015 11:04pm
Quoting radityo.ardi
{quote} Hmmm... I'm not sure as well how to do it with backtest. Last time I checked, no matter you change the set config to GMT, Local or Server time, it always do this logic: GMT Time = Local Time = Server Time. So, if I set time start at 03:00 with GMT, it will start at 03:00 based on the history. It will also start at 03:00 if I set to Local Time, or Server Time. So, be watch out with this bug in Strategy Tester. Though I feel that my MT4 is updated to the latest, but this bug still exist. {quote} Then you need to check which version of EA you...
Dear, why not print the version number in the screen?
  • #2,659
  • Dec 6, 2015 11:13pm Dec 6, 2015 11:13pm
Quoting polomine
{quote} Dear, why not print the version number in the screen?
Version is there on the tab when you attach EA.
Attached Image (click to enlarge)
Click to Enlarge Name: Screenshot1.png Size: 49 KB
If you ask me to code/fix your EA... it's probably not for free...
  • #2,660
  • Dec 6, 2015 11:35pm Dec 6, 2015 11:35pm
hi radityo, really thanks for your contributions to society .
good karma : ) i will surely support your charity

i have been backtesting your ea, latest version using your live.set file
and i think i found some strange behaviour

the fixed stoploss did not work, i set 1000 usd , its mean if my equity drop to 1000 usd, should all close .
but i cannot get it active, please tell me how to set the stoploss

please see the attachment
Attached Image (click to enlarge)
Click to Enlarge Name: fixedstoploss error.png Size: 150 KB
0 traders viewing now