Shelley's multi-pair basket trader

[Kenboi]

Bunker, may I ask what's your BasketSendHour for the Asian session?

[michaelhryu]

Here are my results for the Asian session. Not bad for a Sunday night.
Everything OOTB
H4 made $80 and D1 made $35. All this within an hour.
Cheers!

Bunker

Hi Bunker,

I like your templet, esp., the Slope Diplay with bigger fonts and diplayed in two colums. Can you please tell me how to change fonts, etc., please? I've tried myself, but to no avail.

[mackaozy]

I'm holding off trading until Wendsday- bank holiday today and tomorrow here in London for the Queen's Jubilee hurrah!

Although I'm still at work

[SteveHopwood]

Ehup all members of the Superior Gender.

Oh, and the guys as well.

Version 1u is in post 1. This is a bugfix and it is a biggy.

Gary alerted me to a problem with Shelly's Woh 2x1 reading this morning. It is a complicated problem, so I will not describe it.

I had no London trades this morning. On my chart, I saw that Woh was always opposite to that of the Slope, so the trade was cancelled.

Doing my usual morning trawl through my live-trading charts, I noticed that my chart Woh and those of Shelley's were mostly opposites. When I looked at Shelly's code, I could see nothing wrong. I thought to have a look at the Woh 2x1 source code and found I had copied the calculation code incorrectly. Goodness knows how.

My guess is that we did not notice this last week because the week was established by the time we loaded Shelley onto our charts. Not sure; nor does it matter.

If you are one of those who insists on running a previous version, then you have no alternative other to go into the code editor and make the changes manually. If you have never done this, then now is the perfect time to learn how. Go to http://www.stevehopwoodforex.com/phpBB3 ... ?f=21&t=64 and learn to edit a script code. With a little bit of imagination and brain-power, you can use the techniques to do the required editing.

Go to Void ReadTable()
Find this line of code:
double wo = iMA(symbol,PERIOD_W1,1,0,MODE_SMA,PRICE_OPEN,0);
Change it to:
double wo = iMA(symbol,PERIOD_W1,2,1,MODE_LWMA,PRICE_OPEN,0);

Then find this line of code:
TradePair[cc][6] = none;
and change it to:
TradePair[cc][2] = none;

Don't re-compile. Save the edited file, close down and restart the platform. The edited version will be re-compiled automatically and your settings retained. If you recompile, you have to restart each instance of S and load up your set file.

Gary, I think this solves your thingy.

Until I get around to fixing it, this probably applies to Simple Shelley also.

[SWG123]

Steve, is this correct? You didn't highlight it.

Go to Void ReadTable()
Find this line of code:
double wo = iMA(symbol,PERIOD_W1,1,0,MODE_SMA,PRICE_OPEN,0);
Change it to:
double wo = iMA(symbol,PERIOD_W1,2,1,MODE_LWMA,PRICE_OPEN,0);

[Jemook]

Thanks for the fixed version, will DL now.

[feucht]

I thought that it looked funny that the Slope and WOH were all opposite of each other, but then had some existential angst that I didn't really understand WOH and Steve was going to call me a cretin

All looks fine now to me. I would say the code correction bit in your post Steve is a bit confusing as there are changes that are not in red. I redownloaded the latest version, but I can see people only changing the bits in red and missing the other bits.

Many thanks!

[SteveHopwood]

Steve, is this correct? You didn't highlight it.

Go to Void ReadTable()
Find this line of code:
double wo = iMA(symbol,PERIOD_W1,1,0,MODE_SMA,PRICE_OPEN,0);
Change it to:
double wo = iMA(symbol,PERIOD_W1,2,1,MODE_LWMA,PRICE_OPEN,0);

Yes. Here is the code from the indi:
wo = iMA(NULL,PERIOD_W1,2,1,MODE_LWMA,PRICE_OPEN,j);
ma = iMA(NULL,0,1,0,MODE_SMA,PRICE_MEDIAN,i);

Bib likes to shift the moving average a bit, to avoid the 'wriggling snake' effect of using the most current.

[phil_trade]

Ehup all members of the Superior Gender.

Oh, and the guys as well.

Version 1u is in post 1. This is a bugfix and it is a biggy.

Gary alerted me to a problem with Shelly's Woh 2x1 reading this morning. It is a complicated problem, so I will not describe it.

I had no London trades this morning. On my chart, I saw that Woh was always opposite to that of the Slope, so the trade was cancelled.

Doing my usual morning trawl through my live-trading charts, I noticed that my chart Woh and those of Shelley's were mostly opposites. When I looked at Shelly's code, I could see nothing wrong. I thought to have a look at the Woh 2x1 source code and found I had copied the calculation code incorrectly. Goodness knows how.

My guess is that we did not notice this last week because the week was established by the time we loaded Shelley onto our charts. Not sure; nor does it matter.

If you are one of those who insists on running a previous version, then you have no alternative other to go into the code editor and make the changes manually. If you have never done this, then now is the perfect time to learn how. Go to http://www.stevehopwoodforex.com/phpBB3 ... ?f=21&t=64 and learn to edit a script code. With a little bit of imagination and brain-power, you can use the techniques to do the required editing.

Go to Void ReadTable()
Find this line of code:
double wo = iMA(symbol,PERIOD_W1,1,0,MODE_SMA,PRICE_OPEN,0);
Change it to:
double wo = iMA(symbol,PERIOD_W1,2,1,MODE_LWMA,PRICE_OPEN,0);

Then find this line of code:
TradePair[cc][6] = none;
and change it to:
TradePair[cc][2] = none;

Don't re-compile. Save the edited file, close down and restart the platform. The edited version will be re-compiled automatically and your settings retained. If you recompile, you have to restart each instance of S and load up your set file.

Gary, I think this solves your thingy.

Until I get around to fixing it, this probably applies to Simple Shelley also.

Hello Steve

I suppose you mismatch the code between Woh 1x0 et 2x0. So One question appear, why don't you use both Woh like in NB 10.2 EA ?

[SteveHopwood]

Ehup all members of the Superior Gender.

Oh, and the guys as well.

Version 1u is in post 1. This is a bugfix and it is a biggy.

Gary alerted me to a problem with Shelly's Woh 2x1 reading this morning. It is a complicated problem, so I will not describe it.

I had no London trades this morning. On my chart, I saw that Woh was always opposite to that of the Slope, so the trade was cancelled.

Doing my usual morning trawl through my live-trading charts, I noticed that my chart Woh and those of Shelley's were mostly opposites. When I looked at Shelly's code, I could see nothing wrong. I thought to have a look at the Woh 2x1 source code and found I had copied the calculation code incorrectly. Goodness knows how.

My guess is that we did not notice this last week because the week was established by the time we loaded Shelley onto our charts. Not sure; nor does it matter.

If you are one of those who insists on running a previous version, then you have no alternative other to go into the code editor and make the changes manually. If you have never done this, then now is the perfect time to learn how. Go to http://www.stevehopwoodforex.com/phpBB3 ... ?f=21&t=64 and learn to edit a script code. With a little bit of imagination and brain-power, you can use the techniques to do the required editing.

Go to Void ReadTable()
Find this line of code:
double wo = iMA(symbol,PERIOD_W1,1,0,MODE_SMA,PRICE_OPEN,0);
Change it to:
double wo = iMA(symbol,PERIOD_W1,2,1,MODE_LWMA,PRICE_OPEN,0);

Then find this line of code:
TradePair[cc][6] = none;
and change it to:
TradePair[cc][2] = none;

Don't re-compile. Save the edited file, close down and restart the platform. The edited version will be re-compiled automatically and your settings retained. If you recompile, you have to restart each instance of S and load up your set file.

Gary, I think this solves your thingy.

Until I get around to fixing it, this probably applies to Simple Shelley also.

Hello Steve

I suppose you mismatch the code between Woh 1x0 et 2x0. So One question appear, why don't you use both Woh like in NB 10.2 EA ?

Because upside-down Shelley doesn't use it manually. It would be easy enough to include, but let's see how we get on without it. I am using none of the confirmation filters on my own demo.