Better use higher timeframes such as minute charts.
Announcement
Collapse
No announcement yet.
Partner 728x90
Collapse
NinjaTrader
Point and Figure doesn't shows the true highs and lows
Collapse
X
-
Hi Jonson,
Thanks for checking in, I was just getting ready to update this with information I was working on with Brett who was leading this thread at that time.
We know that should you use anything higher than a 1-tick resolution, you may lose accuracy in terms of the the PnF charts.
As you're using 1-second and 1-minute base time frames, there may be ticks lost in the bar generation. Can you please provide us with another sample you're checking in the other programs by using 1-tick as the base time frame?MatthewNinjaTrader Product Management
Comment
-
hi
1-tick resolution works perfectly and precisely with other platforms, no differences
but if use a time intervals sometimes visible differences, but these differences were also observed between other platforms, not just your
I do not want to provide samples of pictures I have no time, I can only say that those who use the paf look at building with a tick period, as even in this case, you will see the timely movement of the column
all success
PS: in the documentation, you can add nuances about it that people did not experience difficulties
THANKS
Comment
-
Originally posted by Harry View PostI think this answer might be an understatement of the problem.
The P&F charts have two settings available. They can be either calculated from the high/low range (traditional method) or from the close. The NinjaTrader P&F chart from the close looks good, where as the NinjaTrader P&F chart calculated from the highs and lows does not look correct...
I have not looked into this in a very detailed way but would appreciate, if you had it checked by your development team.
I trade exclusively, PnF and Renko
Ninja PnF where "Price" is "Close" works just fine.
If "Price is HighsAndLows" it is butchered beyond belief, as the algorithm treats the bar individually not respecting the trend of the previous bar.
The bar gets chopped up into xxx and ooo s
It's not that it doesn't "see" the High or Lows in the bar, it sees it all too well; however it disregards the previous bar's closing as the determining factor on whether a new x or o should be made.
How or why and if it takes notice of the following bar; I've no idea.
Hope this helps all.
By the way, I do use PnF in Ninja.
Comment
Latest Posts
Collapse
Topics | Statistics | Last Post | ||
---|---|---|---|---|
Net Change
by Segwin
Started by Segwin, 05-07-2018, 02:15 PM
|
14 responses
1,788 views
0 likes
|
Last Post
by aligator
Today, 11:47 AM
|
||
Started by Jimmyk, 01-26-2018, 05:19 AM
|
6 responses
837 views
0 likes
|
Last Post
by emuns
Today, 11:27 AM
|
||
Started by jxs_xrj, 01-12-2020, 09:49 AM
|
6 responses
3,293 views
1 like
|
Last Post
by jgualdronc
Today, 10:56 AM
|
||
Started by Touch-Ups, Today, 10:36 AM
|
0 responses
13 views
0 likes
|
Last Post
by Touch-Ups
Today, 10:36 AM
|
||
Started by geddyisodin, 04-25-2024, 05:20 AM
|
11 responses
63 views
0 likes
|
Last Post Today, 10:08 AM |
Comment