TDesk User Indicators Playground

[ianp]

Baluda.superslopev2.2

I use MPTM and move stop to b/e at +5

[littlereddot]

REQ:

Hi all.
I try find any filter for better entry timing.
I have to much entry at an inappropriate time - see attached.

I think that Hurst (e.g.) can be filter bad timing entry.

Can some coder wizard on SHF modify attached indi for work MTF with TDesk and Desky please?

Many thanks in advance.
Lubos

Hi Lubos

I've been studying the HGI with Hurst discussion and it so happened I did a quick and dirty hack today of the indicator today for my own testing. The modified indicator appears to work as it should but since I'm not a really good coder there might be bugs that I've overlooked. Happy for you to see if it helps you. Let me know if you notice any bugs.

Cheers
littlereddot

[tgm0]

I had some demoes running with Experimental version 1x where I had set different Slope Inputs on 3 different TimeFrames. I wanted to try and see If I could do the same using TDesk and initially I was loading 3 iterations of tomele’s version of Baluda SuperSlope TD and configuring each one of them to run only 1 timeframe with the settings I wanted.

I got tired of it and decided to modify the indicator in order to have the possibility to independently set Slope Inputs on the different TimeFrames.
From what I have seen so far, this will give more flexibility at the time of fine tuning your entry and exit signals.
I am using this modified version since a couple of weeks and so far so good, but please take a look under the hood to see if I did it right; I’m no real coder like you guys, just an amateur enjoying tying to be in my spare time…

Here is the code.

[FxFoil]

I had some demoes running with Experimental version 1x where I had set different Slope Inputs on 3 different TimeFrames. I wanted to try and see If I could do the same using TDesk and initially I was loading 3 iterations of tomele’s version of Baluda SuperSlope TD and configuring each one of them to run only 1 timeframe with the settings I wanted.

I got tired of it and decided to modify the indicator in order to have the possibility to independently set Slope Inputs on the different TimeFrames.
From what I have seen so far, this will give more flexibility at the time of fine tuning your entry and exit signals.
I am using this modified version since a couple of weeks and so far so good, but please take a look under the hood to see if I did it right; I’m no real coder like you guys, just an amateur enjoying tying to be in my spare time…

Here is the code.

Many thanks. I have been hoping someone would code this. Would you consider adding the code found in SPB:
extern double LtfSsSlopeBuyAbove=1;
extern double LtfSsSlopeSellBelow=-1;

Thanks again

[tgm0]

Many thanks. I have been hoping someone would code this.
Would you consider adding the code found in SPB:
extern double LtfSsSlopeBuyAbove=1;
extern double LtfSsSlopeSellBelow=-1;

Thanks again

Hello FxFoil.

I forgot I added that logic as well when I changed the code.
If I got it right it should be working just fine, but as I said before , should some real coder take a look and double chek my doing it will not hurt.

As in your example, if you set TF1_levelCrossValue=1 it will send a long signal for slope values bigger then 1 and a sell signal for values lower then -1 and so on for the next 2 TF if you decide to use them at all.

TDesk signals gets triggered by these lines of code:

Code: Select all

//TDesk code
               if(SendTDeskSignals)
               {
                  if((Slope1[i] >  TF1_differenceThreshold*0.5) && (Slope1[i] > TF1_levelCrossValue)) s1=LONG;  else
                  if((Slope1[i] < -TF1_differenceThreshold*0.5) && (Slope1[i] < -TF1_levelCrossValue)) s1=SHORT; else s1=FLAT;
                  if((Slope_2   >  TF2_differenceThreshold*0.5) && (Slope_2 > TF2_levelCrossValue)) s2=LONG;  else
                  if((Slope_2   < -TF2_differenceThreshold*0.5) && (Slope_2 < -TF2_levelCrossValue)) s2=SHORT; else s2=FLAT;
                  if((Slope_3   >  TF3_differenceThreshold*0.5) && (Slope_3 > TF3_levelCrossValue)) s3=LONG;  else
                  if((Slope_3   < -TF3_differenceThreshold*0.5) && (Slope_3 < -TF3_levelCrossValue)) s3=SHORT; else s3=FLAT;
                  if(s1!=l1 && NoOfTimeFrames>0) {PublishTDeskSignal("SS-1",(ENUM_TIMEFRAMES)userTimeFrame1,Symbol(),s1); l1=s1;}
                  if(s2!=l2 && NoOfTimeFrames>1) {PublishTDeskSignal("SS-2",(ENUM_TIMEFRAMES)userTimeFrame2,Symbol(),s2); l2=s2;}
                  if(s3!=l3 && NoOfTimeFrames>2) {PublishTDeskSignal("SS-3",(ENUM_TIMEFRAMES)userTimeFrame3,Symbol(),s3); l3=s3;}
               }

just customize the respective TFx_ levelCrossValue in order to do the trick.

[lbs48]

Hi Lubos

I've been studying the HGI with Hurst discussion and it so happened I did a quick and dirty hack today of the indicator today for my own testing. The modified indicator appears to work as it should but since I'm not a really good coder there might be bugs that I've overlooked. Happy for you to see if it helps you. Let me know if you notice any bugs.

Cheers
littlereddot

Hi LRD.

Many thanks for your Hurst indi modification and sharing.
I will try it and share my experience.
I think, that current TF working correct. But MTF does not look very good.

Cheers
Lubos

[rapple]

Dear all

I noted on the FXTestify website that Slopey Candle Bob (SCB, SCaB) is going very well

Based on these results I set up SCB to work with TDesk and Desky where SCB just sends the the signals to TDesk and Desky looks after the trade management. I also included H4 Peaky...

As you can see the results look promising.

Based on these preliminary results would anyone be willing to create a TDesk compatible 'Candle Direction Indicator' similar to that used by SCB where you can set the number of candles for a BUY/SELL and also the timeframe.

Kind regards Richard

ps...TDesk/Desky are just AWESOME!!!!!!!!!

[SteveHopwood]

Dear all

I noted on the FXTestify website that Slopey Candle Bob (SCB, SCaB) is going very well

Based on these results I set up SCB to work with TDesk and Desky where SCB just sends the the signals to TDesk and Desky looks after the trade management. I also included H4 Peaky...

As you can see the results look promising.

Based on these preliminary results would anyone be willing to create a TDesk compatible 'Candle Direction Indicator' similar to that used by SCB where you can set the number of candles for a BUY/SELL and also the timeframe.

Kind regards Richard

ps...TDesk/Desky are just AWESOME!!!!!!!!!

Isn't this what I am already doing? http://www.stevehopwoodforex.com/phpBB3 ... 84#p164184

[rapple]

Isn't this what I am already doing?

Yep...Sorry about that Steve. I will now concentrate on XY42

Cheers Richard

[lbs48]

REQ.:

Hi dear traders.
Can some one of you coders, modify QQE indicator to be comaptible with TDesk if it seems useful to you?
I presume that can be useful for trigger and/or for filtering.

Idea is:
BUY when blue line cross red line up above level 50
SELL when blue line cross red line down below level 50

When blue line cross red (or blue ?) line up below level 50, is FLAT and vice versa.
Level 50 filter can by set true/false.

See attached charts.

Thanks a lot in advance.
Nice weekend to all.
lbs