I have tried to set this up for automatic trading, and I get this error:
The following changes must be applied before sending the code to ProOrder :
– Trading systems with orders that partially close a position cannot be sent to ProOrder (ex: SELL 3 SHARES AT MARKET). Make sure that no quantity is specified in instructions to close positions (in this case, the instruction closes the entire position). Ex:
SELL AT MARKET
EXITSHORT AT 1.5 LIMIT
Yes – as far as I can tell it’s mainly an issue where I was flat over night.
At the moment I’m saying “if not onmarket and fastMA>slowMA go long”, but that’s not true – I might have closed a long position the night before and there’s been no crosseover to make me go long against. What I want it to do is check whether at 9pm fast MA<slowMA, and has now risen above it, then go long.
I think you should clean up the code first. Because you have used the “simplified creation” system, some variables are repeated twice (moving average) and that is a mess to debug it 🙂
It don’t needs to have the same moving average to be declared more than one time, so when you are making your conditionals statements, you may have type the wrong MA variables names (indicatorX).. You should also named them : “SlowMA”, “FastMA”, etc.
Then, about the 7am trades, you can easily debug it with only testing one condition at a time. Firstly, test “//close long”, if it’s ok test “//close long and go short”, etc.
I’ve been trialling the system on a demo account for a couple of weeks, and it’s mainly performing as I would expect.
However, there are times when it’s not doing what I want it to – for example when I have a ‘close call’ where the moving averages crosses in one bar, but then goes back the other way in the next bar. In real life I wouldn’t take the trade (or close the trade), but the system is.
What I want the system to do is “if the previous candle saw a cross, AND this candle sees the MA stays over/under, then take the trade at the close of the 2nd candle”.
Here is my code for a long example:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
// Conditions to enter long positions
indicator1=ExponentialAverage[x](close)
indicator2=ExponentialAverage[z](close)
c1=(indicator1CROSSES OVERindicator2)
indicator3=ExponentialAverage[x](close)
indicator4=ExponentialAverage[z](close)
c2=(indicator3>indicator4)
IFc1ANDc2THEN
BUYpositionsizePERPOINTATMARKET
ENDIF
// Conditions to exit long positions
indicator5=ExponentialAverage[x](close[1])
indicator6=ExponentialAverage[y](close[1])
c3=(indicator5CROSSES UNDERindicator6)
indicator7=ExponentialAverage[x](close)
indicator8=ExponentialAverage[y](close)
c4=(indicator7<indicator8)
IFc3ANDc4THEN
SELLATMARKET
Attached is a screenshot from this morning, where a short position was closed due to the fast MA crossing over the middle MA – but each time it dropped back down below in the next bar (so I wouldn’t exit the short position).
Yes, whether it’s long or short, and whether it’s entering a new trade or closing one.
For example, if using 10 minute candles – if during the 7am candle the fast MA crosses over the slow MA, and at the end of the 7.10 candle it’s still above it – open a new long position. If it crosses over, but falls back below, no trade.
I have seen another great example this morning – where a new long position was closed and reversed to a short position when it shouldn’t have.
Attached are the 10 minute candles, the blue circles are where trades were taken, and the red circle is where the trade would have been (if I were trading manually).
It makes a big difference, especially in a volatile open like today!
just been reading through your posts. It looks like I manually trade a very similar system to you, did you happen to learnt it from an online course? (Could be the same one) I have also been trying to code the system but my results so far have been way off my manual results.
To help us continually offer you the best experience on ProRealCode, we use cookies. By clicking on "Continue" you are agreeing to our use of them. You can also check our "privacy policy" page for more information.Continue
