Herklos
commented
3 years ago HI @mertdogan, you have to have 4h time frame data in your backtesting data file to run backtesting for your configuration.
Open mertdogan opened 3 years ago
Herklos
commented
3 years ago HI @mertdogan, you have to have 4h time frame data in your backtesting data file to run backtesting for your configuration.
DrBlackross
commented
4 weeks ago yea, this is the reason why i use the docker version and bind all my "/octobot" folders to a usb stick
/media/usb-stick/backtesting /octobot/backtesting etc...
i basically will fire up mc (midnight commander) and use the search option and find all the " 4h" (with space in front of the 4) to grep through all the files and either swap the " 4h" with " 6h" or just remove the " 4h" (usually there's a ", 6h" in front of one) and save the files using nano.... it will stick till the next docker update/upgrade, when it doesnt i go back through and repeat the process (since i use coinbase exchange), not a glitch just a feature, lol
update /user/profiles/signal_trading/specific_config/MoveSignalsStrategyEvaluator.json <--- is where the edit needed to be
Step 1: Have you search for this issue before posting it?
If you have discovered a bug in the bot, please search our issue tracker. If it hasn't been reported, please create a new issue.
Step 2: Describe your environment
Step 3: Describe the problem:
Describe the bug Backtesting with BTCTURK fails with error below: 2021-04-28 00:55:33,133 ERROR IndependentBacktesting Impossible to start backtesting on this configuration: Missing time frame in data file: 4h (RuntimeError)
Expected behavior I think this error can be related cctx. I upgraded latest version but allready error occures for backtesting.
Steps to reproduce:
Observed Results:
Error occured at web area and console.
Relevant code exceptions or logs: