Slopey Slope

[glabbeek]

What I mean is that using direction of the slope will get you in a trade when the market is ranging. (between -0.4 and 0.4). I would expect that if you use a filter that looks for a pull back:

"the angle at the close of the previous candle must be > that of 2 candles ago.
- I have added the condition that the angle of 3 candles ago must be > that of two candles ago, indiating that the angle first fell, then rose again. If not, the chart feedback will show the angle as, "Rising, but not tradable."

That the result will be that you'll focus on ranging markets, above trending markets.

[SteveHopwood]

What I mean is that using direction of the slope will get you in a trade when the market is ranging. (between -0.4 and 0.4). I would expect that if you use a filter that looks for a pull back:

"the angle at the close of the previous candle must be > that of 2 candles ago.
- I have added the condition that the angle of 3 candles ago must be > that of two candles ago, indiating that the angle first fell, then rose again. If not, the chart feedback will show the angle as, "Rising, but not tradable."

That the result will be that you'll focus on ranging markets, above trending markets.

From post 1:

You have the option of using the Slope value as well, so the usual HtfBuyLevel etc are there. By default, SS does not use the Slope value - note UseSlopeValue set to 'false'.

[glabbeek]

I agree that using the slope value can filter out the trading ranges, but what is the advantage of using the slope value AND slope direction, above just using slope value?

I haven't tested this EA, but my gut feeling says that it will enter the market faster and more often then the regular slope value based EA's. The expected downside is that with low volatile, ranging markets it will DD large amounts.

I'm looking forward to some test result over a longer period.

[cuzgeorge]

Hi Steve, all,
I'm making some changes to Slopey SLope as i have gathered enough results to see where this EA is headed.
I have added this to my myfxbook dingus , link at the bottom.

Most closed positions are winners but i had bigger losses because of a large SL. See attached set file for new settings. Simple setup, like i run most the ea's now with MPTM on a seperate chart.

SS is a slow trader, dont expect the wild west here.So far, SS seems to chose direction correctly.

I will try to use MPTM like i'm using on the rest of the ea's lately. High lot to hedge based on Steve's experimental MPTM direction checker options. envelope, adx or candles.

regards and good luck,
cuzgeorge

[SteveHopwood]

Hi Steve, all,
I'm making some changes to Slopey SLope as i have gathered enough results to see where this EA is headed.
I have added this to my myfxbook dingus , link at the bottom.

Most closed positions are winners but i had bigger losses because of a large SL. See attached set file for new settings. Simple setup, like i run most the ea's now with MPTM on a seperate chart.

SS is a slow trader, dont expect the wild west here.So far, SS seems to chose direction correctly.

I will try to use MPTM like i'm using on the rest of the ea's lately. High lot to hedge based on Steve's experimental MPTM direction checker options. envelope, adx or candles.

regards and good luck,
cuzgeorge

George, thanks very much. This is your second xxxxx Slope post today, so you are clearly giving these bots some space. Let me know if you need any changes/additions to the code.

FWIW, I am finding that Slopey builds up some decent trades, then gives most of the profit back before the trades are closed. I have taken to using mptm to close the entire position at a global profit target of 1% of account balance.

[hilavoku]

Hi Steve,

cause of much programming on my own i didn't follow this thread that often. I just found a copy/paste error in teh original slopeyslope EA.

Code: Select all

void InsertStopLoss(int ticket) {
	//Inserts a stop loss if the ECN crim managed to swindle the original trade out of the modification at trade send time
	//Called from CountOpenTrades() if StopLoss > 0 && OrderStopLoss() == 0.

	while(IsTradeContextBusy()) Sleep(100);
	if (!OrderSelect(ticket, SELECT_BY_TICKET) || OrderCloseTime() > 0) return;

	double stop;

	if (OrderType() == OP_BUY) {
		stop = CalculateStopLoss(OP_SELL]);
	}//if (OrderType() == OP_BUY)

	if (OrderType() == OP_SELL) {
		stop = CalculateStopLoss(OP_SELL);
	}//if (OrderType() == OP_SELL)


	OrderModify(ticket, OrderOpenPrice(), stop, OrderTakeProfit(), OrderExpiration(), CLR_NONE);

}//End void InsertStopLoss(int ticket)

The OP_SELL should be OP_BUY when having a buy order ...



see you
Guido

[SteveHopwood]

Hi Steve,

cause of much programming on my own i didn't follow this thread that often. I just found a copy/paste error in teh original slopeyslope EA.

Code: Select all

void InsertStopLoss(int ticket) {
	//Inserts a stop loss if the ECN crim managed to swindle the original trade out of the modification at trade send time
	//Called from CountOpenTrades() if StopLoss > 0 && OrderStopLoss() == 0.

	while(IsTradeContextBusy()) Sleep(100);
	if (!OrderSelect(ticket, SELECT_BY_TICKET) || OrderCloseTime() > 0) return;

	double stop;

	if (OrderType() == OP_BUY) {
		stop = CalculateStopLoss(OP_SELL]);
	}//if (OrderType() == OP_BUY)

	if (OrderType() == OP_SELL) {
		stop = CalculateStopLoss(OP_SELL);
	}//if (OrderType() == OP_SELL)


	OrderModify(ticket, OrderOpenPrice(), stop, OrderTakeProfit(), OrderExpiration(), CLR_NONE);

}//End void InsertStopLoss(int ticket)

The OP_SELL should be OP_BUY when having a buy order ...



see you
Guido

Cheers Guido. That is a historic bloop from when I first created the shell that I use to code ea's. It is fixed now but crops up in some of the recent ea's.

V 1d in post 1 with this fixed.

[hilavoku]

Thx for the fast feedback.

I have a question which might be in the wrong place but i saw it at the current EA i'am 'using'. (slopey slope)

The 'DisplayUserFeedback' function tells me that the Spread is 1.4.

When i look at the current values when taking a trade i see this:

Spread.JPG

This tells me that the spread is 14 ?! .
When i use the code

Code: Select all

MarketInfo("EURUSD",MODE_SPREAD),1)

it shows me 14 ...


Or is it just that the display says spread is 1.4 pips and converted is 14 points ?
(I'am looking at those SL/TP thingys cause i get many modifyorder errors (130) in the function 'TrailingStopLoss' and there where the 'hard' stop loss will be set...)


thx in advance
Guido

[gaheitman]

Thx for the fast feedback.

I have a question which might be in the wrong place but i saw it at the current EA i'am 'using'. (slopey slope)

The 'DisplayUserFeedback' function tells me that the Spread is 1.4.

When i look at the current values when taking a trade i see this:

Spread.JPG

This tells me that the spread is 14 ?! .
When i use the code

Code: Select all

MarketInfo("EURUSD",MODE_SPREAD),1)

it shows me 14 ...


Or is it just that the display says spread is 1.4 pips and converted is 14 points ?
(I'am looking at those SL/TP thingys cause i get many modifyorder errors (130) in the function 'TrailingStopLoss' and there where the 'hard' stop loss will be set...)


thx in advance
Guido

Yep, you guessed it, the display is in pips. If you have a broker offering EURUSD with a 14 pip spread, you should probably change brokers...

George

[SteveHopwood]

Also, depending on when I coded SS, it might not be MarketInfoo.... returning the spread.

All mu latest ea's calculate the spread as (Ask - Bid) * factor, to return the spread in pips. One of the proper coders here bullied me into making the change, as MarketInfo is so unreliable.