new_point -> next_point in optimization
standardizing output of GradientDescentOptimization
standardizing:
UpdateCurrentPoint -> SetCurrentPoint
UpdateHyperparameters -> SetHyperparameters
fixing bug where num_multistarts = 0 or num_random_samples = 0 could crash the server
standardizing "status" dict outputs from C++ optimizers
remove next_points output from GradientDescentOptimizer
naming standardization
now if the POST has num_multistarts=0 or num_random_samples=0, we will error or handle appropriately
previously we would overwrite w/the default value. now if the user has specified something, we will
alert them
Merge branch 'master' of github.com:yelp/MOE into eliu_gh_186_189_345_cleanup_and_make_optimizer_arguments_consistent_fix_0_multistarts_bug
review responses
Merge branch 'master' of github.com:yelp/MOE into eliu_gh_186_189_345_cleanup_and_make_optimizer_arguments_consistent_fix_0_multistarts_bug
Merge pull request #348 from Yelp/eliu_gh_186_189_345_cleanup_and_make_optimizer_arguments_consistent_fix_0_multistarts_bug

Eliu gh 186 189 345 cleanup and make optimizer arguments consistent fix 0 multistarts bug