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.
Bug: Point vs Tick when building range bars
- Mark Brown
- Posts: 182
- Joined: 29 Nov 2016
- Has thanked: 114 times
- Been thanked: 18 times
Bug: Point vs Tick when building range bars
Last edited by Mark Brown on 03 Dec 2020, edited 1 time in total.
Re: Point vs Tick when building range bars
Good point
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 ?
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 ?
- Mark Brown
- Posts: 182
- Joined: 29 Nov 2016
- Has thanked: 114 times
- Been thanked: 18 times
Re: Point vs Tick when building range bars
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.Good point
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 ?