bubo wrote:

MrLong wrote:Hi Traders,

To backtest, you need to do the following.

string Pairs[] = { "EURUSD" }; <== enter the pair to backtest

//CreateSymbolList(); <== Highlight out, like //
//CreateADRList(); <== Highlight out, like //

extern bool useBoundryFilter =false; <== make sure it's set to false.

extern bool useOneDailyTrade = true;

Andy - have you managed to backtest the way you suggest? I tried your solution before on v1.07 and it did not produce trades during a period when the EA set pending orders on demo.

I agree that an optimization orgy is hardly of much benefit, but it would be useful for debugging and learning about some behaviours of the EA via backtest over a few weeks time, even if backtests are never perfect.

Thank you also to Brian - looking forward to hearing more about your backtesting!

zentauro67 wrote:I am very optimistic about the future of this ea but for now the results are a bit disappointing. Maybe there is something important that should be added. EA closely follows 10.4 but needs a human touch to filter low-probability trades. Perhaps the key is to consider the angle of the 240MA,avoiding trades when 240 is too flat and setting minimum levels of slope for 240.

TraderDesk wrote:

zentauro67 wrote:I am very optimistic about the future of this ea but for now the results are a bit disappointing. Maybe there is something important that should be added. EA closely follows 10.4 but needs a human touch to filter low-probability trades. Perhaps the key is to consider the angle of the 240MA,avoiding trades when 240 is too flat and setting minimum levels of slope for 240.

Hi there, what I would do in conjunction with the development of this EA is to match it with a risk management component that will decrease your R/R ratio. I am always looking for ways before I open a position to lower my risk and maximize my profit. If and when you can create a R/R that is better then 1/3 you will find that even losing EA's start to become profitable.

Finding the best R/R is for me, will make a trader successful... Can't stress that enough...

So what I would look at is where can I get in and get out giving the pending the best practical R/R? Is there a time during the trade where it is more favorable to get out? When I am in the money should I add more positions and if so where? What is the amount of volatility and currency strength needed to even open a position?

Now can this be coded and attached to this EA? If not then a manual oversight is needed to make this EA even better...

In the meantime I await the newest version of the EA with abated breathe...

nubika wrote:10.4 ver 1.08 rsi_stoch does not work at all for me. No trades all week last week and nothig so far today on Global Prime and FXCM brokers.

10.4 ver 1.07 also did not place any new pending orders last week and I noticed that the already placed pending orders were not closed by the EA at day 5 as per the settings in the EA. So something is not right on my side here.

If any one has a working EA (version 1.08) please post your setup file here so I can compare it with mine.

Thanks
Frank

MrLong wrote:Hi Traders



Version 1.08a, with a couple of bug fixes.

It's been running all night with no problems, so lets see how this version does.

When Jurgen, sends me his code for the display, I'll upload version 1.09.

Remember the magic number for existing trades and check settings before turning on Experts.

Andy

MrLong wrote: When Jurgen, sends me his code for the display, I'll upload version 1.09.
Andy

if ( trendDirect(Pairs[y], OP_BUY))
	ObjectSetText("signal" + 0 + y, "Long", fontSize, displayfont, BullishColor);
else if ( trendDirect(Pairs[y], OP_SELL))
	ObjectSetText("signal" + 0 + y, "Short", fontSize, displayfont, BearishColor);

if ( trendDirect(Pairs[y], OP_BUY))
	ObjectSetText("signal" + 1 + y, "UT", fontSize, displayfont, BullishColor);
else if ( trendDirect(Pairs[y], OP_SELL))
	ObjectSetText("signal" + 1 + y, "DT", fontSize, displayfont, BearishColor);

simplex wrote:

MrLong wrote: When Jurgen, sends me his code for the display, I'll upload version 1.09.
Andy

Andy,

I think that I am (nearly) ready now integrating my optimization stuff into 1.08.
Please check the following to make sure I did not miss something important:
I figured out you made the following changes from 1.07 to 1.08:
1. candletiger's RSI stuff in init() - doesn't bother me / trendDirect() - doesn't bother me / DisplayGrid() - integration done
2. bar time in footer - integration done
3. new var showdisplay - integration done

That's it. Missed something? By the way: do you have some kind of change log? Would make integration work much easier.

Now two final questions:

Q1. In your grid columns 'Type' and 'Trend' follow exactly the same signal. Did you
code it this way intentionally or is it a bug? Original code:

Code: Select all

if ( trendDirect(Pairs[y], OP_BUY))
	ObjectSetText("signal" + 0 + y, "Long", fontSize, displayfont, BullishColor);
else if ( trendDirect(Pairs[y], OP_SELL))
	ObjectSetText("signal" + 0 + y, "Short", fontSize, displayfont, BearishColor);

if ( trendDirect(Pairs[y], OP_BUY))
	ObjectSetText("signal" + 1 + y, "UT", fontSize, displayfont, BullishColor);
else if ( trendDirect(Pairs[y], OP_SELL))
	ObjectSetText("signal" + 1 + y, "DT", fontSize, displayfont, BearishColor);

There is no difference between them.

Q2. As a final step (for now) I would like to make positioning of the 'buttons'
DELETE PENDING and CLOSE ALL OPEN more flexible. I never used this kind of
improvised buttons before. How does it work? When replacing your hardcoded
horizontal coordinates (900 and 1090) by variables for easier code maintenance
I would touch the following functions:
CloseAllButtonBeenHit()
DeletePendinglButtonBeenHit()
DisplayGrid()
Correct?

When this is done, and you tell me I did not miss anything relevant, I will be ready to post very soon.

Final remark: I'm afraid the use of iCustom for the RSI stuff will cost some cpu power ...

Cheers, Jürgen