Hi JCL,

Thanks for the reply. I'm sorry but you will have to noobify that answer a little for me.

Cygwin does not return to the command line before Zorro opens. The above copy/paste from the Cygwin terminal is all that appears before Zorro starts. THere are no messages printed in Zorro (I added a tonne of print statements to see where it's hanging and there is nothing returned).

Is there something I can add to the python or zorro script to ensure their operation lines up properly?

Cheers,
BobbyT

Edit: just had another look; neither the bash script or the python script terminate properly. They both hang Cygwin. Maybe there's a dependency or plugin issue (?)

Not sure if I understand the question correctly but I'll try to reply anyway (hopefully on topic) - in the latest version the name of the produced asset file is e.g. EURUSD_2016.t1 and the name of a dummy file is the same but beginning with an exclamation mark (e.g. !EURUSD_2016.t1). The first file contains ask prices (which are normally used by Zorro) and the second one contains bid prices. One of the ways how to use these files is decribed here: http://statsmage.com/zorro-on-steroids-iii-backtesting-with-variable-spread/ - then the price which is used during backtesting is the ask price and the bid price is used only to calculate the spread.

BobbyT: The produced files are indeed stored in different folder than Zorro/History so you don't accidentally overwrite some important history files.

The line reversion and file splitting are slow but when this part is done the Zorro conversion part should be very fast. I've just tried with a fresh install of Zorro 1.59 and everything works fine for me. The question is - are you using the latest version of the conversion scripts? I know the thread is a mess and I'm sorry for that. I would edit the first post but it's probably too old to do so. You can find links to the latest version here: http://statsmage.com/zorro-on-steroids-ii-data-conversion/ in the "Implementation" section. It's these two:

https://gitlab.com/panaczech/ZorroToolbox/blob/master/converter/convert.py
https://gitlab.com/panaczech/ZorroToolbox/blob/master/converter/ConvertData.c

There's no need for the bash script anymore. I'll try to keep the files in the repository updated in the future as well.

Hi PCZ,

That makes sense about the file locations. I had just misunderstood where they were meant to be saved.

The python/zorro scripts were downloaded Friday night so unless they have been updated since then they should be the most recent ones.

Regardless of if I use the bash/zorro or python/zorro combination the following happens:

-The tick files are correctly converted to M1 files with the lines reversed
-Zorro is opened
-Then nothing, no messages in zorro, no further messages in Cygwin (beyond what I had previously posted)

CSV files can successfully be converted to t6 files via the zorro interface after Cygwin is forcefully closed.
So it seems that ConvertData.c (or converT6.c) does it's job and convert.py (or convert.sh) also does it's job. The problem seems to be with the calling of ConvertData.c from convert.x (although as I mentioned, Zorro is successfully started by convert.x).

Could it be a windows thing? I'm running from Cygwin to try and avoid any Windows nonsense.

Cheers,
BobbyT

BobbyT: In your example you tried to convert AUDCHF which is not in Zorro's asset list by default. Did you include it in the asset list file? When the asset is missing the conversion fails but the Cygwin shouldn't hang anyway.

Hi PCZ,

I had previously copied AssetsCurr to AssetsFix (minus USDMXN) and updated the broker information via the download script through FXCM. Zorro had also successfully downloaded AUDCHF data from FXCM following the updates to AssetsFix.

Dukas has more data available than FXCM though so that's why I'm here.

Cheers,
BobbyT

Update: To anyone that is trying or had tried to get this to work, pcz is using Zorro S. Zorro S has a string of command line functions/options which are not available on Zorro F.

I will try an make a Zorro F compatible version over the next week. Stay tuned for any further updates.

Cheers,
BobbyT