Skip to content
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.

Bug in darwin.js #1253

Closed
ttrd06 opened this issue Jan 31, 2018 · 2 comments
Closed

Bug in darwin.js #1253

ttrd06 opened this issue Jan 31, 2018 · 2 comments
Labels

Comments

@ttrd06
Copy link

ttrd06 commented Jan 31, 2018

Please go to Stack Overflow for help and support:

https://stackoverflow.com/questions/tagged/zenbot

If you open a GitHub issue, here is our policy:

  1. It must be a bug or a feature request.
  2. The form below must be filled out.

Here's why we have that policy: Zenbot developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies hundreds of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.


System information

  • Have I written custom code (as opposed to using zenbot vanilla): NO
  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): linux amd64
  • Zenbot version: latest from unstable
  • NodeJS version: 8.9.4
  • Python version: no
  • Exact command to reproduce:
    ./scripts/genetic_backtester/darwin.js --selector="gdax.ETH-EUR" --days=7 --currency_capital=800 --asset_capital=1 --use_strategies=bollinger --population=190

Describe the problem

If you launch the command above, the error "Bad output detected TypeError: Cannot read property 'currency_capital' of undefined" appears between the lines of generations.
At the end of generations, you can not have the results in the simulation folder.
Before i git pull the latests commits, this command worked !

Source code / logs

Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

@DeviaVir DeviaVir added the bug label Jan 31, 2018
@glennfu
Copy link
Contributor

glennfu commented Feb 3, 2018

Simple explanation for why this happened is that one of the inner sims blew up, and the output was "unparsable". So when it tries to process the result, the first piece it checks is params.currency_capital and gets nothing good. It would be awesome if it would actually bubble up the inner error.

@station384
Copy link
Contributor

This error is addressed in unstable

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants