Skip to content
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.

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

optimize: Add a unit test when the initial F is NaN or Inf #666

Closed
vladimir-ch opened this issue Jan 19, 2015 · 4 comments
Closed

optimize: Add a unit test when the initial F is NaN or Inf #666

vladimir-ch opened this issue Jan 19, 2015 · 4 comments
Assignees

Comments

@vladimir-ch
Copy link
Member

No description provided.

@btracey
Copy link
Member

btracey commented Jan 19, 2015

We have this now in getStartingLocation. Were you looking for something else?

@vladimir-ch
Copy link
Member Author

Er, I meant "unit test" or whatever these go test things are called. Just for completeness and safety.

@vladimir-ch vladimir-ch changed the title Add a test when the initial F is NaN or Inf Add a unit test when the initial F is NaN or Inf Jan 19, 2015
@btracey btracey changed the title Add a unit test when the initial F is NaN or Inf optimize: Add a unit test when the initial F is NaN or Inf Mar 16, 2017
@vladimir-ch vladimir-ch transferred this issue from gonum/optimize Nov 22, 2018
@vladimir-ch
Copy link
Member Author

Again, I don't recall what exactly I intended with this, it was in my beginnings with Go/Gonum. But now that we have this here anyway: we check for NaN or Inf in the local methods in getStartingLocation but perhaps we could check the initial location at a higher level in Minimize.

@vladimir-ch vladimir-ch self-assigned this Nov 22, 2018
@vladimir-ch
Copy link
Member Author

I checked the code again and I think it is best to leave it up to individual methods how they deal with NaN/Inf initial function values.

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

No branches or pull requests

2 participants