Palinuro, I have both NT and TN datafeeds and the volumes match up pretty darn closely all morning. The IB spike thingy I've seen before and never got a good explanation for it except perhaps that it is related to their 100 msec/data package protocol. So maybe the NT artifact is 'local' as opposed to systemic. lj
lj, I suppose it must be local. But it's only happening on the ES, and only since switching to the new contract, so I really don't know what to investigate. Seems mostly to affect relatively high activity bars. -i.e, 1:05 had a good 30-40% more volume 'live' than after I redownloaded. Perhaps it'll clear up on Monday - I'm just going to shut down for today. Thanks for the info. - palinuro
Palinuro, you wrote some terrific stuff for Ninja -- thanks very much. A related question for you. Why do the Ninja Automated Pace Lines differ from the ones in Trade Navigator? Aren't the TradeNavigator lines the authoritative standard that we should try to match in our coding? Is the difference because Spyder's code does not avoid half-day trading days/holidays? Spyder, do you have some insight as well? The pace lines for Trade Navigator as of 1pm EST: 0.1 = 3.4K; 0.3 = 10.1K; 0.5 = 16.7K; 0.7 = 23.2K; 0.9 = 30.0K; AND 1.0 = 33.2K. The ones for Ninja are significantly higher.
Pali's a genius. Just hit "/" in the numpad when you have a channel selected, and numbers 1, 2 and 3 appear at the appropriate points, auto-adjusted to the thickness and colour of the channel lines. Use Customize Toolbars (in the View menu) to remove all the unnecessary buttons then click-and-hold the horizontal line at the top of the drawing toolbar to drag it wherever you like.
Bar Numbering EasyLanguage code <img src=http://elitetrader.com/vb/attachment.php?s=&postid=2219397> Code: // indicator name: Bar_number // author: TUMS // date: July 25, 2008 // description: prints the bar number on the screen, // with the option to bold, frame or reverse specific intervals. Input: start_time(0935), end_time(1615), color(black), bold_bar(6), boldcolor(red), frame(false), reverse(true); var: bar_num(0), id_txt(-1); if Time > start_time and Time <= end_time then begin if bar_num = 0 then bar_num = 1; end else bar_num = 0; if bar_num > 0 then begin id_txt = text_new_self( d, time[1], 0, text(bar_num:0:0) ); text_setcolor(id_txt,color); bar_num = bar_num + 1; end; if bold_bar = 0 then value1 = 9999 else value1 = bold_bar; if mod(bar_num - 1, value1) = 0 then begin text_setattribute(id_txt, 1, true); if reverse then begin text_setcolor(id_txt, white); text_setbgcolor(id_txt, boldcolor); end else begin text_setcolor(id_txt, boldcolor); if frame then text_setborder(id_txt, true); end; end; .
Since I don't know how TN caculates the levels, or on what data, I really can't answer your questions. The low-volume filter in AutoPace makes very little difference, and in any case you can easily comment it out and find out for yourself. I'm not aware of TN's lines having any magical or authoritative properties. For me, the important thing is to find useful levels, and understand what they mean. HTH - palinuro
Hi, Anyone know how to get Pepe's 'JHInfo" tool to hold the offset value for the chart time? I have to reset it (+3 for PST to EST)every time I reboot the program. TIA lj
Since you're not likely to change time zones very often, why not just edit the default setting for the variable? - palinuro