Bug: Point vs Tick when building range bars

Questions about MultiCharts and user contributed studies.
User avatar
Mark Brown
Posts: 182
Joined: 29 Nov 2016
Has thanked: 114 times
Been thanked: 18 times

Bug: Point vs Tick when building range bars

Postby Mark Brown » 23 Nov 2020

MC crew FYI

A point represents the smallest possible price change on the left side of a decimal point, while a tick represents the smallest possible price change on the right side of a decimal point.

When you build a range bar it should be stated as ticks per bar and not points per bar. Please get this changed it is not industry standard.
Last edited by Mark Brown on 03 Dec 2020, edited 1 time in total.

Mydesign
Posts: 177
Joined: 15 Feb 2017
Has thanked: 32 times
Been thanked: 39 times

Re: Point vs Tick when building range bars

Postby Mydesign » 24 Nov 2020

Good point :wink:

Actually despite the fact that Marc is correct, please DO NOT change it ! Otherwise we will have to rebuild tons of chart already set with current scaling rule :? Unless they convert automatically...

Once you know it, it's not a big deal. Terminology is not always standard, and sometimes standard can be confusing: for instance a "tick" is either a minimal price increment or a new quote, so what exactly should be a tick based chart ?

User avatar
Mark Brown
Posts: 182
Joined: 29 Nov 2016
Has thanked: 114 times
Been thanked: 18 times

Re: Point vs Tick when building range bars

Postby Mark Brown » 30 Nov 2020

Good point :wink:

Once you know it, it's not a big deal. Terminology is not always standard, and sometimes standard can be confusing: for instance a "tick" is either a minimal price increment or a new quote, so what exactly should be a tick based chart ?
depends on the data feed tt will give you every tick esignal and other sub par feeds will give you only changes from current price.


Return to “MultiCharts”