Login Page - Create Account

Support Board


Date/Time: Wed, 01 May 2024 14:42:28 +0000



can trading evaluator symbology match denali?

View Count: 482

[2020-02-20 08:27:27]
uM8137 - Posts: 180
The trading evaluator is very nice. But the symbology is different from Denali.

Evaluator needs "ZNH20", whereas Denali needs "ZNH20_FUT_CBOT".

For my DTC trading client that wants to test on the evaluator and trade live on Denali, this is a pain. Could they be made consistent?
[2020-02-20 09:51:36]
Sierra Chart Engineering - Posts: 104368
When you say Denali you are referring to the Sierra Chart/TT order routing service. The symbols you see for the order routing service are based on what are required for TT. They are derived from TT symbol specifications (somewhat).

But you can translate quickly between them:
Edit Menu: Edit >> Translate Symbols To Current Service
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
[2020-02-20 10:11:17]
uM8137 - Posts: 180
Yes, when I said Denali, I meant the "Sierra Chart/TT order routing service". It could use a shorter name. :)

My standalone DTC client is what needs the right symbology. It's not in an ACSIL DLL.

It looks like I can issue EXCHANGE_LIST_REQUEST and SYMBOLS_FOR_EXCHANGE_REQUEST and probably figure it out from there.

So I can code up a differentiator. Its just one more thing different between sim and prod. And I like to minimize those(!)

So anyway: a nice to have would be to make the evaluator match the TT/SC order routing symbology.

Thank you.
Date Time Of Last Edit: 2020-02-20 10:12:21
[2020-02-20 10:58:37]
uM8137 - Posts: 180
I see that sending EXHANGE_LIST_REQUEST to the "Sierra Chart/TT order routing service" returns Exchange:"B3", and an empty Description field;

while issuing DTC message EXHANGE_LIST_REQUEST to the TradingEvaluator simulation service returns Exchange:"" (the empty string), and an empty Description field.

Can these Exchange values be relied upon to differentiate the two? The empty string makes me nervous, and "B3" is not particularly revealing or unique.
Date Time Of Last Edit: 2020-02-20 10:59:07

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account