Awesome - original version

[1Direction]

Daily and weekly profit target.

For your information I wrongly assumed that once the daily/weekly target was reached it would close all open trades and only restart to trade next day / next week but instead the EA will not initiate new trades and manage existing ones as stated in the manual (read the manual

Setting the values to zero and re- initialize the EA will not disable the function and the EA won't take new trades. You have to restart the Empty4 instance for it to be cleared / disabled and forget about previous target.

What a blast reaching daily target is like having xmas and my birthday the same day

Using v 1c M1 set file

[Dragonian]

Did you try clearing "Global Variables"? If this is a repeatable issue perhaps an automatic global clearing could be built into the next offering?

[getdown71]

Daily and weekly profit target.

For your information I wrongly assumed that once the daily/weekly target was reached it would close all open trades and only restart to trade next day / next week but instead the EA will not initiate new trades and manage existing ones as stated in the manual (read the manual

Setting the values to zero and re- initialize the EA will not disable the function and the EA won't take new trades. You have to restart the Empty4 instance for it to be cleared / disabled and forget about previous target.

What a blast reaching daily target is like having xmas and my birthday the same day

Using v 1c M1 set file

Great reports on awesome to date. Can you post v1c M1 set file ?

[1Direction]

Great reports on awesome to date. Can you post v1c M1 set file ?

It's the one in post 1 "Awesome M1 Basket.set" with Symbol Basket disable

EDIT: You can also check here for running stats and set files http://www.stevehopwoodforex.com/phpBB3 ... 40#p155573

[1Direction]

Steve, what do you think of an option to exclude pairs in recovery from the global basket closure?

Or this is defeating the purpose of it and will be useless?

My current situation with one pair gbpjpy in recovery basically block the global target to ever hit until the pair recover.

awesome is awsone

[SteveHopwood]

Steve, what do you think of an option to exclude pairs in recovery from the global basket closure?

Or this is defeating the purpose of it and will be useless?

My current situation with one pair gbpjpy in recovery basically block the global target to ever hit until the pair recover.

awesome is awsone

It seems to me that it would negate the point of treating the entire position as a single basket. That is before I start to contemplate the nightmare it would be to code.

[1Direction]

Steve, what do you think of an option to exclude pairs in recovery from the global basket closure?

Or this is defeating the purpose of it and will be useless?

My current situation with one pair gbpjpy in recovery basically block the global target to ever hit until the pair recover.

awesome is awsone

It seems to me that it would negate the point of treating the entire position as a single basket. That is before I start to contemplate the nightmare it would be to code.

Yes, maybe the AllPairTradeManager(APTM) will do the trick of closing baskets that reached profit target, still studying how to set it up.

Thx

[spyderman]

Chugging away after a couple of days using.

Statement.png

Awesome M1 Baske modt.set

[acostafulano]

Hello Steve,

I am testing some different setfiles in v1c, and among these I was trying to get Awesome to trade Each set of Symbol/Timeframe as a basket for a set Cash Profit Target,

Settings were (For all 4 timeframes being tested):

tb1=---- Trade1 basket trading ----
Trade1AsBasket=true
Trade1BasketCashTarget=5
Trade1BasketCashPercentageTarget=0.0

I was noticing closures on sets of trades that (for each timeframe) hit the Basket TP of 5, however INDIVIDUAL trades that were hitting this TP were not closing.
This took me to the code and I noticed the following in line 3707 of v1c:

//Check for individual time frame basket closure.
if (MarketTradesTotal > 1)
if (TradeAsBasket[cc] )
if (HaveWeHitBasketTarget(cc) )

I changed this to
if (MarketTradesTotal >= 1)

and with this change individual trades started being treated as the basket as well and closed properly at TP5, even if it was only one trade and not properly a "basket" of trades.

Just thrwing this out there in case it's of use to anyone

[TraderJoeForex]

Yes, maybe the AllPairTradeManager(APTM) will do the trick of closing baskets that reached profit target, still studying how to set it up.

Thx

My thoughts on this led me to the set files I am testing in our forward test, which have recovery false and individual basket false so the only way the trades can close is a global basket. In theory had I been testing this set last week it might have led to a GBPJPY close before it got temporarily out of hand because all the other pairs in profit would have stayed open until they could counterbalance GBPJPY rather than closing as individual baskets.

So far this week, only closing as a global basket is working beautifully and it has now closed it's 20th basket in 4days. Just waiting for the next sudden move on a pair to see whether that pair will get closed or whether the whole basket will still get stuck for a while.

So kinda the opposite of what you are thinking, and I don't know which way will be best but we've got it covered between the set files in our test so hopefully the data will be useful once we have enough of it.

My original M1basket which still has the GBPJPY drawdown is still happily closing individual baskets on other pairs whilst waiting for GBPJPY to get back to it's long intended direction.

I think the thing to remember is that we are trading long cycles here so a few weeks drawdown from time to time can be expected and is no different to when we stuff up our manual entries. And I do plenty of that too! But trading in the direction of the yearly cycle has a certain comfort to it, even when GBPJPY has 10 recovery trades all in deep drawdown

One thing that is apparent is that my set files will need to have a wider recovery spacing. 10pips was always going to be asking for trouble but I think that helps the testing because it highlights the strengths or weaknesses of the rest of the settings rather well. Once we have found the right balance with the rest of the choices then using wider recovery should be the icing on the cake?