Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 27 Apr 2024 04:30:54 +0000
Trading System Based on Alert Condition: Constraints/Limits
View Count: 523
| [2018-10-07 06:02:40] |
| gayer2428 - Posts: 75 |
|
I have been playing with TSBAC for a while now and I became aware of some severe limitations in its capabilities. For instance, I have a simple alert (ID53) that says: OR(ID29.SG1 = 1, ID8.SG1 >= 1, ID3.SG23 = 2, ID3.SG23 = 4) Now when I try using ID53 in a BUY-ENTRY/SELL-ENTRY as a shortcut (instead of deep diving and referencing the individual elements of ID53) like this: AND(ID13.SG1 > 0, ID26.SG1 > 0, ID53), TSBAC fails to detect it when the entire condition becomes true. Now I break up ID53 into its basic components, and also combine it with a couple of other (no-shortcut, basic) conditions. It worked! AND(ID13.SG1 > 0, ID26.SG1 > 0, OR(ID29.SG1 > 0, ID8.SG1 > 0, ID3.SG23 = 2, ID3.SG23 = 4)) SC has a 500-char limit in the Alert box; using shortcuts is one way I manage to stay within the limit. My question is, why does SC impose such a limitation on TSBAC capabilities? Any alert, however complex, entered into the BUY/SELL ENTRY/EXIT Alerts should work just as they would if they were standalone alerts not attached to TSBAC. TSBAC is a powerful tool when it works. It's been needlessly hobbled with such severe limits. Please, SC, won't you fix this soon? Thanks. |
| [2018-10-07 11:42:42] |
| gayer2428 - Posts: 75 |
|
By shortcut, I meant encapsulation. Encapsulating complex conditions in alerts makes it easier for use elsewhere in the chart as opposed to repeatedly referencing the individual components from the encapsulated alert condition. |
| [2018-10-07 21:28:39] |
| |
|
TSBAC fails to detect it when the entire condition becomes true. It would be exceptionally unlikely to be some kind of Sierra Chart software problem. You need to tell us why. Refer to this option on the Alerts tab to help you with this:Study/Chart Alerts And Scanning: Log Evaluated Formula at Each Evaluation It could also be related to this: Chart Studies: Study Calculation Precedence And Related Issues Now I break up ID53 into its basic components, and also combine it with a couple of other (no-shortcut, basic) conditions. It worked! My question is, why does SC impose such a limitation on TSBAC capabilities? What are you referring to?Any alert, however complex, entered into the BUY/SELL ENTRY/EXIT Alerts should work just as they would if they were standalone alerts not attached to TSBAC. We cannot know what the issue is. You need to go through this and debug this.Encapsulating complex conditions in alerts makes it easier for use elsewhere in the chart as opposed to repeatedly referencing the individual components from the encapsulated alert condition. 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: 2018-10-07 21:29:37
|
To post a message in this thread, you need to log in with your Sierra Chart account: