-
Notifications
You must be signed in to change notification settings - Fork 186
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
if self.live_data is already true, why am I still in the history? #59
Comments
idk why you confusing between historical data and live data. because it is obvious that start from Live it is live and it is not historical data but live. when you see ccxt.feed code there is notification once
and load function has no notification so you can consider live as '==' |
I met the same situation in using "binancecoinm" exchange, and I found that the "ohlcv_limit" parameter whose default value is 20 can affect the LIVE notification. To put is smaller, for example 5, after 4 bars recieved with mode DELAYED comes historical bars with mode LIVE. Put it big enough can avoid meeting the historical data come early problem. |
same issue here using kucoin exchange !
`
... my code:
|
the issue happens because loading historical data stopped after the first call. i added a pull request with a fix for this. |
Hi ccxtbt,
I found something I don't understand while playing with ccxtbt. I think if
self.live_data
is true I should be getting the current data instead of still being in the history. Am I understanding it incorrectly? Some logs and codes to illustrate:If
self.live_data
is not designed to provide this, and I'd like to determine if I'm at current data or still in the history, what's the suggested way to do so?The text was updated successfully, but these errors were encountered: