Menu
Sister Sites

Options

Bookmark Thread

First Page First Unread Last Page Last Post

Print Thread

Similar Threads

Extreme TMA System 16,197 replies

Happs with TMA Trading Journal 25 replies

Forex Reality Tour #1 - Market Trend % 48 replies

MTF TMA 287 replies

SnakeForce - simple TMA with alert? 3 replies

Attachments: TMA Reality Tour
Exit Attachments

TMA Reality Tour

Quoting charvo
awesome, ZZ, just found ur thread. ......am googling TMA slope and got here......because i try to figure out that "baluda indicator" s 'currency slope' algorithm.

the 1st look of those "currency strength slope" indicator over steve's site made me wondering if it repaints. it surely does, and i don't understand why would the author need that repainting for the indicator. ......nothing magic......

nice work, thanks again.
Thanks for your kind words.

I have never heard of a "baluda indicator"...so I'm not sure what algorithm it uses.

I just try to help folks with some of the technical aspects of forex trading. I leave it up to them to figure out what works and what doesn't. Some of the strategies using Tma (and its derivitives) are flat-out comical...some really don't have a clue. But I've always said there are 1000s of different ways to succeed in this business...to each their own I guess.

Having said that...I've created and explored a few Tma and TmaSlope (both individual pairs and currencies) indicators, and I must say they do not do much for me...certainly not as a trend determiner. I could maybe see using it as a tool to help identify reversals. But quite frankly, it's still just a Moving Average...albeit a "fancy" one. You can dress it up with different views and sophisticated algorithms, but, in the end, it is still just a Moving Average and has many of the same benefits and liabilities. As you said, there is "nothing magic" about it.

The TmaSlope has been a bit of a pain since the time I created it. My only hope is that it will help at least 1 person realize long-term profits...that would make it all worth while.

I hope your trading is going well!
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
Hi, first I have been using a lot of your indicators so thanks for your time I really like the TMASlopeTrue-CB, I added the norm slope indicator to show the Daily value0.51 all my TMASlopeTrue-CB’s are set at 0.40 so the Daily should be Green not grey it works fine on eurusd any ideas why it is grey on audusd.
Thanks, PC
Attached Image (click to enlarge)
Click to Enlarge Name: Daily.png Size: 97 KB
Of all the things I've lost I miss my mind the most .
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
Here both the Slope norm & CB are set to 0.40 & -0.40 they should be Ranging on W1 not Red so the problem is not new.
PC,
Attached Image (click to enlarge)
Click to Enlarge Name: eee.png Size: 95 KB
Of all the things I've lost I miss my mind the most .
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
Here again both the Slope norm & CB are set to 0.40 & -0.40 the CB H1 should be Red not grey and the W1 grey not green, and the slope norm D1 should be grey not Red.
Is there a way to display the value of the slope on the CB indicator bar to confirm color.
PC,
Attached Image (click to enlarge)
Click to Enlarge Name: eee.png Size: 99 KB
Of all the things I've lost I miss my mind the most .
Quoting Mr C
Here again both the Slope norm & CB are set to 0.40 & -0.40 the CB H1 should be Red not grey and the W1 grey not green, and the slope norm D1 should be grey not Red.

As stated in this post:

http://www.forexfactory.com/showthre...61#post5862861

you need to update the calcTmaSlope() function to reflect the algorithm you are using to calculate the slope. My best guess is that someone else created the "Slope norm" indicator you are using...thus that indicator probably has a different way of calculating the slope values than I used in the CB indicator. This difference in calculation methods is leading to the discrepencies between the indicators.

Quote
Is there a way to display the value of the slope on the CB indicator bar to confirm color.

Set eblnDebug = true
  • Post #66
  • Quote
  • Edited 10:50am Jul 31, 2012 9:49am | Edited 10:50am
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
Hi, the extrem tma info and Slope norm 1.5 have the same values, the tma true and CB are different from all values I will have to change the CB to match values of the Slope 1.5 norm and extrem tma info values thanks again for your time I will try and figure this out.

PC,
Attached Image (click to enlarge)
Click to Enlarge Name: z.png Size: 145 KB


Edit: I had the TMASlopeTrue set to 20 at 56 they match so the only one that does not match is the CB I will test it as is and compare the results and try to figure out how to match them.
Of all the things I've lost I miss my mind the most .
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
So it won’t be about just changing a few numbers, do you have any suggestions on a good book to figure this out.
Thanks’ PC,

Attached Image (click to enlarge)
Click to Enlarge Name: tsn1.5.png Size: 42 KB
Attached Image (click to enlarge)
Click to Enlarge Name: ttcb.png Size: 55 KB
Of all the things I've lost I miss my mind the most .
Quoting Mr C
So it won’t be about just changing a few numbers, do you have any suggestions on a good book to figure this out.
Yes, it is about just changing a few numbers. I don't know of any books that will help...sometimes it is just best to analyze the code and update it per your requirements.

If you are using one of the normalized versions of TmaSlope that is popular in some of the threads around here, then you probably just need to change this code:

Inserted Code
 
   // Calculate the TMA Slope
   double dblSlope = ( dblTma - dblPrev ) / gdblTruePoint;
 
   if ( eblnNormalize )
   {
      double dblAtr = iATR( Symbol(), gintTf, 100, 1 );
      int int15 = iBarShift( Symbol(), PERIOD_M15, iTime( Symbol(), gintTf, 0 ) );
      double dblAtr15 = iATR( Symbol(), PERIOD_M15, 100, int15+1 );
 
      if ( ( dblAtr > 0.0 ) && ( dblAtr15 > 0.0 ) ) 
      {      
         dblSlope *= ( dblAtr15 / dblAtr );
      }
   }

To this code:
Inserted Code
 
 
   // Calculate the TMA Slope
   double dblAtr = iATR( Symbol(), gintTf, eintAtrPeriod, 10 ) * 0.1;
   double dblSlope = ( dblTma - dblPrev ) / dblAtr;

Delete the eblnNormalize user input and add a new user input for eintAtrPeriod.

Then your values should match exactly. If not, then you are using a different algorithm and will need to update it to match. Screenshot below using Tma period = 20.
Attached Image (click to enlarge)
Click to Enlarge Name: ts-cb2.gif Size: 20 KB
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
Quoting zznbrm
Yes, it is about just changing a few numbers. I don't know of any books that will help...sometimes it is just best to analyze the code and update it per your requirements.

If you are using one of the normalized versions of TmaSlope that is popular in some of the threads around here, then you probably just need to change this code:

[code]
// Calculate the TMA Slope
double dblSlope = ( dblTma - dblPrev ) / gdblTruePoint;

if ( eblnNormalize )
{
double dblAtr = iATR( Symbol(), gintTf, 100, 1 );
int int15 = iBarShift(...
Thanks' again I have a direction to go in now, I also want to shorten the values to 2 digits EX: 0.30 not 0.30456 on the displayed bar if I am not back in a few days send Help!
PC,
Of all the things I've lost I miss my mind the most .
  • Post #70
  • Quote
  • Edited 7:58pm Jul 31, 2012 3:43pm | Edited 7:58pm
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
Hi again it all went good I made the changes compiled and no errors were found. But when I open the properties window it appears on the chart and seemed to be fine until I hit OK then the properties window goes white if I hit it again the whole screen goes white and I have to exit MT4, as long as it gave me errors I kept going but now I am lost.
PC,
Attached File(s)
File Type: mq4 MrC remixTmaSlopeTrue-CB.mq4   14 KB | 3,619 downloads


Edit: Thanks' for all the help, so far I like it the way it is, if you could let me know what I did wrong it would be nice to have a copy with the same readings as your 10.2 TmaSlopeTrue 4.30.
Of all the things I've lost I miss my mind the most .
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
It took a lot of coffee and a few walks before I realised I was an idiot once I figured that out everything came together I am testing it now it seems to work ok.
Thanks’ for pointing me in the right direction, PC
Of all the things I've lost I miss my mind the most .
Quoting Mr C
It took a lot of coffee and a few walks before I realised I was an idiot once I figured that out everything came together I am testing it now it seems to work ok.
Thanks’ for pointing me in the right direction, PC
Great...I'm glad it is working for you.
Mike - I thought I would answer your questions publicly because I'm sure there are others that don't understand either.

Q1) Does the TmaSlopeTrue measure the slope of the LWMA or the TMA?

As I have stated previously, the TmaSlopeTrue indicator measures the slope of the TMA.

See the screenshot below. The 1st indicator window shows the slope of the LWMA. Compare that to the slope of the Tma in the 2nd indicator window. The LWMA slope is more "jagged" than the Tma slope. Why? Because the algorithm used in the TMA "smooths" the previous value whereas the LWMA does not use any such smoothing algorithm.

Q2) Why does the MACD look very similar to the TmaSlopeTrue?

It really just boils down to the math involved. All of these indicators are based on moving averages. So they are all going to look similar, depending on the parameters used. This is why there is nothing magical about the Tma Slope - it is just a different way of calculating the difference between two moving averages.

See the screenshot below. The 3rd indicator window shows the MACD with settings that correspond to the Tma slope in the 2nd indicator window. They are very close. Why are they not exact? Because of the differences in the formulas used. Why are they very close to each other? Because they are both based upon the same moving averages.

I hope this clarifies it for you.
Attached Image (click to enlarge)
Click to Enlarge Name: eu-3.gif Size: 21 KB
Hi Z,

Great explanation with regards to the fuss about the TMA. So basically we are just looking at moving averages.

Could we therefore make a TMA of the T3 triple exponential average as this a particularly smooth ma ?

Btw I'm not a Techie or coder so if I'm talking out of my hat please ignore this post.

Thanks for the great work

Eamonn.
  •  Mr C
  • Joined Mar 2012 | Status: Knowledge is "potential" power | 439 Posts
Just a quick thank you, almost every cool indicator I open up has your name in it.
PC,
Of all the things I've lost I miss my mind the most .
Quoting Eamonn
Could we therefore make a TMA of the T3 triple exponential average as this a particularly smooth ma ?
You could probably somehow triangulate the T3 and then wrap a ATR envelope around it. But I can't imagine it would provide anything earth-shattering.

Creating an indicator to plot the slope of the T3 is possible also...you would just need to calculate the difference between the T3 value of the current bar and the T3 value of the previous bar.

Quote
Thanks for the great work

Thanks for your kind words.
Quoting Mr C
Just a quick thank you, almost every cool indicator I open up has your name in it.
PC,
Great...I'm glad I can help!
Quoting zznbrm
CB stands for Crystal Ball....
zznbrm, may I ask you how I can add those TmaSlope levels back up on the main chart? Thanks
Attached Image
Humble & Kalcker CLO2 = Covid killer
Quoting jusiur
zznbrm, may I ask you how I can add those TmaSlope levels back up on the main chart? Thanks
The "TmaSlopeTrue-CB" indicator applies the crystal ball algorithm to the current bar to identify the price levels to be displayed in the right margin of the chart.

To show these price levels for previous bars in the chart, you would need to apply that same algorithm to the previous bars and use indicator buffers to store that data.
Thanks for your reply. . . is a good challenge for a non coder like me, but I accept it !
Humble & Kalcker CLO2 = Covid killer
2 traders viewing now