Someone was asking me how easy it is to make a basic strategy out of the elite function series I am offering through eotpro.com. In particular, their mail said:
Do you have an example strategy with the Easy Language code that utilizes some of the Elite functions? …. For instance take the first PattyB signal after a bias line change, but only if Market Sync is with the trade.
My response:
…here is a strategy that gets in on the first patty b after a bias line change, if market sync is with it. It keeps a stop 2 ticks behind the last plot cycle, and gets out if it shows $200 profit:
vars:
pb(0),
ms(0);// set up the indicators
pb = $rtFirstNPattyBs(…pattyb input values…);
ms = $rtMktSyncPredict;// entry rules
if(pb = 1) and (ms >= -1) then buy next bar at market;
if(pb = -1) and (ms <= 1) then sell short next bar at market;// keep a stop beyond last plot cycle
sell next bar at $rtPlotCycleStopL(2) stop;
buy to cover next bar at $rtPlotCycleStopS(2) stop;// take $200 if we can get it
setprofittarget(200);
That’s not intended for real-world use! But, it’s an example of how simple things are simple, with these building blocks. The kinds of things that eotpro clients tend to ask for are packaged up, ready to be dropped into a strategy or custom indicator. Stuff that trips up non-programmers, like tracking the bias line and making sure you only take one signal (and only if it’s within the first few bars after the bias change, etc.) is all taken care of for you.
