Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Fri, 03 May 2024 13:16:50 +0000
TPO value area incorrect calculation using 2 level counting at the time !!!
View Count: 1241
| [2015-04-29 16:32:46] |
| JingIt - Posts: 44 |
|
When I compare TPO value area with my trading room, we got same value after SC team update 2 level counting level, but we got different value on some days. I was curious and do manual calculation on the day we can't match the value high & value low and found that SC did the calculation incorrectly on some days (usually different 1 point). My calculation match with value high and value low with my friend chart. Please refer to my attached excel file on how I count the TPO profile on 27/4/15 ES contract The counting rule I used was: 1 Compare sum of TPO of 2 level upper and lower POC 2 start counting the level has higher sum first, if both equal, we can pick one then start 3 continue counting in direction has higher sum compare to the level on other side of POC, if both sides equal again, we will count in direction has shorter distance from POC Repeat the process until the sum TPO meet 70% of total TPO The correct VH & VL on 27/4 are 2113.50 & 2101.50 While SC result is 2113.50 & 2100.50 There are days the VH and VL is lower 1 point compare to correct value (compare to another chart vendor calculation which I believe it is correct) Date Time Of Last Edit: 2015-04-29 16:37:52
|
 2015-04-30_0159.png / V - Attached On 2015-04-29 16:07:12 UTC - Size: 158.06 KB - 360 views  TPO calculation.xlsx - Attached On 2015-04-29 16:28:35 UTC - Size: 39.45 KB - 317 views |
| [2015-04-29 21:26:04] |
| |
|
We will check on this today.
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-05-01 03:46:42] |
| |
|
There are differences in the calculation method and the method currently used for counting single levels at a time is correct and accepted. Counting 2 levels at a time, follows the same method except counting two levels at a time. This is how it is done: http://www.sierrachart.com/index.php?page=doc/doc_TPOVolProfileCharts.html#Calculations 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-05-01 07:58:27] |
| JingIt - Posts: 44 |
|
Thank you SCE, seem like SC algo adds both the two prices above and the two prices below when those level are equal. Would it be possible SC team tweak and give users the another calculation method option? If both two prices above and two price bellow are equal, we will only add the one closest to TPO. I'm in a trading room with many users using SC and we will be very happy if this option available. Thanks in advance for consideration of this! |
| [2015-05-01 08:21:22] |
| |
|
When two levels are encountered which have an equal number of TPOs, add the one which is closest to the point of control?
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-05-01 08:53:11] |
| JingIt - Posts: 44 |
|
I take the calculation in my first post to give you an example, please check the attached file. Hope you can get my idea. This calculation method used by Esignal and Investor RT. Thank you for consideration SCE!! Date Time Of Last Edit: 2015-05-01 09:11:42
|
| 2015-01-30_0917.png / V - Attached On 2015-05-01 09:11:35 UTC - Size: 44.52 KB - 324 views |
| [2015-05-01 18:26:33] |
| |
|
We will solve 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-05-02 05:38:03] |
| Acro - Posts: 436 |
|
Thanks SC. I'd really appreciate this too. |
To post a message in this thread, you need to log in with your Sierra Chart account: