TDesk Universal Drones

[chartartist]

Hi Thomas, with all humility I request for the next update to add the symbol suffix feature for TDesk Universal Buffers Drone.ex4

Thank you for your kindness

Cheers
ChartArtist

[taipan]

Hi Thomas, with all humility I request for the next update to add the symbol suffix feature for TDesk Universal Buffers Drone.ex4

Thank you for your kindness

Cheers
ChartArtist

I second his request too. In fact I had made this request sometimes ago.

taipan

[tomele]

Hi @all.

Version 2.3 of UBD and USD are in the respective posts. The prefix/suffix input got added and the lifespan got prolonged.

Cheers
Thomas

[chartartist]

Thank you Thomas ...

[m0nk111]

Hi @all.

Attached is PeakyBuffers, an indicator based on Steve's PeakHiLo indicator and optimized for use with UBD. The main settings are:

NumberOfBars: The indi looks for peak high / peak low within this number of bars window.

TradeableRangeDivisor: The high/low range gets divided into this number of sections. You can decide that signals are only valid when the price is in the topmost (short) and the lowermost (long) section.

FreezeTradeableRange: As the opposite peaks scroll out of the window, the sections usually narrow over time. You can inhibit that and freeze the sections to the size they had when the signal started.

The attached UBD setfile doesn't use the sections. The signal is always long or short and identical to the original PeakHiLo indicator with default settings. If you want to have directional signals only when the price is in the two outer sections, you just have to use other buffers:

Buffers 0/1 (or 2/3) are always long/short
Buffers 4/5 (or 6/7) are only long/short in the outer sections


2019-06-16
Attention: The default for TradeableRangeDivisor has changed from 6 to 2.


Cheers
Thomas

.

hi,

i added a second barscount
it uses a tolarable pip distance, so if the possible new peak is within TolerableDistanceInPips, change direction


in a nutshell this is what i added:

Code: Select all

//Use a tolarable pip distance, so if the possible new peak is within TolerableDistanceInPips, change direction
extern bool    UseTolerableDistance=True;
extern int     TolerableDistanceNumberOfBars=841;
extern int     TolerableDistanceInPips=50;

   if (UseTolerableDistance)
   {
      int currentPeakHighBar2=iHighest(Symbol(),Period(),MODE_CLOSE,TolerableDistanceNumberOfBars,shift);
      int currentPeakLowBar2 =iLowest (Symbol(),Period(),MODE_CLOSE,TolerableDistanceNumberOfBars,shift);
      double highest2=iClose(Symbol(),Period(),currentPeakHighBar2);
      double lowest2 =iClose(Symbol(),Period(),currentPeakLowBar2);
      if ((highest - highest2) < (TolerableDistanceInPips/factor)) { highest = highest2; currentPeakHighBar = currentPeakHighBar2; }
      if ((lowest2 - lowest) < (TolerableDistanceInPips/factor)) { lowest = lowest2; currentPeakLowBar = currentPeakLowBar2; }
   }

edit:
im not sure yet if this is better..
//extern int TolerableDistanceNumberOfBars=841;
int TolerableDistanceNumberOfBars=NumberOfBars/2;

result:

[lbs48]

Hi to all,
many thanks for sharing your hard works.

Sorry for my noob question, but is possible, using indicator like this (i don´t have code) with UBD?
I think, that is impossible, because need set more parameters than 3.
Do I understand it correctly?

Many thanks in advance for answer.
Lubos

[tomele]

Hi Lubos.

Who said you can use only 3 parameters? Look at the example in "TDesk UBD Custom Parameters.mq4". You can use as many parameters as you want.

Cheers
Thomas

[lbs48]

Many thanks for reply Thomas.
My mistake, I see everywhere only 3 x parametres, that's why I thought it was the maximum.
So, parametres like on screen below is correct?
L

[tomele]

[lbs48]

Hi to all,
Can anybody tell me please, if I'm doing the right?

Many thanks in advance.
Lubos