Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I keep getting requests for people to share their GomRecorder data. A few threads have been started on the subject but not many are following thru it would seem.
I am collecting data from IQFeed via QCollector. All data contains bid/ask and is tick …
) to the standard NT7 tick import format, which Mike has already pointed out and that can be found here ( NinjaTrader Version 7). I will kick the tires on this and let you know how it works.
Broker: Mirus (Broker), Continuum (Data), Dorman (Clearing)
Trading: Futures
Posts: 202 since Mar 2013
Thanks Given: 428
Thanks Received: 202
Nicolas--
So the program works perfectly. However, I have a couple of suggestions for potential improvements that are based on how the QCollector files are downloaded from the QCOllector thread.
When one downloads the QCollector data from the QCollector thread, the files are all housed in an instrument specific folder. For instance, with the January 2011 QCollector file, the folder contains all of the CL contracts that traded volume during January 2011--and in January 2011, the following CL contracts were traded:
So the procedure to use your tool, would be to drop in the .jar file into the folder, rename the file that you'd like to convert, execute the .jar file, which will in turn create a new file called "input.txt, which will then need to be renamed to the NT7 import requirement of "<instrument name> <mm-yy>.txt" (ie, "CL ##-##.txt" or "CL 02-11.txt"). The tool clearly works, it just requires a few steps that if I could wave my magic wand would be incorporated into the .jar program. So, given the above, here are my magic wand requests:
Request #1: Have the program be placed in a folder with numerous .txt files and ran once. The program would automatically note the file name, which is in the correct format for NT formatting but with data that is not formatted correctly, and copy the original file name. The program would then rename the original file with an "_original" in it and create a new file with the original file name (and which would have the correctly formatted data and file name to import into NT7). For example, the "CL 02-11.txt" original file would be renamed to "CL 02-11_original.txt" and the new file with the properly formatted data would be called "CL 02-11.txt"
Request #2: The newly formatted output files, which would have the correct file name and data formatting, would then be placed in a new folder that would contain all of the converted files.
By making the two magic wand wishes come true, one would then be able to process an entire month's worth of data with a single mouse click--albeit over a considerable amount of time. My thinking here is that this process would just run in the background, and when it was done one could start on the next round of conversions.
At this point it is probably worth noting what I am hoping to accomplish and provide back to the futures.io (formerly BMT) community. If I can make this happen, I plan on posting all of the newly formatted data into the appropriate threads so that other futures.io (formerly BMT) members will just have to download the data instead of going through the process that I've asked you to help out with above--and my time associated with converting all of the available QCollector data for the instruments I am interested in. We're all in this together, and I am hoping that together we can provide something of use to the other members.
Please let me know if you have any questions. I really appreciate the effort that you have put forth thus far on the converter program, and I am hopeful that some facsimile of the above requests can be achieved.
The converted files could be automatically stored in a newly created sub-directory. In such a case, I think that we do not need to rename the original files, since there is no risk of confusion any more. Ok?
What is the converter which works for you? "Big Mike request 2"?
great program, I was looking for this. Like BigMike posted in request 2, I was also very interested in a converter for Qcollector data to NT-format. This is a horror in excel, besides excel has not enough rows.
I wanted to check the output, and did what you said, put the Qcollector data and the Jar file in the same directory, and try to run the Jar file. Somehow, nothing happens when I double click or run the Jar file:
Java is correctly installed:
Can you see what I do wrong?
Thanks!
One of my worst enemies are my own false assumptions
So the problem is just my computer. I do not see the option to open the file as administrator, but then I will figure it out, or just try the same on another computer /laptop.
Thanks for your help!
Edit: computersavvy as I am , I renamed the Qcollector file "input.txt" as it already was a .txt file. Renaming the file in "input" did the job.
One of my worst enemies are my own false assumptions
I propose to use a Windows batch file to apply the jar to the various .txt files of the directory.
1. In the directory of your CL .txt files, make sure that there is :
- no "input.txt"
- no "output.txt"
- no ConvertedFiles sub-directory
2. In the directory of your CL .txt files, copy the jar file
3. Copy/paste the code below into NotePad (or similar) and save it in the CL .txt folder under the name "convert.bat" (no .txt suffix)
4. At this stage, your directory should like:
5. Launch the batch console from the Window "Accessories" Menu.
Navigate to the above-mentioned directory with "cd"
Type "convert"
It should launch the process, ending with something like:
The ConvertedFiles sub-directory should contain the output files.