so if we use the millisecond version, there's no improvement in any way when compared to the binary format? The updates that you mentioned, that works with the binary format as well ?
( ie GomOnBarUpdateDone method to allow better performance).
I'm assuming based on your reply that the gom millisecond data is only to check for network jitter?
Sorry if these questions seem redundant, just try to figure out the best way to go at it. I also see the new converters on there, thank you.
For people playing around with the q collector version file format, i talked to tim and he said you can have it update every 5 seconds, but its not suitable for day trading. Its also a bit slow.. sorry guys.
Last edited by Michael.H; June 11th, 2010 at 05:20 PM.
BigMike is having a programmer put together a new downloads module. I would like your permission, once it is complete, to begin putting all of your great work into this as my test/debugging project. The new downloads section will be thread like and have a lot of easy to use features. Including auto update notification and places for comments.
Am trying to envision a way to combined this with Sam BMCodex Project as a way to organize large coding projects.
More to come as I begin to get familiar with the new GUI.
R.I.P. Andy Zektzer (ZTR), 1960-2010.
Please visit this thread for more information.
Gotcha, after reviewing some videos, the indicator shows a roughly a negative ~15000-16800 ms lag on es and ym with my dtn feed and internet connection. Is this something that the indicator might be useful for, or is that about standard in your opinion? My pc lock is pretty accurate. I've read your other posts, and noticed no delay( at least so far)
Last edited by Michael.H; June 14th, 2010 at 04:49 AM.
While trying to develop something similar to your Volume Ladder, I felt that CalculateOnBarClose should be true, since all the live data is based on MarketData event. However, when rebuilding the information, I had an off by one error since the bar on which the data-was to be plotted was already completed before the Gom functions were call. I offset it by one, but then faced a problem when transitioning from historical to live data. The bar which is currently being built was part historical and part real-time.
Will the new updates help in the transition? I am not sure whether the setting for the CalculateOnBarClose would make any difference in overall performance for the Gom based indicators but wanted to optimize as much as I could.
Favorite Futures: Gameplay KlownbineŽ Trading of Globex
Posts: 1,276 since Jul 2009
Thanks: 1,227 given,
Millisec file format of GomRecorder
The millisec file format has time stamps with millisecond resolution instead of one second resolution. For most indicators that use the GomRecorder, this is not necessary, and unless otherwise stated, the preferred file format is generally binary.
The millisecond time stamps are helpful for indicators that do things such as counting the number of trades per unit of time. If the unit of time is less than one second, or for that matter less than a few seconds, one second time stamps would be too coarse to give meaningful results. For example, trying to determine the average volume traded within each of the 0.8 second time periods within a bar. So this is a great feature for indicators that measure TRADE INTENSITY.
For best results it's important to keep your computer clock synchronized with a reference clock using an NTP client such as Meinberg.
The following user says Thank You to Zondor for this post: