Got an exception using the historical data provided for MTGox, was working fine yesterday:
syncing C:/SierraChart/Data/mtgoxUSD.csv
Updating CSV: bytes 312690830 to 313739405 of 316504899
312690798: ,670.000000000000,3.727747830000 ::: 00
1387445072,640.549000000000,0
Traceback (most recent call last):
File "scfeed.py", line 739, in
csvupdater(csv_filename, s)
File "scfeed.py", line 406, in csvupdater
raise Exception('Local and remote CSVs do not match')
Exception: Local and remote CSVs do not match
Yep, I got it also.
The updating method is based on the assumption that in the complete nightly CSV files, older trade data wouldn't be changing, there would just be new trades added to them. I, of course, don't just blindly add new data to your local CSV file, I get an overlapping range and make sure that we are appending to identical data. My checks caught the alteration.
the last 32 bytes of your local file :::
the bytes that are now being returned when re-checking that range312690798: ,670.000000000000,3.727747830000 :::
001387445072,640.549000000000,0
The problem here seems to be that bitcoincharts made CSVs with
different old history than was previously downloaded (after several days of the nightly updates being the same and working correctly.) The files appear to have changed for other tickers too.
Sierrachartfeed will work again by deleting and letting it re-download the C:/SierraChart/Data/mtgoxUSD.csv file. On bitcoincharts, this is the only file and method to get trades that are older than five days, so if the CSV data continues to change in this way that the file download can't be "resumed", I'll need to think of different ways to synchronize this data and resume from the last time scfeed was run.