Support Board
Date/Time: Tue, 26 Nov 2024 13:31:13 +0000
VbP Valley shown when another level has equal volume
View Count: 277
| [2023-12-06 20:43:24] |
| User719512 - Posts: 264 |
|
Please see attached image. At 12/6/2023 around 8:40am PT the ES contract shows a profile with a Valley at 4574.00 with 179 volume. There is a level at 4573.50 with 179 volume as well, with 226 volume in between. The Sensitivity was set to 8. According to the docs Volume By Price Study: Peaks and Valleys Sensitivity a Peak or Valley is only detected if all the volume "Sensitivity" ticks above and below are higher/lower, not equal. In the case when the sensitivity is set to 10, if the 10 price levels above and 10 price levels below a particular price level have a lower volume than the volume bar at the price level being compared to, then this will be considered a Peak Volume bar and a horizontal line is drawn outward from the Peak. In the case when the sensitivity is set to 10, if the 10 price levels above and 10 price levels below a particular price level have a higher volume than the volume bar at the price level being compared to, then this will be considered a Valley Volume bar and a horizontal line is drawn outward from the Valley. Please clarify the expected behavior, and why the higher 179 volume level was chosen, and not the lower, or perhaps why both were not identified? This seems to give misleading information, and another question if this is behaving as you have designed it, just how many (higher) levels could be between two low levels to have one/both identified as a valley? I am guessing you have a <= or >= in your code where it should be < and > only. Please advise. Depending on your response, I would assume either the docs or the code needs to be changed so they are in alignment. Thank you! Date Time Of Last Edit: 2023-12-06 22:30:46
|
 Screenshot 2023-12-06 122942.png / V - Attached On 2023-12-06 20:42:16 UTC - Size: 164.94 KB - 70 views |
| [2023-12-07 20:33:59] |
| Sierra_Chart Engineering - Posts: 17179 |
|
We will look this over.
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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2023-12-07 22:06:54] |
| Sierra_Chart Engineering - Posts: 17179 |
|
Documentation has been precisely updated to explain how this works. We do not want to change the implementation as there is a reason why it is designed the way it is. Probably to avoid side-by-side Peak or Valley lines.
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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2023-12-07 22:07:07
|
To post a message in this thread, you need to log in with your Sierra Chart account: