How to add slope detection comparative to an oscillator/price? | Forex Factory

Options

Permalinks
Print Thread

Similar Threads

Looking for the slope of a slope histogram? 0 replies

Comparative Price Action 75 replies

Comparative Bar size Indicator 0 replies

Automatic Trend line, trend channel, support, resistance detection 3 replies

add slope of line to an indicator. 0 replies

Attachments: How to add slope detection comparative to an oscillator/price?
Exit Attachments

How to add slope detection comparative to an oscillator/price?

  • #1
  • First Post: Oct 10, 2014 12:26pm Oct 10, 2014 12:26pm
Hello guys,

Is there a drop in code or anyone know how to make a comparative slope detection against two values?

Many thanks

MM
  • #2
  • Oct 10, 2014 12:45pm Oct 10, 2014 12:45pm
Hi Madmoney,

Do you mean something like this? http://newtonexcelbach.files.wordpre...11/linest1.jpg I.e. first line's slope is 7.94428, second line's slope is 5.85028.
Even if you fall on your face, you're still moving forward.
  • #3
  • Oct 10, 2014 12:57pm Oct 10, 2014 12:57pm
Quoting Ralome
Hi Madmoney, Do you mean something like this? http://newtonexcelbach.files.wordpre...11/linest1.jpg I.e. first line's slope is 7.94428, second line's slope is 5.85028.
Yes, something like that. Let me go into more detail...

1. Up slope would be + and down slope would be -
2. Measures overall in diff or %
3. Comparison is done bar by bar
4. The comparison would be between type of MA (SMA,EMA,LWMA) and chosen indicator

Not sure if it is viable or how intensive it will be on CPU.

Thanks

MM
  • #4
  • Oct 10, 2014 1:04pm Oct 10, 2014 1:04pm
I've already experimented with stuff like that, so the code must be here somewhere. As for CPU, maybe when you start MT4 and it has to calculate several thousand bars at once, then it might take a few seconds. But, when it calculates latest bar only, should be instant.

I'm too braindead to try anything this evening, but I'll get back to it tomorrow and knock up a sample code.
Even if you fall on your face, you're still moving forward.
  • #5
  • Oct 10, 2014 7:03pm Oct 10, 2014 7:03pm
Quoting Ralome
I've already experimented with stuff like that, so the code must be here somewhere. As for CPU, maybe when you start MT4 and it has to calculate several thousand bars at once, then it might take a few seconds. But, when it calculates latest bar only, should be instant. I'm too braindead to try anything this evening, but I'll get back to it tomorrow and knock up a sample code.
Thanks Ralome.

Maybe a lookback feature would save it from calculating thousands of bars at once.

MM
  • #6
  • Oct 11, 2014 10:27am Oct 11, 2014 10:27am
Hi Madmoney,

please take a look at this. A bit of explanation:

1. ComparisonPeriod = 60 -> it will compare the slope of the last 60 pieces of data in each dataset.
2. MA_Method, MA_Period -> type and period of the MA (this will be DataSet1)

DataSet1[i]=iMA(NULL,0,MA_Period,0,MA_Method,PRICE_CLOSE,i);

3. DataSet2 will be the chosen indicator. I put a Stochastics for testing, you need to replace this with an iCustom in your case.

DataSet2[i]=iStochastic(NULL,0,240,1,1,MODE_SMA,STO_LOWHIGH,MODE_MAIN,i);

4. These two datasets have different units. In the MA's case, the unit is a pip = 0.0001. In the stoch's case, the unit is 1. This means one of the slopes need to be adjusted.

d1_slope=d1_sumxy/d1_sumx2*10000;

I hope this is what you had in mind, please test and get back to me if you have any questions.

Greets,
Ralome
Attached File(s)
File Type: mq4 Madmoney_SlopeComparison.mq4   3 KB | 822 downloads
Even if you fall on your face, you're still moving forward.
  • #7
  • Oct 11, 2014 10:37am Oct 11, 2014 10:37am
Quoting Ralome
Hi Madmoney, please take a look at this. A bit of explanation: 1. ComparisonPeriod = 60 -> it will compare the slope of the last 60 pieces of data in each dataset. 2. MA_Method, MA_Period -> type and period of the MA (this will be DataSet1) DataSet1=iMA(NULL,0,MA_Period,0,MA_Method,PRICE_CLOSE,i); 3. DataSet2 will be the chosen indicator. I put a Stochastics for testing, you need to replace this with an iCustom in your case. DataSet2=iStochastic(NULL,0,240,1,1,MODE_SMA,STO_LOWHIGH,MODE_MAIN,i); 4. These two datasets have different units. In...
That's ace!

Is this iCustom code applicable on line 84? -
double iCustom(
string symbol, // symbol
int timeframe, // timeframe
string name, // path/name of the custom indicator compiled program
... // custom indicator input parameters (if necessary)
int mode, // line index
int shift // shift
);

Many thanks

MM
  • #8
  • Oct 11, 2014 12:59pm Oct 11, 2014 12:59pm
Quoting Madmoney
{quote} That's ace! Is this iCustom code applicable on line 84? - double iCustom( string symbol, // symbol int timeframe, // timeframe string name, // path/name of the custom indicator compiled program ... // custom indicator input parameters (if necessary) int mode, // line index int shift // shift ); Many thanks MM
You're welcome!

83 in my editor, but yes. You simply replace

DataSet2[i]=iStochastic(NULL,0,240,1,1,MODE_SMA,STO_LOWHIGH,MODE_MAIN,i);

with

DataSet2[i]=iCustom(symbol, timeframe, etc...., i);

and it should be all right.

Ralome
Even if you fall on your face, you're still moving forward.
  • #9
  • Oct 11, 2014 1:15pm Oct 11, 2014 1:15pm
Quoting Madmoney
{quote} That's ace! Is this iCustom code applicable on line 84? - double iCustom( string symbol, // symbol int timeframe, // timeframe string name, // path/name of the custom indicator compiled program ... // custom indicator input parameters (if necessary) int mode, // line index int shift // shift ); Many thanks MM
...And don't forget to check the units and adjust if necessary, here (lines 106 & 107):

d1_slope=d1_sumxy/d1_sumx2*10000;
d2_slope=d2_sumxy/d2_sumx2;

Either remove the 10000 (if for example you compare two percentages), or change it to the appropriate number.
Even if you fall on your face, you're still moving forward.
  • #10
  • Oct 12, 2014 1:20pm Oct 12, 2014 1:20pm
Quoting Ralome
{quote} ...And don't forget to check the units and adjust if necessary, here (lines 106 & 107): d1_slope=d1_sumxy/d1_sumx2*10000; d2_slope=d2_sumxy/d2_sumx2; Either remove the 10000 (if for example you compare two percentages), or change it to the appropriate number.
I will try to make them small changes this week without causing an error, lol.

Many thanks

MM
  • #11
  • Oct 13, 2014 9:45am Oct 13, 2014 9:45am
Quoting Madmoney
{quote} I will try to make them small changes this week without causing an error, lol. Many thanks MM
I attempted to make the changes but there are errors and the resulting mess will not load on a chart.
  • #12
  • Last Post: Oct 14, 2014 4:03pm Oct 14, 2014 4:03pm
Quoting Ralome
{quote} ...And don't forget to check the units and adjust if necessary, here (lines 106 & 107): d1_slope=d1_sumxy/d1_sumx2*10000; d2_slope=d2_sumxy/d2_sumx2; Either remove the 10000 (if for example you compare two percentages), or change it to the appropriate number.
Thanks Ralome.

I think I gonna have to combine the two indicators somehow, to get rid of a certain issue.

MM
0 traders viewing now