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

Error: invalid bucket size spec: undefined #994

Closed
albabosh opened this issue Dec 26, 2017 · 5 comments
Closed

Error: invalid bucket size spec: undefined #994

albabosh opened this issue Dec 26, 2017 · 5 comments
Labels

Comments

@albabosh
Copy link

./scripts/auto_backtester/backtester.js gdax.ETH-USD --days=10 --currency_capital=5 gives:

/home/tradeops/zenbot/node_modules/timebucket/lib/bucket-size.js:15
if (!match) throw new Error('invalid bucket size spec: ' + spec);
^

Error: invalid bucket size spec: undefined
at BucketSize.parse (/home/tradeops/zenbot/node_modules/timebucket/lib/bucket-size.js:15:21)

@haxwell
Copy link
Contributor

haxwell commented Dec 26, 2017

Addressed in PR #996 .

@DeviaVir DeviaVir added the bug label Dec 27, 2017
@JensvdHeydt
Copy link
Contributor

I was wondering why the parameter periodLength was introduced at all? Now we have period and periodLength. What's the benefit here?

@haxwell
Copy link
Contributor

haxwell commented Dec 27, 2017

@JensvdHeydt See PR #926. I agree there should not be both 'period' and 'periodLength', but the thought was to remove 'period' slowly, a la deprecation. After the initial commit, it started becoming more apparent, it should probably just be cut quickly.

But the tl;dr on "why?", is an effort to make the code easier to understand. Previously, 'period' was being used to describe two different concepts.

@JensvdHeydt
Copy link
Contributor

Ah, I see! Thanks for explaining. I totally agree, it’s a little bit confusing to have two meanings for the term period. We‘d better clean this up soon.

@DeviaVir DeviaVir reopened this Dec 28, 2017
@DeviaVir DeviaVir closed this as completed Jan 7, 2018
@kenorb
Copy link

kenorb commented Apr 18, 2018

Related: #938

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

5 participants