Can Prorealcode handle a supertrend crossing a moving average (Hull) for buying and selling?
Also, can it be programmed to buy & sell according to a rise or fall (change in colour) of a supertrend or a moving average?
Thank you.
MazParticipant
Veteran
Yes.
Compare indicatorA with indicator A[1] and indicatorB with indicatorB[1]
You could also use the crosses over and crosses under syntax
>> Please update your country flag in your profile. Thank you 🙂 <<
You’ll find a lot of conversations about how to trigger trades depending of colour change:
https://www.prorealcode.com/topic/place-orders-when-a-curve-change-colour/
(this one is a good example).
Merci mes amis Maz et Nicolas.
I am a complete wimp when it comes to code and would rather pay an expert to get it right, even for simple things, than waste time making mistakes.
Could you tell me the approximate cost of private coding for the simple examples I gave above, i.e. supertrend/MA crosses to buy/sell & colour-change (=up/down) on a MA as buy/sell orders (not closed at specified levels)?
For customized help and quotes, please use the form on the
trading Programming Service page. Thank you.
Whereas a supertrend crossing a moving average is normally clear and unambiguous, a moving average change-in-colour from down (white) to up (black) can ‘flicker’ between colours until the bottom is fully formed. One could set the moving average to a higher number for smoothing (as viewed after the ‘U’) but flicker could have triggered several unintended trades during the colour transition. Could any members suggest a more-objective criterion than colour change to define the broad change from ‘short’ to ‘long’ which moving averages only fully reveal after the event? Thanks.
DaveParticipant
Senior
Hi Trevor, I found Increasing the smoothing factor or lookback to have a negative effect on order triggering itself, Hull’s, dema’s and tema’s on short periods have the most decisive colour change for me. Several unintended trade creations shouldn’t occur if your using accumulate order ‘false’ command in your code. dave
Dave: many thanks but can you explain a little more about Accumulate Order ‘False’ Commands? Is this a mechanism to prevent closing/re-opening trades which occur within the same candlestick, or the following few candles, to avoid whipsaw trading? Is it discussed in any other forum threads? Presumably our good friend Nicholas could include it in any paid service?
DaveParticipant
Senior
It just means the program will deal with each trade individually regardless of signal ‘flicker’ and not create any new orders until the previous one is closed. A few systems might want to build orders ‘in direction of trend’ say and would therefore set the accumulate order command to ‘true’.
Regards
Dave
