Fixing tuple, 'UTC has no key' errors and update alpaca_history to comply with the latest version of pandas in FinRL_PaperTrading_Demo.ipynb #82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kurone02
changed the title
|
thanks for your codes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An updated version of the
gymnasiumpackage changes the behavior ofgymnasium.Env.reset. The return value of theresetmethod now returns a tuple ofobservationandinfo, which causes the tuple error mentioned in #78. Please refer to the gymasium's documentation for more details. This is fixed by ignoring the second value in the returned tuple.The current version of the
exchange-calendarspackage requires the dates to be timezone native, which causes the "UTC has no key" error mentioned in #81. This was resolved by erasingtz=pytz.UTC.Also, the current version of pandas has deprecated
DataFrame.append. For more details, please refer to the pandas' documentation. This is solved by simply changing the code fromdf.appendtopd.concatin thealpaca_historyfunction.