Here's the new "Goblin" ea...little brother to Predator - page 54

 
EnkiJr:
On behalf of the silent majority of this tread readers... I would like to thank you Bluto for starting this tread... your work... also, for work of all the contributors here and your collective insightful mind... The Goblin... Congratulations...!!! Probably many people such as myself read here, but they don't know enough yet to get involved... thanks again Bluto and... I will be following you at Jugulator...

Thank you for the kind words, Enki.

 
 

hello bluto,

im working on the hedging as well, HEDGING is the only way to fix the problem and will fix it pretty good........these are the steps needed to win and to create the closest thing to the holy grail:

Phorex Phreak Solution To Big Moves

For this kind of EA to have a chance at any longevity long term and avoiding its prime weakness of the big 400-500 move without a retracement there are 2 steps that MUST be implemented in the EA before even considering using it.......

#1- when a position goes against you and lets say your second order is executed to open, the EA MUST close the first one at a loss, why??? to avoid building up positions and using unecessary margin..so if a 3rd position is opened, that second one is closed at a loss as well, and so on, until you current position covers the losses for the other losing closed positions and profits some..

#2- starting with .01 nano lots, now lets say your max trade is open all the way at 10, this means that your down 5.12 lots, now if the position goes against you another 20 pips, which would be at the 200 pip mark from the first order, open a hedge at 1.05 lots the other way simultaneosly, if it goes against you another 10 pips, add another 1.05 lots, another 10 pips, add another 1.05 lots, all with 30 pip trailing stops on the hedge orders only, to a max of a combined 5.25 lots ( so 5 X 1.05 lots) in order to buffer the other side, that way if you have a nasty 500 pip drop due to an unexpected news anouncement at least you have some built in hedge protection and even might profit from it because your using 5.25 versus the other 5.12 from the original orders....

bluto:
Let me fill you in on where I'm at after pouring over and pondering this 10Point3 engine for the past few days and what the future should hold..

My most recent efforts have been targeted at having the EA constantly monitor the trend (short-term swings, medium term, etc.) via the indicators instead of once every Maxtrades cycle. The idea was to address the flaw of placing gobs of countertrend orders. That was fairly easy to implement but the results were offset by the fact that there's open orders on the turn left to be dealt with, typically by closure resulting in losses greater than accrued profits. No throttle exists to ease off on the trades (at increasing lot sizes) as the slowdown in velocity approaches.

Bottom line....there's really no way to make the 10Point3 engine a winner in it's current architecture...the runaway fastbars can be dealt with but at the cost of the bailout of open orders. I had thought of maybe using an inverted lot-size scheme where you place the larger order first followed by decreasing lot sizes for subsequent orders.

So, what's the cure? I think you said it best...10Point3/Goblin/Terminator/Jugulator, whatever you want to call it needs......HEDGING. That's the bottom line. And that's going to take a bit of time but I'm working on it. I think that will be my contribution to furthering the cause.

As for Jugulator, it should be the same as Goblin at this point with the exception that the code has been better organized.
 
phorex_phreak:
hello bluto,

im working on the hedging as well, HEDGING is the only way to fix the problem and will fix it pretty good........these are the steps needed to win and to create the closest thing to the holy grail:

Phorex Phreak Solution To Big Moves

For this kind of EA to have a chance at any longevity long term and avoiding its prime weakness of the big 400-500 move without a retracement there are 2 steps that MUST be implemented in the EA before even considering using it.......

#1- when a position goes against you and lets say your second order is executed to open, the EA MUST close the first one at a loss, why??? to avoid building up positions and using unecessary margin..so if a 3rd position is opened, that second one is closed at a loss as well, and so on, until you current position covers the losses for the other losing closed positions and profits some..

#2- starting with .01 nano lots, now lets say your max trade is open all the way at 10, this means that your down 5.12 lots, now if the position goes against you another 20 pips, which would be at the 200 pip mark from the first order, open a hedge at 1.05 lots the other way simultaneosly, if it goes against you another 10 pips, add another 1.05 lots, another 10 pips, add another 1.05 lots, all with 30 pip trailing stops on the hedge orders only, to a max of a combined 5.25 lots ( so 5 X 1.05 lots) in order to buffer the other side, that way if you have a nasty 500 pip drop due to an unexpected news anouncement at least you have some built in hedge protection and even might profit from it because your using 5.25 versus the other 5.12 from the original orders....

So...will you be developing a "Goblin Phreak" EA?

 

a paid programmer is doing it to the 2 specifications above.....im going to name the EA "The Porno Star"

bluto:
So...will you be developing a "Goblin Phreak" EA?
 

Bluto... "So, what's the cure? I think you said it best... 10Point3/Goblin/Terminator/Jugulator, whatever you want to call it needs... HEDGING. That's the bottom line. And that's going to take a bit of time but I'm working on it. I think that will be my contribution to furthering the cause.

As for Jugulator, it should be the same as Goblin at this point with the exception that the code has been better organized."

Bluto... please stay with it... HEDGING... you know i am not in a position to help... just a moral support... *smile*...

 

porno star

phorex_phreak:
a paid programmer is doing it to the 2 specifications above.....im going to name the EA "The Porno Star"

porno star ,,,,wow

i think i'm gonna be tired after using this EA every day;)

 
typhoon_gr9:
porno star ,,,,wow i think i'm gonna be tired after using this EA every day;)

LOL

 
EnkiJr:
Bluto... "So, what's the cure? I think you said it best... 10Point3/Goblin/Terminator/Jugulator, whatever you want to call it needs... HEDGING. That's the bottom line. And that's going to take a bit of time but I'm working on it. I think that will be my contribution to furthering the cause.

As for Jugulator, it should be the same as Goblin at this point with the exception that the code has been better organized."

Bluto... please stay with it... HEDGING... you know i am not in a position to help... just a moral support... *smile*...

You can count on the fact that I'm going to stay with it....I never give up. I've already got a solid design together on how I want this thing to work. This should leverage the pseudo-Martingale approach of the 10Point3 order engine with a security net to take over when things turn the wrong way. I think it's going to be cool.

 

Time factor

When a big move happens it normally goes pretty fast so the 10Point3/Goblin/Terminator/Jugulator or the Porno star will open orders in sequence very fast ( really fast ).

Ok now let’s say we add a time factor here.

Case there were 3 or 5 orders opened simultaneously in less than ( x seconds ) that means it’s a big fast move, then we send a command to close all the orders with loss, and I would suggest not to hedge but to wait at least 5 minutes before letting the EA placing more orders so as not the be caught in the reverse candle and lose more money.

Ex: Lets say every time an order is placed by the Goblin we place a timer value of 10 then value decrease within 10 sec. then we keep checking the added value of the Goblin orders.

Now lets say the Goblin opens 3 orders and the added value of the timers was something like 27 ( 9 + 8+ 10 ) that means it’s a fast trend and the Goblin is placing orders very fast so we either close the orders with losses and wait for some time lets say 5 min, or take a heodge position

Just an idea what do you think guys? Could it be done?

Reason: