Indicators for Igroks method | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Custom Indicators vs. Technical Indicators 6 replies

Indicators and Rules for Simple Method of Scalping GBP/Jpy on 5 min chart 18 replies

Digital Indicators of Adaptive Trend & Cycle Following Method 4 replies

bo7a method... method for GBP/JPY 205 replies

Post your Sidus Method add on indicators here. 5 replies

Attachments: Indicators for Igroks method
Exit Attachments

Indicators for Igroks method

  • #1
  • First Post: Edited Jun 17, 2009 1:00am May 29, 2009 11:43am | Edited Jun 17, 2009 1:00am
Post your indicators, suggestions and updates in here.
Measure twice, cut once
  • #2
  • May 29, 2009 11:49am May 29, 2009 11:49am
Here's Labais53 latest update, I'm looking forward to test it It should include all main moves along with ATR for d/w/m. Well done so far !
Attached File(s)
File Type: mq4 # RANGE_TRADER_9.03 Labais53.mq4   10 KB | 874 downloads
Measure twice, cut once
  • #3
  • May 29, 2009 12:50pm May 29, 2009 12:50pm
Still got ranging (monthly)
Attached Image (click to enlarge)
Click to Enlarge Name: eu.jpg Size: 53 KB
Measure twice, cut once
  • #4
  • May 29, 2009 8:07pm May 29, 2009 8:07pm
Quoting aediaz1
Still got ranging (monthly)
Looks OK for me But still it is an early beta, so much more needs to be done to check if data is present for analysis. RANGING means that indicator did not find time of high and low with the chosen precision: M1 for day and week, H1 for month D1 for year. Precision is important if there is one big bar making both period highs and lows - if bar has too high timeframe, then who knows which end came first
Attached Image (click to enlarge)
Click to Enlarge Name: usdjpy.gif Size: 51 KB
  • #5
  • May 30, 2009 1:23am May 30, 2009 1:23am
I completely changed main moves code, so now it should work No RANGING anymore, it says "no history" if there is no M1 or H1 timeframe history long enough to get the appropriate move. It also says "no bars" if one bar makes both high and low for the period - might happen in its beginning.

As for history, I read in mql4.com that there are problems with iLow() and local history (info in MT History Center), no other solution as to load history manually was given.

I also made the first step for visually better picture (rather than info dump in the left upper corner) and moved main moves info as label box to the right - where most of such indis usually are put. Enjoy
Attached File(s)
File Type: mq4 # RANGE_TRADER_9.04 Labais53.mq4   16 KB | 618 downloads
  • #6
  • May 30, 2009 1:44am May 30, 2009 1:44am
posting to subscribe
  • #7
  • May 31, 2009 4:53pm May 31, 2009 4:53pm
Quoting Labais53
I completely changed main moves code, so now it should work No RANGING anymore, it says "no history" if there is no M1 or H1 timeframe history long enough to get the appropriate move. It also says "no bars" if one bar makes both high and low for the period - might happen in its beginning.

As for history, I read in mql4.com that there are problems with iLow() and local history (info in MT History Center), no other solution as to load history manually was given.

I also made the first step for visually better picture (rather than info dump...
Great news! I liked your visual changes, looked much better
Wish I had something to tribute with on your history case, but I'm 100% clueless when it comes to programming, thats why I appreciate your work

I think it would make sense to add last day/week/month main moves. Some of the templates depends on previous main moves.
Measure twice, cut once
  • #8
  • May 31, 2009 9:57pm May 31, 2009 9:57pm
Quoting aediaz1
Great news! I liked your visual changes, looked much better
Wish I had something to tribute with on your history case, but I'm 100% clueless when it comes to programming, thats why I appreciate your work

I think it would make sense to add last day/week/month main moves. Some of the templates depends on previous main moves.
Ultimately my goal is to have everything on the right side as label, keeping left upper side comment style optional for compatibility.

First we need to test this algo for main moves, if it is more or less OK I will extend it to last period moves. As for history - I think it is just an issue to be aware of, if pros at mql4.com site don't know how to solve it (force history download in code), so be it Besides, I need to implement timezone adjustment, for all daily moves to start at 23 CET, now they start with daily candle of broker. Dont know how important it is for longer moves.
  • #9
  • May 31, 2009 10:12pm May 31, 2009 10:12pm
I just had an idea, dont know if it makes sense. Rather than simply programming last period move, I could provide info for the length of present move, e.g. if it says:

- main move (daily) UP @ 1 period - it means that yesterdays move was down and we are dealing with fresh up move
- main move UP @ 3 periods - you know that yesterday was up, and more - it is already for the third day in the upmove.

Does it make sense at all?
  • #10
  • May 31, 2009 11:57pm May 31, 2009 11:57pm
Looks like I found reason for RANGING - No History Indicator fails at the moment when the last bar actually makes new high low which defines main move, i.e., when M1 bars for daily/weekly and H1 bars for monthly/year make new moves higher-lower, the appropriate MT4 functions fail.

This is my first priority to solve this issue and I will work on it.
  • #11
  • Jun 1, 2009 12:34am Jun 1, 2009 12:34am
Quoting Labais53
Looks like I found reason for RANGING - No History Indicator fails at the moment when the last bar actually makes new high low which defines main move, i.e., when M1 bars for daily/weekly and H1 bars for monthly/year make new moves higher-lower, the appropriate MT4 functions fail.

This is my first priority to solve this issue and I will work on it.
I did a quick dirty solution to this issue, if it works then we can make it permanent new version out
Attached File(s)
File Type: mq4 # RANGE_TRADER_9.05 Labais53.mq4   16 KB | 522 downloads
  • #12
  • Jun 1, 2009 8:17am Jun 1, 2009 8:17am
Quoting Labais53
I just had an idea, dont know if it makes sense. Rather than simply programming last period move, I could provide info for the length of present move, e.g. if it says:

- main move (daily) UP @ 1 period - it means that yesterdays move was down and we are dealing with fresh up move
- main move UP @ 3 periods - you know that yesterday was up, and more - it is already for the third day in the upmove.

Does it make sense at all?
Should work for MMOTD at least, how about week/monthly ? I'll try your newly posted indi and provide some feedback in a few minutes

Edit; yeah that could work for a start :=)
Measure twice, cut once
  • #13
  • Jun 11, 2009 3:25am Jun 11, 2009 3:25am
Hello Labais53,

I like your indicator a lot, but I guess it has been programmed for 5 digits brokers. What can I do to adapt it to 4 digits brokers?

Thanks,

Ramon
  • #14
  • Jun 12, 2009 7:09am Jun 12, 2009 7:09am
Quoting oblo
Hello Labais53,

I like your indicator a lot, but I guess it has been programmed for 5 digits brokers. What can I do to adapt it to 4 digits brokers?

Thanks,

Ramon
Hi!

This version should autodetect broker digits, a small but nice improvement is also added - % of range completion
Attached File(s)
File Type: mq4 # RANGE_TRADER_9.07 Labais53.mq4   17 KB | 636 downloads
  • #15
  • Jun 13, 2009 3:01am Jun 13, 2009 3:01am
Quoting Labais53
Hi!

This version should autodetect broker digits, a small but nice improvement is also added - % of range completion
That's a nice improvement ! Thanks Labais !
Measure twice, cut once
  • #16
  • Jun 13, 2009 2:22pm Jun 13, 2009 2:22pm
Thanks a lot, now it works wonderfully.
Thanks,

Ramon

Quoting Labais53
Hi!

This version should autodetect broker digits, a small but nice improvement is also added - % of range completion
  • #17
  • Jun 14, 2009 3:59am Jun 14, 2009 3:59am
Thanks for the nice work Labais
  • #18
  • Jun 14, 2009 5:45pm Jun 14, 2009 5:45pm
Thanks for the indi. I have some issues using this indi whereby the info given by the indi of the main move does not tally with the actual PA on the chart. Eg. Day Main move by indicator is down but on the chart it is up and so on. Is it because of the broker time different. If it is so, can we have the choice of time selection base on the individual broker opening hour.

Secondly im requesting for the indi to draw the following line on the chart

1.Daily open
2.Weekly open
3.Monthly open
4.Yearly open

It has been observed these lines have been respected by the PA quite a bit as support and resistance. It will be helpful for the traders to see on the chart whereabout these line so that you can make appropriate decision when to enter the market as well leaving the market besides deciding when to take profit and deciding your stop lost.

I have indi for daily open attached. May be someone can code the above request.
Attached File(s)
File Type: mq4 daily_open_line.mq4   2 KB | 442 downloads
  • #19
  • Jun 16, 2009 2:47am Jun 16, 2009 2:47am
I was thinking that having the indicator to plot where a new week/month starts/end would be quite handy. Maybe by coloring the w/m bar open with 2 different colors. What do you guys say?
Measure twice, cut once
  • #20
  • Jun 16, 2009 9:32pm Jun 16, 2009 9:32pm
I will try to include open time adjustment for main moves calculation in the next release of indi, gold standard for such things is the multi pivot indi utilised by THV team (THV SDX-TzPivots) - I myself use it for drawing daily opens and yesterdays High and Low. But I remember that this indi required a lot of support from the THV team (explaining time zones, GMT, DST to traders all around the globe), so my adjustment will be very basic - hourly shift (+ or -) of broker candles vs desired open time.

Besides, I am thinking about including some basic daily candlestick analysis - nature of opening range (I have noticed that main moves lower do not reverse if daily High-Open is low), nature of daily candle vs yesterday's - inside, outside, top/bottom broken bar etc. Would it be a good idea?
0 traders viewing now