-
-
Notifications
You must be signed in to change notification settings - Fork 566
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
bug: IndicatorFactory - Unnecessary column level while operating with single column #641
Labels
Comments
andreas-vester
changed the title
bug: IndicatorFactory - Unnecessary column level with only one column
bug: IndicatorFactory - Unnecessary column level while operating with single column
Aug 16, 2023
You could set |
I would rather like to get rid of "a" in both examples. Is this possible? |
This issue is stale because it has been open for 90 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am making use of the sample from the documentation (https://vectorbt.dev/api/indicators/factory/#naive-approach), with the exception that my price only consists of one security (column).
When running the indicator with any kind of
window
combination, the resulting dataframe will consist of multiple columns. Everything is fine here.As soon as I reduce the number of parameters to a single parameter, the output looks a bit different, i.e. there has been added another column level with no name and the value
a
.This might causing issues when further processing these results. I wouldn't expect any difference in the column levels no matter how many columns.
Is there an easy way to avoid this behaviour?
The text was updated successfully, but these errors were encountered: