Hi!
I don't want to wait for 20 days to have a reliable signal from RSI indicator, so how can I add the historical data on top of the data collected by the bot in its runtime?
Bitcoincharts.com has the historical data, and it's easy to put them in the form of {"s":1239,"o":628.372,"h":628.372,"l":628.372,"c":628.372,"v":0.033,"p":628.372,"_id":"plNRczdJWMI7ds5V"}, but what's "s", can it be negative? And what's _id? And I guess p is the adjusted price. Is it vwap?
Thank you very much in advance
{
start: [moment object],
o: [open of candle],
h: [high of candle],
l: [low of candle],
c: [close of candle],
p: [average weighted price of candle],
v: [volume]
}
That's the exact spec... as for the "_id" it's related to the format used for the database...
The "s" is the "start" time for when that candle opened... It's in "moment" format:
http://momentjs.com/docs/... and the _id is a fancy key identifier specific to nedb... but I have no clue what format that _id is in.
not sure if that helps you to know gekko stores its data in a "nedb" database:
https://github.com/louischatriot/nedb(
it's an open-source database for node.js, the language gekko is written in)
Changing gekko over to using the nedb database for storing historical data was one of the last things to happen before the original author stopped supporting gekko completely
But I'm just gonna warn you in advance, I think there's a bug which prevents gekko from reliably loading data more than 24 hours old... it doesn't happen every time, but if you ever have to restart gekko there's a chance the history could be invalidated due to corruption and you'll lose all but the most recent 24 hours or so worth od data.
As I understand, the way RSI is traditionally works requires long-term (
generally more than 2 days) of data, so you I really hope you're using a fork of gekko which doesn't have issues with database correction...
I really don't test or debug the historical datastore "local DB" system since there's other bugs I'm working on fixing and the database rewrite itself originally took several months to complete, so there's a lot of code involved in figuring out what's wrong
