Support Board
Date/Time: Sat, 11 Jan 2025 11:45:22 +0000
Number Bars Pullback Column
View Count: 2315
[2016-12-01 09:11:00] |
User19165 - Posts: 346 |
Hi there, I'm running a number bars chart on the DAX with a pullback column enabled and I'm noticing, consistently, that the pullback column is not resetting on new bar highs. It was difficult to capture because the dax is moving quite whippy right now, but here is an illustration. pb_2 shows the same pullback column values after price has made a new high for the current bar. |
[2016-12-01 09:23:25] |
User19165 - Posts: 346 |
Another example - again, this is only a problem for up bars making new bar highs.
|
[2016-12-01 09:51:44] |
Sierra Chart Engineering - Posts: 104368 |
Clearly the Tick Size and Value Format of that chart are not set correctly. You are creating your own problem. Those must be set correctly. You cannot alter them and expect Numbers Bars to function properly. Follow the instructions here: Global Symbol Settings: Update/Apply Symbol Settings to Charts Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
[2016-12-01 10:20:51] |
User19165 - Posts: 346 |
tick size is set to 1 point (not 0.50) and scale is set to 1 rather than 0.1. When I had started to explore these number charts I wanted to only show 1 point details (2 ticks) rather than every tick, because the dax moves so much I wouldn't be able to see a chart otherwise. Thinner markets benefit from this sort of data compression. I had searched on google about doing this in the number bars charts and I'm pretty sure I had read either on support forum or in the docs that this is how you achieve tick compression on number bar charts. OK, I just dug it up. http://www.sierrachart.com/index.php?page=doc/NumbersBars.php#AdjustingTickSizeForLargerIncrement If that is the incorrect thing to do, please advise what is. Thank you. Date Time Of Last Edit: 2016-12-01 10:21:25
|
[2016-12-01 19:00:01] |
Sierra Chart Engineering - Posts: 104368 |
OK understood. We do acknowledge that particular documentation. However, upon a code review, the Pullback column is not going to function correctly unless the Value Format is set to what it actually should be. In this case it needs to be .1. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
[2016-12-02 01:09:56] |
User19165 - Posts: 346 |
Just to clarify, you are meaning the settings in the chart settings window of the price display format must be set to 0.1 and I can leave the tick size set to 1 - this should make it work properly? I am strictly talking about the chart settings window - the underlying symbol settings of tick size and price display format remain unchanged at 0.5 and 0.1 respectively. |
[2016-12-02 02:34:37] |
Sierra Chart Engineering - Posts: 104368 |
The Price Display Format does need to be set to .1. It does not appear as though that setting the Tick Size to a larger value will cause a problem. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2016-12-02 02:36:10
|
To post a message in this thread, you need to log in with your Sierra Chart account: