Skip to content

Set the bounds in a smarter way #127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
jbweston opened this issue Dec 19, 2018 · 1 comment
Closed

Set the bounds in a smarter way #127

jbweston opened this issue Dec 19, 2018 · 1 comment
Labels
bug

Comments

@jbweston
Copy link
Contributor

(original issue on GitLab)

opened by Bas Nijholt (@basnijholt) at 2017-08-18T15:11:34.731Z

Right now, in an empty learner choose_points(n) will always return maximum two points (the bounds).

We need to think of a better way.

The current functionality will already break when adding a known point before the bounds are evaluated.
@jbweston
Copy link
Contributor Author

originally posted by Bas Nijholt (@basnijholt) at 2017-08-30T10:50:38.164Z on GitLab

The current functionality will already break when adding a known point before the bounds are evaluated.

Fixed in 940342e

jhoofwijk pushed a commit to jhoofwijk/adaptive that referenced this issue Apr 17, 2019
@basnijholt
fix typo in 'uniform_loss' doc-string, closes python-adaptive#127
c0012a9
@basnijholt basnijholt added the bug label Jun 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jbweston @basnijholt