Resolution of this issue (and other symmetry issues) will speed up builder production of useful symmetrical strategies drastically plus will eliminate a LOT of the work trying to figure out which ones are actually symmetrical (some of them only a programmer could figure out.)
The ultimate solution which would solve this bug is to simply have PRICE_HIGH negate to PRICE_LOW and vice versa all the time.
If we can't have that simple solution then...I get that it's hard to make complex blocks symmetrical but can we at least have it so that when symmetry is turned on we do not use PRICE_HIGH or PRICE_LOW in cases where we cannot negate? Like for moving averages and BB width? Also, can we please have a more standard Highest-High / Lowest-Low calculation that IS actually negatable for stop and limit order price levels?
Description changed:
Subject changed from BB width ratio using "PRICE_LOW" as applied price for both longs and shorts not symmetrical. Maybe just make that type of thing based on "Close" or "Typical" is best. to Many limit order order price level calculations are not symmetrical. They use "PRICE_LOW" or "PRICE_HIGH" and do not negate....
Description changed:
For this type of stop and limit order price level calculation.... I get that it's hard to make complex blocks symmetrical but can we at least have it so that when symmetry is turned on we do not use PRICE_HIGH or PRICE_LOW in cases where we cannot negate? Like for moving averages and BB width? Also, can we please have a more standard Highest-High / Lowest-Low calculation that IS actually negatable for stop and limit order price levels?
Attachment Strategy 0105 - temabug.sqx added
Here's another where entry price is based on TEMA:
Looks like about 20% of strategies produced by builder are effected plus these ones are hard to notice till you get deep in to testing because they don't give a hint in the pseudo code.
Attachment fsc.sqx added
Attachment Strategy 017 - builder - applied - bugged.sqx added
Attachment Strategy 016844-signalpricebugged.sqx added
Status changed from New to Fixed
I also added display of applied price in pseudo code.
Also for this type of stop and limit order price level calculation.... I get that it's hard to make complex blocks symmetrical but can we at least have it so that when symmetry is turned on we do not use PRICE_HIGH or PRICE_LOW in cases where we cannot negate? Like for moving averages? Also, can we please have a more standard Highest-High / Lowest-Low calculation that IS actually negatable for stop and limit order price levels?
I think how it is now, the builder can never produce a symmetrical limit order strategy where the order price is based on highs and lows... Is that correct?I wouldn't mind seeing the applied price in the pseudo code for everything!