Robot Lab Project

thanks

Hello Abokwaik,

I wonder if you can do one more version for this EA. I'm just curious looking at the chart on post your #2.

Fast MA =20
Slow MA = 100
Slower MA = 400

BUY Entry #1
If Fast MA crosses up over Slow MA
Buy Entry #2
Fast MA crosses Up over Slower MA
BUY Entry #3
Slow MA crosses up over Slower MA

Exit Buy Entry #1 either by Set TP or
If Fast MA crosses below Slow MA
Exit Buy #2 either by SET TP or
If Fast MA crosses below Slower MA
Exit Buy #3 either by Set TP or
If Slow MA crosses below Slower MA


Buy Re-entry #1 If Slow MA is still above Slower MA and Fast MA crosses back up above Slow MA
and if Price touches and bounces off above Slower MA while Fast MA and Slow MA are still over Slower MA.

Sell Entry #1
If Fast MA crosses below Slow MA
Sell Entry #2
If Fast MA crosses below Slower MA
Sell Entry #3
If Slow MA crosses below Slower MA


Sell Re-Entry If Slow MA is still below Slower MA and Fast MA crosses back below Slow MA
and if Price touches and bounces off below Slower MA while Fast MA and Slow MA are still below Slower MA.

Hopefully you can do this.

Much respect and appreciation for what you do.

Thanks.
G

In the original robot, the slower MA is used as a filter. So We take only long trades above Slower MA, and Only short entries below it. Thus filtering out bad trades (trades against the major trend identified by Slower MA).

As I understood from your post, applying your entry rules could lead to having buy and sell entries active at the same time, which means hedging of some positions. Also it will generate more trades (in the same period), and in most cases more trades lead to more draw down or more loss.

We have some important robots coming into the Lab. However once I have some extra time I will try to apply your rules and see how it goes.

Thanks,

Ok Re: HA_Rider EA:

EA opens and closes Positions like it is supposed to do but it does so "as soon as" the EA is activated...we would prefer if the EA only opens positions at the OPEN of a new candle only to minimize opening positions instantly.

=> If this is not possible, a way to circumvent this "problem" would be to create a template with HeikenAshi alone (minus the HA_Rider EA). This template will act as a sort of "scope" temp to view how HA currently paints on a pair without the risk of having open trades which we don't want.

=> Then once we get a "favourable" HA view, we can then apply/activate the HA_Rider EA on that currency pair. So far, this works wonderfully. What I think is to wait until HA begins a new "trend" and then let HA_Rider loose on that pair!

I will continue to update as I test and get results.

Fantastic job abokwaik!

Regards,

Ty

1. we would prefer if the EA only opens positions at the OPEN of a new candle only to minimize opening positions instantly
   1. Possible and Logical. I will do it as soon as I finish Pinocchio beta.

Some notes for traders forward testing robots :

 

1. Since I am providing the MQ4 (source files), this will allow you to enter your preferred parameters in the MQ4 file instead of changing the defaults each time you forward test the robot. If you want to apply this to multiple instances of the same robot you need to save each copy of teh robot under a different name.
2. If you want to run multiple instances of the same robot (even if robot file names are different), make sure you change the Magic_Number parameter, so that each instance has a unique Magic_Number

For people un-familiar with editing MQ4 files, follow these steps:

1. Highlight (put the cursor on) the Robot (Expert Advisor) that you like to edit and press Enter key, as in the following image
   1. Attached Image

      
      .

2. MQL editor will open the MQ4 file for editing, as in the attached image
   1. Attached Image (click to enlarge)

      
      

3. Now you can modify the "input parameters" as you wish, if you need to save the file under a different name use "Save As". Then you need to compile the file as in the attached image by pressing F7 or using the compile button
   1. Attached Image (click to enlarge)

      
      

4. Now yo can close the editor and go back to trading terminal.

For further assistance you can check the Platform Tech

Hi abokwaik, when I was back-testing MA_CROSS_WT System 04 from Jan 1 to today it says "TestGenerator: unmatched data error (volume limit 1442 at 2014.12.08 05:00 exceeded)" and then opened ten Long trades with lot size of 0.10. No positions were closed until the test ended. What's the problem?

Please not the MA_CROSS_WT_04 has a parameter for the Time_Frame used. Inside MQ4 you can use PERIOD_D1, PERIOD_H4 ... etc. But if you enter it in the Input Parameter Window, it should be entered as number of minutes in the time frame (e.g. for D1 : 1440, for H1:60, for H4:240 .. etc).
Then you can run the test on same time frame chosen or on lower time frames. The tester report I attached earlier used D1 time frame as Time_Frame parameter while the test was run on M5 time frame.

If you'd applied the above correctly and still have this issue, I will need more details

1. copy of the complete tester report , you can save it (as html) and compress it and attach it to your reply
2. copy of the journal. Its better to clear the previous journals before running the back test. you can take a copy by selecting all journal lines (CTRL+Shift+End), paste it into Excel, compress and attach.

Regards,

The Pinocchio Robot is taking some time in the oven, due to large number of parameters used, end of year work load, and my birthday!. LOL.

Happy Birthday

Happy Birthday Bro!!!

Regards,

Ty

Pinocchio System

This is the first version of Pinocchio robot (described at post # 161), and probably the last one.

After running multiple tests on different time frames, it seems that the robot has around 50% Chance of winning which is not better than tossing a coin or random entries.

If you tighten the rules, you get very few entries, and if you loosen the rules you get many false entries.

However, the code can be used as a base to generate new robots based on single candle (like Engulfing Candle).

Input parameters :

1. Magic_Number = 40020
   1. Unique number for Robot, used to differentiate between orders made different robots (EAs)

2. Time_Frame = 0
   1. 0:current time frame, n:number of minuets in the required time frame

3. Fixed_Lot_Size = 0.2
   1. Lot Size (1:Standard, 0.1 Mini, 0.01 Micro), you can use any combinations supported by y broker

4. -------------- Pin bar validation options -----------------------
5. Max_Body_Perc = 0.30
   1. Body is the absolute difference between close and open prices
   2. use 1 to disable

6. Min_Tail_Perc = 0.60
   1. Tail for bullish bar is the absolute difference between (Minimum of Open or Close) and Low
   2. Tail for bearish bar is the absolute difference between High and (Max of Open or Close)
   3. use 0 to disable

7. Max_Head_Perc = 0.20
   1. Head for bullish bar is the absolute difference between High and (Max of Open or Close)
   2. Head for bearish bar is the absolute difference between (Min of Open or Close) and Low
   3. use 1 to disable

8. Prev_Bars = 2
   1. Bar is Lower/Higher than previous number of bars
   2. use 2 to disable

9. Prev_Pips_as_ATR_M = 0
   1. Bar is Lower/Higher than Prev Bar Low/High by number of pips in terms of ATR multiples
   2. use 0 to disable

10. Size_as_ATR_M = 0
    1. Bar Size in terms of ATR Multiples (for now we'll use ATR(20)
    2. Whole bar size (High-Low)
    3. use 0 to disable

11. Same_Close_Type = 0
    1. Bar closes same as Bar type (i.e. Higher close for Bullish, Lower close for bearish)
    2. 1:enable, 0:disable

12. -------------- Trade Entry Options -------------------
13. Break_by_x_pips = 0
    1. 0:disable (Enter at open of next bar if other inputs are OK), n:n number of break pips.

14. Retest_after_break = 0
    1. 0:disable, n:n number of break pips. Enter at the high/low at retest

15. After_Confirmation_Bar = 0
    1. 0:disable, 1:enable. Enter after Close of the next bar confirming a valid break

16. -------------- Stop Loss Options ----------------------
17. Hard_SL_Pips = 300
    1. Hard Stop Loss in Pips regardless of Bar size or ATR

18. Pips_From_Tail = 0
    1. Stop Loss will be at n pips beyond the Tail

19. SL_as_Bar_M = 0
    1. Stop Loss as Bar Size Multiples

20. SL_as_ATR_M = 0
    1. Stop Loss as ATR multiples

21. Use_Min_Max_SL = 0
    1. 0 : use minimum SL, 1:use maximum SL

22. -------------- Take Profit Options ----------------------
23. First_TP_pips = 300
    1. Partial (First) Take Profit in number of pips

24. Partial_TP_Lot_Size = 0.2
    1. Partial Take Profit Lot Size

25. Trailing_SL_Pips = 0
    1. Variable Trailing Stop in pips

26. trail_stop_jump = 50
    1. Trailing stop jumb to minimize order modification requests

27. Close_on_Opp_Signal = 0
    1. Close on Opposite Signal 0:no 1:yes

Pinocchio System

Tester report for EUR/USD H4 (2010 - 2014)

Sorry for maybe derailing the thread here a little, but Khalil do you suggest any good sites to where you can learn mql4? I've been using the official MQL website, they have a good tutorial but it seems there are mistakes in it here and there and that really puts me off. Any other suggestions?

Happy Birthday and may all your wishes come true on your special day.

G

Because of my programming background, I didn't need any.

With a quick search, here are some posts with links to such resources, here on FF:

1. Where can I learn how to code Expert Advisors?
2. Should I Learn MQL4 and WHY?
3. how to learn mq4 ?
4. MT4 programming resources

Just go0gle and you'll find more.

Regards,

Thanks, i was personally asking if maybe you had specifically learnt somewhere but i see you did not :^)

I have some coding knowledge but i was never a natural at it. I was just getting confused with the official MQL site and their material. I mean look at this:

https://www.mql5.com/en/forum/38789

a post i made about some "errors" in the material.... it has me questioning stuff....is the material wrong or have i missed something and i am not getting it???

You are right. I don't believe how they put such rubbish on their the official site.

I actually use the the MQL4 reference that comes with MT4 (using F1 or under Help menu) to check the syntax for function calls ... etc. And never found such errors.

Pinocchio System

Another test on H4 E/U 2013-2014 on FX..DD with different inputs. Maybe I was unfair to Pinocchio.

Could he turn into a Real Boy ?

well that at least puts my mind at ease, thanks!

I guess it might be best to just start coding and learn as i go along with the 'help' section.