Jemook wrote:

jahill wrote:Thank you for your willingness to implement the "bad basket expiry" feature as well... I think that will go a long way toward making the good baskets make a killing while limiting the injury caused by the bad ones.

Just out of curiosity, what time would you set on this feature? Tonight it took a couple of hours in DD before the trades continued with the trend.

jahill wrote:Oh, also, just right quick...

I am not ignoring those who have requested my set files, but I can almost guarantee they are useless to you. Unless you are using the exact same criminal as I am, they may not work for you in the same way or garner the same results for you at all! Your criminal's platform time, even if off by just one hour, may drastically change your results... The indicator gets it's data from your own platform's bars... Thus, everybody across various criminals will have different pairs trading for different sessions and experience different results. My best advice would be... forward test this thing on a demo using your the criminal you have your live account with, and get it to where you are satisfied with the results. I'm not trying to be a jackarse, I'm just pointing out that other people's setfiles, no matter how successful, may be completely useless to everybody else...

alex_forex wrote:Hi all

Is there anyone who noticed his log file eating all the hard drive space ?

Hundred messages like this one by second :

Code: Select all

2012.05.31 18:52:01	10.2 TMA slope v.1.4B 4.30 for EA USDJPY,Daily: unknown subwindow number -1 for ObjectCreate function

With NB 10.2 EA, and the indicator on charts this error disappeared but not there....

Cheers
Alex

jahill wrote:Hi Jemook,

I would use a 3 hour expiry... Now keep in mind, I start all my sessions at 30 minutes prior to the actual session start time... There is plenty of action there in most cases as well. As I see it though, with this feature, we can POTENTIALLY make excessive money on good baskets now, while losing modest money on bad ones... Of course, this is based on limited observation and speculation. With regard to this past London session as you have mentioned, I lost that one either way, with this feature or without... That's ok because I would've made significantly more money on the other 5 sessions of the past two days that I actually won... Pick your poison I suppose is the name of the game...

Jemook wrote:

jahill wrote:Thank you for your willingness to implement the "bad basket expiry" feature as well... I think that will go a long way toward making the good baskets make a killing while limiting the injury caused by the bad ones.

Just out of curiosity, what time would you set on this feature? Tonight it took a couple of hours in DD before the trades continued with the trend.

jahill wrote:Ahem...
I respectfully disagree with the notion that the entries need to be tweaked with regard to the Shelley EA/strategy. Before you flame me, just hear me out. (I hope Shelley wouldn't mind pitching her two cents in on this, as she has observed the market behavior as it relates to this far longer than I have.)

That said...

We are trading at the beginning of each session when volume, liquidity and hence, movement is at it's peak, right? The idea is, we are scalping... yes, SCALPING... across many pairs that are in a strong trend, trying to accumulate many pips whilst only shooting for a few on a per pair basis. Thus, I'm not sure we need an optimal entry, as has been suggested. In the past 6 sessions, 2 of each, I have lost just this past London session... That is Phenomenal! Consider the issue of "drawdown" for a moment... I am shooting for the same basket TP as I am risking basket SL... so, to have over an 80% winrate for the past two days is quite remarkable, no matter how you slice it!

Also, as Caillou pointed out in a previous post, if you wait for a retracement, you may miss the boat (profits) for XYZ Session altogether! I know that based on what I've observed, only the most recent London session had said retracement, and so I lost the basket. However, the other 5 sessions that I did bank, didn't have much of a retracement to speak of if any at all... So... in theory at least, with the retracement logic in place, I would be 1-0, whereas I am actually 5-1 without it. See the difference? Losses are INEVITABLE! Why try to fight that and try to make a system that is impervious to losses, since it is IMPOSSIBLE anyway?

Now, I can offer two tidbits that will improve the system, in my opinion... First, I would like to humbly suggest a setting that closes the basket at an expiry, ONLY IF THE BASKET IS IN DRAWDOWN, as opposed to only when it is in profit... Why you ask? Well, simple... Every single winning basket I have had has closed in under 3 hours... but, I would rather let those RUN! On the contrary, if I am sitting in DD after 3 hours, I would rather just close up shop and wait until the next session to try again... Thus, I am limiting my exposure (and losses) when the basket goes against my favor, but I am maximizing my profit when the basket shoots off in my favor, and besides, I'm covered by my jumping stops, breakeven, etc. in the "good" scenario anyway...

Second... And I have suggested this previously, but it seems to go ignored or unnoticed... I think that if we could have a Percentage Risk setting Per Basket, or a Dollar Value per Basket risk setting, this would afford us the opportunity to risk the same amount of money on each basket, regardless of the number of currencies we are trading for each basket... This would help significantly in my opinion to maximize the profit potential.

Ok, there's my .02... Now lead me to the slaughter...

Baluda wrote:Steve,

You could consider to change the GetTmaTrue() function in Shelley to this:

Code: Select all

void GetTmaTrue(string symbol, int shift)
{
   double IB_TMA = iMA( symbol, 0, xi_Period, 0, MODE_LWMA, PRICE_CLOSE, shift );
   double ld_Range = iATR( symbol, 0, xi_ATR.Period, shift + 10 );

   TmaUpper = IB_TMA + (ld_Range * xd_ATR.Mult);
   TmaLower = IB_TMA - (ld_Range * xd_ATR.Mult);
}//void GetTmaTrue(string symbol, int shift)

to get rid of the 'iCustom' call. It brings the TMA True calculation into Shelley.

Side note: I would like to get rid of those ugly, seldom to never changed variables like 'xi_Period' and 'xd_ATR.Mult'. I would like them to be internal instead of 'extern'.

Paul