stevehopwoodforex.com
https://www.stevehopwoodforex.com/phpBB3/
Print view

Baluda Indicators
https://www.stevehopwoodforex.com/phpBB3/viewtopic.php?t=629		 Page 44 of 81
Author:  Baluda [ Mon Oct 29, 2012 12:40 pm ]
Post subject:  Re: Baluda Indicators
Athar,

That is a lot of questions. No disrespect, but did you read about the settings of SlopeValues in post 1 of this thread since most of the answers are there?

Paul
Author:  atharmian [ Mon Oct 29, 2012 1:09 pm ]
Post subject:  Re: Baluda Indicators
Paul,

Sorry to interrupt you again. I went through your Slope Value description fully again as in your Post #1. Also looked at several other posts, one of them talking about the same fonts problem. It was replied by NeoTrader saying that one should try different fonts.

Above only answers my questions on the font problem, which is where the display of Trend Icons issue arises. So looks like this is not an easy problem as you mention.

So I have found that actually a prop font like 'times new roman bold' in size 8 works best for me. Size 9 (default) on all the fonts I tried (Times New Roman, Verdana, Tahoma, Comic Sans, Georgia, Arial and then non-props like Lucida Console, Courier New. Fixedsys, Monaco and Andale Mono) looks bad in all cases, resulting in overlaps.

The other questions (Pivot Direction explanation, Column display issue in Curr Strength, Trend Icon orientation/color, update interval) are not addressed in your post #1. Are there other posts I should look at ?

The other comments (multi-bullet Top Buy/Sells, TMASlope v. zznbrm etc.) are not related to set up. One is a suggestion, another is a general question ...

I asked all above questions because I am experimenting quickly, and I was hoping that other forum members might also be able to answer, without you necessarily getting involved !

Regards,
Athar.
Baluda wrote:Athar,

That is a lot of questions. No disrespect, but did you read about the settings of SlopeValues in post 1 of this thread since most of the answers are there?

Paul
Author:  atharmian [ Mon Oct 29, 2012 1:17 pm ]
Post subject:  Re: Baluda Indicators
Paul,

Additional Note:

1. Your Post #1 only half answers my Pivit question, about ordering, but not re: the ++ looking characters in some cases, blanks in others, and no pivot order display in most.

2. So I was right about assuming re: the Trend Icon (it seems ?) You just had to say, yes.

Athar.
atharmian wrote:Paul,

Sorry to interrupt you again. I went through your Slope Value description fully again as in your Post #1. Also looked at several other posts, one of them talking about the same fonts problem. It was replied by NeoTrader saying that one should try different fonts.

Above only answers my questions on the font problem, which is where the display of Trend Icons issue arises. So looks like this is not an easy problem as you mention.

So I have found that actually a prop font like 'times new roman bold' in size 8 works best for me. Size 9 (default) on all the fonts I tried (Times New Roman, Verdana, Tahoma, Comic Sans, Georgia, Arial and then non-props like Lucida Console, Courier New. Fixedsys, Monaco and Andale Mono) looks bad in all cases, resulting in overlaps.

The other questions (Pivot Direction explanation, Column display issue in Curr Strength, Trend Icon orientation/color, update interval) are not addressed in your post #1. Are there other posts I should look at ?

The other comments (multi-bullet Top Buy/Sells, TMASlope v. zznbrm etc.) are not related to set up. One is a suggestion, another is a general question ...

I asked all above questions because I am experimenting quickly, and I was hoping that other forum members might also be able to answer, without you necessarily getting involved !

Regards,
Athar.
Baluda wrote:Athar,

That is a lot of questions. No disrespect, but did you read about the settings of SlopeValues in post 1 of this thread since most of the answers are there?

Paul
Author:  Baluda [ Mon Oct 29, 2012 1:59 pm ]
Post subject:  Re: Baluda Indicators
Athar,

In short:
  • Arrow icon: show the trend as the approximate direction of the TMA Slope based on the last 5 bars of the indicator's timeframe.
  • Bullet icon: indicates if the TMA Slope of the immediate lower timeframe is over/under slopeLevel1.
  • Pivot order: show DWM pivot order, include 'p' for Price.
  • Column width: try to set variable 'horizontalShift' to 150 (in code).

    Paul
Author:  atharmian [ Tue Oct 30, 2012 2:54 am ]
Post subject:  Re: Baluda Indicators
Paul,

Many thanks. Now how about the refresh rate (important owing to PC drag) ?
Is it fixed, and if yes, at what rate? Ticks, current TF? Can it be changed?

Again, I am not a programmer, but can edit and re-compile.

PS. I'l just assume TMA Slope supersedes zznbrm's indy.

:)
Athar.
Baluda wrote:Athar,

In short:
  • Arrow icon: show the trend as the approximate direction of the TMA Slope based on the last 5 bars of the indicator's timeframe.
  • Bullet icon: indicates if the TMA Slope of the immediate lower timeframe is over/under slopeLevel1.
  • Pivot order: show DWM pivot order, include 'p' for Price.
  • Column width: try to set variable 'horizontalShift' to 150 (in code).

    Paul
Author:  tx413 [ Tue Oct 30, 2012 10:12 pm ]
Post subject:  MPBM
MPBM has been of great use to me; mostly I've used it in its "ShellyNow" incarnation. It is basically the same code, right?

One thing I've noticed that might be a bug -- or might be a feature -- I'm not sure. But if you're using adaptive SL & TP or adaptive ANYTHING then I don't think it makes sense to include pending orders, does it?

If I have, say, 2 open positions and 2 pending orders (BUY STOP or whatever) then the adaptive SL and TP will be based on having 4 open positions in the basket. Not exactly the way I think it should work.

By adding these 3 lines in the CountOpenTrades() procedure, you can have it only count open positions. The lines go just above the "OpenTrades++" line in the for() loop.

Code: Select all

//Ignore pending orders
int type = OrderType();
if ( type != OP_BUY && type != OP_SELL ) continue;
EDIT: After thinking about this, I realize that I might not do things the way MPBM is supposed to work. I don't always fire off my baskets in one shot. I usually set up about 4 or more pending orders and give them an hour or so to get filled and therefore added to the basket. After that time I cancel any orders where the market either has not moved or moved the wrong way (and therefore didn't open a position.)
Author:  ross [ Wed Oct 31, 2012 8:50 am ]
Post subject:  Re: Baluda Indicators
I like that FM413 icon! :-)
Author:  atharmian [ Thu Nov 01, 2012 6:14 am ]
Post subject:  Suggestions for PC perf/extensions. Re: Baluda Indicators
Paul,

The reason I have asked you many questions is that your work on slope strength makes a lot of sense from a trading edge point of view (as my recent rants about lead-lag indicators would say.)

The fact is that slope and change in slope, CSDiff and CSSDiff can be thought of as 'leading' indicators most of the time since the slope would turn before a price turn, and a change in slope would turn before the slope itself, except in cases of extreme movement (whiplash, singularities.) Even with highly volatile situations, with use of statistical pairs movement probabilities, one can make good use of CSDiff and CSSDiff with some choice of a TF. The options theory and practise for underlying stocks and futures is based on standard deviation, which is actually a more complex form of slope (lognormal) and change in slope (binomial.)

But the problem was my programming naivette. So now that I am comfortable with displays, having found the way to tweak code minimally myself, I have suggestions:

1. Would it be possible for you to separate the calculation engine from the display code in your various indys, so when a user runs multiple Baluda indys, the same engine is the source ? This will save a lot of PC processing, given the crappy nature of Empty4, and would be nice in the age of tablets which are mobile, but are currently limited to under 2GHz clock/ 2GB ROM. Empty4 does have an Android version whose use should go up quickly with the tablet wars.

This way, you would be free to create many multi-purpose indys while updating the calculation engine separately as well.

2. Extension for the Slope Values Indy. I see that this shows pair slope strength in the current TF and, optionally, the lower TF.

How about building a new indy with display of two major columns, each housing 14/28 major pairs, with sub-columns showing pair slope strength differences in sub-columns, e.g. M30, H1, H4, D1 and WK ? The current color scheme, with the option of displaying either arrows/bullets/LED bars v. values, would be great.

To conserve space, I suggest that the pairs not be separated by green v. red, because then one column could become much longer than the other. Rather the indy should simply order them in ascending/descending order, from left column to right column, based on the strengths in the current time frame.

The user can then visually realize what is going on in each TF, and make his/her own trading decisions !

3. Extension for Currency Slope Strength chart, and CSSDiff charts etc. Best would be to tweak the current indys so one can display multiple instances (3-4-5) on same chart with a choice of different TFs. This way the user would have the main tradable information on the same chart without the need to flip between TFs and lose context for other TFs.

One can dedicate a chart for this by minimizing the actual price window (or perhaps a single indy can be placed in the main chart window with strength charts for multiple TFs.)

Of course providing a separate, common engine indy or script that works in the background as single source for all such indys would be a great relief for the poor PC :) Not to mention some options for adjusting fonts and spaces in the indy pop-up menu.

Cheers,
Athar.
Author:  fxozgirl [ Wed Nov 07, 2012 6:58 am ]
Post subject:  Re: Baluda Indicators
Paul, I am using MPBM with Bob's 10.3 Manual strategy and the EA is counting pending trades with open trades and calculating the TP etc from the combined total.

Is it possible to have the EA only count the open trades for calculation of ATP and make the adjustment if any other pending trades are opened?
mpbm_tradecount.gif
Author:  Baluda [ Wed Nov 07, 2012 9:49 am ]
Post subject:  Re: Baluda Indicators
New version MPBM v1.0.3 in post 3.
Changes:
  • Excluded pending orders from order count
Enjoy,

Paul
All times are UTC Page 44 of 81

Powered by phpBB® Forum Software © phpBB Limited