Topic: SierraChart bridge - Realtime Bitcoin charts [v0.5] (MtGox, Intersango, ...) - page 4. (Read 142274 times)

Delete everything Sierrachart from your system, and try this build:

http://we.lovebitco.in/schart/SierraChartSetup.exe

well mine stop working, and creating new user didnt fix. very sad

They can not patch the old builds unless you are talking about the most recent.

Their subscription doesn't even unlock some advanced charting tools..

this no longer work with trial version, sierrachart patched this hack, u need to buy subscription.

The nginx gateway has become very intolerant of the type of requests that were being sent, or the api server was taking to long to return the result. For some reason the default URL http://api.bitcoincharts.com/v1/trades.csv?symbol=mtgoxUSD returns the most recent 20,000 trades again and again with no error, but when specifying a time range, anything other than a very small amount of data gives a 502 gateway timeout error.

I altered the parameters of sierrachartfeed to make many small requests instead of desiring larger data blocks. This seems to be working OK. I also increased the default max history to 14 days:

http://we.lovebitco.in/schart/sierrachartfeedUTC-0.6.020.py (requires github source files also)
(new version available)/sierrachartfeedUTC-0.6.020.exe (Win32)

md5sum:
a163db9dc95a5352bac68f4e223d0250 *sierrachartfeedUTC-0.6.020.exe


History files are also updated to today's date; refer back to this full post for sierrachart instructions:

 
Something weird is happening here.
The hist api is up and accessible in the browser.
It doesn't look like any api specs have changed also.
But the lovely bridge can't get historical data at all.
Is this user-agent filtering of some sort or something?

I added the history command-line option, and set the default to just seven days, to discourage abusing the API server to catch up a full three year history by default. This also makes SierraChart useable for recent trade analysis in just a few minutes instead of hours or never.

When you start sierrachartfeedUTC.exe, it will resume downloading from the last timestamp, unless it's been over seven days since you last ran it (or if you are starting with my complete history file that's now 12 days old). The history option sets the maximum number of days back that will be resumed. If you have already downloaded the full SCID file or might not use bridge for over a week, you can then use the history option like above, setting it to 200 days for example, and it will still resume just where it left off when you last ran bridge (not downloading more data than needed).

I will update the history SCID download in a bit. This file is made with modified code that downloads history just to a certain checkpoint and doesn't pollute data with live stream, so it is a 100% true record of historical trades.


This gets its data from bitcoincharts.com; mtgox API doesn't have a feature to retrieve past trades.

I had the same problem! What I did was; I downloaded the mtgoxUSD.scid from here

Then I made a new text file and named it scUTC.cmd. I edited this file with this
I used 13 because as of writing (12-5-2013) the last record in the mtgoxUSD.scid file is over 12 days ago. The default is 7 days, so it skips the 6 days before it creating the hole
Once you have all historical data, it does "opening streaming socket..."

a separate question, please:
how can one avoid data gaps when not online? I am using the new bridge.

Also, how can one use the historical data and then continue with the bridge data. when I tried, it does not add the new data at all.

thanks you

I have been watching this thread for a while. A few glitches were reported.

As of now, does Sierra works flawlessly with MtGox API or are there some problems?

Thanks

It sounds like you are using the new Mtgox data direct from SierraCharts, and not the bridge. It may not have a complete history.

Try this:
1. Go to menu -> Chart -> Chart Settings, and set "Days To Display" to 1100 or more,
2. Set Bar period to 1-0-0 (1 day per bar),
3. Scroll to the left and see how far back it goes.

If they don't have older history, you can follow the instructions for using the sierrachartfeed above, using the mtgoxUSD SCID file, which has all history trades.

Just trying out SierraChart now. I'm inexperienced and trying to figure out how to get data before <2011/06/26 for gox?

For some reason that's as far back as it goes. I used the "Bitcoin Data (MTGOX)" feed that came with the default install. I never tried the "MtGox Bitcoin Trading (under development)" option.

Am I doing it wrong?

Hi DeepCeleron,

I quit using SierraCharts for a few weeks, as the old data feed was in trouble, and neither could I get one of your first versions to work properly. Just came back to this thread and I am happy to see that you have done a great job. Thanks also for the SCID uploads with full history (might it be a good idea to keep doing so, e.g. on a monthly or weekly basis?) .

All this is of great help, and I thank you for that.
THUMBS UP FOR YOU !!!  

thanks DC

Sorry, I forgot to actually upload the "other history" file, it's up now and includes other exchanges and currencies. Funny how nobody dropped me the 411 on the 404.

This "Volume/Open Int. Multiplier" setting refers to the amount of BTC per trade (which you see when you do a volume study), not the price. It should be set to 0.01 to match the default SierraChartFeed precision of "2".

SierraChart doesn't support fractions of a trade volume like a currency would have, it apparently was designed for stocks, where the minimum trade volume is 1 stock. The Sierrachartfeed solution to this is to take trade amounts and multiply them, adding "precision" decimal places (the option at the command line), so a trade of 50.01 BTC becomes a volume of 5001 sierrachart units. Unless you you want to analyze volume with super-accuracy, this setting is adequate. The maximum display divisor in SierraChart is 0.0001 (precision 4).


edit: the raw data does have eight decimal places of accuracy (1 satoshi), see volume amounts of these trades:

bitcoincharts csv:
1367391587,133.500000000000,0.596380140000

mtgox market api json:
"vol":
{"value":"100624.73892887","value_int":"10062473892887","display":"100,624.74\u00a0BTC","display_short":"100,624.74\u00a0BTC","currency":"BTC"}

The only way to use this many decimal points in SierraChart is to set the precision option to -p8, erase all SCID data and get data again, and deal with the volumes in SierraCharts being in billions of satoshis.

i used to have 0,0001 for 4 digit precision

Announce: Sierrachartfeed w UTC time data, improved network

Update 018:
-All times in UTC instead of local time (allows easy data file interchange with other users and comparison with other ticker sources),
  REQUIRED: remove all existing C:\SierraChart\data\*.scid files before using this new bridge version.

-properly close IP sockets (not a fix for all 502 errors, apparently)

-faster update,

-remove about 1-5MB of redundant downloading at initialization,

-cosmetic tweaks: error stats and download times on console.

note: when using the single-letter option, there is no space between the option and the parameter


Download links:
(see later post for newest version)

SCID full history files:
from first trade 2010-07-17 23:09:17, to 2013-05-26 23:59:59 (UTC, tick accurate, precision 2):
(extract to C:\SierraChart\data\ before starting SierraChart)

http://we.lovebitco.in/schart/mtgoxUSD.scid.UTC.7z (18.2MB/182MB)
http://we.lovebitco.in/schart/otherALL.scid.UTC.7z (8.2MB/86.4MB)


Original Instructions:


Optimal settings in SierraChart:

My signature address works! Although a diff/patch gives 67 chunks of procedural spaghetti code changes against git master, I've done far less work than original creator slush, and you might also thank bitcoincharts.com for providing the feed, and let them know why you donated.

Thanks deepceleron, I've got it working now, and I really appreciate your help with this!  After updating my batch file, I've been able to successfully download the historical trade that I missed.  Is there any particular address you'd like me to send some donations to (I assume the one in your signature is fine)?  Also I would like to further commend you, as this sierrachartfeed update is a significant improvement over the older version I used, and has now removed the 10-15 minute gaps of trade data between the historical data and live streaming feed which is great

I've noticed time switching..

Then there gotta be an ids in place and protection based on fuzzy logic ruling out bogus data.
That way it would be similar in resistance to 51% of the bitcoin system itself.