Volume Bar Charts

[bwolinsky]

Quote from tenthousandmen:

With all due respect to my friend blowinsky,

I think it's important to point out to anyone not aware of the fact that anyone who is Russian is extremely bent on multicharts, because Multicharts is developed by a Russian-only group (understandable) I wouldn't of commented on this other than blowinsky was condemning CQG, Zenfire AND Kinetik. I have no experience with Kinetik, however I am aware of firms that use CQG and Zenfire AND the historical data with them.

I have my negative opinions about ninja trader, related to support and strategy analyzer - however overall it is positive and definitely better than any other retail platform I have used (including esignal, sierracharts, multicharts, lightspeed). In fact the charting of N T is superior to others, considering the multitude of volume tick and time charts. There are also many add in charts by users who actually know what they are doing when programming (no offense to the younger NT developers and software managers).

I would recommend anyone into retail trading to try the Ninja download if they have not already - try the charts, the strategy analyzer, and then move on after a few minutes..... it is worth while to become familiar with as many platforms as possible so you can save yourself lots of pain and gain tools in the future. imo.


Bottom line.....cqg - zenfire are rock solid reliable. I dont know why B would say otherwise....sad to mislead others. If you want to use kinetik, fine, I have no reason to believe it's bad.

cheers

The issue is with volume bar charts. Only e-signal and barchart calculate it correctly.

Example 7 contract bar.

2 trades for 6 contracts at 1390 and 1390.25, respectively.

E-signal and barchart are the only ones that recognize that 1 of the contracts in the first 7 contract bar is part of the first bar. Other datavendors will lump the next bars trade without partitioning it the way we'd know, 7 contracts, all 6 of the first trade, 1 of the second trade, then 5 contracts for the remainder of the bar. The price discrepancy creates a tick differential between correctly calculated and incorrectly calculated data that is noticeable in my backtesting.

The next two contracts traded complete the bar, but say they're more than two, the same crap happens again. They fail to partition the trades according to their volume bar chart, and e-signal and barchart are the only ones that do this correctly.

I know because it makes a huge difference.

 

[funnyguy]

Quote from NinjaTrader_Ray:

Right, I said the statements you posted were inaccurate. I am not disputing the post referencing SC support nor am I saying it’s related or not related.

My intent is really simple and clear… to defend and set the record straight when there are inaccurate statements made regarding my company and my partners.

I posted quoted statements. So which one of them are inaccurate and why?

 

[funnyguy]

Quote from tenthousandmen:

just a quick followup for the possible critism I might get.....

Renko charts in NT do NOT work. Nor does backtesting anything but minute and volume bars. Strategy development in NT alone is difficult, but you should be using other programs if you are able to make profitable automation anyways.

There is also a bug in range bars. Don't remember the exact detail end of last year but there was a wrong display.

 

[funnyguy]

Quote from bwolinsky:

The issue is with volume bar charts. Only e-signal and barchart calculate it correctly.

Example 7 contract bar.

2 trades for 6 contracts at 1390 and 1390.25, respectively.

E-signal and barchart are the only ones that recognize that 1 of the contracts in the first 7 contract bar is part of the first bar. Other datavendors will lump the next bars trade without partitioning it the way we'd know, 7 contracts, all 6 of the first trade, 1 of the second trade, then 5 contracts for the remainder of the bar. The price discrepancy creates a tick differential between correctly calculated and incorrectly calculated data that is noticeable in my backtesting.

The next two contracts traded complete the bar, but say they're more than two, the same crap happens again. They fail to partition the trades according to their volume bar chart, and e-signal and barchart are the only ones that do this correctly.

I know because it makes a huge difference.

But data vendors esignal, ...., ... don't deliver 7, 8, 9, .... contract bar data feed. It's the software that constructs the bars depending on your settings. No?

 

[tenthousandmen]

Quote from bwolinsky:

The issue is with volume bar charts. Only e-signal and barchart calculate it correctly.

Example 7 contract bar.

2 trades for 6 contracts at 1390 and 1390.25, respectively.

E-signal and barchart are the only ones that recognize that 1 of the contracts in the first 7 contract bar is part of the first bar. Other datavendors will lump the next bars trade without partitioning it the way we'd know, 7 contracts, all 6 of the first trade, 1 of the second trade, then 5 contracts for the remainder of the bar. The price discrepancy creates a tick differential between correctly calculated and incorrectly calculated data that is noticeable in my backtesting.

The next two contracts traded complete the bar, but say they're more than two, the same crap happens again. They fail to partition the trades according to their volume bar chart, and e-signal and barchart are the only ones that do this correctly.

I know because it makes a huge difference.

I've made money on NT volume charts so to say firstly that they are wrong makes me very doubtful.....

if you upload a screenshot of some contract with volume charts in your platform, I'll do the same.

I really doubt that thread on the other side has ANY substance.

 

[Stan_MultiCharts]

Quote from tenthousandmen:

With all due respect to my friend blowinsky,

I think it's important to point out to anyone not aware of the fact that anyone who is Russian is extremely bent on multicharts, because Multicharts is developed by a Russian-only group (understandable) I

I've seen this come up before, you mentioned the same thing here - http://www.elitetrader.com/vb/showthread.php?s=&postid=3501574&highlight=russian#post3501574

Just thought I'd comment, we have about 20 Russian users out of thousands that have bought MC over the years. And I've never seen one comment on ET or any other non-Russian resource. While I wish that all Russians loved and supported MultiCharts the way you describe, unfortunately I don't think that's the case

 

[tenthousandmen]

Quote from sbokov:

I've seen this come up before, you mentioned the same thing here - http://www.elitetrader.com/vb/showthread.php?s=&postid=3501574&highlight=russian#post3501574

Just thought I'd comment, we have about 20 Russian users out of thousands that have bought MC over the years. And I've never seen one comment on ET or any other non-Russian resource. While I wish that all Russians loved and supported MultiCharts the way you describe, unfortunately I don't think that's the case

I know of (american) russians who seem to be very fond of mc.

 

[RenkoTrades]

I use Ninjatrader7 charts and Zenfire feed with no problems running volume charts. I use Renko charts for my HT market track and use some other chart styles like volume charts for very low time frame work. I dont have volume chart issues with Ninjatrader7 with two different feeds from testing.

 

[JayF_eSignal]

Quote from funnyguy:

But data vendors esignal, ...., ... don't deliver 7, 8, 9, .... contract bar data feed. It's the software that constructs the bars depending on your settings. No?

The latest version of eSignal 11.4 takes advantage of some new server technology we put into place to calculate the tick-based bars server-side (like volume bar, tick bar, range bar, etc.). This dramatically speeds up the delivery of this bar type, saves a tremendous amount of local memory (no need to store all that tick data locally) as well as improving consistency from workstation to workstation.

 

[piranhaxp]

Quote from bwolinsky:

The issue is with volume bar charts. Only e-signal and barchart calculate it correctly.

Example 7 contract bar.

2 trades for 6 contracts at 1390 and 1390.25, respectively.

E-signal and barchart are the only ones that recognize that 1 of the contracts in the first 7 contract bar is part of the first bar. Other datavendors will lump the next bars trade without partitioning it the way we'd know, 7 contracts, all 6 of the first trade, 1 of the second trade, then 5 contracts for the remainder of the bar. The price discrepancy creates a tick differential between correctly calculated and incorrectly calculated data that is noticeable in my backtesting.

The next two contracts traded complete the bar, but say they're more than two, the same crap happens again. They fail to partition the trades according to their volume bar chart, and e-signal and barchart are the only ones that do this correctly.

I know because it makes a huge difference.

Multicharts is going the same way like you explained. But it's not my point. It's not the question who is going the right way ! The question is which way you prefer !

Separated volume is hard to be analyzed correctly. In 73.81% it gives you unrealistic OPEN & CLOSE, which could lead into wrong HIGH's & LOW's ... I don't want to say it's wrong. Just saying "unrealistic".

The realistic and best practicable way is to cut volume which is is an overhang for each bar. Because you can't trade an open of a new bar from separated volume if the next possible trade is higher or lower compared to the open. Worst case "open" is high or low of the bar. So in my opinion.

You can discuss it the next ten years. There were so long discussions running for years and there's still no answer ... It's just what you prefer.

SO PLEASE DON@T CALL ANY SOFTWARE TO BE WRONG OR RIGHT. It's bullsh..... And who is complaining about missing ticks in volume charts is on the totally wrong way. Missing ticks means in 99% of the cases that different ticks were combined into one tick, but the volume traded is correct and the same ... Just saying.

Have a nice weekend.