TD Sequential Ultimate

[Enivid]

Hello! I like the indicator very much. There is only one issue: It runs so slow in my mt5 terminal. It needs almost 10 minutes till the numbers are shown on the chart. Is there any way to make it faster?

It is slower than in MT4, but it shouldn't take 10 minutes to calculate the values for one chart. Unless that's M1 chart with several years worth of bars...
You could try limiting its total range by adding a line like this just above the line #169:

limit = MathMin(limit, 1000); // Change 1000 to any number of bars you believe is enough for you.

BTW, the numbers always disappear as soon as the session begins. So I cannot use it to follow a live session ...

Are there any errors in the Experts tab of the Terminal panel when this happens?

 

[Ichimoku]

It is slower than in MT4, but it shouldn't take 10 minutes to calculate the values for one chart. Unless that's M1 chart with several years worth of bars...
You could try limiting its total range by adding a line like this just above the line #169:

limit = MathMin(limit, 1000); // Change 1000 to any number of bars you believe is enough for you.

This has solved my problem practically. Now it's much faster. Thank you! Maybe this should be included in the inputs in the future version, just my thought.
I have been using M15 chart actually. But maybe my computer is too old.

Are there any errors in the Experts tab of the Terminal panel when this happens?

No error output. It seems to be caused by the limitation of my pc memory space. If I use fewer indicators or reopen the chart, it works again sometimes.

 

[Enivid]

This has solved my problem practically. Now it's much faster. Thank you! Maybe this should be included in the inputs in the future version, just my thought.
I have been using M15 chart actually. But maybe my computer is too old.

No error output. It seems to be caused by the limitation of my pc memory space. If I use fewer indicators or reopen the chart, it works again sometimes.

OK. I will probably add this as an input parameter in the next version of the indicator.

 

[kris82wt]

No, it doesn't add any new features. It just fixes the bugs that prevented it from working as described.

@Enivid generally script works great, but there is still room to improve. Since I don't know mql language would you be so kind and willing to make some changes? I have lately read few books of Demark, so I can attach examples and books extracts to explain/confirm DeMark methodologies...

 

[Enivid]

@kris82wt You can post your suggestions here and I will consider implementing them, but I cannot promise anything.

 

[kris82wt]

@Enivid, ok let's start from most important stuff imho:
1) TDST support/resistance should be considered as Average True Range for Setup. What currently is in the script is as below
Which is correct, until bar before "1" didn't close higher than highest bar from Setup. So, TDST should be max/min value from Setup or close of previous bar prior "1" if is higher/lower

Basically difference seems to be minor unless we have gap. Also in "The new science of technical analysis" DeMark suggesting that TDST is holded until price bar didn't close above/below TDST and next bar wasn't trading 1 tick above/below. This can make difference. Other examples from his books:

 

[kris82wt]

Next point I mentioned in posts before. Buy/Sell Setup does not end with "9". For sake of clarity in charts - yes, but if your trading plan is to playing Setups (DeMark suggests taking into account mainly "Perfected" ones because of limited risk) you shouldn't blindly go short long after '9'. In one of his books his mentioning that very clearly "If Setup recorded a count of 11, only 1-9 counts remain on the chart"





It would be nice to have kind of mark (different arrow, any symbol) when last bar which meets requirement of Setup.

I will continue in next post next days to keep clear track and separate things from 1 long post where is everything....

 

[kris82wt]

I'm not quite sure if I was clear in latest post, because I was tired... Anyway, few examples

The idea is to mark, where last bar which still meets requirement of Setup phase is. It's important for trading only setups and for judging which setup (if there is more than one after another is more valid). Here DeMark marks it via rectangles (it's most common way in Bloomberg platform or Aspen), but I think it's enough to mark it with kind of symbol like I did below with red cross.



And again, let's leave Setup numbering 1-9 as completed Setup and for clarity instead of this way

 

[kris82wt]

Next, regarding 'Perfected' Setup. I'm not sure how you have in your code, but... arrow should appears not only at 8 or 9, but also at any subsequent bar which is still meeting requirement of Setup. So if Setup consist of 15 bars and 15th bar low/high is greater than low/high bars 6&7 then arrow should be over bar 15...

In below example Setup is unperfected till bar 9, but following bar which close is still higher than 4 bars earlier makes Setup perfected.

 

[kris82wt]

And the last request to the script, which I believe should be easy to implement because most of coding is already done could be add a TD Combo. Basically it's the same, but counting of Countdown starts from first bar of Setup, when setup is completed (I can provide all requirements). It occurs rare but is more powerfull. This could be switched on/off from main indicator menu. IMHO doesn't make sense to create another script when 90% coding is the same.

I can support in backtesting, providing any examples, building trading plan, because here DeMark doesn't give any strict rules, maybe besides how to take position in multitimeframes.

 

[kris82wt]

@Enivid BTW. Arrows acc to post above, works as supposed to...



but TDST suuport/resistance lines - no

 

[kris82wt]

Found some bugs in indicator AUDCHF, H4:

- without marking where price flip occured (purple "X") during Setup phase arrow indicates perfected buy setup on wrong bar
- in this particular case , countdown is missing (have no idea why) - I marked with blue numbers
- in circle I marked some bug of not deleting setup count

 

[Enivid]

Found some bugs in indicator AUDCHF, H4:

Which broker is that? I would like to test it on the same feed, but all the brokers I check AUD/CHF @ H4 with offer a significantly differing picture here.

 

[kris82wt]

AxiTrader

 

[Enivid]

AxiTrader

I've just attached the indicator to the AUD/CHF H4 on AxiTrader (US03-Demo server) and although the bars look the same as on your chart, the output of TDSU looks different. I don't see any stray "3" from a sell setup count:

Are you sure you are using the latest version (1.01)? And if so, did you add any modifications to it?

 

[kris82wt]

Hi, yes I'm using your original script v 1.01, unfortunately I don't know mql what I regret. What are assumptions for stop countdown counting in your script? Looks like price flip is one of them.
I was suprised with your screenshot from AxiTrader but I repeat exercise for other brokers. Here you go:

• JAFX

• AxiTrader Live

• CMC Markets

Looks like AxiTrader Live generates some issue, but take a look at Countdowns - there are bunch of these which ends somewhere in the middle and are not cleared out. You can rewind AUDCHF chart and you'll find quite a lot such Countdowns

 

[Enivid]

@kris82wt Yeah, I've noticed lots of such stray sell counts in other places. Anyway, I've tried to fix the issue - both with stray sell counts and with missing Countdowns in some cases. Please try the attached version and let me know if it fixes the issues on AxiTrader Live feed. Thanks!

 

[kris82wt]

This version fixed issue with "3" on Sell Setup, but counting Countdowns still remain. Best chart to test it seems to be S&P500 H4, here below I attached from JAFX broker

 

[Enivid]

@kris82wt What's the issue with the Countdowns here? As far as I can see, they are printed correctly and then get interrupted by the opposite Count.

 

[kris82wt]

There are not necessary if not completed. The cleaner, the better.
BTW. Could you correct TDST support/resistance lines if not done already (as in above posts)? It will be also better just to keep horizontal lines, the ones at angle do not act as support/resistance.