ShelleyJemNOW autotrader

[SteveHopwood]

I am starting to plan the autotrader. The function of this thread is to invite comments and feature requests.

To make sure I have the basics correct:

• - D1 Slope must be >= 0.8 or <= -0.8
  - for buys:
  • - daily pivot > weekly pivot > monthly pivot
    - market must retrace below the daily pivot and then close above OR
    - market must retrace below the H4 5.1 moving average and then move up to touch it again.
  
  - for sells:
  • - daily pivot < weekly pivot < monthly pivot
    - market must retrace above the daily pivot and then close below OR
    - market must retrace above the H4 5.1 moving average and then move down to touch it again.
  
  - most of the pairs must have reached their trigger before we send the basket.

Have I missed anything.

The new EA will mostly be an amalgamation of ShelleyJem and ShelleyNOW. Extra features I plan to add are:

• - trading hours to give users the option to disable basket-send during unfavourable periods.
  - an optional close-basket time with the usual options re profitability.

Any other ideas, guys?




Ignore this. It is a reminder to me
http://www.stevehopwoodforex.com/phpBB3 ... 841#p16841

[Jemook]

Hi Steve,

I think this would work best for the auto EA (please note this is re-written to what Steve posted):

• - D1 Slope must be >= 0.8 or <= -0.8
  - for buys:
  • - daily pivot > weekly pivot > monthly pivot
    - market must retrace below the daily pivot and then close above OR
    - market must retrace below the H4 5.1 moving average and then move up to touch it again.
  
  - for sells:
  • - daily pivot < weekly pivot < monthly pivot
    - market must retrace above the daily pivot and then close below OR
    - market must retrace above the H4 5.1 moving average and then move down to touch it again.
  
  - most of the pairs must have reached their trigger before we send the basket.

In saying this I'm also still testing out a few things about closing a non performing basket using the H1 Currency Slope Strength.

[spotdespot]

One thing Jemook didn't explicitly highlight there Steve is that he is talking about price reacting to the daily pivot not the weekly.

[Jemook]

I was thinking with ShelleyNow (and this) it would be great if we could see in the info text;

- the highest number of pips made / amount of pairs in the basket
- the highest number of pips lost / amount of pairs in the basket

ie basket makes 460 pips / 10 pairs = 46 pips per pair highest gained
ie basket loses 460 pips / 10 pairs = -46 pips per pair highest DD

This would greatly influence what I input on adaptivepipsTP/SL

[NeoTrader]

hi steve, jemook,

Please take account of the daily pivots.
- for buys:

• - daily pivot > weekly pivot > monthly pivot
  - for sells:
  • - daily pivots < weekly pivot < monthly pivot

fok made a point...according to the 10.2a rules daily pivots should also align in place and should be in the rules.
And I think jemook also uses this rule if i remember correctly.

only want it to be checked..

happy trading,

NeoTrader

-

[SteveHopwood]

Hi Steve,

I think this would work best for the auto EA (please note this is re-written to what Steve posted):

• - D1 Slope must be >= 0.8 or <= -0.8
  - for buys:
  • - daily pivot > weekly pivot > monthly pivot
    - market must retrace below the daily pivot and then close above OR
    - market must retrace below the H4 5.1 moving average and then move up to touch it again.
  
  - for sells:
  • - daily pivot < weekly pivot < monthly pivot
    - market must retrace above the daily pivot and then close below OR
    - market must retrace above the H4 5.1 moving average and then move down to touch it again.
  
  - most of the pairs must have reached their trigger before we send the basket.

In saying this I'm also still testing out a few things about closing a non performing basket using the H1 Currency Slope Strength.

Gotcha.

If your CSS experiments bear fruit, it will be easy to add the relevant code.

[SteveHopwood]

I was thinking with ShelleyNow (and this) it would be great if we could see in the info text;

- the highest number of pips made / amount of pairs in the basket
- the highest number of pips lost / amount of pairs in the basket

ie basket makes 460 pips / 10 pairs = 46 pips per pair highest gained
ie basket loses 460 pips / 10 pairs = -46 pips per pair highest DD

This would greatly influence what I input on adaptivepipsTP/SL

Do you want this to be restarted when there is a new basket, or only updated when the all-time record is broken, as in the current max pips loss thingy?

[Jemook]

Restarted for every new basket

[garyfritz]

Maybe I'm just an anal-retentive over-analyzing geek (shut up Steve ) but what I'd really like to see is a full history of the open equity. The max/min would be useful, but a full history would give you a MUCH better picture for the bot's behavior.

This could be done as simply as "write out a line to a file when you open a basket, close a basket, and once every X minutes while it's open." Include the open equity for each pair and optionally the basket as a whole. Then you could open that in Excel and chart the behavior of the bot while the basket is open.

I think that would be tremendously valuable data for characterizing the EA's performance, deciding on stops, etc.

Example dump:
2012.06.25 02:30,AUDCAD,AUDNZD,EURUSD,EURNZD,GBPUSD // Open-basket message -- tells pairs in basket
2012.06.25 03:00,10.1,15.3,-5.4,18.2,-10.5,27.7 // Open equity for each pair & for the whole basket
// similar lines each 30 minutes or whenever, including a final one when the basket closes

[slowkey]

After reading what must have been hundreds of post from Shelly to the present new iteration of the basket trader starting in this thread, my eyes are more than a little blurry. Never have we been able to define trend so precisely and the lack of being able to do this has been the Achilles heel in EA performance and development in the past I think. Just look at all the trend detection methods we tried in the shell. My hat off to Shelly and Jemook. My hat off to you Steve and your coder colleagues here. This forum is popping with great ideas. Now that I am caught up for a second maybe I can contribute some.