Here's the new major release of GomPackage, released this time in Elite because it was a lot of hard work.
THIS VERSION IS FOR NT 7 ONLY
Indicators developed with GomRecorder 1.3 still work on 2.0
Majors changes with 1.3b are the following :
GomRecorderIndicator
Architecture
*Added a Data access abstraction layer, Gom.IDataManager, that allows to dynamically add data providers without the need to modify the Recorder
File Management
*Added a recording mode setting that allows to record one file per day, or one big file (like 1.3b mode). Default is to create one file per day, which allows simpler data exchange and file maintenance. Files are split at 00:00 GMT
*Added the Millisec format, where Time[0] is replaced by DateTime.Now, so obviously will only record correctly real-time. The recorder will try to find the offset between the computer and the Exchange and show it on the plots.
Millisec indicators are Millisec file format (binary), and Flat (make sure you select Use Millisec)
Note on Millisec indicators : the millisec format is only useful if :
*you use millisec designed indicators
*your network jitter is small : your lag with the exchange must remain constant. Check the indicated lag on the chart, or for a visual analysis you can check GomTimeMeasure here :Exchange Data Delay Test ( . It will give a histogram of your network lag. For millisec to be any useful, your network lag must stay constant, or move a few millisecs. If it moves around the mean value about 500 ms, the millisec format is pretty useless, because you're not recording with millisec precision.
*The recorder is now able to read IR, QCollector, QCollectorIQ and Ninja export files directly, in read-only mode
*Like in1.3b you can define the Recording Folder by setting the GOMFOLDER environment variable to whatever path you want.
see How to Add, Remove or Edit Environment variables in Windows 7? ( for instructions.
*Remember you MUST enable Write Data to true for one indicator per instrument, or recording won't happen.
*As in 1.3b, the recorder can't write date before the last known tick. In 1.3b the only solution was to delete the whole data file and run replays to repopulate, now with 2.0 you only have to delete the file corresponding to the date you want to repopulate. Careful : files are split at 00:00 GMT
* added a three-state status when recording : OK,KO and NotNeeded. With the new version, the write file is not opened until there is a tick to write. So at first status is NotNeeded, then after the first tick we get OK or KO. This avoids seeing OK when actually the recorder isn't recording.
*Changed the file format and recording mode to Parameters instead of Settings category, so now they've gone up in the properties. The advantage is that you can select them when you do a composed indicator, like EMA of GomCD., or EMA of any Recorder based indicator. You can now choose format and mode. As a result dropped GomCDMA.
*You can instantiate GomCDs using
gcd = GomCD(GomCDCalculationModeType.BidAsk, GomCDChartType.CumulativeChart, "Binary",Gom.FileModeType.OnePerDay, GomFilterModeType.None, 1, false);
new in 2.3
*This version provides futures merging capability, meaning
it will automagically load ES 12-10.xxx files before ES 03-11 rollback date, and ES 09-12, ES 06-12 etc...
it will obey Ninja merging settings, and apply continuous offsets as needed. So you get exact prices either using DoNotMerge, MergeBackAdjusted and MergeNonBackAdjusted
new in 2.4
Added a NinjaTickFile data manager that directly reads Ninja Tick files, so Gom files are unnecessary. However
Ninja files don't contain bid/ask data , so you can only use it in GomMP, or GomCD with UpDownTick mode.
Set Write Data to true or you will miss last hour of data when you refresh your charts.
Rollover is disabled when you set your indicator to write mode, this allows to be sure to only write in the base instrument file.