Is FXCM T1 data that reliable, or is it worth using duka.
Variable spread is handy though.



Futher, I'm definitely a noob with this, but where do you include in the your py script the csv file name?

Also, do you then just drag and drop the py script into the cygwin terminal?

Code:
$ /cygdrive/d/Trading/DukaData/QmYybyXg.py
/cygdrive/d/Trading/DukaData/QmYybyXg.py: line 1: from: command not found
/cygdrive/d/Trading/DukaData/QmYybyXg.py: line 2: import: command not found
/cygdrive/d/Trading/DukaData/QmYybyXg.py: line 3: $'r': command not found
/cygdrive/d/Trading/DukaData/QmYybyXg.py: line 4: syntax error near unexpected t                  oken `sys.argv'
'cygdrive/d/Trading/DukaData/QmYybyXg.py: line 4: `if len(sys.argv) != 2:


I also tried using the CSVtoT6 script as I noticed in that script there has information about converting trade station csv into t1.
So I put my csv file name into that line:
Code:
#ifdef TRADESTATION
#define TCK T1
string InName = "HistoryEURCHF_UTC_Ticks_Bid_2015.02.01_2016.12.19.csv";  // name of the CSV file
string OutName = "Historyticks.t1";


But that didn't work. Is it meant to?
I am using the normal zorro, not zorro s. Do I need to have zorro s for this to function properly?

If I wanted to test T1 data on EURCHF for example can I create a fxcm account, and download it from there?
Or what is a suitable way to pull it from a CSV file from dukascopy? (without worrying about variable spread at this point in time)

Do I simply create a back the front CSV file divided into years, into the format of:
Date, value

Or does your python script do that?

I do apologise for jumping off topic a little (since i'm now just talking about tick imports)
Thanks

Last edited by CaptainChezza; 12/21/16 08:51.