scooby-doo BOJ JPY pairs trading robot | Page 375 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Trading correlation pairs by using the other pairs 843 replies

Export All pairs or selected pairs to .csv with script 3 replies

Pairs of Currency Pairs 4 replies

Trending Pairs / Ranging Pairs 0 replies

Robot trading 120 replies

Attachments: scooby-doo BOJ JPY pairs trading robot
Exit Attachments

scooby-doo BOJ JPY pairs trading robot

  • #7,481
  • Mar 14, 2010 2:18pm Mar 14, 2010 2:18pm
Quoting charvo
Scoobs, could you please solve one of my confused part above?

as to LagRSI(0.5):

one way will be like: if LagRSI(0.5) > 20, buy; if LagRSI(0.5) < 80, sell;

or a more complicated way ?:

LagRSI(0.5) of bar(0) > 20 > LagRSI(0.5) of bar(1) ----- Buy
LagRSI(0.5) of bar(0) < 80 < LagRSI(0.5) of bar(1) ----- Sell

As this latter conservative way might better identify the price is coming out of OB/OS zones.

i am trying the latter for now as a conservative start, but last week from Thur~Fri got only 2 entries....
Yes this is ofcourse a better way but it depends how you are going to code it, i.e. if you wait until Bar(0) > Bar(1) then it may of already come out of OS on M15 and/or H1 etc so you would miss a trade.

Another way is to look for OS in M15, H1 and H4. Then enter a new loop waiting for Bar(0) > Bar(1). This however could get tricky to code.

Scoobs.
  • #7,482
  • Mar 14, 2010 2:38pm Mar 14, 2010 2:38pm
Thank you scoobs. You are a total legend.

IS there anyone who is here who can take scooby's comments and code them accordingly? Anyone willing to share (i would, but I cannot code - its all MQL to me!). Ofcourse, only if its ok with scooby.

Thanks once again.
  • #7,483
  • Mar 14, 2010 2:48pm Mar 14, 2010 2:48pm
I think Charvo is working on incorporating these ideas, which is my he is asking detailed questions. I am also trying to incorporate some in my own mods - although I am much closer to being a hacker than a programmer . Lots of fun learning how things work, though.
  • #7,484
  • Mar 14, 2010 2:52pm Mar 14, 2010 2:52pm
lack of codin knowledge is the bain of my life. I really wish I could code decently. I can do bits and peices, but nothing like these guys.
  • #7,485
  • Mar 14, 2010 2:59pm Mar 14, 2010 2:59pm
Scoobs, so the D1 trend needs to be as:

MA(25)>MA(50)>MA(100)>MA(200) for buy?

MA(25)<MA(50)<MA(100)<MA(200) for sell?

Could you please confirm this?

My concern is that when daily trend reverse, this condition may lag well behind the reversal, we just accept it is not a perfect world?

Please see this picture attached:
1. Dec 2009, if using MA(25)>MA(50)>MA(100)>MA(200) for BUY, then i bought falling knives;
2. from Dec 2009 till now, MA(25)<MA(50)<MA(100)<MA(200) for SELL, it seems impossible to generate any sell entries.



Quoting scooby-doo
Trend=25,50,100,200 on D1

Scoobs
Attached Image (click to enlarge)
Click to Enlarge Name: 4mas.gif Size: 25 KB
  • #7,486
  • Edited 3:28pm Mar 14, 2010 3:08pm | Edited 3:28pm
Quoting charvo
Scoobs, so the D1 trend needs to be as:

MA(25)>MA(50)>MA(100)>MA(200) for buy?

MA(25)<MA(50)<MA(100)<MA(200) for sell?

Could you please confirm this?

My concern is that when daily trend reverse, this condition may lag well behind the reversal, we just accept it is not a perfect world?

Please see this picture attached:
1. Dec 2009, if using MA(25)>MA(50)>MA(100)>MA(200) for BUY, then i bought falling knives;
2. from Dec 2009 till now, MA(25)<MA(50)<MA(100)<MA(200) for SELL, it seems impossible to generate any sell entries.
My mistake.

The trend is H4 as this is the highest TF we look at for OB/OS.

If you want more trades then just take the trend on H1. But it remains to be seen how many of them will turn out to be profitable.

I am a long term trader by default but retail traders dont like this because trades are generally few and far between.

Scoobs.
  • #7,487
  • Mar 14, 2010 3:11pm Mar 14, 2010 3:11pm
Quoting charvo
Yes, you need, very good question. i also didn't realise this issue....
Currently the EA enters the loop on every tick which is CPU intensive. One way to optimize it is to only check the trend on every new bar and set a flag if trend is consistent for a pair. Then check the lower timeframe for trade trigger on every tick. If the trend is not consistent across MTF, do nothing.
  • #7,488
  • Edited 4:10pm Mar 14, 2010 3:58pm | Edited 4:10pm
Thanks a lot!

Now sure when my questions will exhaust you, but I seem unable to stop

I was a firm believer of long term trader (daily/weekly/monthly) until I identified your EAs on this thread. I used to believe 2 pips spread in EurUsd are already more than enough to kill 90% so called profitable systems.

Though seemingly few are interested, but I am especially eager to learn from you how you do daily/weekly long term trading?

To trade daily/weekly, do you frequently check news, read papers/report, and do some fundamental thinking before enter?

or is it very similar to your EAs ---- just escalate M5/M15/H1/H4 to higher timeframe, say, H1/H4/D1/W1?

i believe that long term trading style is more FUNDAMENTAL/VALUABLE to our reference, though every success cannot be simulated but invented.

btw, i'll continue demoing my stupid guess HG v2.2 as it is using H1 to determine the trend, will report back by next weekend.

Quoting scooby-doo
My mistake.

The trend is H4 as this is the highest TF we look at for OB/OS.

If you want more trades then just take the trend on H1. But it remains to be seen how many of them will turn out to be profitable.

I am a long term trader by default but retail traders dont like this because trades are generally few and far between.

Scoobs.
  • #7,489
  • Mar 14, 2010 4:17pm Mar 14, 2010 4:17pm
ahhh... i hate myself when i see me all over the whole screen, but i cannot refrain... sorry, Scoobs, bother you again:

this ATR is changed from H4 (you mentioned before) to H1 now?
but how many bars? still 20? it used to be "ATR(20) for H4".

Thanks!

Quoting scooby-doo

TP=2xATR(H1)
SL=1xATR(H1)

Scoobs
  • #7,490
  • Mar 14, 2010 4:32pm Mar 14, 2010 4:32pm
Quoting scooby-doo
Yes this is ofcourse a better way but it depends how you are going to code it, i.e. if you wait until Bar(0) > Bar(1) then it may of already come out of OS on M15 and/or H1 etc so you would miss a trade.

Another way is to look for OS in M15, H1 and H4. Then enter a new loop waiting for Bar(0) > Bar(1). This however could get tricky to code.

Scoobs.
Scoobs,


Is this what you mean?



Initial variables:
bool osCond=false;
bool obCond=false;
bool TrendLong=false;
TrendShort=false;

If(MaM15>MAH1 && MaH1>MaH4 && maH4>MaD1) TrendLong=true; else TrendLong=false;

If(MaM15<MAH1 && MaH1<MaH4 && maH4<MaD1) TrendShort=true; else TrendShort=false;

if(TrendLong && RS1_M15<os && RS1_M15<os && RS1_M15<os ) osCond=true;
if(osCond && LagM05[0]>0.2 && LagM05[1]<0.2) BuyFunction;

if(TrendShort && RS1_M15>ob && RS1_H01>ob && RS1_H4>ob) obCond=true
if(osCond && LagM05[0]<0.8&& LagM05[1>0.8) SellFunction;

// buy function
ticket=ordersend
if (ticket>0)osCond=false;
similar for sell conditon

Or

if(TrendLong && !osCond && RS1_M15<os && RS1_M15<os && RS1_M15<os ) {osCond=true; obCond=false;}
if(osCond && LagM05[0]>0.2 && LagM05[1]<0.2) BuyFunction;

if(TrendShort && obCond && RS1_M15>ob && RS1_H01>ob && RS1_H4>ob) {obCond=true; osCond=false}// we are looking for shorts only
if(osCond && LagM05[0]<0.8&& LagM05[1>0.8) SellFunction;



Pat
  • #7,491
  • Mar 14, 2010 4:42pm Mar 14, 2010 4:42pm
The second code scenario will retain obCond or OsCond to true irrespective of a change in OB/OS requirement. In other words, once these conditions are met, we just wait for Lag crossing the 0.2 or 0.8 level.

The ob/osconditions should be changed to false once
_Order is placed or
_the OrderTotal() is once again 0 or
some other conditons such a TradeAllowed conditions .

Pat
  • #7,492
  • Mar 14, 2010 4:45pm Mar 14, 2010 4:45pm
Quoting Pat1
The second code scenario will retain obCond or OsCond to true irrespective of a change in OB/OS requirement. In other words, once these conditions are met, we just wait for Lag crossing the 0.2 or 0.8 level.

The ob/osconditions should be changed to false once
_Order is placed or
_the OrderTotal() is once again 0 or
some other conditons such a TradeAllowed conditions .

Pat
Correct.

Scoobs
  • #7,493
  • Mar 14, 2010 4:56pm Mar 14, 2010 4:56pm
Quoting Pat1
Scoobs,


Is this what you mean?



Initial variables:
bool osCond=false;
bool obCond=false;
bool TrendLong=false;
TrendShort=false;

If(MaM15>MAH1 && MaH1>MaH4 && maH4>MaD1) TrendLong=true; else TrendLong=false;

If(MaM15<MAH1 && MaH1<MaH4 && maH4<MaD1) TrendShort=true; else TrendShort=false;

if(TrendLong && RS1_M15<os && RS1_M15<os && RS1_M15<os ) osCond=true;
if(osCond && LagM05[0]>0.2 && LagM05[1]<0.2) BuyFunction;

if(TrendShort && RS1_M15>ob && RS1_H01>ob && RS1_H4>ob) obCond=true
if(osCond && LagM05[0]<0.8&& LagM05[1>0.8) SellFunction;...
Is trend not determined by MA25 > MA50 && MA50 > MA100 && MA100 > MA 200 on the H4 based on Scooby's corrected reply to char above?

Sandy
  • #7,494
  • Mar 14, 2010 5:04pm Mar 14, 2010 5:04pm
Quoting nubchai
Is trend not determined by MA25 > MA50 && MA50 > MA100 && MA100 > MA 200 on the H4 based on Scooby's corrected reply to char above?

Sandy
Yes, this is correct for the trend.

Personally I wouldnt go against the daily trend but this will cut down the number of trades for you people, so use H4.

If this is still to low on trades then use H1 for the trend.

Scoobs.
  • #7,495
  • Mar 14, 2010 5:08pm Mar 14, 2010 5:08pm
Quoting scooby-doo
Yes, this is correct for the trend.

Personally I wouldnt go against the daily trend but this will cut down the number of trades for you people, so use H4.

If this is still to low on trades then use H1 for the trend.

Scoobs.
Thanks Scooby.

Sandy
  • #7,496
  • Mar 14, 2010 5:45pm Mar 14, 2010 5:45pm
Following a pm from a contributor late last week, I have come up with another robot.

Details of Scooby-doo Monica Rsi Overkill are in post 1; the robot is in the robots zip file.

  • #7,497
  • Mar 14, 2010 5:47pm Mar 14, 2010 5:47pm
Hi,

Just a reminder for everyone who lives in a timezone where Daylight Savings Time has begun today (Clocks shifts 1 hour ahead), we must change the BOJ Original's Buy Hour Start and Sell Hour Start settings accordingly.

- Jason


Edit - I just saw that someone already mentioned this, so consider it a second reminder
  • #7,498
  • Edited 6:23pm Mar 14, 2010 6:22pm | Edited 6:23pm
removed
  • #7,499
  • Mar 14, 2010 6:26pm Mar 14, 2010 6:26pm
Quoting Invisible
removed
Hehe. But not in time for the post contents not to be shown in my 'new posting' email notification.

So, the answer is, you choose.
  • #7,500
  • Mar 14, 2010 6:48pm Mar 14, 2010 6:48pm
If you want lots of trades then just......

Go Long
- 25 EMA > 50 EMA > 100 EMA on H1 only
- OS in H1 only (<10)
- TP = 2 x ATR(H1)
- SL = 1 x ATR(H1)

Go Short
- 25 EMA < 50 EMA < 100 EMA on H1 only
- OB in H1 only (>90)
- TP = 2 x ATR(H1)
- SL = 1 x ATR(H1)

Should be easy to back test.

Scoobs
35 traders viewing now