changed a couple config settings so they can be disabled via command line arguments
fixed CoinbasePro and Kucoin API errors for standard API access - believe all errors causing restarts are now resolved
Only an occasional HTML Error which can't be fixed on our end.
moved getTicker call up pycryptobot.py to be inline with getHistoricalData and add a new row data with ticker before technical anlaysis is performed. This creates more asynchonous data and makes output as accurate as we can based on last call.
changed getHistoricalData call to only be called at candle close instead of every iteration and use ticker to fill data between candle open and close.
known problems with CoinbasePro and Kucoin websocket functions still exist, but above fixes will make websocket fixes easier
fixed standard indicators still being process when custom strategies are enabled
consolidated a bunch of locations where code was duplicated based on Exchange
added additional dataframe function to PyCyptoBot that will store additionally called dataframes dynamically and update them with ticker date like the main dataframe. This greatly reduces the number of API calls when running SmartSwitch, checking
"bullonly" or wanting to check anything else on a differen granularity than what is currently running. This is used for all additional calls for live and non-live checks, but not for Sims as that has it's own cache system already. Might be able to clean up Sim code as well in the future.
consolidated numerous indicators and signals in Trading_Pta.py to help prevent dataframe fragmentation
revised default Strategy_CS.py to be a little less risky and include so new features. Added extra comments to code.
shortened dataframe references in Strategy_CS.py to hopefully be less confusing for users
added additional dataframe features to Strategy_CS.py
Type of change
Please make your selection.
[x ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[x ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change requires a new dependency
[x ] Code Maintainability / comments
[x ] Code Refactoring / future-proofing
How Has This Been Tested?
Running live code for 6 weeks for API fixes, about 2-3 weeks for data frame revisions and constant revisions of Strategy Code, but no errors currently.
Checklist:
[x ] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[x ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x ] My changes generate no new warnings
[ ] I have added pytest unit tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x ] I have checked my code and corrected any misspellings
Description
Type of change
Please make your selection.
How Has This Been Tested?
Running live code for 6 weeks for API fixes, about 2-3 weeks for data frame revisions and constant revisions of Strategy Code, but no errors currently.
Checklist: