Dev7 Custom indicators for Tradestation break older SQX algos

I imported custom indicators from the SQ.ELD file dated 8/31/22 into Tradestation 10 and many of my SQX v135 developed algos are now throwing TradeStation verify errors with these four functions:



SQ_StocksSizeByPrice

SQ_ConvertToPips

SQ_EMA

SQ_CorrectMinMaxSLPT



I've attached one of the algos for testing on your end.

Attachments
AAPL_15M_Algo1_01320913.sqx
(841.01 KiB)
  • Votes +3
  • Project StrategyQuant X
  • Type Bug
  • Status Fixed
  • Priority Normal

History

TR
#1

Tim

19.11.2022 16:09

Task created

TR
#2

Tim

19.11.2022 16:10

Subject changed from Dev7 Custom indicators for Tradestation in Dev7 break algos to Dev7 Custom indicators for Tradestation in break older SQX algos

TR
#3

Tim

19.11.2022 16:10

Subject changed from Dev7 Custom indicators for Tradestation in break older SQX algos to Dev7 Custom indicators for Tradestation break older SQX algos

TR
#4

Tim

19.11.2022 16:10
Voted for this task.
TR
#5

Tim

19.11.2022 17:13
Update:  I dug deeper into the changes in the four functions listed above and the build errors are all caused by changes made to the SQ_StockSizeByPrice function.  The changes involve an additional input added called "Multiplier" and several other new lines of code in the v136 version vs. the v135 version.  If I revert that function back to the v135 version then the older algos are able to verify.
E
#6

Emmanuel

19.11.2022 17:38
Voted for this task.
TR
#7

Tim

20.11.2022 16:50
Another update:  OK, I tried one more thing.  I opened the attached SQX file in v136 Dev7 and looked at the source code and lo and behold, it adds the 5th input (“nnMultiplier”) to the source code.  When viewing the source code of the SQX file in v135, that input isn’t there.  


Does this mean one needs to re-open each pre-v136 algo’s SQX file in v136 and re-copy the source code to TradeStation to use the v136 custom indicators?  If so, this needs to be remedied before release IMO as many many users have older algos that will break once v136 rolls out and will not want this hassle.

g
#8

Lee Guan Chuan

25.11.2022 09:17

Status changed from New to Fixed

Hi Tim,


You need to use the SQ.ELD from the SQX that you used to generate the code. This is because the indicator or functions can be updated in our new version when we update. 


Thank you.

TK
#9

t.kissels@outlook.de

30.12.2022 15:28
Voted for this task.

Votes: +3

Drop files to upload

or

choose files

Max size: 5MB

Not allowed: exe, msi, application, reg, php, js, htaccess, htpasswd, gitignore

...
Wait please