Menu

Options

Bookmark Thread

First Page First Unread Last Page Last Post

Print Thread

Similar Threads

Trading the Sixths with Snowballs 68 replies

Gann High-Low System with Laguerre/Fisher/VSA/Sixths and others 124 replies

My Sixths trading journal with TOB EA 50 replies

sixths indicator 1 reply

Steve Trading Journal 3 replies

Attachments: Sixths trading - an EA by macman, Bob and Steve mk 2
Exit Attachments

Sixths trading - an EA by macman, Bob and Steve mk 2

I woke up in the middle of the night and listened to BBC talk about the Japan earthquake. I was able to just picture what the JPY issues were doing.

TOB is playing it just right and just the way a pro trader would.

An event like this also shows me I have a little more wiggle room and I might dare up the ante a little and go from .03 lots to .04.

Thanks Steve.
Quoting MurphyMan
I woke up in the middle of the night and listened to BBC talk about the Japan earthquake. I was able to just picture what the JPY issues were doing.

TOB is playing it just right and just the way a pro trader would.

An event like this also shows me I have a little more wiggle room and I might dare up the ante a little and go from .03 lots to .04.

Thanks Steve.
Oh, the thrill of a lot size increase. Makes a hell of a change from having to reduce it because we have lost money. Again. As usual.

I am rather enjoying myself these days as well.

Quoting SteveHopwood
He is trying to work out why Recovery is not doubling the lot sizes at L3 (1.1.2.4).


Dear Steve:

I am having the same problem and I think the error is in CalculateTrades(), in the following line (marked in red):



//Buy
stop = 0;
SendLots = Lot;
.......

Please, verify. Thanks

José Luis
Quoting Forexjlcg
Dear Steve:

I am having the same problem and I think the error is in CalculateTrades(), in the following line (marked in red):



//Buy
stop = 0;
SendLots = Lot;
.......

Please, verify. Thanks

José Luis
Ye Gods Alive, Dead or Existential, I am such a spoon.

I would have spotted this eventually. After tearing out my hair in frustration for a couple of weeks.

Thanks muchly José Luis. This will indeed solve the problem.

I have made a few other changes as well, including re-ordering the order in which TOB checks for breakeven at Gold and close at gold, so it looks for the closure first.

All this and José Luis's fix in post one.

Hi Steve, I have had a trade which is my only proper loser, on USDCAD using Beastie with no Tt's.

The bot has run perfectly since 20th Feb and has really stacked up the dosh !! However just a short while ago it placed a sell of 0.04 lot when it already had two 0.02 lot outstanding buys open.

Please ignore the Turquoise BE line I've moved it manually as it was below the white middle line after the 0.04 sell closed.

Looking at the chart you can see that if no trades had been open it would have been a standard sell as signaled by the Magenta lines (which have moved since the trade was placed) however with two buys open from 24th and 28th Feb it should not have made any trade as far as I can see. It opened a sell today at 1300 server time and closed it at 1309 for a net loss of -£2.12

I don't know if this problem may be carried over to TOB using Chaser as I don't know how much of the code is the same between them but I suspect it may be useful for you to know what has happened.

The recovery on Beastie seems to have been working ok up to this as I have had three recovery trades i.e where it has got to a 0.04 trade on three currency pairs over the last 3 weeks and it has turned in a profit on them. Maybe this will help you with the recovery problem you are looking at on TOB chaser at the moment.

Many thanks as always.

Looks like you've found some of your answers already !!
Attached Image (click to enlarge)
Click to Enlarge Name: usdcad.gif Size: 25 KB
Don’t know if its my imagination, but the minimum pips from entry looks to be setting the second order ‘ closer ‘ to the first trade than on previous versions ?

The 50 default re entry line is allowing trades to be placed when the SOLID magenta line has crossed it, this gives only somewhere in the order of 20 – 30 pips between actual trades ... should it not be the DASHED magenta line which has to cross the re entry line, which then gives a full 50 pip + between orders ?

Just dont remember trades being so close on previous versions, but I have been looking at these charts for so long I could just be going doodoo
I know I can change this by altering the settings, but wondered if something had changed

Also anyone else noticing the re entry line not redrawing after the second trade has been taken ?
I am having to delete it to get it to move to correct position
Ras, I had something similar this morning.

Most of my DD is caused by a GJ hedge sell left over from the end of December 30th. I got myself into a tangle with this one, having closed the trade it was hedging a long time ago.

The market has moved up so far that the bottom line is higher than the trade's open price. The market hit the bottom line this morning, so TOB obediently sent a pending buy.

I think the only thing to do in this situation is turn off trading in the 'wrong' direction.

Quoting jcs
Don’t know if its my imagination, but the minimum pips from entry looks to be setting the second order ‘ closer ‘ to the first trade than on previous versions ?

The 50 default re entry line is allowing trades to be placed when the SOLID magenta line has crossed it, this gives only somewhere in the order of 20 – 30 pips between actual trades ... should it not be the DASHED magenta line which has to cross the re entry line, which then gives a full 50 pip + between orders ?...
Well spotted.

This is LUC kicking in. I forgot to code TOB to adjust the re-entry line when it modifies the pending open price. This means that the distance between the trade when it fills and a subsequent trade will be less than it should, as TOB consults the line to get REntryPips, not an internal calculation.

Quote
Also anyone else noticing the re entry line not redrawing after the second trade has been taken ?
I am having to delete it to get it to move to correct position
I will look at this as well.

I forgot to add, guys, that I added code to make TOB wait for a full pip's movement before modifying the pending open price.

The variable is PipsMove if you want to play with it. Remember to change its type if you want to use fractions.

Quoting SteveHopwood
I will look at this as well.

Steve,
Just one other thing that I have never had working on any version
The breakeven line draws correctly when the second trade is placed, but for any subsequent trade placed it does not adjust automatically to the new BE point, the only way to get it to do this is to delete it and then it goes to the correct position
Quoting Forexjlcg
Dear Steve:

I am having the same problem and I think the error is in CalculateTrades(), in the following line (marked in red):



//Buy
stop = 0;
SendLots = Lot;
.......

Please, verify. Thanks

José Luis

Dear Steve:

I think that in the code in the first post you don't have eliminated this line.

Please check. Thanks


José Luis
Quoting SteveHopwood
Ras, I had something similar this morning.

Most of my DD is caused by a GJ hedge sell left over from the end of December 30th. I got myself into a tangle with this one, having closed the trade it was hedging a long time ago.

The market has moved up so far that the bottom line is higher than the trade's open price. The market hit the bottom line this morning, so TOB obediently sent a pending buy.

I think the only thing to do in this situation is turn off trading in the 'wrong' direction.

Thanks Steve, it just goes to prove the old adage that you can't 'set and forget' any bot no matter how well it performs. You have to be vigilant at all times.
Quoting jcs

Also anyone else noticing the re entry line not redrawing after the second trade has been taken ?
I am having to delete it to get it to move to correct position
Dear Steve:

I had to make the following changes in the program in order to calculate the correct re entry line in my 5 digits broker:

void CalculateReEntryLinePips()
{
/*
extern int ReEntryLinePips=0;
extern int LookBackDays=20;
extern int LowVolatility=100;
extern int MediumVolatility=150;
extern int HighVolatility=200;
extern int PsychoticallyDeranged=250;
*/


//Adapt to x digit criminals
double multiplier;
if(Digits == 2 || Digits == 4) multiplier = 1;
if(Digits == 3 || Digits == 5) multiplier = 10;
if(Digits == 6) multiplier = 100;
if(Digits == 7) multiplier = 1000;

Volatility*= multiplier;
//Set up volatility level
ReEntryLinePips = 250;

if (Volatility < LowVolatility) ReEntryLinePips = 150;
if (Volatility >= LowVolatility && Volatility < MediumVolatility) ReEntryLinePips = 175;
if (Volatility >= MediumVolatility && Volatility < HighVolatility) ReEntryLinePips = 200;
if (Volatility >= HighVolatility && Volatility < PsychoticallyDeranged) ReEntryLinePips = 225;


ReEntryLinePips*= multiplier;

//Calculate non-recovery re-entry pips for the re-entry line
if (OpenTrades < Start_Recovery_at_trades && MinPipsFromLastEntry > 0) ReEntryLinePips = MinPipsFromLastEntry;


}//End void CalculateReEntryLinePips()


Please check the order of the sentences in the code.

Thanks


José Luis
Quoting Forexjlcg
Dear Steve:

I think that in the code in the first post you don't have eliminated this line.

Please check. Thanks


José Luis
Thanks for that. Sorry everyone, it looks as though I mucked up the upload.

The fix really is in post 1 now.

Quoting Forexjlcg
Dear Steve:

I had to make the following changes in the program in order to calculate the correct re entry line in my 5 digits broker:

void CalculateReEntryLinePips()
{
/*
extern int...
Thanks again José Luis. I have made this change and will release in time for market open on Sunday night.

Coders who want to make this change now, the function code is:
Inserted Code
void CalculateReEntryLinePips()
{

/*
extern int     ReEntryLinePips=0;
extern int     LookBackDays=20;
extern int     LowVolatility=100;
extern int     MediumVolatility=150;
extern int     HighVolatility=200;
extern int     PsychoticallyDeranged=250;

*/
   
   
   //Set up volatility level
   ReEntryLinePips = 250;
   
   //Adapt to x digit criminals
   double multiplier;
   
   if(Digits == 2 || Digits == 4) multiplier = 1;
   if(Digits == 3 || Digits == 5) multiplier = 10;
   if(Digits == 6) multiplier = 100;   
   if(Digits == 7) multiplier = 1000;   
   
   Volatility*= multiplier;

   if (Volatility < LowVolatility) ReEntryLinePips = 150;
   if (Volatility >= LowVolatility && Volatility < MediumVolatility) ReEntryLinePips = 175;
   if (Volatility >= MediumVolatility && Volatility < HighVolatility) ReEntryLinePips = 200;
   if (Volatility >= HighVolatility && Volatility < PsychoticallyDeranged) ReEntryLinePips = 225;
   

   
   ReEntryLinePips*= multiplier;

   //Calculate non-recovery re-entry pips for the re-entry line
   if (OpenTrades < Start_Recovery_at_trades && MinPipsFromLastEntry > 0) ReEntryLinePips = MinPipsFromLastEntry;
   
   
}//End void CalculateReEntryLinePips()
Quoting jcs
Steve,
Just one other thing that I have never had working on any version
The breakeven line draws correctly when the second trade is placed, but for any subsequent trade placed it does not adjust automatically to the new BE point, the only way to get it to do this is to delete it and then it goes to the correct position
I will look at this over the weekend.

I am off out now, so enjoy the rest of today's trading guys.

Quoting SteveHopwood
I will look at this over the weekend.

I am off out now, so enjoy the rest of today's trading guys.

Hey Steve, can you take a boo at the NB v5 Auto trading EA and see if there needs to be any changes to it as well regarding the Breakeven lines and other stuff you had to fix with this EA if it relates to that EA. I think there may be an issue with that other EA if the Recovery trade is closed prematurely and it getting back on track at Recovering the original trade. Thanks
24 hours in a day – 24 bottles of beer in a case – Coincidence? I think not
A question: If you limit the MaxTrades to 2, could you safely increase the lot size?
Quoting matrixebiz
Hey Steve, can you take a boo at the NB v5 Auto trading EA and see if there needs to be any changes to it as well regarding the Breakeven lines and other stuff you had to fix with this EA if it relates to that EA. I think there may be an issue with that other EA if the Recovery trade is closed prematurely and it getting back on track at Recovering the original trade. Thanks
No.

Quoting sevenjones
A question: If you limit the MaxTrades to 2, could you safely increase the lot size?
No.

0 traders viewing now