On this EA...kayvan and you made Lcfx's TFX profitable for me..and I again watch it with interest.

kayvan states there are fill problems...and he wants a modified chain which extends the progression beyond a primitive doubling from the beginning...but regardless... the EA works in its present state with my settings thus far on Cable H1 with primitive doulbling and the stated errors.

If you work on this EA further, please scrole up and reread some of my suggestions for open architecture. This will minimize much future work for you wolfe. This thread may become one of the all time hall of fame threads in tsd...and we might just make some profit to boot...

ES

__________________
ElectricSavant Challenge™

Live Portfolio

to reiterate...now this is my opinion only...

Us Testers need from you coders the following....

• A candlestick lookback for breaches that we can set in the user friendly input menu.
  
• An Average Down or Pyramid Up method to choose in the user friendly input menu
  
• Number of PIPS breach zone that we can set in the user friendly input menu

This is what I have so far...and these proposed options present a myriad of possibilites to test in an idiot-savant way Wolfe you can do it!

ES

__________________
ElectricSavant Challenge™

Live Portfolio

I wish us luck next week

ES

__________________
ElectricSavant Challenge™

Live Portfolio

ES,

So I can try to do this right the first time, could you break down and explain exactly what you mean? I want to be sure I fully understand before I try to implement these changes.

BTW, where has kayvan been lately? He started all this!

Wow I feel like a kid in a candy store yes I will be thrilled to explain my ideas...others reading...please chime in if you agree or disagree...ok? Sometimes I get delussional in my thoughts and dreams and need to be brought back down to earth..

Here is a detailed explanation of my "open architecture" vision..

I think that some of us want to add to the position as the original TFX, thus adding additional positions as the original entry did and others would like to do the opposite and buy on a downtrend or sell on an uptrend thus averaging down towards the long or averaging up towards the short entry.

So for those testers I suggest the input titled:

Pyramid: Default =True (False would equal averaging down/up in the kayvan breach zone ...2...3...4....5...etc... pips below the low of the previous candlestick ...or vice versa for the high)

---------------------------------------------------------------------------------------------------------------
To define the number of pips for the entry to trigger from the low or high I suggest an input of this:

EntryLag: 1...2...3...etc PIPS (this would be the number of pips needed to exceed the high or the low before an entry is triggered with wolfes most excellent and stable ordersend chunk of code)

--------------------------------------------------------------------------------------------------------------

Now some of you may want to look at the low or high to be breached with more than just the previous candlestick...like maybe the last two...or last three...and so forth...as each TF marches forward on the right edge of the chart this would recalc...anyways here is the input suggestion:

Lookback: 1...2....3....4... (now this is the number of candlesticks that is looked at for the high or the low...remember that this could be whatever the user loads this on...M5, m15, m30, H1....etc)

--------------------------------------------------------------------------------------------------------------

Ok I have some new inputs to suggest also...

Here is one:

LastEntryFilter: default is true. (true means that the next entry must exceed the last entry accoording to if it is a pyramid or an average down choice in the above input. false means that the last entry is ignored and simply enters on the criteria)

-----------------------------------------------------------------------------------------------------------

One more extra input suggestion:

TF in minutes: 60 is the default (5...30...60...240....1440....etc...this would remove the danger of the user flipping through timeframes accidentally and screwing up his current trade, thus I suggest a user definable hardcode)

ES

__________________
ElectricSavant Challenge™

Live Portfolio

wolfe..

that just about covers all the options Many posters have differing ideas and can simply use these inputs and it will avoid further coding if you put all of these options in from the get-go...This will be the all-in-one TFX solution™

Have I missed anything readers? I have read everone of your posts...speak up now...

ES

__________________
ElectricSavant Challenge™

Live Portfolio

ohhh

Here is another two inputs:

DoublingProgression: default=false


and then here:

SequentialProgression: default=false (this is kayvans modified doubling)


If both of these are false then the entry does not grow...it remains the same as indicated in the increment...ummm...if both are true kayvans superscedes...

__________________
ElectricSavant Challenge™

Live Portfolio

kayvan was an angel...he was not real.

ES

__________________
ElectricSavant Challenge™

Live Portfolio

ES,

I like your ideas, and will try to implement them. The more options, the more complicated the coding becomes. This could take a while.

How about simply an input such as this-

Logic=1; //1=trend, 2=counter-trend

Trying to figure out good ways to implement all the new ideas, without over complicating the code.