You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I only have 60min freq data.
When I try to backtest with 60min. It report can't find day data.
So I look into the stack, and found the reason that it use default param freq='day' for create Account obj.
I hope you could add a 'freq' in backtest config, and convert it into Account obj.
To Reproduce
Steps to reproduce the behavior:
user code
freq = '60min'
# backtest and analysis
with R.start(experiment_name="backtest_analysis"):
recorder = R.get_recorder(recorder_id=rid, experiment_name="train_model")
model = recorder.load_object("trained_model")
# prediction
recorder = R.get_recorder()
ba_rid = recorder.id
sr = SignalRecord(model, dataset, recorder)
sr.generate()
# backtest & analysis
par = PortAnaRecord(recorder, port_analysis_config, freq, freq)
par.generate()
framework code
class PortAnaRecord(ACRecordTemp):
def _generate(self, **kwargs):
# custom strategy and get backtest
portfolio_metric_dict, indicator_dict = normal_backtest(
executor=self.executor_config, strategy=self.strategy_config, **self.backtest_config
)
🐛 Bug Description
I only have 60min freq data.
When I try to backtest with 60min. It report can't find day data.
So I look into the stack, and found the reason that it use default param freq='day' for create Account obj.
I hope you could add a 'freq' in backtest config, and convert it into Account obj.
To Reproduce
Steps to reproduce the behavior:
user code
framework code
There exists param 'freq' in the Account init method.
But I can't change it from outer.
Expected Behavior
I hope you could add a 'freq' in backtest config, and convert it into Account obj.
Screenshot
Environment
Note: User could run
cd scripts && python collect_info.py all
under project directory to get system informationand paste them here directly.
Windows
,Linux
,MacOS
):Additional Notes
The text was updated successfully, but these errors were encountered: