Jump to content

bgrtz

Members
  • Posts

    66
  • Joined

  • Last visited

Posts posted by bgrtz

  1. Saya curiga PointZeroOscillator itu adalah sebuah program semacam MACD channeling / awesome oscillator yang dibumbui dengan aroma perkalian tertentu misalkan selisih High-Low pada bar sebelumnya... hmm.. atau apa ya..hahaha.. yang jelas bukan HeikenAshi oscillator itu.. karena Array nya jadi bingung tuh kalau Heiken manggil heiken lagi lalu setiap ketemu heiken yang lama pada array saat ini selalu dibuat = 0 lagi untuk di tampilkan di layar.. hahaha.. nah kalau 0 maka apa yang harus di tampilkan.. hahaha... bener2 PointZerro.. (titik Nol)... Hahaha.. programmernya juga punya ide bagus tuh.. ngerjain programmer lainnya.. nah sebelum dapetin wajah aslinya maka kita semua blom bisa crack / buat educatednya...

     

    SEFC..

     

    Asal jangan keluarga fisher aja, Pak... wkwkwkwwkkkk...

     

    Btw, memang agak mirip dengan awesome tapi periode MA-nya diset berbeda (bukan default)

  2. Not Same Result ..

    HeikenAshiOscillator # PointZeroOscillator ..

    since i compile again.. still no pictured.. i think result iCustom(... PointZerro...) not same iCustom(...HeikenAshiOscillator...)

    Who have original PointZero...:) ?

     

    Kalau dilihat kodenya memang begitu, Pak.

     

    File "container"-nya (2 fixed1.mq4) memanggil "PointZeroOscillator", "Parabolic" dan "Heiken Ashi". Sementara "Heiken Ashi Oscillator" memanggil "Heiken Ashi". Jika "PointZeroOscillator" == "Heiken Ashi Oscillator" maka muter di "Heiken Ashi" saja.

     

    Kecuali programmer-nya lagi iseng... :)

     

    NB.

    It's just a comment for Mr. SEFC above. Not really useful for others. Cheers...

  3. lol. here is one of the indiis. between what I shared and this only experts please get cracking http://www.4shared.com/file/rroe3ue3/Point_Zero_Oscillator.html

     

    It's a HTML file.

    1. You must change the extension from .mq4 to .html

    2. Open it in your browser (IE, chrome, firefox, etc.)

    3. Block & copy the text shown at the browser

    4. Paste on any text editor (notepad)

    5. Save as "Heiken Ashi Oscillator.mq4"

     

    Yes, it's "Heiken Ashi Oscillator". I don't know if it's the same with "PointZeroOscillator" mentioned in "2 fixed1.mq4"

    icustom_36 = iCustom(Symbol(), 0, "PointZeroOscillator", CalculateOnBarClose, ChannelPeriod, 6, li_16);
    

     

    Or, just visit:

    http://[email protected]/file/_iD40vrg/Heiken_Ashi_Oscillator.html
    --or--
    http://[email protected]/8242
    

  4. e-Invester,

     

    Can you elaborate this indicator more?

     

    from this line:

     

    double R, TR, AA, BB, CC, DD, Tpoints, X, K, ER, SH1, SH2, SI;

     

    variable TR, K, ER, SH1, SH2 and SI is defined but not used.

     

    from this line:

    if (AA > BB && AA > CC) {
    R = (AA+BB)/2 + DD/4;
    }
    
    if (BB > CC && BB > AA) {
    R = (BB+AA)/2 + DD/4; 
    }
    

     

    why variable R calculated with exact same formula, although it has 2 different condition

     

    and most vital question:

     

    extern double T = 300.0;
    ..
    ..
    Tpoints = T * MarketInfo(Symbol(), MODE_POINT);
    

     

    the Tpoints value did not affect anything, because Tpoints is calculated outside, and never used inside the loop function. Since T is external variable, so changing T variable will not change anything

  5. I think historical screenshot are useless if we think that this indicator are repainting, because repainting indicator will change its history to "perfect" position after the fact.

     

    If Mr. Robert are willing to spare some time & provide some screenshot, please capture the screen every 15' (using TF 15 only) from 0700 - 1000 GMT (means 0700; 0715; 0730, etc.) in real time. I mean when "now" is 0715 GMT, then capture the screen, and post it here. And do same every 15 minutes.

     

    Then we can analyze the indi's behavior only for last "n" bars (lets say last 2 - 5 bars) for each captured screen. It's a long shot, but i believe will provide more accurate data

  6. sorry matrixfx, 4xmeter, my bad...

     

      for (i=0; i<=limit; i++) {
         valMA[i] = iMA(Symbol(), 0, MA_Period, 0, MA_Method, MA_Price, i);
         valVol[i] = iVolume(Symbol(), 0, i);
      }
      
      for (i=0; i<=limit; i++) {
         valVolMA[i] = iMAOnArray(valVol, 0, MA_Period, 0, MODE_SMA, i);
         
         if (((valVolMA[i] - valVolMA[i+1]) / valVolMA[i+1]) / ((valMA[i] - valMA[i+1]) / valMA[i+1]) > 1) {
            buffer1[i] = 1;
            buffer2[i] = EMPTY_VALUE;
            buffer3[i] = EMPTY_VALUE;
            
         } else if (((valVolMA[i] - valVolMA[i+1]) / valVolMA[i+1]) / ((valMA[i] - valMA[i+1]) / valMA[i+1]) < 1) {
            buffer1[i] = EMPTY_VALUE;
            buffer2[i] = 1;
            buffer3[i] = EMPTY_VALUE;
            
         } else {
            buffer1[i] = EMPTY_VALUE;
            buffer2[i] = EMPTY_VALUE;
            buffer3[i] = 1;
         }
      }
    

  7. I simplify the code. Modify to suit your needs, then share your final result with others here with more comprehensive description (what this do, how to use, or, if any, the relation to other indi's)

     

    #property indicator_separate_window
    #property indicator_buffers 6
    #property indicator_color1 Blue
    #property indicator_width1 3
    #property indicator_color2 Red
    #property indicator_width2 3
    #property indicator_color3 Yellow
    #property indicator_width3 3
    #property indicator_minimum 0
    #property indicator_maximum 2
    
    extern int MA_Period = 14;
    extern int MA_Method = 0;
    extern int MA_Price = 6;
    string shortName = "Elasticity";
    
    double buffer1[];
    double buffer2[];
    double buffer3[];
    double valMA[];
    double valVol[];
    double valVolMA[];
    
    
    int init() {
      SetIndexBuffer(0, buffer1);
      SetIndexStyle(0, DRAW_LINE, STYLE_SOLID, 1);
      SetIndexLabel(0, "Elasticity");
      SetIndexBuffer(1, buffer2);
      SetIndexStyle(1, DRAW_LINE, STYLE_SOLID, 1);
      SetIndexLabel(1, "Inelasticity");
      SetIndexBuffer(2, buffer3);
      SetIndexStyle(2, DRAW_LINE, STYLE_SOLID, 1);
      SetIndexLabel(2, "Idle");
      SetIndexBuffer(3, valMA);
      SetIndexStyle(3, DRAW_NONE);
      SetIndexBuffer(4, valVol);
      SetIndexStyle(4, DRAW_NONE);
      SetIndexBuffer(5, valVolMA);
      SetIndexStyle(5, DRAW_NONE);
      
      IndicatorShortName(shortName);
      
      return(0);
    }
    
    
    int start() {
      int limit = 1500;
      
      for (int i=0; i<=limit; i++) {
         valMA[i] = iMA(Symbol(), 0, MA_Period, 0, MA_Method, MA_Price, i);
         valVol[i] = iVolume(Symbol(), 0, i);
         valVolMA[i] = iMAOnArray(valVol, 0, MA_Period, 0, MODE_SMA, i);
         
         if (((valVolMA[i] - valVolMA[i+1]) / valVolMA[i+1]) / ((valMA[i] - valMA[i+1]) / valMA[i+1]) > 1) {
            buffer1[i] = 1;
            buffer2[i] = EMPTY_VALUE;
            buffer3[i] = EMPTY_VALUE;
            
         } else if (((valVolMA[i] - valVolMA[i+1]) / valVolMA[i+1]) / ((valMA[i] - valMA[i+1]) / valMA[i+1]) < 1) {
            buffer1[i] = EMPTY_VALUE;
            buffer2[i] = 1;
            buffer3[i] = EMPTY_VALUE;
            
         } else {
            buffer1[i] = EMPTY_VALUE;
            buffer2[i] = EMPTY_VALUE;
            buffer3[i] = 1;
         }
      }
      return(0);
    }
    

     

    http://img857.imageshack.us/img857/7340/elasticity.png

    Blue line is "elasticity", red is "inelasticity"

     

    Regards

  8. 1. Your Vol is not an array, so

    2. mv always return false, which is -1

    3. When you use mv as multiplication factor, the formula mv*((V1+100)/100) always give negative results

    4. Since V_1_0 is iVolume, so it always give positive results

    5. Final result, formula V_1_0 > (mv*((V1+100)/100) will compare "is [any positive value] bigger than [any negative value]". Of course the answer always TRUE

    6. It will pass the other condition (the else part). You will only see Lime bars

     

    NB.

    1. The mv is the index of array, not the value. So I believe you should use something like Vol[mv]

    2. I just read the code, did not have time to try it yet. Sorry if I was mistaken, just trying to help

     

    Regards

×
×
  • Create New...