-
Notifications
You must be signed in to change notification settings - Fork 746
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
backtest_plot Error with Crypto or any stock not listed in yfinance #27
Comments
Thanks very much for your detailed feedback! Would you like to work with us and improve it? We welcome your inputs! |
Of course, thats why I am here!! quite impressed with all the hard work you guys have put in, would definitely like to help you further! @XiaoYangLiu-FinRL |
Welcome to join our Slack channel to have more interactions with the community. |
The slack channel is: https://ai4financeworkspace.slack.com/ssb/redirect |
can i join your slack channel ? |
Can i join the slack channel, it seems it needs an invitation |
Will update the new link in one or two days. It needs monthly update. |
So I was testing out one of the crypto notebooks, it came to my attention that new new project master branch has a new naming convention for the backtest methods, so old notebooks will need to be updated with that.
I also realized a few issues with the data intake of the methods. They are only accepting data formatted in a specific way, like the date column, needs to be named "date" (unlike in crypto "time").
One of the major issues with the project right now is the non standardized methods, classes, inputs and naming conventions used.
Also, there is a redundancy in the operations, for example the below method uses get_baseline, which typically redownloads the data that you have downloaded at the beginning of the notebook? is there something I am not seeing? can we not create a deepcopy of the data at the beginning once and for all and use that as the baseline?
All the above are just me writing down my thoughts, please do let me know what you all think and the best solution so we work on it together to reduce inefficiency and redundant fixes. would truly love to hear your thoughts!
@XiaoYangLiu-FinRL @BruceYanghy
The text was updated successfully, but these errors were encountered: