Aussiedoc's 6 Ducks in a Row

[Aussiedoc]

HI DOC

"Trade Context Busy" is another way for Empty4 to remind us it is free and as Steve keeps reminding us, utterly CRAP. (sorry for the strong language). I even get this message during my manual trades, in particular during high volume trading times (e.g. important new releases). Quite often once it gives me this lovely message the only cure is to close and restart Empty4. This is the quickest and surest way of getting rid of this problem.

Kind regards

We use that expression here too... usually precede by the word 'absolute'.
Cheers

[Aussiedoc]

Steve, thinking this past week about about Ducks; I figured that the only way I was going to get it configured and working well - 'quick-time' - was to jump in at the deep-end; and back-test! After extensive Google research, today, I did my first ever back-test... on the Ducks EA. Ran a back-test. Dropped into routine 'Doc' test mode. Kept getting the same results until I read the Journal page. Learned the EA needs the 'EMA crossover indi' in the indi folder Corrected that; pressed on - and ran into a really good problem.

The first time(s) through I back-tested with ootb settings to get my BSR (base reference standard) values. Then I went into the compiler; modified and compiled the TP, then ran another backtest... with exactly the same results. (Several times!).

It was only when I displayed the chart that I noticed that, even though I had compiled a different TP value, the original TP value had not changed. (See below)

One of the components of 'Doc's test mode' is sitting; cup of tea in hand; staring at the ceiling - talking out loud to myself! Being the problem-solver she is Wendy asked 'What is your problem this time?" As usual; her answer was short, sharp and to-the-point.

I know the answer will belt me over the ahead with its simplicity.

Will you please point me in the right direction?

Thanks. Take care.
Cheers

[Dixpat]

Hi Doc

I haven't been following this thread but I suspect that you have to change the setting via the EA input fields rather than changing & recompiling

Try F7 to get to the properties and then changing and then saving the new set file

Regards

[Alpenkorps]

What is a set file, and how does one go about creating one.

Step by step, please.

I badly need a Know Your Empty4 forum.

Thank you.

Khalid

In every EA, under the input tab, there is a option to save the settings into a set file (xx.set) and load the set file in future. The image will make it clear.

[Alpenkorps]

Empty4 can be quite enjoyable, at times.

Tell that to Steve when he is in a bad mood

[bobasker]

Empty4 can be quite enjoyable, at times.

Hehe, the only time Empty4 is enjoyable is over the weekend when it's NOT running!

[garyfritz]

I haven't been following this thread but I suspect that you have to change the setting via the EA input fields rather than changing & recompiling
Try F7 to get to the properties and then changing and then saving the new set file

Doc, Dixpat has the right idea. Changing the code and recompiling changes the default values for the next time you insert the EA onto a chart. To change the currently running EA you need to change the EA inputs, by hitting F7.

[SteveHopwood]

Steve, thinking this past week about about Ducks; I figured that the only way I was going to get it configured and working well - 'quick-time' - was to jump in at the deep-end; and back-test! After extensive Google research, today, I did my first ever back-test... on the Ducks EA. Ran a back-test. Dropped into routine 'Doc' test mode. Kept getting the same results until I read the Journal page. Learned the EA needs the 'EMA crossover indi' in the indi folder Corrected that; pressed on - and ran into a really good problem.

The first time(s) through I back-tested with ootb settings to get my BSR (base reference standard) values. Then I went into the compiler; modified and compiled the TP, then ran another backtest... with exactly the same results. (Several times!).

It was only when I displayed the chart that I noticed that, even though I had compiled a different TP value, the original TP value had not changed. (See below)

One of the components of 'Doc's test mode' is sitting; cup of tea in hand; staring at the ceiling - talking out loud to myself! Being the problem-solver she is Wendy asked 'What is your problem this time?" As usual; her answer was short, sharp and to-the-point.

I know the answer will belt me over the ahead with its simplicity.

Will you please point me in the right direction?

Thanks. Take care.
Cheers

You go into Strategy Tester and click Expert Properties, select the Input tab, the click Reset. This sets the inputs to those you have just compiled. You can also make changes to the inputs you are testing in this tab.

Something to remember with ST backtest results; they are bollocks. The only value ST has is in testing code. There are a whole host of reasons why, but the easiest to understand is spread. ST works with current spread, not historical spread. Weekend backtests are especially bad as the crims customarily widen their spreads, often ludicrously so, simply to bugger up weekend backtesters of EA's. Welcome to the wonderful world of Empty4/mql4.

Well done for coming to grips with basic source code editing; this will make your life a whole heap easier.

Remember that I have put development of this EA on hold until George finishes his Ducks indi. I am hoping that the EA will be able to extract all the info it needs from this to function accurately.

[SteveHopwood]

Empty4 can be quite enjoyable, at times.

Tell that to Steve when he is in a bad mood

[magft]

Steve, thinking this past week about about Ducks; I figured that the only way I was going to get it configured and working well - 'quick-time' - was to jump in at the deep-end; and back-test! After extensive Google research, today, I did my first ever back-test... on the Ducks EA. Ran a back-test. Dropped into routine 'Doc' test mode. Kept getting the same results until I read the Journal page. Learned the EA needs the 'EMA crossover indi' in the indi folder Corrected that; pressed on - and ran into a really good problem.

The first time(s) through I back-tested with ootb settings to get my BSR (base reference standard) values. Then I went into the compiler; modified and compiled the TP, then ran another backtest... with exactly the same results. (Several times!).

It was only when I displayed the chart that I noticed that, even though I had compiled a different TP value, the original TP value had not changed. (See below)

One of the components of 'Doc's test mode' is sitting; cup of tea in hand; staring at the ceiling - talking out loud to myself! Being the problem-solver she is Wendy asked 'What is your problem this time?" As usual; her answer was short, sharp and to-the-point.

I know the answer will belt me over the ahead with its simplicity.

Will you please point me in the right direction?

Thanks. Take care.
Cheers

Guys, F7 works for when forward testing. Mark is talking about back testing in Strategy Tester. You have to do the following:

• Select EA from Drop Down List
• Select TimeFrame
• Click Expert Properties - This is where you change parameters for a run
• Click Start

Have a look at the attached picture, this is testing the ChangeTheColor EA on H4 chart.

Here is a link that summarises the steps, there are plenty of other references in Google.
Or here.

Hope this helps

Mike