This repository has been archived by the owner on Feb 15, 2022. It is now read-only.
REST API UI v1.1 #1013
Closed
REST API UI v1.1 #1013
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
before fix: zenbot balance --debug bitfinex.xrp-usd 2017-07-09 05:57:33 0.24 XRP-USD Asset: 1190.00000000 Currency: 0.75283021 Total: 285.11523020999994 after fix: zenbot balance --debug bitfinex.xrp-usd 2017-07-09 06:08:49 0.23815000 XRP-USD Asset: 1190.00000000 Currency: 0.75283021 Total: 284.15133021
* updates to srsi_macd * rename strategy to srsi_macd * srsi_macd and sma indicator tweaks * CCI SRSI first commit * new strategy cci + srsi
```node zenbot``` throws error. Corrected.
* Quadriga CX Fixes * Add amount for takers fee * Minor update to backfill warning text * Fix variable shadowing error * Trades with the same timestamp are now ordered oldest to newest when r eturned from getTrades * Trade volume now returned as number and not a string, prevents NaN on volume report * Filter results on timestamp start to prevent re-reporting the same trades in the results * Sometime opts.from is undefined, and we should return all results. * Formatting
* Windows support * Fixed spawn command when trading * Fixed backtester runCommand * Added docker-compose-windows.yml which addresses DB volume exposing issues on Windows * Update readme.md * Untabify file...
…der(), check for it in engine.js (DeviaVir#391) - Sometimes I would get "0% funds on hold (0.000000)". New check if balance on hold is > 0
* Quadriga CX Fixes * Add amount for takers fee * Minor update to backfill warning text * Fix variable shadowing error * Trades with the same timestamp are now ordered oldest to newest when r eturned from getTrades * Trade volume now returned as number and not a string, prevents NaN on volume report * Filter results on timestamp start to prevent re-reporting the same trades in the results * Sometime opts.from is undefined, and we should return all results. * Formatting * Quadriga now supports trading LTC * Fixing QCX API handling of numbers Some argument about the lack of type safety in javascript. * QCX fix incorrect error reporting
…TA-lib stats (DeviaVir#389) * Add a 'noop' strategy, which just does nothing. Can be used to generate e.g. candlestick data for model training. * - Add option to `sim` to disable output of option - Add option to `sim` to disable writing HTML results * Add forex_analytics training, simulation and strategy (see https://github.com/mkmarek/forex.analytics and DeviaVir#385) * - .gitignore trained models - Limit width of progressbar in training to 80 cols * - Added timezone to datetime displays - Fixed hang when not using a test dataset - Changed default indicators * Windows fixes for sim spawn * Write a final model including sim results (output while training less pretty) * Made train pretty again. Also write simulation Results as HTML files in models/ * Speed up parseSimulation() * Properly name simulation result HTML files after training * - Use the defaults of the forex.analytics project for training - Add a check for unknown indicators * forex_analytics documentation * !!! -> !
* Added support for the BTCe exchange * A minor cleanup * Even more cleanup * Visible RSI values in the free space along with the RSI graph and some minor cosmetic changes to make for a more pleasant formatting * Adjusted display for (RSI === 100) * Fixed a line that got lost in copy
* Fixed docker build * Added --paper according to github comments
node-gyp and node v8.x are not friends, stick to boron for now Rename talib's MACD (DeviaVir#2) * Rename talib's MACD so it doesn't overlap with original macd
* use of xmpp * xmpp configs * Update conf-sample.js * Update engine.js
* Quadriga CX Fixes * Add amount for takers fee * Minor update to backfill warning text * Fix variable shadowing error * Trades with the same timestamp are now ordered oldest to newest when r eturned from getTrades * Trade volume now returned as number and not a string, prevents NaN on volume report * Filter results on timestamp start to prevent re-reporting the same trades in the results * Sometime opts.from is undefined, and we should return all results. * Formatting * Quadriga now supports trading LTC * Fixing QCX API handling of numbers Some argument about the lack of type safety in javascript. * QCX fix incorrect error reporting * * Adding debug output to help troubleshoot any more issues * Clean up use of Number(), numbro() and String() in various API calls * Fix error with error reporting for getTrades * Clean up error handling conditions * Remove excess semicolons for consistency * Fix error with retry in getBalance * QCX - Fix look up order * Re-enabled taker order processing in buy/sell command This doesn't appear strictly necessary, but if it reduces API calls back to the platform it could result in fewer API over-limits.
* Add missing node-gyp for forex.analytics * Fix docker build of forex.analytics Needs --unsafe-perm option to properly build dependant ta-lib libraries since docker run the container build with root permissions
* Updating product lists for most exchanges Largely this is adding support for BCH Updated: bitfinex, bittrex, kraken Poloniex and gdax was updated, but had no changes. BTC-e could not be updated (broken update script) Quadriga doesn't support BCH BCH currency pairs on Kraken don't fully match what is returned by their API. ie: API says BCH-ZUSD, but only accepts BCH-USD. This is manually updated in the product list, I suspect it is a bug that will be rectified on their side in a few days. Tested all pairs via backfill. * Forgot to stage the BCH fix in Kraken.
* Update developer document to address common bugs in getCursor * Fix bug with implementation of getCursor We call this function with either a trade, or timestamp in the case of a backfill * Quadriga - Fix bug with incorrect implementation of getCUrsor Made some of the error reporting a bit prettier Fix incorrect use for the numbro 'format' method * Kraken - Fix bug with the way rejected order were handle, pass the proper status and flags now Increase rate limit to 2000 after having some issues with backfilling * Add support for Gemini exchange Updated the readme to add QCX and Gemini support * I always forget to format before submitting * Forgot to stage conf-sample with Gemini updates * More formatting :)
* basics of using the websocket api for getTrades and ticker * Fix authentication * Pin gdax-node dependency to version 0.5.0
…code, as it is depreciated.
…nse all current included css and js
…t consumed in api.js also initializes the lib.output later and announces it at the start of live trading
|
welp rebase gone wrong, will resubmit this once its cleaned up. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This is mostly a transfer of code from PR #850, with a refactor from bower to webpack and few small changes related to bootstrap4.
TODO
move to partials, integrate ajax updating
integrate --api flag which sets auto stat dumping and prevents toggle
explore best representation for multiple running zenbot instances