Indiors for Igroks method
Page 1 of 843 123 LastLast
Results 1 to 10 of 23

Thread: Indiors for Igroks method

  1. #1
    Post your indiors, updates and suggestions in here.

  2. #2
    Nevertheless obtained ranging (monthly)

  3. #3
    esSojesndresub00
    Guest
    Quote Originally Posted by ;
    Nevertheless got ranging (monthly)
    Looks OK for me personally But still it is an early beta, so more must be done to check if information is present for analysis. RANGING means that indior didn't find time of low and high with the chosen precision: M1 for week and day, H1 per month D1 annually. Truth is important if there's one massive pub making both period highs and lows - if pub has too large interval, then who knows that end arrived first

  4. #4
    esSojesndresub00
    Guest
    I totally changed main moves code, so now it should work No more RANGING anymore, it says no background if there's absolutely no M1 or H1 timeframe history long enough to acquire the appropriate move. It also says no bars if a single bar makes both low and high for the time - might happen in its own beginning.

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

    Additionally, I created the first step for better picture (rather than info dump in the left upper corner) and transferred main moves info as tag box into the right - in which many of such indis usually are put. Appreciate
    https://www.forexforum.co.za/attachm...21533748988.04

  5. #5
    caStttta
    Guest
    posting to subscribe

  6. #6
    Quote Originally Posted by ;
    I totally changed main moves code, so now it should operate No more RANGING anymore, it says no history if there is no M1 or H1 timeframe history long enough to acquire the appropriate move. It also says no pubs if a single bar makes both low and high for the time - might happen in its own beginning.

    As for history, I read in mql4.com that there are issues with iLow() and local history (info in MT History Center), no other remedy compared to load history manually was granted.

    Additionally, I made the first step for visually better picture (rather than info dump...
    Good news! I enjoyed your visual changes, appeared much better
    Wish I had something to tribute with on your own history case, but I'm 100% clueless in regards to programming, thats why I value your work

    I think it would make sense to add last day/week/month main moves. Previous moves that are main are depended on by some of the templates.

  7. #7
    esSojesndresub00
    Guest
    Quote Originally Posted by ;
    Great news! I enjoyed your visual adjustments, appeared much better
    Wish I had some thing to grapple with on your own history case, but I am 100% clueless when it comes to programming, thats why I value your work

    I personally think it could make sense to add last day/week/month main moves. Some of the templates depends on previous main moves.
    Ultimately my goal is to get everything on the right side as tag, maintaining left upper side comment design optional for compatibility.

    First we need to test this algo for main moves, if it is more or less OK I could stretch it to continue period moves. In terms of 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), therefore make it Besides, I need to implement timezone adjustment, for all daily moves to begin at 23 CET, now they begin with daily dose of broker. Dont know how significant it is for longer moves.

  8. #8
    esSojesndresub00
    Guest
    I only had an idea, dont know if it makes sense. As opposed to only programming last period move, I could provide info for the duration of present transfer, e.g. if it says:

    - primary move (daily) UP @ 1 interval - it usually means that yesterdays transfer was down and we're dealing with new up movement
    - primary move UP @ 3 phases - you know that yesterday was up, and much more - it's already for the third day in the upmove.

    Does this make sense at all?

  9. #9
    esSojesndresub00
    Guest
    Looks as though I found reason behind RANGING - No Background Indior fails in the moment when the previous bar actually makes new high which defines primary move, i.e., when M1 pubs for daily/weekly and H1 pubs for monthly/year make new moves higher-lower, the appropriate MT4 functions neglect.

    That is my first priority to work out this issue and I will work on it.

  10. #10
    esSojesndresub00
    Guest
    Quote Originally Posted by ;
    Seems like I found reason for RANGING - No Background Indior fails at the second when the last bar actually makes new high which defines main movement, i.e., when M1 bars for daily/weekly and H1 bars for monthly/year create new moves higher-lower, the proper MT4 functions neglect.

    That is my first priority to solve this matter and that I will work with it.
    I did a quick dirty solution for this dilemma, if it works then we can make it permanent new version out
    https://www.forexforum.co.za/attachm...42015957636.05

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.