READ-ONLY

The forum is now a read-only archive.

For bug reports & platform questions → [email protected]

Our community lives on Discord and YouTube — come join us!

AlgoWizard – Adding Short to LongOnly Template – Unexpected behaviours

1 replies

AC1962

Customer, bbp_participant, community, sq-ultimate, 90 replies.

Visit profile

1 year ago #289896

Hi SQ Support Team and Forum Members

When using SQX v142 AlgoWizard, to convert existing SQ template – RSI Rider template.sqx – from LongOnly a template to a LongShort template I encourter the following unexpected behaviours:

  1. The Short ‘Identification’ field repeatedly won’t allow me to alter name ‘EnterAtLimit1’ to anything else, e.g. ‘EnterAtLimit2’, (after multiple save attempts), thereby invoking an Error Message each time I attempt to use the new LongShort template in SQX ‘Build Strategies’. See attached annotated PDF of screenshots.
  2. When changing the Short field ‘At price level’ from original source Long ‘Random’ code to Short ‘Same as’ code, the ‘talib_ATR1’ variable no longer appends data range ‘7:21:7’, unlike all other Random variables that have been converted to ‘Same as’ for the Short template. See attached annotated PDF of screenshots. I’m not sure if this observation is a performance problem or not, but this unexpected behaviour seems to be peculiar to the ‘talib_ATR1’ variable, as none of the other Short ‘Same as’ variable exclude the data range in their name.

See attached copy of both *.sqx Template and *.cfx Project files.

I am new to using AlgoWizard, but otherwise very familiar with SQX. This converted SQ template is just a training example for me to learn to use AlgoWizard.

I welcome support in resolving Item 1 and understanding Item 2 above.

Thanks

AC1962

 

Attachments:
You must be logged in to view attached files.

0

tomas262

Administrator, sq-ultimate, 2 replies.

Visit profile

1 year ago #289991

Hello,

just to let you know .. we are completely reworking the AlgoWizard module. This new version will include fixes for all known issues reported so far including the one you mentioned. We want to make the new AW update available in the build 143

0

Viewing 1 replies (of 1 total)