Support Board
Date/Time: Sat, 11 Jan 2025 14:48:37 +0000
Volume At Price Threshold markers not always appearing
View Count: 1073
[2015-08-12 12:49:24] |
kas64h - Posts: 87 |
The Volume At Price Threshold Alerts visual markers (configured on the Subgraphs tab), do not appear to always be firing. I've double-checked my settings which seem ok. Sometimes a marker will be added when the threshold is exceeded, and other times nothing is added. I'm adding them to a Numbers Bars Chart displaying Bid Vol x Ask Vol colouring numbers on the dominant side only. This is happening regularly, BOTH using a paid and/or free data feed. Sierra is completely up to date. Not sure if I have something setup incorrectly (it seems fairly straight-forward), or a potential bug?
|
[2015-08-12 13:52:15] |
Sierra Chart Engineering - Posts: 104368 |
We will look into this.
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 |
[2015-08-14 22:46:27] |
Al SC Developer - Posts: 434 |
In our testing we do not see any issues. It is possible that there is a study ordering issue though. In your study list (F6), be sure your Threshold Alert study is after the numbers bar study, or the markers may be drawn behind the numbers bars. To see if the study is marking bars, you can also use the Tool Values Window to see if the trigger prices are set for any bar. If the triggered values are zero, then they were not triggered, otherwise there should be a marker at the indicated price. |
[2015-08-15 12:01:51] |
kas64h - Posts: 87 |
Thanks for your reply. I've checked the study order, and the Volume At Price Threshold Alert is last in the list as advised. However, I think I've figured out what's going on: As can be seen from the screenshots attached, the marker is only put in place once per bar, ignoring any further threshold breaches within the same bar. When the Bid Volume Threshold is set to 70, the Marker is added at 11080, but nowhere else. When the Bid Volume Threshold is set to 80, the Marker is added at 11100, but nowhere else. I hadn't realised this, and had assumed a marker would be entered every time the threshold limit was breached (even within the same bar). Is there a setting somewhere that will ensure a marker is added every time the threshold is breached within the same bar? I thought the 'Alert Only Once per Bar' setting on the Alerts tab may effect this (see the 'Threshold_Alerts Tab' attached screenshot), but it has no impact on the marker behaviour. Date Time Of Last Edit: 2015-08-15 12:35:44
|
Private File Private File Private File Private File |
[2015-08-15 13:42:13] |
Al SC Developer - Posts: 434 |
No, this is by design. There can only be one alert per bar with this study because a subgraph is used to place the marker on the chart, and a subgraph can only have a single value per bar.
|
[2016-12-01 02:49:57] |
zippyzip - Posts: 293 |
i noticed u made v2 with 60 subgraphs , what is point of that , ? anyway to add options to each subgraph so i can have diff size points fire off at different size volume , with out having to put study on 5 times ? thanks |
[2016-12-01 05:10:00] |
Sierra Chart Engineering - Posts: 104368 |
We can only refer you to the documentation here: https://www.sierrachart.com/index.php?page=doc/TechnicalStudiesReference.html#s386 There is no additional work will be doing on the study. 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 |
To post a message in this thread, you need to log in with your Sierra Chart account: