-
Notifications
You must be signed in to change notification settings - Fork 237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
inconsistent historical ohlc #112
Comments
Issues involving That said - yes, this is a known upstream (Kraken's) implementation detail. Using plain Here's a (historic) gist when this has first been brought to my attention. Rather annoyingly, the discussion is in a sub-reddit ( This can (theoretically) be explained by OHLC data being provided by a cluster of machines accessed through a high-availability/load-balancing proxy; and the machines having different data (for unknown reason)... But that's just guesswork. Anyway, yes - this is an annoyance, and there seems nothing can be done... except contacting Kraken. ;) |
For ref, the script used to produce the gist was (quite likely an earlier version of) https://github.com/veox/python3-krakenex/blob/master/examples/log-ohlc.py |
Versions
What are you trying to achieve?
get the historical data and update current dataframe with it.
pull original dataframe via pykrakenapi
wait
pull updated dataframe
concatenate dataframes and drop duplicates
# code sample
What do you expect to happen?
dataframe updated with new new lines, duplicate rows from the new dataframe will be dropped as they already exist in the old one
What happens instead?
some of the rows remain, as they have the same datetime index, but different values in series (ie. the closing or opening price is different)
The text was updated successfully, but these errors were encountered: