* Ability to read directy QCollector , QCollectorIQ and IRT files
* Millisec format, which will try to use the current clock to record millisecond timestamps. The recorder will try to adapt the lag between the exchange and the PC to keep timestamps matched (see https://futures.io/elite-circle/3743-exchange-data-delay-test-2.html#post40819 for an indy that monitors the lag). And thanks Zondor, there was indeed a bug ;-)
Added GomOnBarUpdateDone method to allow better performance.
So now the whenever OnBarUpdate is called on the indicator, it calls first GomOnBarUpdate, then it does its internal stuff like reading Gom files, and when everything is finished it calls GomOnBarUpdateDone
Ideally, you should put in GomOnBarUpdate the code thas is used to initialize each new bar, then in GomOnMarketData the code that updates your own data objects, and in GomOnBarUpdateDone the code that plots your internal objects by setting values to time series.
See enclosed GomDeltaVolume to see example implementation.
Last edited by gomi; June 10th, 2010 at 04:38 AM.
The following 12 users say Thank You to gomi for this post:
my chart doesn't say gom millisecond recorder on it. Im not using the delta volume indicator, just the gom cd. I know before you didn't have to actually load the volume recorder on the chart, but do you have to on this one?
Will new indicators need to be written or updated for this recorder, or will the current GOM package benefit from this recorder. (probably a stupid question but I don't quite understand how the GOM stuff works...I'm just glad it does!)
I actually went to edit ninjascripts, and did a compile manually. I then did f5 on all my charts, still won't say millisecond recorder. its says using binary on the side. Here's a pic
Gomi.. sorry.. stupid mistake. I didn't choose milisecond on the bottom. Few question...
1. will it replace the old bid/ask data if i switch formats to millisecond? found out it creates a new file... so disregard.
2. Is there a file converter that allows you to convert old binary data to be ported to millisecond data so it can use it as a lookback?
3. Also, if I have q collector, will it read it as soon as q collector is finished downloading it( after hitting F5 of course)? I don't have q collector yet. Reason i ask is simply because technically, it takes a few seconds to download data, and with this feature, there's no longer a need to leave computer on running 24/5
4.If we use q collector to backfill, can it ammend to millisecond data or is it a totally different file format (meaning you download for missing data, then as new data comes in using the recorder, that picks off where the qcollector left of)?
Is there a file format that you actually prefer or think works best?
this is truely amazing, you managed to overcome ninja's greatest problem, by yourself.....
I was talking to tim about this.... amazing how one person can do so much, but a team of coders at ninja couldn't fix this....
Last edited by Michael.H; June 11th, 2010 at 03:42 AM.
2. no. Millisecond data has to be written real time. It may actually work though if you use an input file (IRT, QCollector etc ) and your input file has milliseconds timestamps.
3. YOu will have a problem because the indicators keep a lock on the file so it won't be updateable by QCollector
I wanted to update the indicator with all the nice job of gooni (https://futures.io/elite-circle/2100-volume-ladder-highlight-addition-16.html#post43142 ) but actually forgot;-)
Anyway, for now, you can't update your file using QCollector while it's used by any Gom indicator
4. I don't think QCollector does millisec.
5. File format preference : this millisec stuff is for guys that want to play around with millisec data. It may not be usable at all(check your network jitter with then monitoring app). If you don't need it you can stick to binary
Careful anyway using directyl QCollector files : in my case with esignal, 1 week is 500Mo, so parsing of the file is very long. Binary uses a few Mo for the same week, so you can read contract-long data with not too much pain.