How to fix the “Line Shake Effect”?

[rafaelcoisa]

Hey guys,
I'm wondering if anyone knows how to fix the “Line Shake Effect”.

“Line Shake Effect”:

(drawing tool used: 'Trend Channel')


Example with the 'Extended Line' tool (without “Line Shake Effect”):

(two ExtendedLines objects were used in the second gif)


Both tools combined:

This “Line Shake Effect” is really annoying.
If anyone knows how to get rid of this that would be really cool.

[NinjaTrader_DrewO]

Hello,

Thanks for your post.


So far I have not been able to replicate this behavior on my end when testing with the Trend Channel drawing tool. So that I may investigate this matter further, I would ask that you please contact me by email at PlatformSupport [AT] NinjaTrader [DOT] com. In your message please include a link to this forum thread and a copy of today's trace files. You will find these diagnostic files in the Documents > NinjaTrader 8 > Trace folder. I will need to review a copy of the files which are named 'trace.20240121.XXXXX.txt'. There will likely be multiple files for each day.

[rafaelcoisa]

Before sending the email.

Open a 5-minute ES chart on 2018-09-01 (trading hours: CME US Index Futures RTH).
And draw the lines like I did in the video above.
I think you will see the same "Line Shake Effect".

[rafaelcoisa]

Hey guys, QuantKey_Bruce, jeronymite

Any thoughts?
I think there is a problem with the GetExtendedPoint() method.
The same issue can be shown with the AndrewsPitchfork tool.

[QuantKey_Bruce]

This seems likely that the tool would have to be redesigned such that it did not put the right anchor to the right of the last data point; or, NT could be enhanced such that as data points are added it would not shift, but that seems less achievable in that I'm not certain how they would fix it since the anchors are by DateTime and the DateTimes of future areas on the screen are speculative until the bars arrive. Those speculations do change.

[rafaelcoisa]

Hey QuantKey_Bruce,
Thanks for a answer.
I managed to reduce the shaking considerably by forcing anchors at the end of the line extension in some very ugly code, but still no real solution.
What do you mean by "it did not put the right anchor to the right of the last data point"?

[QuantKey_Bruce]

If the user manually draws a line, it has two anchor points (other tools are similar, with various numbers of anchor points). If the user does not put either of the anchors past the end of the data series, there is not a problem. However, if the user puts one of the anchors past the last bar (in the empty space at the right of the chart) the way the platform does this is by estimating the DateTime of that location. However, that's only an estimate. As new data arrives, there are new estimates made. It is the fact that there is no specific datetime that can be absolutely assigned to an X coordinate past the last bar that is the root issue here.

[rafaelcoisa]

QuantKey_Bruce

I think you are right.
The first time I thought about this problem, I thought to myself something similar.
It's like the "extension point" cannot be calculated in OnRender.

[QuantKey_Bruce]

It can be estimated. But, as new bars arrive, and then calculates the X pixel coordinate of the DateTime it reversed out from the X pixel coordinate earlier, that calculated X pixel coordinate will vary as more and more bars arrive. This will cause the line drawn that ends in this point to fluctuate.

[rafaelcoisa]

QuantKey_Bruce
And what do you think about the ExtendedLines tool? She doesn't shake.

[QuantKey_Bruce]

I've never seen that, that I recall. I'm just describing the principles involved from my past experience with similar situations.

[rafaelcoisa]

Hey NinjaTrader_DrewO,

Have you tried to reproduce the problem by following the steps in my post number 3? (https://forum.ninjatrader.com/forum/...79#post1287479)

What was the result? Do you think there is a work around for this problem?

[NinjaTrader_DrewO]

Hi rafaelcoisa,

Thanks for replying with that extra information.

I was able to replicate this on my end using your steps. It's unclear in this scenario what might be expected currently, but I'll be happy to create a report on this item regardless for further investigation by our Development team. Appreciate the thorough follow-up!

[rafaelcoisa]

NinjaTrader_DrewO

Thanks.
Hopefully there will be a work around for this problem.