Kang Gun Relative Strength trading - the EA's | Page 2 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Trading system using relative strength 2,816 replies

Trading System Using Relative Strength-Part 2 1,499 replies

Updated CCFp and CFP indis for relative strength trading 55 replies

Relative Strength Basket Trading System 3,479 replies

Dyekid217 Trading relative strength and CICR 0 replies

Attachments: Kang Gun Relative Strength trading - the EA's
Exit Attachments

Kang Gun Relative Strength trading - the EA's

  • #21
  • Feb 12, 2009 1:43am Feb 12, 2009 1:43am
Quoting sahars
Steve,

The EA had an alert for AUDNZD, but after waiting for sometimes, the EA still not execute the order. Why...ah..!!?

sahars.
The most likely cause is the spread being too large for the EA to place the trade. IBFX AUD and, especially, NZD spreads are frequently over 20. My max spread is 10, so I see this situation quite often.

I will add a display of the spread size to the on-screen notification that there is a DC trade pending, so we can confirm/deny that this is the cause.

  • #22
  • Feb 12, 2009 2:19am Feb 12, 2009 2:19am
V1.1 is available from the first post in the thread. I have added the spread to the trades-being-validated display; it confirms that over-wide spreads are the cause of apparently validated trades not being sent.

  • #23
  • Feb 12, 2009 2:59am Feb 12, 2009 2:59am
I have followed the previous thread and run the ea for about 3 weeks. The results have been mixed, but I have persevered to see if it was finger trouble on my side.

Firstly, thanks to all contributors and to Steve for the amazing work he has already undertaken.

I was about to comment ala Eddie when the thread moved. So I await Eddie's synopsis with anticipation.

I will now load the split EA and continu testing and learning.

Many thanks!
  • #24
  • Feb 12, 2009 3:49am Feb 12, 2009 3:49am
Quoting SteveHopwood
The most likely cause is the spread being too large for the EA to place the trade. IBFX AUD and, especially, NZD spreads are frequently over 20. My max spread is 10, so I see this situation quite often.

I will add a display of the spread size to the on-screen notification that there is a DC trade pending, so we can confirm/deny that this is the cause.

Thanks ..for the improvement..I'll check it now..

Cheers

sahars
  • #25
  • Feb 12, 2009 4:38am Feb 12, 2009 4:38am
V1.2 adds code to ensure that DC triggers are moving in contrary motion when triggering a Validating Trades event. This is an attempt to ensure that triggers are not merely leap-frogging one another when crossing, and so going in the same direction, which we do not want. I have left V1.1 in place until we are certain the code and the logic that underlies it, are correct. Download it from the first post here.

Here is the logic that underlies the code. Take a GBP/JPY Cross long as an example:

  1. the EA spots a Cross this way:

    1. Two days ago. GBP rs index was lower than JPY.
    2. Yesterday, GBP was higher than JPY, so a cross has occurred.
    3. Today, GBP is still higher, so begin consulting lower tf's to validate the trade.

With the new code, step 3 is itself subject to validation:

  1. step 3: the Cross is detected, so:

    1. if GBP was lower two days ago than it was yesterday, and yesterday was lower than today, then the GBP index is rising.
    2. if JPY was higher two days ago than it was yesterday, and yesterday was higher than today, then the JPY index is falling.
    3. If either of these conditions is untrue, then the Cross does not become a Validation event because the two trigger indices are moving in similar motion, not contrary motion.

Does the logic look ok to the more logical minds here?

Can anyone suggest a better logic?

  • #26
  • Feb 12, 2009 4:53am Feb 12, 2009 4:53am
Sahas, I have been starting to think about the opposite-direction trade thingy, and have re-read the doc I made from your post in the previous thread.

What you say makes sense and I am going to code it. It might take a while, because I requires a completely new filter. It will be called UseSaharsMethod. I hope to have it up and running by next week.

  • #27
  • Feb 12, 2009 4:55am Feb 12, 2009 4:55am
Quoting SteveHopwood
V1.2 adds code to ensure that DC triggers are moving in contrary motion when triggering a Validating Trades event. This is an attempt to ensure that triggers are not merely leap-frogging one another when crossing, and so going in the same direction, which we do not want. I have left V1.1 in place until we are certain the code and the logic that underlies it, are correct. Download it from the first post here.

Here is the logic that underlies the code. Take a GBP/JPY Cross long as an example:[list][*]the EA spots a Cross this way:[list=1][*]Two...
Looks perfectly logical Steve.
  • #28
  • Feb 12, 2009 5:01am Feb 12, 2009 5:01am
Quoting sundog
Looks perfectly logical Steve.
Cheers, sundog.

  • #29
  • Feb 12, 2009 5:03am Feb 12, 2009 5:03am
Quoting SteveHopwood
V1.2 adds code to ensure that DC triggers are moving in contrary motion when triggering a Validating Trades event. This is an attempt to ensure that triggers are not merely leap-frogging one another when crossing, and so going in the same direction, which we do not want. I have left V1.1 in place until we are certain the code and the logic that underlies it, are correct. Download it from the first post here.

Here is the logic that underlies the code. Take a GBP/JPY Cross long as an example:[list][*]the EA spots a Cross this way:[list=1][*]Two...
Steve...

Your idea is fantastic..!!.The only problem that I can see, daily chart might be become too long for this EA and at the end no trade had been made.

Anyway..we will try it and I believe there are readers in this forum are willing to contribute for forward test of this EA.

The V1.1 is already tested for the whole day, and no orders has been made and the reason due to higher spread than permitted. The idea of using lower spread is very good, and I think this one of the way to avoid wrong direction in the initial stage.

Happy pipping

Sahars.

P/s : Have you check my PM to you...!? I got a proposal for improving that thing..Tq
  • #30
  • Feb 12, 2009 5:04am Feb 12, 2009 5:04am
Hi All the strength traders,

Congratulation for the new thread steve.....as I m new, I m still catching up some infos on the oldest thread.

Base on my short experience on the DC method and trading range; In manual,I have seen that we could catch much more strong and profitable trade if we enter once we have of course strong or weak basket crossing and confirmed signal but also if we make sure that we are above the 50 or 89 sma for a long trade or below if we are going for a short trade.......of course we will have less trades but also a lot less of noisy ones or not so much profitable.

entry:
for instance in a long trade we need something like this: DC method has triggered for a buy if still below 50 or 89 sma wait (pending entry), to be to be above 50 or 89 sma lines (x candles) and make sure the spread is still increasing proportionaly between the pair (spread or strength) since the cross and strength trigger has happened (ie spread or strengh when cross<spread when above 50 sma and rate still increasing (to be monitor)) otherwise do not trade. reverse logic apply for a sell.

I m not convince that we should set a small fix target profit and enter any trade once crossing and strength confirmed only and that we are still in the wrong side of some SMA trigger. I m part of the people that think that we should cut our losses short and let the profit running.


Trailing stop to maximise profits in a profitable trade:
in my scenario once we are in a winning trade we could make the trailing stop (Automatic floating) come closer to the market price once the strengh of a pair start to decrease, no ? .......trailing stop could be floating (after breakeven + set profit) and come closer of the market price once rate/spread/strength between the pair decrease (opposite direction)

Stop loss when a non profitable trade is entered:
set to 10 pips (cut our losses short) most of the trade when they are entered above (buy) or below (sell) 50 or 89 sma early enough and DC crossed and retrace confirmed, retracement do not reach more than between 5 to 10 pips to go or not in the expected direction.

So what do you think about this SMA setting to be added to the logic ?, does someones already worked on this option in manual that could become automatic (part of the EA)? if someone already worked on the options here above please let me know your view.

Cheers
Loichttp://www.forexfactory.com/images/icons/icon3.gif
  • #31
  • Feb 12, 2009 6:21am Feb 12, 2009 6:21am
Quoting SteveHopwood
V1.2 adds code to ensure that DC triggers are moving in contrary motion when triggering a Validating Trades event. This is an attempt to ensure that triggers are not merely leap-frogging one another when crossing, and so going in the same direction, which we do not want. I have left V1.1 in place until we are certain the code and the logic that underlies it, are correct. Download it from the first post here.

Thanks for that Steve - looks good to me.

Cheers
  • #32
  • Feb 12, 2009 6:27am Feb 12, 2009 6:27am
Quoting sahars
Steve...

Your idea is fantastic..!!.The only problem that I can see, daily chart might be become too long for this EA and at the end no trade had been made.

Anyway..we will try it and I believe there are readers in this forum are willing to contribute for forward test of this EA.
The V1.2 at 4HTF just opened 6 trades, and indirectly prove that I was wrong about the idea of additional features in this Ea will make the Ea place less an order.

So, I would appreciate if someone could start testing V1.2 at Daily chart and post the result in this forum and we can compared it against 4H TF.

Thanks

Sahars.
  • #33
  • Feb 12, 2009 6:37am Feb 12, 2009 6:37am
Quoting sahars
The V1.2 at 4HTF just opened 6 trades,
Great. I have removed V1.1 to avoid possible confusion.

  • #34
  • Feb 12, 2009 6:56am Feb 12, 2009 6:56am
The V1.2 look good so far...Just now 3 out of 6 open orders has been closed partially...while the other 3 orders still open at DD less than $1. Another 1 trade just open with immediately on $0.3 profit....

Cheers

sahars.
  • #35
  • Feb 12, 2009 8:21am Feb 12, 2009 8:21am
Can I assume this daily DC will fail to work in the following scenario:

When there is no significant strength occur or each currency alternate between strong and weak in the interval of 3 days, we long GBP/JPY after passing the validation, but it reversed very soon and the TP is not hit. Then sell signal occur and we short GBP/JPY, same problem again, TP is not hit and we have long signal.
  • #36
  • Feb 12, 2009 9:00am Feb 12, 2009 9:00am
Quoting sahars
The V1.2 look good so far...Just now 3 out of 6 open orders has been closed partially...while the other 3 orders still open at DD less than $1. Another 1 trade just open with immediately on $0.3 profit....

Cheers

sahars.
Only 1 trade left and 1 new trade opened. In 4 hours trade, the EA V1.2 already produced 118 pips with the highest DD during that period was -$3.5.

The EA look promising so far, but yet still to early to conclude it.

Anyway...Thanks Steve for your effort and kindness for contributing the EA.

Cheers

sahars.
  • #37
  • Feb 12, 2009 9:18am Feb 12, 2009 9:18am
sundog,

The KG RS ALL V1.2c that I opened last monday has reached my maximum limit of DD which -$55 (Around 1830 pips), but the old KG RS ALL V1.2b that I opened since 3 weeks ago still not reach my limit yet (the max DD so far was -$35).

Since it reach my limit, I would conclude that I may stop to further test KG RS ALL EA until this weekend in order to give a way for new KG RS DC to be tested in my computer. Currently, I running 7 demos in my computer..2 old V5 Kg Relative Strength EA, 2 KG RS ALL Ea, 1 New KG RS DC Ea and 2 others EA.

Anyway, the bottom line... the KG RS All Ea is profitable EA as long we follow the money management procedure. You'll be surprised if I tell you that for the last 3/4 days of trade, the KG RS ALL V1.2c is collecting 1,308 pips. Since my objective was looking for an EA with low DD, this EA I will put aside for while.

Thanks Matrixebix for your contribution on this EA.

Cheers

sahars.
  • #38
  • Feb 12, 2009 10:01am Feb 12, 2009 10:01am
I can't seem to find the post but if you put the dc on h4 chart what are the time frame settings to check against? Default?
or would it be possible / worthwhile to have the ea adjust to the proper time frame checks so regardless of which tf you use it knows the right tf's to check against?

Been up all night so a bit of a brain fart session going on here in case what I just wrote seems gibberishy.

Thanks
It takes me 1.5 bars on the M1 chart to eat a pancake.
  • #39
  • Feb 12, 2009 12:53pm Feb 12, 2009 12:53pm
V1.3 is the first attempt to introduce opposite-direction scalp trades in addition to the main Cross trade. It is a bit of a blunt instrument approach, but will save me a lot of coding if it works. If not, I have the basis to expand outwards into more complex routines.


From the user guide:

 

  1. Opposite direction trades: the EA has the ability to open a simultaneous trade in the opposite direction to the main Cross trade. For example, the EA takes a GBPJPY buy as the main trade, so it also takes a sell at the same time. This counter-trade has a tight tp and sl, so it is a quick in-and-out. The settings are:

    1. TakeOppositeDirectionTrades: set this to 'true' to send these trades.
    2. TodtImmediate: I plan to code a number of different strategies for placing these trades. This is the first one, so set it to 'true' to use it; this forces the EA to send a counter-trade immediately it successfully opens the main trade.
    3. TodtTP: the take profit for these counter-trades.
    4. TodtSL: the stop loss for these counter-trades.


I know the coding works, because I have been testing it on a 15m chart and the counter-trades are obediently placed by the bot. Whether such a simple strategy works is another matter; testing will tell.

When looking at the code for sending DC trades, I noticed a fault in the sl calculation that meant that the auto-calculated sl was always less than 200, and so was set to the minimum (200 by default). I hadn't noticed that, and nether did anyone else, it seems. I have gone back through the history and see that most of the trades had a 200 sl.

Now that this is corrected, perhaps the keen-eyed here might like to keep an eye on the sl's and make sure they are being placed within reasonable bounds.

  • #40
  • Feb 12, 2009 1:54pm Feb 12, 2009 1:54pm
Quoting SteveHopwood
V1.3 is the first attempt to introduce opposite-direction scalp trades in addition to the main Cross trade. It is a bit of a blunt instrument approach, but will save me a lot of coding if it works. If not, I have the basis to expand outwards into more complex routines.


From the user guide:...
how fast ur work steve..just finishing download ur v1.2

thks mate, will try to forward test tomorrow although just begin testing v1.2.
0 traders viewing now