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

Baluda Indicators
https://www.stevehopwoodforex.com/phpBB3/viewtopic.php?t=629		 Page 54 of 81
Author:  arskay [ Tue Mar 05, 2013 5:30 pm ]
Post subject:  Re: Baluda Indicators
Hi Spotdespot,thanks for help I trying to use Currency Slope Strength and CSSDiff,which are on the first page.
Author:  spotdespot [ Tue Mar 05, 2013 5:34 pm ]
Post subject:  Re: Baluda Indicators
arskay wrote:Hi Spotdespot,thanks for help I trying to use Currency Slope Strength and CSSDiff,which are on the first page.
That's what it will be then - the maxBars - change it to something other than 0 - I use 400 and only increase it when I want to check something specific in the past.
Author:  jako [ Thu Mar 07, 2013 8:00 am ]
Post subject:  Re: Baluda Indicators
calvin1006 wrote:Dear all,

I really like the CSSDiff indicator, but anyhow, can someone kindly add the alert option into this indicator?

Alert message, box and email when CSSDiff cross above 0.8 or below -0.8.

i am very appreciate if someone can do me a favour!!!!!

Regards,
Calvin
Me too please add alerts.
Author:  jako [ Sun Mar 10, 2013 8:56 am ]
Post subject:  Re: Baluda Indicators
http://www.stevehopwoodforex.com/phpBB3 ... f=45&t=639
Author:  Frenetic [ Mon Mar 18, 2013 5:54 pm ]
Post subject:  Re: Baluda Indicators
Baluda wrote:New version DWMPivots v1.0.9 in post 2.
Changes:
  • Added order label with background for 10.2a
  • Some more color changes and arrow directions by NaningBob
  • Introduced hour shift for pivot calculation, defaults to GMT+2
  • Added 'shiftTextFibs' user setting
  • Added user setting 'show10.x' to display NB 10.x features, deafults to true
The 'hoursFromGMT', default 2, sets the day change for calculation of the daily pivot and daily open to GMT+2. There is no need to adjust this for your b*roker, DWMPivots will make the change for you.

Enjoy,

Paul
Hi Paul,

First off, excellent indicator.

I've noticed with this week's EUR gap, that the week pivot logic polls the nearest Sunday instead of the past Sunday for the previous week's high/low/close for the calculation of the current Week Pivot.

Chart with Sunday bar showing lower current Week Pivot because it included the most recent Sunday's prices (for low and close):
2013-02-19%20week%20pivot%20_%20sunday%20bars%20_%20near%20sunday%20low+close%20used%20for%20calcs.gif
Chart with no Sunday bars showing 'correct' Week Pivot:
2013-02-19%20week%20pivot%20_%20no%20sunday%20bars.gif
The immediate thing that comes to mind is to replace:

Code: Select all

lastLow = iLow ( NULL, PERIOD_W1, pivotBar + 1 );
lastHigh = iHigh ( NULL, PERIOD_W1, pivotBar + 1 );
lastClose = iClose ( NULL, PERIOD_W1, pivotBar + 1 );
with a brute count-back of current day to the first Friday up to Sunday (for Sunday bars present) and Friday up to Monday (for Sunday bars absent), polling their iLowest & iHighest (MathMin & MathMax along the way) & Friday iClose.

There's got to be a more elegant way though. Would be interested in anyone's idea(s).
Author:  Frenetic [ Thu Mar 21, 2013 5:25 pm ]
Post subject:  Re: Baluda Indicators
Alright, to prevent Empty4 recognising a week as
Mon,Tue,Wed,Thu,Fri,Sun instead of Sun,Mon,Tue,Wed,Thu,Fri

Replace this:

Code: Select all

// Weekly
lastLow = iLow ( NULL, PERIOD_W1, pivotBar + 1 );
lastHigh = iHigh ( NULL, PERIOD_W1, pivotBar + 1 );
lastClose = iClose ( NULL, PERIOD_W1, pivotBar + 1 );
With this:

Code: Select all

// Weekly
int day = TimeDayOfWeek(iTime(Symbol(),PERIOD_D1,0)); //current day
if ( sundayCandlesDetected ){
   lastHigh = iHigh ( Symbol(), PERIOD_D1, iHighest ( Symbol(), PERIOD_D1, MODE_HIGH, 6, day+1+pivotBar*6 ) );
   lastLow = iLow ( Symbol(), PERIOD_D1, iLowest ( Symbol(), PERIOD_D1, MODE_LOW, 6, day+1+pivotBar*6 ) );
   lastClose = iClose ( Symbol(), PERIOD_D1, day+1+pivotBar*6 );
}
else {
   lastHigh = iHigh ( Symbol(), PERIOD_D1, iHighest ( Symbol(), PERIOD_D1, MODE_HIGH, 5, day+pivotBar*5 ) );
   lastLow = iLow ( Symbol(), PERIOD_D1, iLowest ( Symbol(), PERIOD_D1, MODE_LOW, 5, day+pivotBar*5 ) );
   lastClose = iClose ( Symbol(), PERIOD_D1, day+pivotBar*5 );
}
Broker with no sunday bars showing Weekly Pivot correctly as expected:
2013-02-19 week pivot _ 3 _ no sunday bars.gif
Broker with sunday bars showing Weekly Pivot correctly now:
2013-02-19 week pivot _ 4 _ sunday bars _ corrected.gif
Instead of pre-edit:
2013-02-19 week pivot _ 5 _ sunday bars _ uncorrected.gif
Author:  KevinT [ Sat Mar 23, 2013 4:26 pm ]
Post subject:  Re: Baluda Indicators
Awesome frenetic, well spotted as well as solved, kudos to you and all the "brain trust" guys here...
Author:  Frenetic [ Sun Mar 24, 2013 3:53 pm ]
Post subject:  Re: Baluda Indicators
Thanks, wouldn't count myself in the same league as Baluda and the others but thought I'd contribute where I can.

That said, this might be useful.
I initially used High[iHighest(Symbol(),timeframe,MODE_HIGH,barcount,startbar)] to get the highest of a range of bars, as indicated by http://docs.mql4.com/series/iHighest, but I found that the timeframe parameter defaults to 0 (the current chart's timeframe) regardless of the setting.

Had to work around with this instead:
iHigh(Symbol(),timeframe,iHighest(Symbol(),timeframe,MODE_HIGH,barcount,startbar));

With hindsight (as with everything else), it's apparent why, but at the juncture it was a little puzzling.
Author:  KevinT [ Mon Mar 25, 2013 1:21 am ]
Post subject:  Re: Baluda Indicators
KevinT wrote:Awesome frenetic, well spotted as well as solved, kudos to you and all the "brain trust" guys here...
These compile warnings are OK right?
Author:  Frenetic [ Mon Mar 25, 2013 4:13 am ]
Post subject:  Re: Baluda Indicators
Yes, they are non-accessed functions in the original.
All times are UTC Page 54 of 81

Powered by phpBB® Forum Software © phpBB Limited