There seems a bug in Jugulator for calculation of ActualOrders.
In my test, only one position opened for GBPJPYm at some point. It was closed because of ConfirmedOrders=1 and ActualOrders=2.

Not sure where this problem comes. In the code, ActualOrders seems will always increase by 1 when an order is sent. If the SendOrder fails (due to various reason), ActualOrders would still increase 1. Perhaps, it is better to check the error from SendOrder. If no error, then ActualOrders increase by 1.

Thanks!

MATT
FYI there is a thread on non lagging indicators that may be useful. especially the info on the stepma7.1 and the absolute strength v1.1. These 2 guys are also very good programmers and maybe you could get some feedback from them.

Hello yeoeleven,

Thank you for your answer and your councils.
I will follow them

__________________
All long voyages always start from the first small steps ...

That should be fixed here (Page 89, post 890, Jugulator.zip). There is a new variable in the EA that gets set to the order number. If the order fails there shouldn't be an order number and the code checks that before it increments the ActualOrders variable.

void OrderNeedsOpening() {

//Preserve value before changing them
double TempActualLotSize = ActualLotSize;

//Increase Lot Size
ActualLotSize = NormalizeDouble(ActualLotSize * LotsIncreaseBy, LotPrecision);

//Are we trying to go long?
if (OrderDirection == 1) {
//Set Take Profit and open a Long order
ActualTP = Ask + (TakeProfit * Point);
LastTicket = OrderSend(Symbol(), OP_BUY, ActualLotSize, Ask, OrderSlippage, ActualSL, ActualTP, "Order" + (ActualOrders + 1), Magic, 0, Blue);
}
//Are we trying to go short?
else if (OrderDirection == 2) {
//Set Take Profit and open a Short order
ActualTP = Bid - (TakeProfit * Point);
LastTicket = OrderSend(Symbol(), OP_SELL, ActualLotSize, Bid, OrderSlippage, ActualSL, ActualTP, "Order" + (ActualOrders + 1), Magic, 0, Red);
}

//If the order went thru it will be greater than 0
if (LastTicket > 0) {
ActualOrders++;
}
//Order failed so we need to set the value back
else {
ActualLotSize = TempActualLotSize;
}

}

Does the code you are using reflect this change because this is what I am running and I don't have any problems opening multiple order and having them close when they should TP or SL. Note that this type of change is also in other areas of the code so copying and pasting this section alone will not fix the problem.

Here are the 0.10 and 0.01 results for this morning.

Attached Images

	Jugulator (0.01) 2006-12-15.gif (4.7 KB, 118 views)
	Jugulator (0.10) 2006-12-15.gif (4.7 KB, 117 views)

Attached Files

	Jugulator (0.01) 2006-12-15.htm (86.8 KB, 70 views)
	Jugulator (0.10) 2006-12-15.htm (78.1 KB, 54 views)

Here are the 0.10 and 0.01 results for this morning at 10am EST after several major news reports.

0.01 account went up $268.94
0.10 account went up $1,912.44

Attached Images

	Jugulator (0.01) 2006-12-15 2.gif (4.7 KB, 108 views)
	Jugulator (0.10) 2006-12-15 2.gif (4.8 KB, 104 views)

Attached Files

	Jugulator (0.01) 2006-12-15 2.htm (106.7 KB, 31 views)
	Jugulator (0.10) 2006-12-15 2.htm (98.9 KB, 34 views)

Closed for the week 10points3 Dynamic Stop. Closing off pairs as they became in profit. Settings previously posted

A good week overall.

Am still waiting for USDJPY to retrace prior to closing off Jugulator.

John

Attached Images

10points3#19.gif (4.9 KB, 109 views)

Attached Files

10points3#19.htm (111.7 KB, 44 views)

Carrying on from the settings on post #891 and previous results on post #898. Here is the detailed statement after closing for the week.

Will look at the settings prior to opening on Monday likely to use closer to Matt's since they are clearly better than mine.

John

Attached Images

Jug#4.gif (5.4 KB, 109 views)

Attached Files

Jug#4.htm (66.9 KB, 21 views)

The version I am testing does not contain the above change. I will use the newer version. Thanks mtaboneweb!

Are you still using the orginal 10points3 Dynamic Stop which is on page 18 ?

Thanks